cancel
Showing results for 
Search instead for 
Did you mean: 

CubeMX 6.14 migration bug

trzeci
Associate II

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

2 REPLIES 2
TDK
Guru

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".
trzeci
Associate II

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.