exxos's Atari, Amiga & retro forum

Great work! Out of interest, I am assuming that error happens on the earlier accelerators too? I am sure I've seen that error when trying to format floppies with the 16Mhz v1 board.

GadgetUK164 wrote: ↑Fri Jan 04, 2019 2:29 pm Great work! Out of interest, I am assuming that error happens on the earlier accelerators too? I am sure I've seen that error when trying to format floppies with the 16Mhz v1 board.

Shouldn't happen on earlier versions because they switch back to 8MHz on any bus activity. These new SEC boosters don't, they run at 50MHz all the time, so a bit more complicated to get going than the earlier gen boosters.

Just installed the v2.3 booster and TOS board and I'm having same disk problems. Reading data seems to have the same problem. Same from a gotek drive. I have a IDE controller board and Marpet with 4Mb also installed. Reading from flash/IDE seems fine.

Started adding in the ROM decoding code..

First run..


Vs the 16MHz V2.X booster...


Need to figure out why TOS206 isn't working next

Tighter control of ROM access.. pretty much maxed out now...



With the blitter enabled...


It runs super sweet

EDIT:

Putting the blitter back in is causing that floppy error thing again.. So I have another issue to investigate..

Right so this is annoying.. It wasn't the blitter it seems which made the format go wonky, but my new ROM code I still not figured out why TOS206 isn't working yet.. but obviously bypassing GLUE's ROM decoding for "fast decoding" has brought back the floppy error again

I also found a small "bug" that if blitter access ROM, the logic can't issue ST_DTACK, but will fix that next version anyway.

After faffing about all day with this, It all seems to work fine other than that initial error when formatting a floppy. The diagnostic cart and FCOPYIII work fine.. So I can only assume it's some "bug" in TOS itself.. I have asked EMUTOS guys if they have any clues about it...

I've not been able to figure out TOS206 not working either yet. Its the same code as my V2.X boosters and same ROM board...

Oddly GLUE doesn't like being isolated during ROM access. The V2.X boosters isolated GLUE, but those were switching to 8MHz a lot of the time, so likely why I only just started seeing more problems.

GLUE isolation seems to be work now.. I think I must have had a typo somewhere in my code as I reverted back to a previous versions and made the changes again

So the PLD is totally in control of ROM decoding and DTACK.. just 206 isn't working at all... I know the ROM itself is good as works on V2.3 booster.. the code in the PLD is the same as the V2.3 booster...

I could only think there is a bad addressline on the PCB preventing 206 from booting, but metered the addressbus out to the PLD and CPU and seems OK...

exxos wrote: ↑Fri Jan 04, 2019 11:14 am I never thought about it with the floppy acting up... Can you format a floppy OK on it now then or does that act up still?

I've had everything working nicely but currently (since trying to get the HDMI board in) the machine is in non-working condition Will get back to it at some point. I need to work less.

I'm even more confused now...

TOS102 & TOS104 ROM board works fine with no booster, so that board is good.

I put the booster in, TOS104 boots, TOS102 doesn't,

Similar with TOS206, that should be working, but isn't, its why I thought to test my ROM boards and put in TOS102 & TOS104 as should be same address space, but doesn't boot...

I don't get it

EDIT:

I put the diagnostic cart it, its says "I7 BUS ERROR NOT DETECTED" ?!