From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: usbtmc makes Rigol DS1052E oscilloscope crash
Date: Tue, 25 May 2010 19:34:09 +0200 [thread overview]
Message-ID: <4BFC0A11.1030902@gmx.de> (raw)
Hi folks,
I'm experiencing trouble connecting to a Rigol DS1052E oscilloscope via
the usbtmc USB class driver. When requesting small amounts of data it
works quite nicely, but when requesting a large chunk (i.e. when
requesting the whole memory to be transferred), the read aborts, the
connection times out and ultimately this leads to the oscilloscope crashing.
The commands I'm executing in the example I have provided are:
Cmd: *IDN?
Rigol.Technologies,DS1052E,DS1ED120100155,00.02.04.00.00
Cmd: :WAVEFORM:POINTS:MODE?
MAXIMUM
Cmd: :RUN
Cmd: :FORC
Cmd: :CHAN1:MEMD?
1048576
Cmd: :WAV:DATA?
After the ":WAV:DATA?" command, the oscilloscope crashes, here's how it
looks before for those who are interested:
http://s1.directupload.net/file/d/2169/r3m4l97m_jpg.htm
And after:
http://s10.directupload.net/file/d/2169/egvgv7hq_jpg.htm
I've captured the USB traffic which is going on using usbmon, debugfs
and wireshark, it's a 5kB pcap file:
http://www.file-upload.net/download-2544840/usb_rigol.pcap.html
To further trace the problem, I've patched usbtmc.c to emit some more
debug output. Here's the patch:
http://pastebin.com/fMkA5xSJ
Here's what the extended dmesg output looks after I applied my patch
against 2.6.34 (I annotated it so that it is clear which output is
emitted after which read):
http://pastebin.com/CXRwxxe8
I really hope this can be resolved,
Kind regards,
Johannes
next reply other threads:[~2010-05-25 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 17:34 Johannes Bauer [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-29 14:41 usbtmc makes Rigol DS1052E oscilloscope crash Mark Whitis
2010-08-23 20:49 ` Mark Whitis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFC0A11.1030902@gmx.de \
--to=dfnsonfsduifb@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox