[kucza]

These are not ” Chinese clones of the ST devices”. These are geniuine devices with ARM licence. Shure they are pin to pin compatibile (and peripherial as well) with ST.  Gigadevices MCUs are fully suported by IAR or KEIL compilers.

[kucza]

Run “C:\Users\info\AppData\Local\VisualGDB\Python3\scripts\mbed.exe compile –supported” in directory “…       failed to create process.

Then I have deleted Python3. VisualGDB have found missing Python and let me download it again. This time I chose 2.7 version and looks it works now.

Thank you for support.

• This reply was modified 4 years, 10 months ago by kucza.

[kucza]

I can confirm that build 2609 solves the issue. Thank you.

[kucza]

Linker script in txt format.

Attachments:

You must be logged in to view attached files.

[kucza]

I can confirm that after  Regenerate MCU-specific files i was able to compile project with new Mbed OS. However it doesn’t work like on older OS version. After run it stuck in Reset_Handler of startup_stm32f407xx.S file. Default linker scrip (in attachment) is:

C:/Users/kucza/AppData/Local/VisualGDB/EmbeddedBSPs/arm-eabi/com.sysprogs.arm.mbed/targets/TARGET_STM/TARGET_STM32F4/TARGET_STM32F407xG/device/TOOLCHAIN_GCC_ARM/STM32F407XG.ld

Is is proper one? Whay is the RAM shortned by 0x188?

RAM (rwx) : ORIGIN = 0x20000188, LENGTH = 128k – 0x188

 

[Author]

Posts