hex files : bytes vs words

[Guest]

Hello all,

I have a Dataman48Pro programmer with the adapter to program TMS320F2812 devices.
I am not able to program correctly the device, it seems that my hex file is not well understood by the Dataman PG4UW v2.57 software. However, the file can be programmed but when I look to the buffer there is empty line in between code:

;;--- Buffer dump
PG4UW - universal program for Dataman programmers, version 2.57/02.2009
Date: 2.September 2009 Time: 09:15:52
Selected device: TI (TMS) TMS320F2812 [BGA179]

Buffer content from address: 00F60000h, to address: 00F6010Fh

Address +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F 0123456789ABCDEF
0000F60000 AA AA AA AA 00 3D 80 3A FF FF FF FF FF FF FF FF ªªªª.=€:ÿÿÿÿÿÿÿÿ
0000F60010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60020 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60050 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60060 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60070 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F60080 00 06 76 21 77 00 F6 8F 56 C2 19 01 00 06 FF FD ..v!w.öVÂ....ÿý
0000F60090 EC 04 FF 58 19 01 2B 84 00 06 ED FE 00 08 00 20 ì.ÿX..+„..íþ...
0000F600A0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F600B0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F600C0 00 03 FF E0 00 10 00 20 00 03 FF E0 00 00 00 00 ..ÿà... ..ÿà....
0000F600D0 00 00 00 00 B9 C0 76 22 00 68 28 29 8F 00 76 1A ....¹Àv".h().v.
0000F600E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
0000F600F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ

0000F60100 A8 A9 C3 50 80 22 76 7D D4 84 76 7D CC 3A 76 7D ¨©ÃP€"v}Ô„v}Ì:v}

In addition the address seems not to be correct!

see hereafter the begin of my hex file loaded:

:02000004003DBD
:20800000AAAAAAAA803A003DFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD9
:20801000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF70
:2080200076210006F68F7700190156C2FFFD0006FF58EC042B841901EDFE0006002000084A
:20803000FFE0000300200010FFE0000300000000000000007622B9C028290

How can I handle that? Is there any option to select bytes or words format?
Why the software does not inform me of any error?
PS: I know the hex file is correct and has been programmed successfully with another programmer.

Thank you for your support.

Yannick

[Dataman (Neil Parker)]

Hello Yannick,

We tried to load the fragment of the file you posted and it loaded correctly. We really need you to send the whole file and also the full log using the "Help > Create problem report" feature in order for us to tell more.

Can you also tell me what you did with the buffer - because it seems you did a 32 bit swap. Aditionally the addresses where the data is loaded are incorrect (not according to the file).

As I said we will be able to tell more about the situation once we have the whole file and other information. You can email the file directly to me using [email protected]

Regards,

Neil parker

[Dataman (Neil Parker)]

Yannick,

According to Texas Instruments recommendations you can only load an IntelHEX x16 file format into the device.

The fragment of file that you initially posted above was in IntelHEX x16 format, but you did a swap operation which resulted in the data being bad.

The file bootmpm_image_byte.hex which you emailed across is in standard IntelHEX x8 format.

We will shortly be implementing both x16 and x8 IntelHEX load options for this chip, our customers
can then choose the best format for their needs.

To solve your problem you will need to use the IntelHEXx16 file format or wait for the new version of the software which will be out soon.

I will keep you posted on the software.

Regards

Neil Parker

[Guest]

Thanks for this clear answer Neil.

OK I will work with word files (IntelHex x16) waiting for your next implementation of IntelHex x8 (byte files).

Thanks & Regards.

Yannick