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!
