Compile on stm32F207

[olekdata]

Can TFT 3.5 be uploaded soft "normally" using SWD (e.g. ST-LINK V2) and VSC + PlatformIO? Do you have to upload it via SD card?

The program compiles with the settings:

[env:BIGTREE_TFT35_V3_0]
platform = ststm32@9.0.0
framework = stm32cube
board = STM32F103VC
upload_protocol = cmsis-dap

but with the stm32F207, not anymore

[env:BIGTREE_TFT35_V3_0]
platform = ststm32@9.0.0
framework = stm32cube
board = STM32F207VC
upload_protocol = cmsis-dap

I have TFT 3.5 V3.0 with STM32F207. Can I upload firmware version compiled on STM32F103 ? Probably not.

[bigtreetech]

#1562
This PR will fix it. but the ".ld" files should be separated for every borad.
Still working...
And when you use the SWD interface to upload, please be careful not to erase the bootloader

[olekdata]

I probably have a different problem when compiling

a lot of conflicts : e.g.
...stm32f2xx_hal_dcmi.h:71:2: error: conflicting types for 'DCMI_CodesInitTypeDef'
...stm32f2xx_hal_dcmi.h:101:2: error: conflicting types for 'DCMI_InitTypeDef'
...stm32f2xx_dac.h:93:0: note: this is the location of the previous definition #define IS_DAC_TRIGGER(TRIGGER) (((TRIGGER) == DAC_Trigger_None) ||
...stm32f2xx_dcmi.h:103:3: note: previous declaration of 'DCMI_CodesInitTypeDef' was here } DCMI_CodesInitTypeDef;

I think I have uploaded something wrong, the device does not get up - dark screen :-(

[olekdata]

Once again me.

Short questions on how to fix the display

• what to upload.
• and how to upload.

I can see F207 via SWD and STM32 ST-LINK Utility

I will wait for other matters