serious issue when using IAR

Hi,

i'm using IAR(8.11.1) to develop.

I found a serious issue that some values always be changed when booting.

Finally I find the code which break the RAM:

void arch_rom_init(void) { #if defined (__DA14531__) && (!USE_CHACHA20_RAND) // Store value of _rand_state stdlib/rand.c RW variable uint32_t rand_temp = _rand_state_ROM_DATA; #endif test1 = DB_HEAP_BASE; test2 = RAM_UNINIT_START_ADDRESS; test3 = RAM_UNINIT_END_ADDRESS - RAM_UNINIT_START_ADDRESS; test4 = (__section_begin(".heap_db_area")); test5 = RET_MEM_BASE; #if defined (__DA14531__) && (USE_TRNG) // Given that the DA14531 secondary bootloader and flash programmer // (UART version) leaves untouched the memory area between // RAM_UNINIT_START_ADDRESS and RAM_UNINIT_END_ADDRESS address, // this memory area can be used to feed the TRNG buffer with // true random data (random values after RAM block power up). // The maximum size of the TRNG buffer is the difference between the // RAM_UNINIT_END_ADDRESS and RAM_UNINIT_START_ADDRESS. // // Note: The maximum TRNG buffer size should be recalculated // if the application uses the Free Area region (check the // scatter file). In any case, if the used TRNG buffer size is // small enough, the TRNG algorithm will operate with true random // data independently to the maximum size used in the following // memory copy. For further details check the SDK6 documentation. if (trng_state_val != 0x12348765) { memcpy((uint8_t *) DB_HEAP_BASE, (uint8_t *) RAM_UNINIT_START_ADDRESS, RAM_UNINIT_END_ADDRESS - RAM_UNINIT_START_ADDRESS); } #endif

when first boot,the TRNG is enabled and here will do copy to DB_HEAP_BASE.

but i find in boot.h ,all the definitions are compiled to 0.(on keil project,it contains the right address)

at address 0,it contains the address of .(remapped at 0?)

Then data start from are all be overwritten ,then cause crash.

/******************************************************************************************************************@file boot.h**@brief此文件包含启动相关变量的声明。**版权所有（C）2019-2020 Dialog Semiconductor。*此计算机程序包括Dialog Semiconducyabo国际娱乐tor的机密专有信息。版权所有。****************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************外部结构长度；#定义编码地区和地区的长度（2 uint32\U t）定义编码地区和地区的长度（2 uint32\U t）定义编码地区和地区的长度（2 U U U U地区的长度（2 U U U U U U U U U U地区的长度）和；pragma 35；pragma 35；pragma#pragma 35; pragma #\\umumumum地区的保留区的成员和地区的地区的长度（U U区的地区的地区的不不受地区的RET））#定义非\u RET \u heap \u END（uint32&u t*）（（uint32&u t*）（（uint32&u t*））（（（uint32&uint32&u t t*））））））））））））；定义非_ret堆堆堆长度（非_ret堆堆堆端-非_t堆堆端-非t32\u t堆堆端-非tt t t t t 32&u t*）））））（（）））定义定义非_ret堆堆堆堆长度（非t堆堆堆堆堆堆端-端-非t堆端-非t堆堆端-非#定义db_heap_LENGTH（db_heap_end-db_heap_BASE）#endif//\u启动\u_

Futher more,

even if the address is right,

how can it promise the section[heap_db_area] is bigger than (RAM_UNINIT_END_ADDRESS - RAM_UNINIT_START_ADDRESS)?

如果编译器在secton[heap\u db\u area]之后放置一些初始化变量，仍然存在风险。