Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEC Pro350 fails floppy on POST #970

Open
snhirsch opened this issue Mar 3, 2025 · 5 comments
Open

DEC Pro350 fails floppy on POST #970

snhirsch opened this issue Mar 3, 2025 · 5 comments

Comments

@snhirsch
Copy link

snhirsch commented Mar 3, 2025

I've been picking away at this issue for a while now. I'm coming to the belief that the Pro floppy controller is testing for the expected RX50 drive by doing something like this even when no floppy is inserted:

  • Select drive, home head and step inwards to track N (0 <= N < 80)
  • Step out N tracks.
  • If Trk0 is true at that point it assumes an operational RX50, otherwise fail the floppy subsystem.

How does FF behave when the host selects and steps in the absence of an inserted diskette? I can hear the RX50 whirring in and out during POST and I think this needs to be happening with FF as well. If that's not the current behavior, can it be modified to do so when 'host = dec' is set?

This behavior may be particular to the Pro3xx controller firmware as no such problems appear on, e.g. an RQDX3 controller (PDP-11).

@keirf
Copy link
Owner

keirf commented Mar 3, 2025

FlashFloppy obeys step commands and asserts Trk0 as appropriate even when no image is mounted.

@snhirsch
Copy link
Author

snhirsch commented Mar 3, 2025

Hmm. Then I'm back to square one. The only workaround for now is to always have a non-system diskette inserted in the first FF drive. A real RX50 does not require that a diskette be present. I've managed to dump the controller firmware from the masked 8051 and this just provides a bit more impetus to disassemble it.

Just curious: Am I the only person to report such an issue?

@timradde
Copy link

Yes, my 350 does this too. Normally I have a usb stick in so never see this. It seems to boot fine with a stick in at least until I updated from 3.39 to 3.43 flash floppy. I have two images on my stick. Neither boot of course, but neither seemed to prevent the 350 from coming up. Now one image fails and the other succeeds in starting. Neither image can be recognized with something on them. I have the RT-11 OS on mine. A DIR just returns an error on both. Yet, one of these is an image I can boot on my Rainbow so was sure it would work here.

@snhirsch
Copy link
Author

Interesting data point. I only ever tried non-bootable P/OS images.

@timradde
Copy link

timradde commented Mar 21, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants