Hi,
We are using a MC56F8014 on a product. The device comes from Freescale pre programmed with a serial port bootloader (v1.3).
According to the serial port bootloader user guide:
http://www.freescale.com/files/dsp/doc/user_guide/56F801xBLUG.pdf
"Bootloader versions 1.3 and lower are unable to fully process data in S3 records if the S-record data field contains an odd number of bytes. These versions of software assumed that all S3 records would contain an even number of actual data bytes. This assumption was based on the fact the 56800/E is a 16-bit architecture with 16-bit program opcodes.
A PERL script is available to modify S-record files containing odd S3 data. After using the script to convert an S-record file, it should be safe to use on all versions of the Bootloader software. Instructions for use are embedded within the script itself, and can be referenced by executing the script with an “-h” or “-help” option in the command line. Please reference the Freescale FAQ website, http://faqts.freescale.net, to obtain this script; see FAQ #25759 "
I cannot find the above FAQ or perl script and hoped someone could provide it for me?
Thanks for the help
Chris
Solved! Go to Solution.
Below it the contents in FAQ #25759
Abstract | |
| Why does the 56F801x serial bootloader progress halt indefinitely during S-record download ? |
Problem | |
| A fatal error occurs when the 56F801x serial bootloader encounters S3 records containing an odd number of data field bytes. When an S3 record containing an odd number of data bytes is processed, the bootloader uses the S-record checksum field as the most significant byte of the last word of data to program. This problem exists because the bootloader was developed under the assumption that all S3 records would contain an even number of data field bytes. This assumption is based on the fact that data in S3 records is used to re-program Program Flash, which is not byte accessible on 56800/E-based devices |
Solution | |
| (Solution 1) |
Below it the contents in FAQ #25759
Abstract | |
| Why does the 56F801x serial bootloader progress halt indefinitely during S-record download ? |
Problem | |
| A fatal error occurs when the 56F801x serial bootloader encounters S3 records containing an odd number of data field bytes. When an S3 record containing an odd number of data bytes is processed, the bootloader uses the S-record checksum field as the most significant byte of the last word of data to program. This problem exists because the bootloader was developed under the assumption that all S3 records would contain an even number of data field bytes. This assumption is based on the fact that data in S3 records is used to re-program Program Flash, which is not byte accessible on 56800/E-based devices |
Solution | |
| (Solution 1) |