| [hatari-devel] Bug with "24 bits addressing" and reset |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Bug with "24 bits addressing" and reset
- From: Vincent Rivière <vincent.riviere@xxxxxxxxxxx>
- Date: Sun, 5 May 2019 17:03:52 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:to:from:subject:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=GFExS8H3dJpzS6X+vL3/DyxsuYxqljdlq2oobyxveHQ=; b=iic5ljQ3OPmz19Aau49Rc8YUJmfGNqPHv8btnjmyxRdxXis6xedUsR2vb49pEwlFby 7L7lnsZrQv9G/d/3FznmfzNHhiADNWdDYpqEqkN4qVFgFOTo1KHe696WLj/KBHgByTGk SeHJcuPGYzEyD3S5AD5r3vWfq2/8ynjjr55b8cNGOvw/7SGVtwiHTSk4TzOID7OQ6CPJ inn+n4MnwsdYmgWKFo50MDccT6b4Mq+u56JydQni7knLxYuJVn87UKTCHs3UEJpuND0d ArLmiXFIFO0Cz3lT7jTIrPkc+3ygotNqvXzeETll7zA+2X8bMOdLruaG5uJvuuiNMQ0+ zV9w==
Hello,
I use a recent Hatari Git compiled for Cygwin.
It seems there is a bug between "24 bits addressing" and reset.
I use a custom EmuTOS which display traces about the internal IS_BUS32
value. Basically, it is detected by writing a value to address 0x0c (Address
Error vector). If that value also appears at address 0x0100000c (should be
either nothing or TT-RAM), then this is a 24-bit address bus. Also, if
reading that 32-bit address causes a Bus Error, then this is a 32-bit bus,
as it should have read back the value at 0x0c if it was 24-bit.
- I start Hatari with a 68030 configuration, with "24 bits addressing"
unchecked. It is detected as 32-bit, fine.
- F12, CPU. I check "24 bits addressing", click "Back to main menu", click
"Reset machine", click OK. It is still detected as 32-bit (because no bus
error occurred), this is wrong.
- F12. I just click "Reset machine" then OK. It is now detected as 24-bit,
this is good.
The fact that 2 reset are required to take in account that "24 bits
addressing" option is a bug in Hatari.
And of course, this is very confusing when doing tests.
--
Vincent Rivière