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.
Hi Team,
There's an issue from the customer need your help:
Previously, the OUT file and HEX file of the same project were burned with UNIFLASH, and the burning time of the HEX file was obviously longer than that of the OUT file. I don’t know what may cause this situation?
In addition, regarding the verification issue, I would like to know whether there is a difference in the final data on the flash of the MCU when programming with an OUT file and using a HEX file? If there is no difference, should the result of checking with the OUT file and the HEX file be the same; if there is a difference, what is the content of the difference? Because sometimes this happens, when you get a control board, you don’t know whether it was burned with the OUT file or the HEX file at first, so there is a possibility of using the HEX file to verify the program that was originally burned with the OUT file.
Thanks & Regards,
Ben
Ben,
1) Is this concern for a production Or during development? If production, please take a look at this FAQ: How can we improve the Flash tool performance?:
https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/904312
2) How did the user create the HEX file in this case?
3) Regarding the verification: What do you mean by "result of checking"? Please explain how they are checking. Are they using verify from debugger? Please provide a snapshot.
Thanks and regards,
Vamsi
Hi Ben,
I am closing this post since I did not hear back from you.
You can reopen the post or Open a new post if you have further questions.
Thanks and regards,
Vamsi