VisualDSP, HEX op-codes from LDR file

Hello everybody,

I would like to post-proccess output LDR file that contains description of
my program (and hex code as well). This post-proccessed file will be used by
VisualDSP to FILL L2 memory space of BF535, or by JTAG debugger to fill
external memory (SDRAM).
Since LDR file stores HEX op-codes as they are (Intel HEX-32 format), and
memory FILL command uses little endian format, things are getting mixed-up.
Any suggestions how to proccess LDR (or DXE) file into format used by FILL
operation (or JTAG download format) ?

appreciate your comments,
Dubi

"DB" <dbiruski@yahoo.com> wrote in news:bidoa6$gmd$1@news01.intel.com:

> Any suggestions how to proccess LDR (or DXE) file into format used by
> FILL operation (or JTAG download format) ?

The ICE will use the ELF file (.DXE). Read up on ELF format. I think you 
can get the document on the standard from Intel's website, part of the Tool 
Interchange Standard. ADI provides elfdump.exe for dumping out DXE's for 
inspection.

-- 
Kenneth Porter
http://www.sewingwitch.com/ken/

"Kenneth Porter" <ken.blacklist@sewingwitch.com> wrote in message
news:Xns93E34216FDFF4shivawellcom@64.164.98.50...
> "DB" <dbiruski@yahoo.com> wrote in news:bidoa6$gmd$1@news01.intel.com:
>
> > Any suggestions how to proccess LDR (or DXE) file into format used by
> > FILL operation (or JTAG download format) ?
>
> The ICE will use the ELF file (.DXE). Read up on ELF format. I think you
> can get the document on the standard from Intel's website, part of the
Tool
> Interchange Standard. ADI provides elfdump.exe for dumping out DXE's for
> inspection.

Kenneth thanks for the hint - elfdump (and its switches) is what I was
looking for. I just tried it, and I am getting exactly what I need.
thanks,
Dubi