• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 84 subscribers
  • Views 173 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.

TMS320F280025: HEX file abnormal

Angela Zou
Intellectual 1085 points
Part Number: TMS320F280025


Hi experts,

What would cause the address to be shifted two bytes backward when addressing a structure variable in a compiled hex file? For example below, the right compile result would be E2AF0210, but abnormal compile result is E2AF0212. The source code is exactly the same with the same CCS version and compiler version.

  • 0
    TI__Intellectual 1085 points

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/CCS-Project-Analysis.7z

    Here is the project. The passcode is hoymiles@2022

  • 0 in reply to Angela Zou
    TI__Expert 7715 points

    Hi Angela, I apologize for the delay, I am reaching out to the expert and will get back to you soon. Thanks, Ashwini.

  • 0 in reply to Ashwini Athalye
    TI__Guru**** 251690 points
    Angela Zou said:
    the right compile result would be E2AF0210, but abnormal compile result is E2AF0212.

    Are you able to somehow build and get the first result, then somehow build again and get the second result?  If so, what changes between those builds?  

    Please put the build in the state where you get the bad result.  Disassemble with a command similar to ...

    dis2000 final_executable.out > final_executable_dis.txt

    dis2000 is located in the same directory as the compiler cl2000.  Change final_executable.out to the name of the final executable file created by the linker.  Inspect the output.  Find the problem instruction.  Is it good or bad?

    Thanks and regards,

    -George