• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 100 subscribers
  • Views 531 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.

ARM Hex Utility generates odd-length S3 record

guosheng jin
Prodigy 130 points

Processor: OMAPL137 ARM

Compiler: CCS6.0 ARM v5.1.5

I was using ARM hex utlity to generate firmware image in S-record format.

Below is the command file content that specifies the format.

-----------------------------------------

-m3
-image
-map
-romwidth=8
-memwidth=8


ROMS
{ 
    SHARED: org = 0x80000000 len = 0x10000 fill = 0x00
}


SECTIONS
{  .boot:  .text:  .const:  .cinit: DSP_CODE:
}

----------------------------------------------------------

 

As can be seen, Motorola S3-record format is requested. The command file itself seems working, except that the hex file generated is quite odd in that odd number of bytes are generated for each S3-record.

S3228000000054495041635953580D595358050003000200070FB90105000400000007CD
S3228000001D595358040002008841C10105000000000000000D595358020004002184EA
S3228000003A0100C829910E05000878FC0300000D59535806000100030000000D59533A
S322800000575806000100030001000D59535806000100030002000D595358060001006E
S32280000074030003000D59535806000100030004000D59535806000100030005000D97

...

In the record shown about, each record contains 29byte of code. But in other software, I used to see 32-byte code (S3258000.... ) as S3-record being generated.

How can this be fixed ?

  • 0
    TI__Mastermind 43955 points

    Hi Guosheng,

    Would you please provide us the following details.

    1. The link from where you have downloaded the ARM hex utility and its version.

    2. Is it a custom board or DA830 EVM from Spectrum digital.

     

    Meanwhile I will try to provide information on ARM hex utility.

     

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • 0 in reply to Shankari G
    Prodigy 130 points

    This is the Hex Utility comes with CCS6.0.0.00190

  • 0 in reply to guosheng jin
    Prodigy 130 points

    And board is our own board customized based on OMAPl137 EVM.  But i do not think it is relevant.

  • 0
    TI__Guru** 116100 points

    Hi Jin,

    In the record shown about, each record contains 29byte of code. But in other software, I used to see 32-byte code (S3258000.... ) as S3-record being generated.

    Are you getting any issues due to this ?

    Have you tried the same on CCSv5 ?

  • 0 in reply to Titusrathinaraj Stalin
    Prodigy 130 points

    well. I know the format generated was odd long time back. It's only a recent issue in parsing the firmware image (it is based on 16-bit access) that raised my concern. I have not tried this on CCSv5, and actually I was not aware of such utlity in CCSv5 before I migrate to CCSv6.

    CCSv5 has given me enough "blue-screen" problem for which reason I decided to move on to CCSv6. Seeing a Hex Utility as part of tool integrated into CCSv6 is definitely a good surprise but it's just that the software does not seem to allow me to format the image into the style (S37) I want.

    ...

    Is this something that was integrated in CCSv6 but noboday knows how it works?....