AM13E23019: Clarification on ECC behavior for DMA in subsystems - Flash Read Interface (FRI) vs. Read Interface

Part Number: AM13E23019

Hi Team,

I've had a customer ask after the FLASH subsystem, and want to have clarification on how the Read Interface differs from the Flash Read Interface (FRI) in function, and scope with regards to the ECC for DMA read access.
A related question is on using the FRI-x

The AM13E230x TRM, is unclear in some wording between sections 13.5 - Flash Read Interface and 13.6 - Read Interface, specifically with respects to ECC via DMA access.

 

Section 13.5.5 indicates ECC doesn't apply to DMA transferred data, but section 13.6.2.1 indicates DMA is protected for single bit errors (provided it's not all 1 or 0).

The intended application is to do flash writes for firmware updating and data storage.

Per current wording for these two cases of how DMA could have ECC, they are contradictory.
Simple ask is there DMA protection; which of these two instances are true? 

This ties into the application case - aim is to perform FLASH writes for firmware updating and data storage.
Section 13.5.6 - Procedure to Change Flash Read Interface Registers provides a prescriptive procedure for reconfiguring the FLASH peripheral, which would be undertaken to disable data caching before write.

It's unclear how to route FLASH access through the provided FRI-1/FRI-3/FRI-4 sections, ties into the above question given ECC is needed.
I would understand that to be only viable - if ECC is needed via the CPU data read through FRI-3 (or the others).

  • Hi Max,

    1) The DMA can determine address/data errors and are logged in the ADDERR and DATAERR bits. I will file a ticket to have the misleading note text updated.





    For the AM13E230x, ECC protection is applied to the entire MAIN Flash Bank (all partitions).The AM13E230x Flash ECC does not perform checks on data blocks containing all 0s or all 1s. This is a hardware limitation and there is no control to override this behavior.

    - Note that the cache and buffer mechanisms are disabled by default at device boot and must be configured before application execution. The code cache and data cache are enabled with CODE_CACHE_EN (bit 2) and DATA_CACHE_EN (bit 1) in FRD_INTF_CTRL (offset 100Ch).

    - For FOTA and live firmware update, FRI-3 as the region used to program and verify the new image in the second half of flash while the current application keeps executing through FRI-1. The ranges are then swapped with BANKMAP.CPUxSWAP

    - FRI-3 and FRI-4 have no instruction fetch, so they can be configured from code executing from flash, as long as no data access to the covered banks is in progress. Put the configuration code in a separate function and wait nine cycles before returning




    Regards 
    Arpit