DigicoolThings Forum

I played with getting a combined version of the ASSIST09 monitor that Jeff Tranter originally sandwiched together for his 6809 SBD but have adapted it for the MECB version of the 6809 (assuming a 16 KB ROM and I/O at $C000). The code provides an updated version of ASSIST09 with a disassembler command (via the "U start_addr" command). It also includes Microsoft Extended BASIC which can be started with "G C100". I'm still messing with GitHub but I think I now have it on there:

https://github.com/epaell/MECB/tree/mai ... 9/ASSIST09

It's still a work in progress. One thing I'm not too happy with is that the resulting binary is a bit tricky to get mapped into the ROM space because of the way the memory definitions are done in the original source code - so something to be a bit careful with. I'd also prefer to have all of the memory definitions closer to the top so that changes aren't needed all over the rather large source file. I can see why it was originally done the way it was done (to keep the separate functions, well, separate) but it is a bit tedious when memory and rom locations need to be adjusted. Although, I think the current setting is probably the most optimal and provides the most available memory while almost completely filling the available ROM space.

Anyway, I find it useful having all this in the one ROM.

epaell wrote: ↑Tue Jul 02, 2024 11:48 pm I played with getting a combined version of the ASSIST09 monitor that Jeff Tranter originally sandwiched together for his 6809 SBD but have adapted it for the MECB version of the 6809 (assuming a 16 KB ROM and I/O at $C000). The code provides an updated version of ASSIST09 with a disassembler command (via the "U start_addr" command). It also includes Microsoft Extended BASIC which can be started with "G C100". I'm still messing with GitHub but I think I now have it on there:

https://github.com/epaell/MECB/tree/mai ... 9/ASSIST09

You, my friend, are a Legend!

epaell wrote: ↑Tue Jul 02, 2024 11:48 pm It's still a work in progress. One thing I'm not too happy with is that the resulting binary is a bit tricky to get mapped into the ROM space because of the way the memory definitions are done in the original source code - so something to be a bit careful with. I'd also prefer to have all of the memory definitions closer to the top so that changes aren't needed all over the rather large source file. I can see why it was originally done the way it was done (to keep the separate functions, well, separate) but it is a bit tedious when memory and rom locations need to be adjusted. Although, I think the current setting is probably the most optimal and provides the most available memory while almost completely filling the available ROM space.

Anyway, I find it useful having all this in the one ROM.

Love your work! I'll be trying this out in the short term, Cheers for that!

I'll be trying this out in the short term

Nice, in case it helps, I've added some more information in the README under ASSIST09; included the Python script that I used to convert the assembled binary to the more easily programmable binary, and the programmable binary itself (to save you any messing about with picking bits of the original binary and shifting it to the right place in ROM). Ideally, I should actual modify the assembler code to improve this but it probably requires some careful rearranging of things.