• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 145 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-Q1: DCSM configuration embedded into .out file however after converting to hex file, the contents seems not right

Will Gao
Intellectual 2335 points
Part Number: TMS320F280049-Q1

Hi BU experts, 

I am asking this for customer. I used dcsm_security_tool demo and generated the .hex file using project's Hex Utility as below: 

I tried to load the generated hex into the device (DCSM OTP not used before), and the programming process failed. 

However if I just loaded the .out file, the programming process succeed. 

So I checked the generated hex content, and find that the contents are not right as shown in below fig: 

Do you know why? 

Regards, 

Will 

  • +1
    TI__Guru**** 245040 points

    Look closely at the build log in the Console view.  There is probably a diagnostic similar to ...

    Fullscreen
    1
    warning: Data is being written to auto-generated file file_name_here.a01
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    This means half of each 16-bit word is written to file dcsm_security_tool.hex, and the other half of each 16-bit word is written to the automatically created file file_name_here.a01.  That is because, when --ascii is used, the default setting of --romwidth=8.  If you change to --romwidth=16, both parts of each 16-bit word are written to dcsm_security_tool.hex.  For details, please search the C28x assembly tools manual for the sub-chapter titled Understanding Memory Widths.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Intellectual 2335 points

    Hi George, 

    Thanks for your guidance. The problem can be solved.