AM263P4-Q1: How to enable the ECCM module

Hi, 

Understood the usecase, let me check this and get back to you

Thanks & Regards,

Aswin

Hi,

makoto yamashita said:

intend to detect ECC errors when the SBL loads the program from external flash memory; therefore, I would like to include non-XIP regions in the ECC conversion process as well. Please explain how to apply ECC conversion to the entire program area, including non-XIP regions. Note, however, that the external flash also stores data other than the program itself, and I wish to exclude that data from ECC conversion. 

Currently as a part of the build process we are enabling ECC on XIP regions only as they are executing from flash. The non XIP region will be copied to RAM, so RAM ecc would also serve the purpose here. That being said, if the non xip image is appended with the ECC bytes and flashed, then when the flash read happens during the image loading process, the ECC will be checked by ECCM hw. 

The script currently does not do that. It only enables ecc for xip regions.

If ECC needs to be enabled the option would be to Enable Flash ECCM on the address region where the application image is stored. Modify the application image build script/python file to append ecc bytes to the image.

The data which needs to excluded from ECCM, it can be accessed by the last flash memory window FSS region3.

makoto yamashita said:

● In `conf.json`, I specified `"start": "0x60100000"` and `"size": "0x400000"`. However, when analyzing the generated `mcelf_xip` using `tiarmreadelf --headers`, I observed that the usage size increased by approximately 1.125 times even in the region beyond `0x60500000` (calculated as `0x60100000 + 0x400000`). Is it the intended behavior that *all* XIP segments within the `.mcelf_xip` file undergo ECC conversion, regardless of the "start" and "size" address range specified in `conf.json`?

Yes this is the intended behavior . 

> If ECC needs to be enabled the option would be to Enable Flash ECCM on the address region where the application image is stored. Modify the application image build script/python file to append ecc bytes to the image.

Could you please provide the build script/python file that adds ECC bytes to the MCELF (application image) for the non-XIP region in the AM263Px MCU+ SDK: 11.00.00.19 environment?

It is acceptable for the specification to apply ECC bytes across the entire non-XIP region.

Hi, 

I am checking on this, currently the support is not there to enable ecc on non xip region. Allow me some time to get back to you