I dont't see where 4 cycles are added for word-size ROM access... is that somewhere?

M68008 wrote:Taking another look and noticed that the fx68k CPU is using clk_sys as the clock... isn't that the 84 MHz clock?

Never mind, I guess the actual CPU clock must be enPhi1 and enPhi2 instead.

Taking another look and noticed that the fx68k CPU is using clk_sys as the clock... isn't that the 84 MHz clock?

I'll email you the dumps now Daniele. All the cartridges have a few bad sectors. One sector in the first one is also completely missing from the dump... the sector header must be corrupted. Unfortunately, the partial reads of the bad sectors don't look empty, in the sense that they contain varied d...

Yeah - Since SBASIC came of age, I have developed a habit of passing tons of parameters as well as gratuitous use of LOCals just because I can :-) I run on JS and haven't noticed LOCAL bugs, but the same code wouldn't work on some earlier ROMs like AH. Not important for emulator users, though, they...

martyn_hill wrote:As per Chr$ - would you willing to share your adaptations?

Yes, I'll post it here. I've actually just noticed another issue: The SuperBASIC version produces files that are too long. I think it's a SBASIC/SuperBASIC difference in handling LOCAL variables.

vanpeebles wrote:qemulator crashed!

The emulated QL or the Q-emuLator application? In the latter case, maybe you can PM me more details, especially if it can be reproduced?

About the randomness, perhaps RANDOM's implementation is based on a timer?

Not sure about the p-system file format, but if you want to send me the dumps, I can at least take a look at the mdump sectors, perhaps it's possible to see if partially-read damaged sectors look empty or not. With mdump, you can also alternate the src drive to maximize the probability of success. (...

b) I have the raw HEX code of the firmware as compiled with the older tool-chain which you can directly flash to the Teensy. Thank you Martyn, the adapter started working well after I uploaded this version of the firmware! There was a change in the Teensyduino library which might be the cause of th...

Pr0f wrote:I'd be interested in the 3d print files for it - but not for that money.

The files are on Thingiverse.