Version of Intel Hex files

[spoogle]

I generated an intel hex file using the as09 assembler, but could not read it correctly using the l command in sim6809. The parser seems
to expect a one byte checksum character after the initial : on each line of the hex file, but that's not what as09 produces.

I modified the hex file parser in motorola.c to parse the format documented in https://en.wikipedia.org/wiki/Intel_HEX#Record_structure and now it works. I'm happy to make a pull request.

[mjwurtz]

Hi Julian, I use also a09 and sim6809. If I remember correctly, I tried also to submit patches, but never received any reply... Since I was unable to make directly a fork of sim6809, I cloned it, like some other people it seems ;-) : https://github.com/mjwurtz/sim6809 I would gladly incorporate your changes in it. My modifications to sim6809 are a try to implement various peripheral devices : 6840, 6850, 6820, 6522, 6532, WD2123, floppy controllers and a config file to map everything in memory. Actually, I can emulate different kind of hardware using a serial line for I/O : mainly the microbox ][ and a french kit. It work reasonably well, as I can boot flex from a disk image and run some programs. My ultimate goal is to upgrade it in order to also emulate a 6309, including specific instructions and registers... bye Le sam. 25 juin 2022 à 11:25, Julian Richardson ***@***.***> a écrit :

…

I generated an intel hex file using the as09 assembler, but could not read it correctly using the l command in sim6809. The parser seems to expect a one byte checksum character after the initial : on each line of the hex file, but that's not what as09 produces. I modified the hex file parser in motorola.c to parse the format documented in https://en.wikipedia.org/wiki/Intel_HEX#Record_structure and now it works. I'm happy to make a pull request. — Reply to this email directly, view it on GitHub <#2>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB6ALOJZR2J7TCTSB6XPLTVQ3F7NANCNFSM5ZZ7XPAQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Michel Wurtz