| Re: [hatari-devel] No address error when accessing odd addresses? |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] No address error when accessing odd addresses?
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Wed, 11 Sep 2013 21:18:16 +0200
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1378927096; l=723; s=domk; d=seimet.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=uuRpfHdgrd6N6UMtCQGj32uw3f0=; b=mCMLmPdPiogB3TaYte/x5eGRFPRKhSOm8ZAlEU66sxp42NY+KBGhMaANwjRmdN0OYof vr1vaIWkRqgV8N1Wj9Uyz4w8XP5IW/+Ofhx7ccAW9XvuMQGsTbilWIP9qWuBTbxM/BSB8 3CRvIe1DCbpPq0YPZFCvu2MU3TBo8gRSb8U=
Hi,
> Ok, looks like the CPU core correctly switched the instruction tables.
> That means, it should theoretically work.
> Could you maybe do the following tests:
>
> - Start immediately in 68000 mode with "--compatible 1", without using
> TT mode first
I started with --config-file and my ST-compatible configuration file,
there was still no address error.
>
> - Try the old UAE CPU core with "--compatible 1"
I did the same with the UAE core and after enabling "Slower but more
compatible CPU" there was the expected address error, indeed.
So it looks as if the old core works with the right settings, but the
new core does not detect address errors regardless of any settings.
Take care
Uwe