Is display "MKS TS35" supported?

[t0mx]

Hi community,

I try to set up an initial build of PrusaAIO for my MKS Robin Nano V3 based setup. As display I use the mentioned above touch display "MKS TS35". In the past I was able to use it in "stock" Marlin using #define MKS_TS35_V2_0. Is that also supported by PrusaAIO or can be at least made to be supported?

[thisiskeithb]

Not yet.

Once SPI TFTs like the MKS TS35 and BTT TFT35 SPI are supported upstream on STM32H7-based boards (coming soon), I’ll add options for those displays.

Until then, you‘ll have to bypass several Prusa AIO-specific checks/options to enable MKS_TS35_V2_0 since this firmware is tailored to the list of displays in the Prusa AIO config.

[t0mx]

Thank you for quick response!

Could you give me a hint, how to "bypass several Prusa AIO-specific checks/options" or point to similar adaptations had to be performed by someone else in the past?

[thisiskeithb]

The main sanity checks and backend of this fork are located in files that start with Prusa_AIO_ under /Marlin/src/inc/.

To give you an idea of what I changed, the last two commits will always contain the modified files for this fork. I rebase on upstream bugfix-2.1.x to keep the commit history clean and to enable faster updates.

You’re on your own for figuring out how to implement a new display since I won’t have time to walk you through all the changes / supported options.

If that sounds like a lot of work, you’ll have to hang tight & use a supported display or build out your own config.

[t0mx]

I was able to implement a new display option and to compile. But the board doesn't start up.
What I did:

• Changed the the deafault SDCARD-CONNECTION of the Robin Nano V3 in the "Motherboard" section from LCD to ONBOARD (why was it configured this way? Marlin uses ONBOARD as default)
• added a "elif" to Prusa_AIO_Conditionals.h which sets
  #define MKS_TS35_V2_0
#define TFT_COLOR_UI

I also chnged some stepper related settings, but I think, it shouldn't have any impact on start up behavior.

Build environment "mks_robin_nano_v3_usb_flash_drive_msc".

Anything else I need to check?

Update: it works, if I use "TFT_CLASSIC_UI". Not my favourite choice, but at least I can continue.

[thisiskeithb]

why was it configured this way? Marlin uses ONBOARD as default

Marlin also assumes you don’t have a display attached by default. This fork does. If the user enables a display option that has an SD slot, then it is set to LCD.

As I said above, you’re on your own since I’m waiting on STM32H7 + SPI TFT support upstream and I don’t have time right now to implement changes and test every configuration option with this TFT.