On 08/16/2012 02:11 PM, Lisandro Damián Nicanor Pérez Meyer wrote: >> By the way, after I run your test, the device also stops working with >> the "usbtmc" kernel driver. This happens when I try to read and write >> /dev/usbtmc3: > > By modprobing usbtmc after running the test?
Yes, after your test finished I ran "modprobe usbtmc" to insert the kernel module I removed earlier. Then "echo '*IDN?' > /dev/usbtmc3" and "cat /dev/usbtms3" caused the following messages to be added to "dmesg" log: >> [ 1967.869816] usbtmc 1-2:1.0: usb_bulk_msg returned -110 >> [ 1997.751512] usbtmc 1-2:1.0: Unable to send data, error -110 After power-cycling the instrument, these last two commands correctly printed out instrument identification. Regards Tomaž ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
