• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 66 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.

TMS320F2800137: Uniflash Checksum: The same Hex generate different ECC value on F2800135 and F2800137

Zane Wei
Intellectual 1835 points
Part Number: TMS320F2800137


Tool/software:

Hi Team,

My customer use F2800135PMR before, but found F2800135PMR flash size is not enough in new project, so they choose F2800137PMR. Now they want use F2800137PMR to replace F2800135PMR,  because they want to use signal device. For the old project which used F2800135, they want use F2800135 hex file download to F2800137. They use checksum to ensure they have download the right hex. But they found, only ECC value is different.

Please see below picture, the two device use the same hex file, what cause only ECC value different?

Best Regards,

Zane

  • 0
    TI__Genius 15010 points

    Hi Zane, 

    Flash ECC size is dependent on the amount of Flash data, as for every 64 bits of Flash data, there are 8 bits of ECC. By switching device from F2800135PMR to F2800137PMR, the Flash Size is increasing from 128KB to 256KB. 

    It can be noted that the correctable Flash ECC memory address ranges for 128KB variants is 0x01080000-0x01081FFF, and for 256KB variants is 0x01080000-0x01083FFF. 

    So by programming onto the 256KB device, the range that the CalculateChecksum function takes into account will be larger for Main Flash ECC.

    So long as the program they are loading onto the new device's Flash stays consistent, that should be considered. 

    Thanks and regards,

    Charles