.out file convert to bin (out -> hex -> bin)

I think something that needs to be considered is how you will interpret the .bin file after you get it.  Specifically, the bin file has all the address info stripped from it.  In other words, in order to use the bin format it's required that all of your data be in one contiguous image.

FYI, there is a -b option built into the hex conversion utility from TI, so you don't even need hex2bin.  However, you'll still need to have your code/data in one contiguous block.  You can use the -image option to generate an image of your code.

This TI hex conversion utility is called hex470.exe which can be used with the -b option to generate .bin file directly from .out file. It has additional options which may help you to configure your file as your requirements.

Refer this -

http://processors.wiki.ti.com/index.php/Secondary_Bootloaders_on_OMAP-L1x

Regards,

Sid

Thank you your advice~

but when I use -b option, there were warning and .bin file has no data.

Warnings are like this.
warning : section '.text' at 0660000h falls in unconfigured memory <skipped>
warning : section '.cinit' at 066f3fch falls in unconfigured memory <skipped>
.
.
.
.

I used this cmd file, 

-b
-memwidth 16
-o=10122.bin

ROMS
{
  FLASH          : origin = 0x330000, length = 0x00FF80, romwidth=16
}

Could you tell me how to  eliminate  those warnings?
Thank you guys.

Thank you your advice~

but when I use -b option, there were warning and .bin file has no data.

Warnings are like this.
warning : section '.text' at 0660000h falls in unconfigured memory <skipped>
warning : section '.cinit' at 066f3fch falls in unconfigured memory <skipped>
.
.
.
.

I used this cmd file, 

-b
-memwidth 16
-o=10122.bin

ROMS
{
  FLASH          : origin = 0x330000, length = 0x00FF80, romwidth=16
}

Could you tell me how to  eliminate  those warnings?
Thank you guys.

1. You should probably use the -image option so that you get one big chunk of data to program instead of little pieces scattered all over.
2. Your ROMS memory range should reflect the physical memory locations you are planning to program.  I don't know which device you are using so I cannot tell you the correct values.

Thank you in advise.

I use TMS320F28335..
How To use the - image option?

Could you give me examples?

Eunra,

Now that I know you're using F28335 it looks like your last bit of code was more or less correct aside from not having the -image option.  Can you attach your map file to a post (click on the "Options" link to attach a file)?

I would guess one of 2 things is happening

• Your linker command file is incorrectly allocating code to the memory range mentioned (0x660000). -OR-
• There is a syntax issue related to the different memory pages.

Brad

Thanks Brad,

I attached CMD file, but the *.cmd file couldn't uploaded, so i change file extension *.cmd -> *.txt.

And I used  this cmd file through hex2000..
====================================================
-b
-memwidth 16  <--- ( or 8)
-o=10122.bin

ROMS
{
  FLASH          : origin = 0x330000, length = 0x00FF80, romwidth=16
}

hi,

could you please tell me where to write this hex command file and how to link that to project? i am using ccsv4 (code composer studio)

hey people,

could anybody give me a shot of how can I create a *.bin file from an *.hex file??  Where I put the -b with hex2000?

thanks

Hey Brad

 What convertor should I use to convert .out(generated using ccs4) to bin file(I am using DM3730)

regards

shashank

Hello Brad 

Even after build without error i can not get .hex file ... pls give suggestion if you have...