IIRC keyboard registers are outside of vic, so they don‘t need vic-iv enabled...
Announcing the Eleven Development Environment for the MEGA65
-
- Miscellaneous!
- ubik
- Thread is Unresolved
-
IIRC keyboard registers are outside of vic, so they don‘t need vic-iv enabled...
I don't think it's how it works. It's I/O mode (called VIC I/O mode, that's true, kinda confusing), like even changes how CIAs are decoded for example CIAs has "echoes" in the memory map in VIC-II mode (thus being compatible with C64 in this regard - though I am not very sure about this one ...). And so on. As you can see MEGA65 memory map, the whole I/O area have three instances for the three I/O modes at "very high addresses though". For the "legacy" I/O area at $D000 (if it's visible) you'll see the one corresponding of your actual I/O mode. If you see iomap.txt in mega65-core repo, in theory, all registers in the $DXXX area marked as GS are only available for MEGA65 I/O mode (also called VIC-IV I/O mode), C65 marked ones are in C65 mode (also called VIC-III I/O mode). At least this is how I understood and Xemu at every places on decoding ANY I/O area access works this way. So if it is not true it would have caused already many-many problems everywhere, I think. Maybe it's called "VIC" I/O mode since the register is in VIC to "key" the mode. But even in C65 it's not clear that "VIC is only VIC", see for example that VIC-III can map ROMs ... Which wouldn't be VIC's task strictly speaking.
-
Ah. That might explain the error! Could it be that BitShifters ROM enables the vic-iv by default?
It is possible ... Snoopy also had some "binary patches" here for the official ROMs do similar things ... And so on. So if basically this is the problem, it won't work on real MEGA65 either, using "stock" C65 ROM which uses VIC-III (aka "C65") I/O mode by default in C65 mode.
And one possible trap: I am not sure, but IIRC there is also the "trick" that C65 ROM sets I/O back and forth even in IRQ routine (or just when doing disk I/O? I can't remember ...) thus even if you try to "key" vic-iv I/O mode it may have been reset to VIC-III by the ROM. The same even applies to projects written in assembly, C, whatever, if original IRQ may work in the background. Of course a "patched" ROM using VIC-IV I/O mode always instead of VIC-III would workaround this problem, but it always have its dangers that we forget to set I/O mode and then program does not work with ROMs (including "stock" ones) does not do that (as on C65 of course there was only VIC-II and VIC-III I/O modes).
-
Snoopy could you try this one and see if it fixes your problem with Xemu?
That works perfect now with xmega65 (next branch)!
-
- now enhances not only BASIC10 but also your love life, your general well-being and the weather as well
Wow! Works perfect!
-
I wanted to ask if it would be possible to expand ELEVEN to use it for developing in ASSEMBLER language on the MEGA65?
It would be nice to programme on the real machine instead of using Crossassembling.
-
That‘s a wonderful idea! The editor is working independently from the precompiler, so there would be no problem from that side.
Now we just need the assembler module.
With the MEGA65‘s 40MhZ speed it should even possible to implement the assembler part in BASIC65 (or even better, with ELEVEN itself...)
I‘d love to do it myself, but then I‘ll never finish my RPG project (which was pushed to the sidelines already because of ELEVEN...)
So, any volunteers?
