Forum Post: RE: Hex Conversion for Command File without SECTIONS Directive

Hi Archaeologist,

Thank you for your reply. Sorry for my late reply.

I understand that the ROMS Directive needs to roughly match the linker command file's MEMORY specification when the SECTIONS Directive is not used. The ROMS Directive can be different from the linker command file's MEMORY specification when the SECTIONS Directive is used. For example:

===============================================================================================

TEST.out

-i
-image
-o TEST.hex
-memwidth 32
-romwidth 32
-map TEST.hex.map
-order MS

ROMS {
   ROM_INFO: o = 0x00030000, l = 0x007D000
}

SECTIONS
{
 .cpu_info : paddr = 0x00030000
 .intvec   : paddr = 0x00031000
 .text     : paddr = 0x00032000
 .const    : paddr = 0x00052000
 .cinit    : paddr = 0x00053000
}

===============================================================================================

Our customer want to define the base address for the boot ROM. I understand that the SECTIONS Directive must be used to define it.

Is my understanding correct?

Best regards,

Daisuke