- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05148 | Misc. | Minor | Always | Feb 12, 2013, 07:57 | May 8, 2020, 02:28 |
Tester | Robbbert | View Status | Public | Platform | |
Assigned To | AJR | Resolution | Fixed | OS | |
Status [?] | Resolved | Driver | |||
Version | 0.148 | Fixed in Version | 0.222 | Build | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05148: ht68k: Hangs at start | ||||
Description | It displays one line of output then hangs | ||||
Steps To Reproduce | |||||
Additional Information | was ok at 0.146 | ||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | ht68k | ||||
Attached Files
|
ht68k_wd.patch (709 bytes) May 31, 2015, 14:06 Uploaded by Duke (ugly) patch for wd_fdc.c to get it working again [Show Content] [Hide Content]diff --git a/src/emu/machine/wd_fdc.c b/src/emu/machine/wd_fdc.c index 4e922aa..8f5c4bb 100644 --- a/src/emu/machine/wd_fdc.c +++ b/src/emu/machine/wd_fdc.c @@ -961,10 +961,18 @@ void wd_fdc_t::do_generic() { switch(sub_state) { case IDLE: - case SCAN_ID: case SECTOR_READ: break; + case SPINUP_WAIT: + case SCAN_ID: + case SEEK_WAIT_STEP_TIME_DONE: + case SEEK_WAIT_STABILIZATION_TIME_DONE: + if (command & 4) + status |= S_RNF; + command_end(); + break; + case SETTLE_WAIT: sub_state = SETTLE_DONE; break; @@ -1226,6 +1234,7 @@ void wd_fdc_t::spinup() else { sub_state = SPINUP_WAIT; counter = 0; + t_gen->adjust(attotime::from_seconds(1)); } status |= S_MON|S_SPIN; | ||||
Relationships
There are no relationship linked to this issue. |
Notes
8
No.09363
Tafoid Administrator
Feb 13, 2013, 16:00
|
WD1700 floppy emulation was added resulting the system now looking for a floppy and not jumping to monitor. The known images are all .td0 which at the moment are not support by the current emulation. The core case of it "hanging" is likely invalid - just waiting for a floppy. |
---|---|
No.10012
Osso Moderator
Nov 25, 2013, 17:29
|
According to the manual, page 2-2, "The board will first look for a disk to boot the K-OS ONE operating system. When the boot disk is not found, it will go into the MONITOR program". MESS entered the MONITOR program up to 0.146u5, but from 0.147 onwards it's broken. You can now load td0 images and in fact, if you have the boot disk, it will slowly load it and the operating system will start up. I think this should be reopened. |
No.10013
Tafoid Administrator
Nov 25, 2013, 23:54
|
You are a Dev. You are free to open such bugs up especially if you have an interest in it. |
No.10082
Robbbert Senior Tester
Dec 19, 2013, 12:43
|
Reopened because the problem was not fixed. |
No.11698
Duke Developer
May 31, 2015, 14:08
|
I've attached a patch which fixes it. I consider it too ugly though, timeouts need to be handled properly. Problem is, according to the datasheet, there isn't even a timeout and the current implementation is correct. |
No.12545
demotester Tester
Apr 22, 2016, 19:37
|
Tested on 0.172 and seems the problem is still there, it does not boot the K-OS. |
No.15295
Robbbert Senior Tester
Jul 26, 2018, 04:59
edited on: Jul 26, 2018, 10:06 |
Program hangs at @F02014, testing if the previous fdc command has completed. But it never does. If you skip this check, then the system boots the floppy and works perfectly. However the original report of not going into monitor with no floppy present still exists. |
No.17610
Osso Moderator
May 6, 2020, 04:43
|
According to the commit message, this should be fixed by: https://git.redump.net/mame/commit/?id=789761c20cef2a23b63dcdc0c96fd59b532aac54 |