- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hello,
after the flash memory is erased and the (bootloader) program is loaded - all unused memory is nicely blank (0xFFFF). However the enabling of SECDED logic for ATCM interface (the execution of _coreEnableFlashEcc_ function) cause this (screenshot of CCS memory browser):
In the linker file there is a 16-bit memory section specified where a safety key value shall be saved after bootloader accept and load application software:
M_SAFETY_KEY (R) : origin=0x00014000 length=0x00000002
SAFETY_KEY : type=NOLOAD > M_SAFETY_KEY
Then, in a source file there is const volatile variable u16_key defined with #pragma DATA_SECTION(u16_key, "SAFETY_KEY").
Reading data on ???? addresses cause data abort - double bit error detection. As You can see at the screenshot above, the safety key location is ????, therefore the abort occurs.
1. Is that because the correct ECC values for these locations are not computed in the flash ECC memory? If so - why?
2. And why unused flash memory is not 0xFFFF after the SECDED logic is enabled?
With regards,
Tomas
