MSPM33-SDK: ECC configuration

Part Number: MSPM33-SDK
Other Parts Discussed in Thread: MSPM33C321A, SYSCONFIG

Hello,

I am working on MSPM33C321A eval board, and I use Code Composer Studio to build my project.

I would like a confirmation about ECC activation or not. The ECC management (active or not), is it configured in the linker file (.cmd) ?

I mean this, in the .cmd file :

Without ECC:

MEMORY
{
    FLASH           (RX)  : origin = 0x00000000, length = 0x000FFFFF
    SRAM            (RWX) : origin = 0x20000000, length = 0x0003FFFF
....
 
With ECC:
MEMORY
{
    FLASH           (RX)  : origin = 0x10000000, length = 0x000FFFFF
    SRAM            (RWX) : origin = 0x30000000, length = 0x0003FFFF

...

 

Right ? Or is it configured elsewhere ?

Thanks

  • Hi 

    I will reply this question tomorrow

  • Hi Sebastien Le Diouri

    No, this is incorrect. ECC activation or enablement is not controlled by mapping the memory to a different address range in the linker command file (.cmd).
    Where is ECC Configured?
    Instead of modifying the linker file, look to these two primary mechanisms:
    • Non-Main Configuration (BCR / Non-Main Flash): The Boot Configuration Register (BCR) in the NONMAIN flash region dictates the device's boot behavior and global hardware configurations. You can adjust these settings graphically via the SysConfig tool included in Code Composer Studio. Look under the System or Flash / Non-Main settings in SysConfig to toggle default hardware behavior. 
    • DriverLib Code / Peripheral Registers: You can dynamically control or interact with ECC errors using the Flash Controller (FLASHCTL) API provided in the MSPM33 SDK. Functions like DL_FlashCTL_readVerifyFromRAM64WithECCGenerated allow you to handle explicit evaluation steps. 

    Thanks