How to make .bin from .elf

[ko-hey]

Hi all,

I want to try DDR Stress test via JTAG interface with i.MX6SL.

According to the following link, user use elf file which is in ddr_stress_tester_jtag_vX.xx.zip and makes use of *.bin file output.

i.MX6/7 DDR Stress Test Tool V3.00 

http://cache.freescale.com/files/training/doc/ftf/2014/FTF-SDS-F0170.pdf 

I tried to convert from elf to bin file with following link but failed.

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0805bj/CACDFBIF.html

Could you tell me how to get a bin file to use DDR Stress Test via JTAG ?

[Background of the question]

I want to try DDR Stress test via JTAG interface and unzip a ddr_stress_tester_jtag_vX.xx.zip.

Then, I got .elf but those files exceeded capacity of internal RAM.

So I think I need to get bin file from it.

Ko-hey

[Yuri]

Hello,

   Using .elf with JTAG is quite reasonable way. The program in itself in .elf format

uses the same target memory as in just memory image in .bin. But usually it is needed 

to perform system / memory initialization, provided by corresponding initialization script.

   Examples of the initialization script may be found in

ddr_stress_tester_v3.00\script\mx6sl\ directory   

Have a great day,

Yuri

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

Note:

- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored

Please open a new thread and refer to the closed one, if you have a related question at a later point in time.

[ko-hey]

Hi YuriMuhin_ng‌

Thank you for reply.

Do you say it doesn't need to convert to bin from elf file ?

Does it no matter that the elf file exceeds the capacity of internal RAM ?

Are the following steps correct ?

1. User runs DRAM init which is in ddr_stress_tester_v3.00\script\mx6sl\ directory.

2. User loads ddr_stress_tester_jtag_v3.00\ddr-test-uboot-jtag-mx6sl.elf

BR,

ko-hey

[Yuri]

Hello,

 Files  .elf and .bin are really just different formats of the same code / data.

In .elf code / data are stored in records with headers, also additional information 

is added, say for debugging. In .bin memory image is stored. 

  If Your debugger can load and run .elf, using own loader, understanding .elf format - apply it.

Note - special command should be used to load .elf - it is not just copy image file to memory,

byte-to-byte, as for the .bin.  

  Your steps are correct.

Regards,

Yuri.