Difference between revisions of "MB02 DMA Port"
From SpecNext official Wiki
(core 3.1.3 changes/refresh) |
(core 3.1.3 changes/refresh) |
||
| Line 2: | Line 2: | ||
|Number=$xx0B | |Number=$xx0B | ||
|ShortDesc=Controls Z8410 DMA chip via MB02 standard. | |ShortDesc=Controls Z8410 DMA chip via MB02 standard. | ||
| + | |PortMask=---- ---- 0000 1011 | ||
|Readable=No | |Readable=No | ||
|Writable=No | |Writable=No | ||
Revision as of 08:39, 30 March 2020
| Number | $xx0B |
|---|---|
| Decimal | |
| Short desc. | Controls Z8410 DMA chip via MB02 standard. |
| Bit Mask | ---- ---- 0000 1011 |
| Readable | No |
| Writable | No |
| Subsystem | DMA |
since core 3.1.2 this port $0B is supported and always in "Zilog DMA" mode, for "zxnDMA" use Datagear DMA Port ($xx6B / 107).
Currently not supported by latest core 3.0.7
(unclear whether it was ever supported in some older 2.0 cores, or the support was just planned, but currently not working at all)
If you have DMA app expecting the port to be $0B, you have to patch it to use the new data-gear port $6B. Also keep in mind the zxnDMA is by default in zxnDMA mode, while all the regular MB-02 SW does expect Zilog-like functionality, so the Next has to be reconfigured first by bit 6 of Peripheral 2 Register ($06) before running the app.