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.

TMS320F2800157: ECC is not same

Part Number: TMS320F2800157
Other Parts Discussed in Thread: UNIFLASH

Hi Team,

There's an issue from the customer need your help:

Perform uniflash to read the memory operation on the control board, and output the .out file, and write the generated file to another same control board for integrity verification. It is found that the ECC of the two is different, and the others are the same, and the other is the same. Hex file operation, the result is the same, how to solve it?

Could you help check this case?

Thanks & Regards,

Ben

  • Hi Ben,

    Can you please confirm if my understanding is correct?

    1. Perform uniflash to read the memory operation on the control board, and output the .out file.

    2. write the generated .out file to same control card and check the ECC.

    3. ECC from 1st step doesn't match with ECC of 2nd step.

    4. Perform  uniflash to read the memory operation on the control board, and output the .hex file.

    5. write the generated .hex file to same control card and check the ECC. ECC doesn't match.

    Regards,

    Rajeshwary

  • Hi Rajeshwary,

    yes, you're correct.

    Best Regards,

    Ben

  • Hi Ben,

    An 8-bit ECC value is calculated for every 64-bit data aligned on a 64-bit boundary in the Flash main array. Address of the corresponding 64-bit data is also included in the ECC calculation.

    1. After programing the control card with generated .out file or .hex file does Flash main array data matches?

    2. When writing to control card using Uniflash, check_box  for Auto ECC Generation is ticked?

    if it is ticked then Flash  API calculates ECC for the user-provided address (aligned on a 64-bit memory boundary) and the corresponding 64-bit data. API programs the calculated ECC along with the main array data when using this mode.

    3. Did Verify Flash after Program is successful?

    Regards,

    Rajeshwary

  • Hi Rajeshwary,

    1.It matches.

    2.Check or uncheck the check_box of Auto ECC Generation of Uniflash, the ECC in the checksum is different from the ECC of the checksum in the original control card, and the two checked ECCs are the same.

    3.In verifying integrity in checksum, Flash, OTP and OTP ECC are the same, but ECC is different.

    Best Regards,

    Ben

  • Hi Ben,

    I will check on this and get back to you.

    Regards,

    Rajeshwary

  • Hi Rajeshwary,

    My customer met the same question, hope to your reply, thanks!

  • Ben, Bruce,

    When the users downloaded the flash contents form the Uniflash, they might have downloaded for a memory range (or the entire flash range) and not just the initialized sections alone.  Hence, when they reprogram that image (any format), even the erased locations' 0xFFFF might have got programmed (and not just the initialized sections).  This means, ECC got programmed even for the erased locations' data 0xFFFF.

    As long as they don't get an ECC error while executing the application, they should be fine.

    Thanks and regards,

    Vamsi