Page 69 of 97

Re: ST536 STE EDITION

Posted: 05 Jun 2025 10:33
by Steve
Badwolf wrote: 05 Jun 2025 10:28 Unfortunately I put together my IDE SD card after the 144 board became stable for me, so I felt no need to go to all the effort to set up HDDriver-supporting partitions. It now means it's useless for testing outside of EmuTOS.
You realise you can just install HD-Driver on that same setup, when you boot EmuTOS it'll ignore HD-Driver, when you boot Tos206 it'll use HDDriver, no need to re-partition.

Re: ST536 STE EDITION

Posted: 05 Jun 2025 11:05
by Badwolf
Steve wrote: 05 Jun 2025 10:33 You realise you can just install HD-Driver on that same setup, when you boot EmuTOS it'll ignore HD-Driver, when you boot Tos206 it'll use HDDriver, no need to re-partition.
I haven't used a partition format HDDriver understands and for half the drives I've not used a filesystem TOS understands.

HDDriver can see some of the partitions when run from floppy but can't open them. I went for usability rather than compatibility as I'd kind of put a lid on testing. Then the 288 version came along. :)

BW

Re: ST536 STE EDITION

Posted: 05 Jun 2025 13:32
by exxos
CURRENT15A firmware is up. (EDIT: But likely still issues it seems :( )

This one includes the external glitter BR fix. 8MHz clock sync fix. IDE AB fixes, the 8 MHz problem was also manifesting on top of the IDE AB code. The second problem was the patch address I think was glitching for IDE AB. So I've rebuilt that chunk of code to "hopefully" make it more robust..

I'm still running on the external blitter board.. I need to reset the integrated blitter boards later.

Re: ST536 STE EDITION

Posted: 05 Jun 2025 14:03
by exxos
This is what I'm up against, this is the IRQ signal...

IMG_3340.JPG
IMG_3343.JPG

So I need to rebuild the logic again :roll:

I also think that IDE doesn't like running with the CPU at 50mhz, even though its all timed to the CLK8 anyway.

Re: ST536 STE EDITION

Posted: 05 Jun 2025 14:53
by stephen_usher
Nice ringing...

Re: ST536 STE EDITION

Posted: 05 Jun 2025 18:03
by exxos
Finally figured out how to get the H Atari debugger to work in windows!

So loading DOTT..

looks like it crashes at 00FA0058 :shrug: anyone tell anything from this ?! All I can tell is its trying to access the cartridge port for some bizarre reason ?!

Code: Select all

CPU=$e02c42, VBL=28751, FrameCycles=183012, HBL=178, LineCycles=740, DSP=$0
00E02C42 4A38 8C83                tst.b $FFFF8C83.w
> c
Returning to emulation...
Bus error exception at 0xe02b92!

CPU=$e02b92, VBL=28751, FrameCycles=186992, HBL=182, LineCycles=624, DSP=$0
00E02B92 4A38 8E09                tst.b $FFFF8E09.w
> c
Returning to emulation...
Line-A exception at 0xfa0058!

CPU=$fa0058, VBL=28771, FrameCycles=38132, HBL=37, LineCycles=244, DSP=$0
00FA0058 A000                     illegal
> c
Returning to emulation...
Bus error exception at 0xe018ce!

CPU=$e018ce, VBL=29155, FrameCycles=258848, HBL=252, LineCycles=800, DSP=$0
00E018CE 4A39 FFF0 0039           tst.b $FFF00039
>

Code: Select all

Returning to emulation...
Line-A exception at 0xfa0058!

CPU=$fa0058, VBL=58060, FrameCycles=38104, HBL=37, LineCycles=216, DSP=$0
00FA0058 A000                     illegal
> d
(PC)
00FA0058 A000                     illegal
00FA005A 000A                     illegal
00FA005C 4E75                     rts
00FA005E 487A 0016                pea.l (pc,$0016)
00FA0062 3F3C 0009                move.w #$0009,-(a7)
00FA0066 4E41                     trap #$01
00FA0068 5C8F                     addaq.l #$06,a7
00FA006A 3F3C 0007                move.w #$0007,-(a7)
00FA006E 4E41                     trap #$01
00FA0070 548F                     addaq.l #$02,a7
00FA0072 4267                     clr.w -(a7)
00FA0074 4E41                     trap #$01
00FA0076 1B45 0D0A                move.b d5,(a5,$0D0A)
00FA007A 2020                     move.l -(a0),d0
00FA007C 2020                     move.l -(a0),d0
00FA007E 2020                     move.l -(a0),d0
00FA0080 2020                     move.l -(a0),d0
00FA0082 3D3D                     illegal
00FA0084 3D3D                     illegal
00FA0086 3D3D                     illegal
00FA0088 3D3D                     illegal
00FA008A 3D3D                     illegal
00FA008C 3D3D                     illegal
>

Re: ST536 STE EDITION

Posted: 05 Jun 2025 19:19
by exxos
This is what it does when MAPROM is loaded..

IMG_3356.JPG

The corruption is pretty much identical every run there is some moving pixels at the top of the screen and there does appear to be three sampled sounds playing but they are corrupted so cannot tell what they are saying that all.

Maybe it's because of the MMU tables not been set properly for the 030 CPU :shrug:

There's a lot of PAK patches in the mix. So will just disable those for the hell of it, see what happens.

Re: ST536 STE EDITION

Posted: 05 Jun 2025 19:27
by dml
That's kinda how it looks when you point the shifter display address at 0x00000000 :p

The changing dots at the top, near the corner is a tell.

Re: ST536 STE EDITION

Posted: 05 Jun 2025 20:00
by exxos
dml wrote: 05 Jun 2025 19:27 That's kinda how it looks when you point the shifter display address at 0x00000000 :p

The changing dots at the top, near the corner is a tell.
Yeah the pixels around the first line change a bit. Assume its why DMA sound is screwed up as well. But why that happens.. no idea :(

MAPROM must setup something to get the game running, but something is still broken somewhere.

Re: ST536 STE EDITION

Posted: 06 Jun 2025 03:26
by coonsgm
Just a quick update on the new STE I'm testing on.

Works identically to my first STE using firmware current13. Under EmuTOS everything runs perfectly. Under modified TOS 2.06 most working just great. DOTT crashes in TOS 2.06, but not EmuTOS.

I was kind of hoping for a different result, but on the positive side...the results are repeatable.