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

CODECOMPOSER: When generating a hex file with hex utility in CCS, the Entry point is incorrect?

Robert Fleury
Prodigy 100 points
Part Number: CODECOMPOSER

Hello all,

According to the document "SPRA958L – January 2013 Running an Application from Internal Flash Memory on the TMS320F28xxx DSP": The hex utility should generate a .hex file with some starting hex for the bootloader (which includes the entry point), followed by the code to go into flash.  When I put in an entrypoint of 0x3f123456   (Command line options --entrypoint=0x3f123456 --boot --ascii) I get the following first couple lines in the hex output:

 

AA 00 00 00 00 00 00 00 00 12 56 1A 3E 48 FF 00 00 01 FE 02 00 00 00 FE
04 00 00 00 FE 06 00 1D 3E FE 08 00 1D 3E 00 00


only the 12 and 56 from the entry point made it to the hex output. 

If i put 0x3ff4fa, I get the following:

AA 00 00 00 00 00 00 00 00 3F FA 1A 3E 48 FF 00 00 01 FE 02 00 00 00 FE
04 00 00 00 FE 06 00 1D 3E FE 08 00 1D 3E 00 00

Again, missing some bytes for the entry point.


Whats going on here?

  • 0
    Guru 92251 points

    I haven't tried it, but does --romwidth=16 change the behavior?

    The hex2000 documentation says the default ROM width depends on the format used.

  • 0 in reply to Chester Gillon
    Prodigy 100 points

    This worked!  Thanks so much! 

    --entrypoint=0x12345678 --romwidth=16 --boot --ascii

    10 AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 34 56 78 00 1A
    00 3E C8 48 FF FF A0 00 00 00 00 01 FF FE A0 02 00 00 00 00 00 00 FF FE
    A0 04 00 00 00 00 00 00 FF FE A0 06 00 00 C7 1D 00 3E FF FE A0 08 00 00
    C7 1D 00 3E 00 00 00 00