• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 421 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F280049: ECC difference for same project Out file and Hex file

Terry Deng
Intellectual 2485 points
Part Number: TMS320F280049

Dears

My customer report the OTP ECC value is difference after CCS download by out format and by hex format for same project.  Do you know some possible reason? Because customer is waiting to MP their product, so could you please help check this case by urgently? thank you.

Customer cannot send their code to us, so I cannot recur such issue in my side. I collect the information as below:

1, They use CCSv10, device is F280049, project is in COFF format, they set the password and boot-pin in OTP Z1 zone.

2, After CCS download .out file to a new device A, it can run well

3, CCS generate .hex file by "--memwidth=16 --romwidth=16 --intel" setting

4, After CCS download .hex file to a new device B, it can not run

5, Read and compare the data between above A and B device, the OTP and FLASH content are all same, the mostly ECC value are same except the 2nd byte value from address 0x1071000 is 0xFF for .hex download, but 0xEE for .out download.  

6, If re-download the B device by .out file, then B device can resume working, and the ECC value also changed as same as A device.

7, If re-download the A device by .hex file, the A device still keep working, and the ECC value also keep same as original A device.

8, Customer has try 10 pcs device and get the same behavior.

 

  • 0
    TI__Guru** 113685 points

    Hi Terry,

    Can you check the ECC error log register to see which address is causing this error ?

    While working on similar issue earlier with you (COFF vs EABI) we made some fix which is yet to be released. Have you tried fixed version which I provided to you on your setup to see if that fix this issue ?

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Intellectual 2485 points

    Hi Vivek

    This is another customer and have not try the fixed patch you provide before. Because the issue behavior is different.  

    Before issue is EABI format .out file ECC error while COFF format .out file run ok.   This time issue is COFF format .hex file ECC error while COFF format .out file run ok.

    Last issue you help find the root cause that EABI format LINKPOINTER data is mixed to generate the error ECC.

    This time customer also hope to know the root cause what is indeed different for .out file and .hex file? And what cause 2nd byte value from address 0x1071000 is 0xFF for .hex download while it is 0xEE for .out download? 

  • 0 in reply to Terry Deng
    TI__Guru** 113685 points

    Terry,

    Did you check the ECC error log register to see which address has ECC error ?

    Also are you seeing this issue on your setup as well with updated file which I sent ?

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    TI__Intellectual 2485 points

    Hi Vivek

    Today we try the fixed patch your provide before and it solve this time issue again. thank you.

    We still hope can understand the root cause reason? what is different for .out file and .hex file to generate the ECC?  

  • 0 in reply to Terry Deng
    TI__Guru** 113685 points

    Terry,

    It's all about how the different section in USER OTP are partitions when programming. In case of coff file all the section were like what was defined in .asm/.cmd file. In .EABI these were combines hence there was issue and here also when you generate hex file, multiple section could be getting combined hence causing the same issue.

    Regards,

    Vivek Singh