Hello Champs,
Customer found that the .neardata can't be initialized correctly in SPI boot mode.
1. When .text is allocated to LL2 (local L2), the SPI boot is good.
2. When both .text and .neardata are alocated to SL2 (MSMC SRAM), the debug mode and the SPI boot mode are good.
3. When .text is located to SL2, neardata is alocated to LL2, the debug mode is ok, but the SPI boot mode is incorrect, the .neardata isn't initialzed, it is still the default value.
What may cause the issue?
Below is the cmd file
////////////////////////////c6678.cmd/////////////////////////////
-heap 0x8000
-stack 0x19500
MEMORY
{
BOOT_CORE: o = 0x10800000 , l = 0x000000C0(origin地址随DNUM改变,此处只写core0)
LL2: o = 0x108000C0 , l = 0x00040000(同上)
LL2_prog: o = 0x108400C0 , l = 0x00030000(同上)
SL2_prog: o = 0x0C3868C0 , l = 0x00079740
DDR3: o = 0xA0000000 , l = 0x10000000
}
SECTIONS
{
.myboot
{
*.*<boot.obj>(.text)
} > BOOT_CORE
.text > SL2_prog
.cinit > LL2_prog
.const > LL2_prog
.switch > LL2_prog
GROUP
{
.neardata
.rodata
.bss
} > LL2_prog
.far > LL2_prog
.csl_vect > LL2_prog
.stack > LL2_prog
.far_data > LL2_prog
.cio > LL2_prog
.system > LL2_prog
Platform_lib > LL2_prog
.data_ddr3 > DDR3
}
///////////////////End of c6678.cmd///////////////////
Thanks.
Rgds
Shine