Dbug wrote: ↑Sat Jul 30, 2022 1:27 pmImo, a reasonable way of doing that would be to use a cartridge system, like the ones used on the C64, because else you are losing quite a lot of memory, since you basically need to store the entire assembler/monitor/editor system, but also the source code of the program you are assembling.ibisum wrote: ↑Sat Jul 30, 2022 12:12 pm As a non-guru, devoted Oric lover, what I want: an onboard editor and assembler that is worth the effort to set up and learn. Cross-compiling is productive - compiling/assembling/debugging onboard, just much more fun.
I've been trying to get a MONASM.DSK built for the last few weeks in my (very few) Oric sessions, but haven't had much luck. But I continue to yearn for an Otic-onboard set of tools that would allow full assembly-based development with just the machine itself. I've thoroughly enjoyed the options on Amstrad (MAXAM, CHAMP, etc.) and would think we Oric people deserve something similar, at least ..
With a cartridge which would have both 16K of ROM as well as the few components required to access the overlay memory, you could have a system that allows developing 48K Oric software by having the entire editor/assembler/disassembler in the ROM cartridge, but also having up to 16KB of source code inside the overlay memory so no main memory wasted by the source code.
So .. I would imagine that this is something for Orix/Twilighte-Board/Sittler hackers to consider implementing (if iss&Jede&co haven't already done so) in the new memory layout.
Or is there some way to implement a "ROM cartridge mode" for Cumulus/Cumana Reborn/TxDuino/Erebus?
Lets discuss the means/methods by which we can attain a functional, decent development environment for the Oric-1/Atmos/New Oric platforms, which allows us to write assembly directly for the machine, and so on.