| [hatari-devel] Problem with ACSI/DMA: Command is not executed |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Problem with ACSI/DMA: Command is not executed
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Fri, 11 Oct 2013 15:30:03 +0200
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1381498203; l=825; s=domk; d=seimet.de; h=Content-Type:MIME-Version:Subject:To:From:Date:X-RZG-CLASS-ID: X-RZG-AUTH; bh=fL0Dnx+mdvNeJ6CracLBmwY968Y=; b=bb9dJnk7K84aQZYBCYoWqbsFGeX8Vc9OiKJmxdmudvkaSb+sC21VzTs6xPpMZ8riBR1 Fui3gOhvvHXhgLaVaQn1R70ZYEj1Aor5zHvgxlH9rZgpdBJBosO7si0Ss48gUyJYZ7T+n M0LCQPgvkMAben5jlkv4H+N+TXv9oVfYVQI=
Hi all,
I'm wondering whether the TEST UNIT READY command is working properly.
When I use it several times Hatari crashes with a segmentation fault. I
turned the ACSI debug output on and noticed that Hatari does not report
that this command was received by the emulation at all. My guess is that
this has to do with the fact that no (DMA) data are transferred with
this command, i. e. setting up the DMA start address is not required.
Does Hatari rely on the DMA start address to be always set (even when
there is no DMA) before an ACSI command is executed by the emulation? The
transfer should start as soon as the last command byte was written, even
when no DMA address is set, but this does not seem to be the case. Maybe
somebody else can provide details on how Hatari handles this?
Take care
Uwe