Convert .bin file to .elf file

[abhishekvishwak]

Hi All, 

I currently have a  working prototype board and we are using Arduino IDE for programming. We are planning to use KDS for more professional tool and JTAG debugging for our board. 

We have already made the JTAG interface for our device.

for the next step , the question is it possible to convert the .bin file to .elf file that the KDS uses to program a board and flash it using the PnE multi link programmer.

We were successful to program K22F board using PnE multi link programmer with the example sketches from KSDK.

We are planning to push our firmware basically on the board?

Can anyone point us to right direction? Whether it can be done?

Or we have start from scratch creating new drivers for the board.?

Thanks.

Abhishek

[BlackNight]

Hi Abhishek,

converting a bin (Binary) file to an .elf (ELF/Dwarf) file does not make any sense in my view. The binary file does not contain any debug information, while the ELF/Dwarf usually does (including symbols), see Debug vs. Release? | MCU on Eclipse 

But you can use any normal debug configuration to program your .bin to the target, have a read at

Using Eclipse to Program Binary Files to an Embedded Target | MCU on Eclipse 

I hope this helps,

Erich

[abhishekvishwak]

Thanks Erich for the prompt reply.

I will try to program the .bin to the target board with the PnE multilink.

The binary which we will have from arduino if we push through KDS using PnE is only just programming the board. But JTAG like debugging will not be possible on the target. I am right in this assumption?

So if we want to have break-point( boundary scan) style of debugging. we have to have ELF/Dwarf file of our sourceCode generated from the KDS. 

Sorry for being naive. But i am relatively very less experience in KDS.

Thanks.

Regards, 

Abhishek

[BlackNight]

Hi Abhishek,

the level of debugging support depends on the amount of information. So you can debug a file in the binary format, but as this does not contain debug information (information about source files, variables, functions, etc) you have what you have: assembly code level debugging.

If you want to have source level debugging, then indeed you need the symbols or symbolic information which for example is present in an ELF/Dwarf file.

I hope this helps,

Erich