Re: [hatari-devel] Re: [Emutos-devel] Hatari reset loop during EmuTOS automated testing

[Nicolas Pomarède <npomarede@xxxxxxxxxxxx>]

Le 09/04/2021 à 19:42, Christian Zietz a écrit :

> 3. Why the initial detection is wrong and why this particular commit
> broke it. I cannot explain that. Note that the monitor type is detected
> by reading the state of one of the MFP's pins via the GPIP register. But
> tracing 'mfp_read' shows that the wrong monitor detection during EmuTOS
> boot does not even hit the MFP code in Hatari 2.1.0. I can only assume
> that a cached value is used in error.

Hi

as a lot of rewrite was made after hatari 2.1 to add much better 
bus/address errors for 68030 MMU, I'm nearly certain that at one point 
IO registers were cached by mistake and that I resolved this by adding 
the flag CE_MEMBANK_NOT_CACHABLE to the IO memory bank.

Nicolas