Re: [hatari-devel] No address error when accessing odd addresses?

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On keskiviikko 11 syyskuu 2013, Uwe Seimet wrote:
> > For now, I think we can consider it completely broken for ST emulation,
> > it cannot even boot some (most?) TOS versions.  And even for Falcon,

I remember having lots of problems with WinUAE, ST & earlier
TOS versions or EmuTOS, but now that I did fairly extensive
tos_tester run, actually everything except this passed:

=============================
Test report:
------------
...

+ tos104de:
- tos104de-st-mono-floppy-0M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-mono-gemdos-0M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-mono-floppy-4M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-mono-gemdos-4M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-rgb-floppy-0M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-rgb-gemdos-0M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-rgb-floppy-4M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-rgb-gemdos-4M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-vdi1-floppy-0M: ['pass', 'FAIL', 'FAIL', 'FAIL']
- tos104de-st-vdi1-gemdos-0M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-vdi1-floppy-4M: ['pass', 'pass', 'pass', 'pass']
- tos104de-st-vdi1-gemdos-4M: ['pass', 'pass', 'pass', 'pass']

....
Summary of FAIL/pass values:
- Hatari init: all 82 passed
- Test program running: 81/82 passed
- Test program test-cases: 81/82 passed
- Test program output: 81/82 passed
=============================


The failing case is this:
hatari --tos tos104de.img --machine st -s 0 --vdi-planes 1 \
  --vdi-width 800 --vdi-height 600 blank-a.st

Can somebody reproduce that?

Boot failure does NOT happen:
- with old UAE CPU core
- with any other TOS version or US (pal) version of TOS v1.04
- with more memory
- with no disk
- with GEMDOS HD emulation (with just that, or with floppy)
- with smaller VDI resolution taking less memory or
  higher bitdepth resolution taking more memory
  (800x600@1ppp = 60k, 640x400@2ppp = 64k, ppp=planes per pixel)

This is what happens:
------------------------
Exception 2 (fc0ee0) at fc0ee4 -> fc0ee6!
A-Trap a000 at 8fa023e (0x95f49fe)
Exception 2 (fc93ce) at fc93d0 -> 2fc0b0a!
M68000 Bus Error writing at address $ffffea.
M68000 Bus Error writing at address $ffffec.
M68000 Bus Error writing at address $ffffe8.
M68000 Bus Error writing at address $ffffe4.
M68000 Bus Error writing at address $ffffe6.
M68000 Bus Error writing at address $ffffe2.
M68000 Bus Error writing at address $ffffe0.
M68000 Bus Error writing at address $ffffdc.
M68000 Bus Error writing at address $ffffde.
Exception 2 (2fc0b0a) at 2fc0b0e -> 2fc0b0a!
....
------------------------


> I had no problems so far with TOS 2.06, 3.06 and 4.04.
> 
> > Only TOS version that works on ST and supports IDE is EmuTOS...
> 
> I'm not sure if I understand you correctly. Any TOS version for STs
> works with IDE as long as you don't want to boot from IDE. And with TOS
> 2.06 STs can even boot from IDE. That's why ST hardware extensions that
> provide an IDE port usually also offer a TOS 2.06 option.

Ok, I didn't know TOS v2 had IDE boot support.

EmuTOS 512k version has builtin support for IDE, DOS partition table,
and whole drive having just one FAT partition, you don't need any drivers.
Because of that, it's convenient for IDE testing. :-)


	- Eero