Skip to main content
Associate III
March 19, 2025
Question

CubeMX 6.14 migration bug

  • March 19, 2025
  • 1 reply
  • 491 views

CubeMX upgrade 6.13 -> 6.14

left in linker script following configuration:

_estack = ORIGIN(RAM_D1) + LENGTH(RAM_D1); /* end of RAM */

MEMORY
{
/* Start MX regions */
DTCMRAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K
FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 2048K
RAM_D3 (xrw) : ORIGIN = 0x38000000, LENGTH = 64K
ITCMRAM (xrw) : ORIGIN = 0x00000000, LENGTH = 64K
RAM_D2 (xrw) : ORIGIN = 0x30000000, LENGTH = 288K
RAM (xrw) : ORIGIN = 0x24000000, LENGTH = 512K
/* End MX regions */
RAM_D1 (xrw) : ORIGIN = 0x24000000, LENGTH = 512K
}

.data :{} >RAM_D1 AT> FLASH

.bss :{} >RAM_D1

 ._user_heap_stack : {} >RAM

duplicated area of RAM and overlapping heap with data

1 reply

TDK
Super User
March 19, 2025

Include your IOC file if you think it's producing invalid code.

"If you feel a post has answered your question, please click ""Accept as Solution""."
trzeciAuthor
Associate III
March 19, 2025

It generated this linker script during migration.

I had to replace name of RAM to RAM_D1 in this .ioc file (after the problem was diagnosed).

And *YES*, it produced *VERY* invalid code.