Robin nano V2, TFT_LVGL_UI parameter adjustment

[MKS-Sean]

Requirements

• TFT_LVGL_UI add online adjustment parameter interface

Description

Benefits

Related Issues

[rhapsodyv]

Great!!!

I will test it as soon as possible!!

[thisiskeithb]

@thinkyhead I updated the mks_robin_nano35 environment in #18516 since STM32 7.0 was causing the build to fail (it now extends mks_robin_nano instead) if you wanted to include that change here instead of the other PR.

[thinkyhead]

The merge brought in the updated mks_robin_nano35 environment. Now the mks_robin_nano35_V2 environment might need some adjustment too.

[thisiskeithb]

The merge brought in the updated mks_robin_nano35 environment. Now the mks_robin_nano35_V2 environment might need some adjustment too.

That's what I was thinking as well. Can it be extended from mks_robin_nano as well? Then it'd use ${common_stm32f1.platform} instead of STM32 (which wasn't working on the Nano 1.2 due to 7.0 being pushed out).

I don't have a Nano V2, or I'd test it.

[rhapsodyv]

@thinkyhead let me know when you finished the code review / fixing, that I will test it.

[MKS-Sean]

@thisiskeithb @thisiskeithb
Some pins of Nano1.2 are different from Nano2.0, and Robin_nano_V2.0 can use the eeprom mounted on the motherboard (through the following configuration: #define E2END 0xFFF #define I2C_EEPROM), Robin_nano_v1.2 cannot use the eeprom mounted on the motherboard, Because it only has 2k bytes of space, and V2.0 uses 4K space, you can also consider merging them. I can make some distinctions in pins_MKS_ROBIN_NANO.h.

[thisiskeithb]

I'm subscribed to this PR, but let me know when it's safe to test on the Nano 1.2 🙂

[makerbase-mks]

Now robin_nano_v1.2 needs to do the following configuration:
default_envs = mks_robin_nano35_v2
#define MOTHERBOARD BOARD_MKS_ROBIN_NANO
#define TFT_LVGL_UI

[rhapsodyv]

Now robin_nano_v1.2 needs to do the following configuration:
default_envs = mks_robin_nano35_v2
#define MOTHERBOARD BOARD_MKS_ROBIN_NANO
#define TFT_LVGL_UI

If nano v1.2 and nano v2 works with the binary Robin_nano35.bin, we may not need two envs... Right now we have two env just because env "nano" runs mks_robin_nano.py, and "nano 2" runs mks_robin_nano35.py.... the only different in the scripts is the output firmware file name....

[thisiskeithb]

If the Nano V2 can use the same/old Nano 1.2 firmware name to update, then you can merge everything into one environment & let Marlin handle whether to use DOGM or LVGL as the GUI depending on the enabled features.

Otherwise, we're back to needing two different environments: One for DOGM & one LVGL.

[rhapsodyv]

@thinkyhead @thisiskeithb

For me, the current LVGL defines was a bit confusing. I created this PR to change their names to match better with Marlin standards.

makerbase-mks#23

Please, take a look. Let me know If you approve, so MKS can merge it.

[thinkyhead]

Some of the defines from pins_MKS_ROBIN_NANO_V2.h seem to be wrong in our forks. According to the MKS documented pinouts they should be as follows (with PE0 and PE10 rather than PE10 and PA7):

/**
 *        ------                  ------
 *  PC5  | 1  2 | PE13       PA6 | 1  2 | PA5
 *  PD13 | 3  4 | PC6        PE8 | 3  4 | PE0
 *  PE14 | 5  6   PE15      PE11 | 5  6   PE10
 *  PD11 | 7  8 | PD10      PE12 | 7  8 | RESET
 *   GND | 9 10 | 5V         GND | 9 10 | 3.3V
 *        ------                  ------
 *         EXP1                    EXP2
 */

[thisiskeithb]

Some of the defines from pins_MKS_ROBIN_NANO_V2.h seem to be wrong in our forks. According to the MKS documented pinouts they should be as follows (with PE0 and PE10 rather than PE10 and PA7):

Their pinout online is incorrect. PE0 is the Y step pin (which is how it's listed in the schematic). Here's a photo from the physical board:

It's been a while since I've ran this board, but LCDs did work correctly with it at the time.