Re: [Linux-gpib-general] agilent_82357a reverse engineering

[Penkler, D. <dav...@hp...>]

Richard,
No documentation AFAIK. You could ask the Beiming folks.
Also check out usbmon here: http://people.redhat.com/zaitcev/linux/
It will give you detailed log trace of what is going over the USB interface - no need for printk's.
/d

From: Richard Klingler [mailto:ric...@gm...]
Sent: Sunday, August 10, 2014 5:54 PM
To: lin...@li...
Subject: [Linux-gpib-general] agilent_82357a reverse engineering

Hello

I successfully running the F82357 GPIB USB adapter from Beiming on a Intel NUC running Ubuntu 14.04....

A second S82357 adapter I would like to run on my OSX machines....but since Agilent dropped 64bit driver development. I started now digging into the linux-gpib 82357 driver code...

Is there some sort of documentation between the interacts of the gpib library calls and the 82357 kernel driver?

Placed now loads of printk statements everywhere to see what it actually sends over the USB bus...


For example a simple "*IDN?" results in following hex bytes sent down the bus:


04:01:03:0C
01:00:00:1E:03:00:00:00:40:3F:25
04:01:03:0B
01:00:00:0B:05:00:00:00:2A:49:44:4E:3F (actual *IDN? query)
04:01:03:0C
01:00:00:1E:03:00:00:00:3F:20:45
04:01:03:0B


The ones starting with 04 set internal registers, apparently borrowed from TMS9914...
wouldn't expect an old chip being emulated on a 82357 (o;

The second line apparently sets the GPIB address to talk to....
But what does the second to last lines do?


cheers
richard