Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

ARM Hex Utility generates odd-length S3 record

$
0
0

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 ?


Viewing all articles
Browse latest Browse all 17527

Trending Articles