Features and known issues in STM32CubeIDE

Hey, ST! Some feature requests for CubeMX/IDE code generator for custom bootloader/application split firmware development follows.

It would be nice to have control over VECT_TAB_SRAM, VECT_TAB_OFFSET definitions in system_stm32xxxx.c file. I guess it's really easy to implement, but we can go deeper into the forest..

Maybe you could also introduce some control over code address (maybe RAM too?) ORIGIN (with auto-calculation of LENGTH) variables in the linker script? For example, if this is the default for some MCU:

MEMORY

{

RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 20K

FLASH (rx) : ORIGIN = 0x8000000, LENGTH = 192K

}

And I want my code to begin at 0x8008000, it should become:

MEMORY

{

RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 20K

FLASH (rx) : ORIGIN = 0x8008000, LENGTH = 160K

}

or even something more custom:

MEMORY

{

RAM_SHARED (xrw) : ORIGIN = 0x20000000, LENGTH = 1K

RAM (xrw) : ORIGIN = 0x20000400, LENGTH = 19K

FLASH_BOOT (rx) : ORIGIN = 0x8000000, LENGTH = 32K

FLASH_APP (rx) : ORIGIN = 0x8008000, LENGTH = 160K

}

__shared_ram_start__ = ORIGIN(SHARED_RAM)

__shared_ram_size__ = LENGTH(SHARED_RAM)

__ram_start__ = ORIGIN(RAM)

__ram_size__ = LENGTH(RAM)

__flash_boot_start__ = ORIGIN(FLASH_BOOT)

__flash_boot_size__ = LENGTH(FLASH_BOOT)

__flash_app_start__ = ORIGIN(FLASH_APP)

__flash_app_size__ = LENGTH(FLASH_APP)

Thank you!

Auto Complete does not work for me. Vary rarely does it do what it is supposed to do. I've enabled the fix in the preferences, still really frustrating it does not work. Getting it to work using Ctrl Space EVERY time is ridiculous.

Another issue, zooming. On MAC, Command + / - does not zoom in or out. I've changed the preferences to see if that would fix, nope. Zoom is broken as well.

Hi

I'm facing issues with my projects migrated from STM32 System Workbench (created for NUCLEO-H743 and NUCLEO-F746). I followed the migration guide and, at first, the projects were building successfully. Then I reconfigured some timers in built-in CubeMX plugin. After regenerating the code, the projects broke. Firstly I needed to provide again all dependencies to external libraries and includes folder. Secondly the build failed due to duplicated _sbrk function. I found this had been moved to sysmem.c. Since the body of the function was the same I removed duplicated entry from syscalls.c Next, it turned out that startup_stm32h743xx.s file was also duplicated, and there was startup_stm32h743zitx.s with the same content. So I excluded the file from the build and tried building again. Finally, the build succeded however I am not able to debug the application. When I switch to Debug perspective I can only see

STMicroelectronics ST-LINK GDB server. Version 5.2.3

Copyright (c) 2019, STMicroelectronics. All rights reserved.

Starting server with the following options:

       Persistent Mode           : Disabled

       Logging Level             : 1

       Listen Port Number        : 61234

       Status Refresh Delay      : 15s

       Verbose Mode              : Disabled

       SWD Debug                 : Enabled

Waiting for debugger connection...

Debugger connected

and a Thread #1 [main] 1 core.... tree on the left. But the application doesn't stop at the beginning of the main function or anywhere else at the corresponding code lines. After pausing the execution I get "Break at address "0x8009eb4" with no debug information available, or outside of program code." Another thing is, the Build Analyzer is no longer showing any information about memory consumption.

How can I fix these projects?

Hello,

For any new issue or a question related to STM32CubeIDE, please create a new post on its dedicated space (https://community.st.com/s/topic/0TO0X000000y2j7WAA/).

I will close this thread to avoid reporting more issues here as it will be difficult to follow them.

Thanks for your understanding.

Amel