• Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1169 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.

Problem with hex2000.exe on Sysbios

Arpan Sadhankar
Intellectual 335 points

Hi,

 

I want to convert my .out file after project building to .s19 (motorola format)

 

Command i use for generating s19 in the post build setting:

"${CG_TOOL_HEX}.exe" -m2 --byte -memwidth 16 -romwidth 16 -order LS -exclude".trace"  -exclude".args" -exclude"passwords" -exclude"csm_rsvd" -map"${BuildArtifactFileBaseName}.mxp" "${BuildArtifactFileName}" & del ${BuildArtifactFileBaseName}.s19 & ren ${BuildArtifactFileBaseName}.m00 ${BuildArtifactFileBaseName}.s19

 

Expected output (as i was getting with DSP-BIOS):

S0 06 000048 4452 1B

S2 08 600008 0070 5848 7F

S2 22 60000C 7D6A00307D6A00307D6A00307D6A00307D6A00307D6A00307D6A00307D6AE9

S2 22 60002A 00307D6A00307D6A00307D6A00307D6A00307D6A003071C800307B96003006

.....

S2 10 612318 8F0C00308EDC003000000000EE

S8 04 309035 06
 
 

Actual Output (with sysbios build):

S0 06 000048 4452 1B

S2 08 000000 0070 6C54 C7

S2 22 60000C FE02 5200 ED0B 761F 01BF 9A02 9B01 D400 1A05 0002 7670 3CF8 6F1A 761F 01BF AD

S2 22 60002A 9A02D4019B011A03000276703CF828A90DAC76704E1D761F03CD56BF024175

....

S2 08 67FFEC 0070814272

S8 04 306C54 0B

I'm doing this for my debug and release builds, same output.

I am designing a parser to read the S19 output, and hence i am failing here. Please provide inputs to identify the mistake in my conversion command.

  • TI__Guru**** 232900 points

    Arpan Sadhankar said:
    Command i use for generating s19 in the post build setting:

    This command looks fine.

    Arpan Sadhankar said:

    Actual Output (with sysbios build):

    S0 06 000048 4452 1B

    S2 08 000000 0070 6C54 C7

    For those following along, the address in this S2 line should not be 0.  I don't know why it is wrong.  To tell you that, I need to reproduce this error myself.  I'd appreciate if you would send in your executable .out file, i.e. the ${BuildArtifactFileName}.

    Arpan Sadhankar said:
    I am designing a parser to read the S19 output

    Is this the only reason you are converting to a hex file?  Then please consider this alternative approach.  The cg_xml package includes a utility named bootimage.  It converts a TI executable .out file to a very simple hexadecimal format.  The Perl source code is included.  You only need basic Perl coding skills to modify it to suit your exact needs.

    Thanks and regards,

    -George

  • in reply to George Mock
    Intellectual 335 points

    Hi,

     

    Sorry lost track of this issue since a while now.

    I need to look at this on priority, i have to flash the s19 and hex files on the dsp. But with both the conversions

    - .out to .s19 and

    - .out to .hex

     

    i have to modify my binary file (thus generated), and then flash the DSP.

    - .out to .hex

    Actual output binary which doesnt work:

    :04000000007060DF4D

    :020000040030CA

    :20000600FE2202001E5856BF0159761FC2115DAD8A0028A9FFFFDD8A767066F99661520112

    :20001600EDF5FFEF03C95CAD92449B04D500DCA07670112D88AD5CADDE96DCA0767006E73A

    :20002600761F03D7CC562000FFCC96009349925138A89651CC51FF0050079651761F03E34D

    :20003600924A90FF9603CC4AFF00FFC79601934A925238A89652924AFFC7935290FF3CA8B1

     

    Output that works after deleting the first line:

    :020000040030CA

    :20000600FE2202001E5856BF0159761FC2115DAD8A0028A9FFFFDD8A767066F99661520112

    :20001600EDF5FFEF03C95CAD92449B04D500DCA07670112D88AD5CADDE96DCA0767006E73A

     

    .s19 procedure already explained above.

     

    This additional step is not justifiable. Please guide me what is going wrong, help resolve this asap.

    Thanks in advance.

  • in reply to Arpan Sadhankar
    TI__Guru**** 232900 points

    To explain what is happening I need to first reproduce it myself.  Please submit everything that is seen by the hex utility, including the .out file, command line options, and any hex command file you might use.  If this is a bug in the hex utility, I'll submit a record in the SDOWP system so the development team can work on it.

    Thanks and regards,

    -George