|Re: [hatari-devel] TT version of 4getful by gwEm crashes with newer Hatari versions|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
Le 13/02/2016 13:56, Eero Tamminen a écrit :
On 02/09/2016 01:08 AM, Nicolas Pomarède wrote:
Le 08/02/2016 23:52, Eero Tamminen a écrit :
It's only v1.9 and current Hatari WinUAE version with which
4getful TT-version bombs. It starts fine with WinAUE version
from start of last summer, or current OldAUE Hatari version.
It works with WinUAE core too, if I disable *both* cycle-exact
and prefetch mode.
didn't have time yet to look at this, but it's on my never-ending todo
list for Hatari :)
PS. Starting TOS v3 with 4 MB bombs regardless of CPU core version.
If I enable some TT-RAM in addition of 4MB ST-RAM, it boots fine.
this is what I get with TT / TOS 3 :
- if 24 bit addressing is checked, the prefetch and CE mode will give
2 bombs at boot, with or without MMU
- if 24 bit adressing is not checked, the prefetch and CE mode will
work if MMU is not used. If MMU is used prefetch mode will still work,
but CE mode will give the infinite loop you saw.
In TT mode, 24 bit addressing should not be used ; the TT had a 32 bit
68030, so limiting it to 24 bit can have unexpected effects (we can try
to make it work in 24 bit mode with a few hacks (mirroring IO registers
to their 32 bit equivalent) but that would not be a real HW case).
In the end, the non working mode is 32 bit adressing + CE + MMU, I will
have a look at this, some IO regs might be wrongly mapped.