I've tried to post-process the "binary ascii" file into something the decoder should handle, but it doesn't make much sense.I've set my HP to capture all those signals in that order, then edited the capture to take out all extraneous spaces and end up with this:
Let me clarify that a bit...
The control bits make perfect sense, but the data bits look like they might be permuted somehow (and not simply reversed).
Do you think you could confirm they are connected as intended.
A couple of further thoughts...
To make sense of a capture from a suspect/possibly broken machine, it helps enormously if the capture starts from the "held in reset" state. So use reset as a trigger, but making sure the capture includes the 0->1 edge of reset.
It would also be less error prone if you can produce a raw binary file, which is what the decoder consumes. That file would ideally contain pairs alternating data and control bytes:
Code:
<D7 D6 D5 D4 D3 D2 D1 D0><0 RST WAIT IORQ MREQ WR RD M1>
Dave
Statistics: Posted by hoglet — Thu May 22, 2025 11:55 pm