??? 03/09/07 14:03 Read: times |
#134641 - as it doesn't hurt.... Responding to: ???'s previous message |
:020000040000FA :0300000002F446C1 :03918E0002F300E9 :20E00000117D1160114CB41A028027B43AF67900113CF5F0601C05F0113CF583113CF582A4 :20E02000113C113CF0A315F0E5F070F6E960D502E09390E13A1173119B02918E114C115422 :20E04000C4F8114C115448FA29F9EA223098FDC298E59922C2E7B43A0040022409540F2288 :20E0600090E0D3117390E0FC1173223099FDC299F59922E4936005116BA380F72275985401 :20E08000758 ... This is the start of the combined output. I haven't processed that one with packihx yet (which I would normally do) Indeed the very first line has 04 instead of 00 there, however I haven't tried to directly flash that one, only postprocessed ones. I can check if it makes a differences though. Btw. The meaning of the first record ain't clear to me.Address 0x0000 (reset vector) but the contents don'tlook like opcodes. The 2nd line seems to a ljmp at 0x0000 into the Tasking code. |
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 |