??? 03/09/07 14:26 Read: times |
#134642 - OK so that's your problem! Responding to: ???'s previous message |
Kick it out.
And kick out any other which has nonzero "4th byte"; except the last line (:00000001FF). You have at least one more there. I won't tell you where as a punishment for you did not follow our instructions to the last letter :-) (but it's not so hard to find out). I would be surprised if it would not load after that. I also don't believe you really tried to merge those files "manually" by copy as Robert told above. Or you did something else than he told. What do you mean by "postprocessing"??? --- That 4th "byte" is something like "meaning of this line" (1st is data field length, 2nd and 3rd is address, last is checksum and the rest is data) (oficially, the 4rd "byte" is called record type, line is called record). "Meaning" of 00 is "pure data", 01 is "end of file" and anything above is good only for processors/files with; and is often abused for various other things than specified by Intel: that's why programmer softwares don't like them. JW PS. The simple test cases: file1: :02E000001234D8 :00000001FF file2: :02F000004321AA :00000001FF Go try to merge them and load them. |
Topic | Author | Date |
Joining HEX files | 01/01/70 00:00 | |
Use a text editor | 01/01/70 00:00 | |
That didn't help! | 01/01/70 00:00 | |
Details ? | 01/01/70 00:00 | |
Srecord | 01/01/70 00:00 | |
XRAM? relocated? How? | 01/01/70 00:00 | |
Ah yes. | 01/01/70 00:00 | |
HEX records | 01/01/70 00:00 | |
sorry my fault | 01/01/70 00:00 | |
waitaminute... | 01/01/70 00:00 | |
yes | 01/01/70 00:00 | |
XRAM | 01/01/70 00:00 | |
Would you please look ONCE AGAIN?! | 01/01/70 00:00 | |
as it doesn't hurt.... | 01/01/70 00:00 | |
OK so that's your problem! | 01/01/70 00:00 | |
retry srec_cat with option "--address-length 2" | 01/01/70 00:00 | |
The first line was it | 01/01/70 00:00 | |
Hex file specs | 01/01/70 00:00 | |
Intel spec | 01/01/70 00:00 | |
or preferably this one![]() | 01/01/70 00:00 |