Re: Fwd: Fwd: Agilent 82350b can't recover from read timeout?

On Wed, Jul 31, 2019 at 5:47 PM Dirk Niggemann <[email protected]> wrote:
>
>
> H Frank,
>
> I checked the value returned from the DIR register and it's almost always 0xa so the last byte sent on the previously successful read. Or 0 if we never read anything.
>
> I am already testing with the _unaccel driver because i wanted to make sure this wasn't a side effect of using the FIFOs- sorry, I should have mentioned that.

You said the board goes into the bad state after sending an invalid
command to the device.  The controller doesn't care if the command was
valid or not, so what is the device doing that puts the controller
into a bad state?  Does it request service when it receives a bad
command?  You could check the state of the SRQ and other bus lines
using iblines.