No worries! While it started as a way to help out Usagi, it just makes sense to submit the changes for everyone to benefit.
With that said, I'm running into an interesting issue - I managed to get a pinout set up for the Rev. A board, and drive is stepping, however it's not stepping as expected. For example, I can start at cyl 0 and attempt a read, but after it tries to step, it ends up near cyl 3. If I exit and specify "--step -3", I could end up on cyl 2, cyl 5, or back on cyl 3. If I do a "--step 5" instead (just for testing), I could end up anywhere from cyl 1 to cyl 12. If I immediately do another "--step 5", I could end up back on cyl 3, or cyl 10, or cyl 15. Over time, regardless of whatever step intervals I supply, the heads keep moving further and further into the disk. I ended up having to carefully shut down and put the stepper back onto the drive's main PCB in order to get the heads back to cyl 0 (they were out around 372 by that point).
My pinout to J7 is currently this (modified for Rev A):
// J7-3 EN
// J7-7 STBY
// J7-5 ERR
// J7-9 MODE3
// J7-6 MODE0 (was J7-8)
// J7-4 MODE2 (was J7-12)
// J7-14 MODE1 (was J7-15)
I looked at the Mode3 and Mode2 lines on a scope (separate), and did see pulse activity going on - I have a logic probe I can hook up as well in order to verify the actual pulse timings over multichannel, but it might be a day or two before I can get back to it. All of that being said, it's picking up data here and there - though I think I need to tweak the decoding a little bit to make it pick things up in a more stable manner. I don't have the "wait for a certain number of timing bits" logic in place as of yet, so it just goes back and forth between "find the next magic ID" (similar to the 0x4489 of MFM) and hope that it lines up with what it wants (address data vs. user data). I have been able to decode quite a few sectors of ASCII data, so I'm hopeful for things to come...
- Donut