Hi,
(I cross-posted both to Hatari and EmuTOS lists, remove the other one
depending on which one your answer concerns.)
With the Git Hatari version, EmuTOS freezes early in the boot (before
boot info screen), when >030 CPU with MMU is enabled:
--machine tt/falcon --cpulevel 4/6 --mmu on
When it's frozen, Hatari "--log-level debug" output shows constant flow
of these:
------------------------------------
DEBUG: SCC: get status for CTS 1
DEBUG: SCC: get status for DCD 1
DEBUG: SCC: get status for CTS 0
DEBUG: SCC: get status for DCD 0
------------------------------------
And EmuTOS CPU symbol tracing shows only VBL interrupt running after the
freeze:
------------------------------------
...
_jdisint
_rsconf1
_setup_timer
_dsp_init
_memcpy
_dsp_flushsubroutines
_bzero_nobuiltin
_dsp_execboot
_int_vbl
8 repeats of: _int_vbl
16 repeats of: _int_vbl
...
------------------------------------
There's no freeze with June version of Hatari Git, so it could be
something related to SCC support added after that, and SCC handling
either in Hatari or EmuTOS.
This happens both with EmuTOS 1.2.1 and git version, so it's not a
regression on EmuTOS side, only potential latent bug in it.