TFT32 screen support on MKS Robin Nano 1.2 board

[alexeyzel]

Description

MKS Robin Nano 1.2. Board can come with TFT32 screen based on ILI9341, for example on Flsun Q5 3d printer. This changes in pins_MKS_ROBIN_NANO.h file will make new style UI work with this board with TFT32 screen. It will work if #define TFT_320x240 is selected in configutation.h and board type is #define MOTHERBOARD BOARD_MKS_ROBIN_NANO

Benefits

An ability to use sew style UI on MKS Robin Nano 1.2 Board with TFT32 screen (320x240 screen resolution).

Related Issues

[mmajoor]

I think TFT_DRIVER and ILI9341_ORIENTATION, and simular settings, should not be defined in this pins_MKS_ROBIN_NANO.h file but instead in configuration.h or configuration_adv.h if possible (there is already a TFT_DRIVER define in configuration.h).
The main reason is that it assumes that all 320x240 displays are created equal and that is not the case.
In my case, I also have a Q5 printer with a 320x240 display, but this one uses a ST7789V display driver. It is a 'Makerbase MKS TFT24 V1.0' (but -not- the one you willl find on the MakerBase GitHub repositories - it is a simplified version without STM32 CPU).
In my case I did not need to define the TFT_DRIVER setting at all (by default set to AUTO). I did need to rotate the display.

[thinkyhead]

I kind of went the other way, where if TFT_DRIVER isn't defined as AUTO then the type is chosen based on the clues from the pins files. This probably should get a review from @rhapsodyv and other interested TFT integrators.

[rhapsodyv]

I kind of went the other way, where if TFT_DRIVER isn't defined as AUTO then the type is chosen based on the clues from the pins files. This probably should get a review from @rhapsodyv and other interested TFT integrators.

Sure, I think the same. We are trying to add defaults TFT configs to every board that we can test. Maybe sometimes we forget the #ifndef to make it overwritable, but the purpose is to have the most common TFT config ready to be used. It is easier for the user get started.

In the last weeks we received a lot of TFT support. Now that everything looks like stable, we are working in some refactoring, removing old and duplicated code, and changing some configs to make it easier for the user.

In a week or so, I think every option for those 3 new UI will be supported for all TFT.

[rhapsodyv]

I have added I few reviews. I think this PR must be only about add support for TFT32 in nano v1.2. And keep the code about TFT35 as it was, because it's already tested and working.
TFT35 and TFT32 can't conflict with each other in the code, because they have different init codes, and is needed different defines to setup each one.