• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 83 subscribers
  • Views 403 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.

Original question:

CCSTUDIO-C2000: Hex output format --motorola -m=1 / 2 / 3 with F280049

CCSTUDIO-C2000: TMS320F280041 - Generate hex file from CCS

Wai Wei Hui
Prodigy 50 points

Part Number: CCSTUDIO-C2000

Hi all, 

Our team is facing issue when converting hex file from CCS for TMS320F280049 & TMS320F280041. May I have the step by step guide to know how to generate hex file from CCS?

FYI, I have tried using .out file generated by CCS by using UNIFLASH, the application works well. But when I try using hex file generated from CCS, it does work as expected  so I suspect that there is setting that we didn't set correctly in hex 2000 utility.

Thank you.

Best regards,

Waiwei 

  • +1
    TI__Guru* 87105 points

    Waiwei,

    Please choose the romwidth and memwidth as 16 for C28x.

    Also use the output format as intel hex.

    Let us know if you face further issues.

    Thanks and regards,
    Vamsi

  • 0 in reply to Vamsi Gudivada
    Prodigy 50 points

    Hi Vamsi, 

    We are able to generate the hex file successfully but when we check it into details, I realised that the hex file generated using CCS shows different data with the binary file obtained when I read and export from Uniflash after program it with .out file.

    For your reference, read2.bin shows the data obtained when we read the binary file using Uniflash (device has been programmed using .out file).  

    May I know the reason and how to solve it?

    Thank you.

    Best reagrds,

    Waiwei

  • 0 in reply to Wai Wei Hui
    TI__Guru* 87105 points

    Waiwei,

    When you download the image from Uniflash with a given address range, it will include holes (erased locations as well).  Can you check if the differences are only extra 0xFFFF or something else as well?

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    TI__Guru* 87105 points

    Waiwei,

    Do you have any update on this?  Are those 0xFFFFs coming from the unused holes as I mentioned?

    Can I close this thread?

    Thanks and regards,

    Vamsi

  • 0 in reply to Vamsi Gudivada
    Prodigy 50 points

    Hi Vamsi,

    You may close this thread. Our firmware engineer has solved this issue. 


    Thank you.