Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|08511||Core||Major||Always||Nov 10, 2022, 01:09||Mar 30, 2023, 17:27|
|Tester||pnp2084||View Status||Public||Platform||MAME (Official Binary)|
|Assigned To||tlindner||Resolution||Fixed||OS||Windows 10/11 (64-bit)|
|Version||0.249||Fixed in Version||0.254||Build||64-bit|
|Fixed in Git Commit||6ea69b0||Github Pull Request #||#11041|
|Summary||08511: trs80l2: SuperUtility 3 boot fails because of false sync|
The attached su3v30-perl.mfi (from the su3v30.dsk DMK file) fails to boot on the TRS-80 Model I.
The problem is the RADDR commands see false FM 0xFE sync bytes in the MFM data of Track 1.
As a result, the code retries the RADDR a few times until it fails.
The following breakpoints can be used to see the RADDR results.
bp 452d - $c0 RADDR
The groups of 6 bytes at 0x4a00 are:
"FE FE FF F2 B1 F5" - false
|Steps To Reproduce||
The follow command will display "DIsk Error _"
mame trs80l2 -flop1 su3v30-perl.mfi
|Additional Information||Possibly the WD17xx state machine should enforce some "sync zero" bits before detecting the FM IDAM.|
|Affected Sets / Systems||trs80l2|
su3v30.zip (293,565 bytes) Nov 10, 2022, 01:09 Uploaded by pnp2084
SuperUtility 3.0 for TRS-80 Model I
|There are no relationship linked to this issue.|
Feb 28, 2023, 22:03
|Ok, I now know how the wd fdcs detect FM special marks, and the current code is incorrect. I'll try to work on a fix.|