Greaseweazle fw1.4 Failed to Find Track 0

[digitalight]

Greaseweazle fw1.4 Failed to Find Track 0

[Yserra]

@digitalight
I just tested Amiberry V5.6.1 on my Raspberry pi 4/ Retropie with the latest Greaseweazle 1.4 firmware, and I can say it works as expected: Amiberry boots disks on my real floppy drive.

By the way, the error "Failed to find track 0" happens often when you tell the wrong unit number. If your drive is, for instance, a DD drive coming from an Amiga or an Atari ST, then it's jumper-set by default as unit DS0, which is not compatible with the DrawBridge driver. You should change the ID of your drive to DS1 to be compatible.

[digitalight]

@Yserra
The drive is a PC drive so no jumper on the drive itself. It is using a straight floppy cable so I make sure to tick Connected as Drive B.
It works fine under Windows and WinUAE but not under Amiberry so I believe this is software related no hardware.

[digitalight]

I have managed to source a floppy cable with twist and installed that so I don't need to select connected as drive B. It now works.
I don't believe the other cable is faulty as it was working fine under windows so I suppect the code that changes the Drive B isn't working as intended.

[chrisblown]

Confirming that I appear to have the same problem. Same setup Pi and Amiberry version 5.6.1 (2023-06-13). Appears to be an issue with the straight cable and the Drive B option not working. I directly installed gw v1.14 (firmware 1.4) and I can read disks properly using the --drive=b switch. e.g gw read test.adf --drive=b or gw read test.adf --drive=1

[chrisblown]

UPDATE: I'm not sure what I did, however I have just now managed to get this working with the straight cable. I've posted the working config file below. For me the drive doesn't seem come to life the first time (?) and I've had the machine hang once or twice - but if I load a configuration the second time that seems to do the trick and I hear the drive buzz the second I load the config. I'll do some more testing.

amiberry.drawbridge_driver=1
amiberry.drawbridge_connected_drive_b=true
..
floppy0type=8
floppy0subtype=1
floppy0subtypeid=2:Compatible

I am using a straight cable with a HD PC drive

[midwan]

@chrisblown
Did you edit the config manually, or was this saved from Amiberry correctly?
Trying to understand if it's an issue with how the config is saved, or something in the DrawBridge implementation itself that doesn't work right (at least not right away), when Drive B is selected.

[chrisblown]

The config is straight from Amiberry. I was using it the other day and when it first initialises the GW, it kinda hangs the machine for a moment (RPi3), maybe 2-3 seconds. I think previously I wasn't waiting long enough, thought it had crashed due to no mouse movement and impatiently powered it off/on. :\

If I just wait, the drive comes to life and the machine becomes responsive again. (I need to test this some more)

Let me know if there is anything you'd like me to specifically test.

[midwan]

@chrisblown
So, do I understand this correctly, that it's not really an issue in Amiberry, if it works after a small delay?