• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 323 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DATA Abort doesn't happen for Odd 64-Bit Boundary of Erased Flash Space

Pashan None
Genius 5660 points

Hello Support,

I have enabled ECC as well as SECDED Logic within Flash Wrapper correctly.

Now, if I read 64-Bit DATA from Flash Address 0xE060, then I get Correctable Error Address within Flash Wrapper as well as ESM Group 1 Error

Now, if I read 64-Bit DATA from Flash Address 0xE068, then I get Uncorrectable Error Address within Flash Wrapper as well as DATA Abort along with ESM Group 3 Error.

I am using LDRD Instruction to read 64-Bit DATA.

Both the Flash Area have been in ERASED State.

Any idea why the difference between Even Multiple and Odd Multiple of 64-Bit Address even though all the Flash Cells are in ERASED State.

I am assuming all ERASED Flash Cell populated ECC with Wrong Value which should be Double Bit Error.

Please help soon.

Thank you.
Regards
Pashan

  • 0
    TI__Mastermind 22375 points

    Pashan,

    I can only suspect that when flash wrapper removes the address component (in this case 0xE060) of the original ECC checksum which is all ones after erase, it generates a new ECC which causes the CPU to think it is only a single bit error or most likely a three or more bit errors.
    Note that a multiple bit error can break down the SECDED to think it is only a single bit error or even no error.