• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 393 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.

TMS320F28384S: Hex generation

Jordan Zhou
Genius 9790 points
Part Number: TMS320F28384S

Hi,

Just one doubt about *.hex generation.

With compiler V20.2.3 LTS (eabi format), we get two different results in two different ways:

1) C2000 Hex Utility, with --romwidth=16 --ti_txt, the *.hex was generated but didn't work;

2) Cmd: hex2000.exe -i "proj_lab05b.out" -o "proj_lab05b.hex" -order MS -romwidth 16, the *.hex was generated and worked well.

Did I missed some configurations in C2000 Hex Utility?

Thanks a lot.

Br, Jordan

  • +1
    TI__Guru**** 245000 points

    In the output file produced when --ti_txt is used, addresses correspond to 8-bit bytes and not 16-bit words.  Therefore, the addresses are doubled.  A section that is at address 0x1000 in proj_lab05b.out is at address 0x2000 in the --ti_txt output file.  The tools that reads in the file created by hex2000 --ti_txt needs to account for this difference.  If that is not possible, then you have to use another hexadecimal format like -i (Intel).

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    TI__Genius 9790 points

    George,

    Actually 8-bit bytes is used, with the same result as 16-bit bytes.

    Let's try with -i (Intel).

    Thanks a lot.

    Br, Jordan