• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 1698 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Flash programming: problem with hex2000 or with converting hex2000 output to binary

Greg Oakes
Intellectual 590 points

Well, we have the download messaging for custom serial programming while application is running its normal activities. (Same Sci interface I use to communicate to another processor and to a GUI that emulates that other processor.)

No attempts yet to program flash with the downled data. I just tested the messaging using the *.out file, with a file checksum appended to the end.

Now I am trying to produce a *.bin file. I have taken the COFF2BIN batch file ubiquitously promulgated for the F281x and modified the corresponding cmd file ROMS directive for the flash range and length on the f28335.

The hex2000 process seems to have been error free. And the map file looks good.

But ... the hex file is 646643 words (16 bit words) long ... this for a *.out file that the Spectrum emulator successfully uses in flash programming downloads. The map files shows use of 262143 words. So my hex file is 2.5 times the size of the out file.

And that's not the worst of it. Sending this hex file to the FileIOShell crashes, with the message shown below:

The resulting bin file is identical to the first ~half of the hex file, and the size of the bin file is about half that of the hex file.

Should the contents of the hex and bin files be identical, at least for the first half of the hex file (which comprises the entirety of the bin file) ?

What does the failure message indicate ?

I assume that even though I got a bin file, it's not correct since it is identical to the first half of the hex file.

Is there a f28335 specific FileIOShell that should be used ?

  • 0
    Intellectual 590 points

    Solution - for my needs, which involve starting with the .out file in COFF format and then obtaining a binary file for serial programming flash, on an F28335 - omits the generation of the intermediate hex file, and thus omits the use of FileIOShell.  (FileIOShell works for smaller .out files, as used on F281 processors, but not for the larger files accomodated on the F28335.)  Just change the equivalent of the AppCode_hex_2810.cmd file to specify a hex2000 conversion output file of type *.bin, eliminate the memwidth option (allowing default to 8 bits), change the motorola S-record format option to the binary option (-b), and in the ROMS directive specify the origin and length in terms of 8 bit bytes rather then 16 bit words, and eliminate the romwidth option.