sigrok

On 12/04/2012 12:52 PM, W. Ekkehard Blanz wrote:
>  
> 
> I tried connecting my USBee SX for the first time. It is listed as
> "supported" in http://www.sigrok.org/wiki/Supported_hardware, so I guess
> there must be a set of people who got it to work. Unfortunately, I don't
> seem to be a member of this set (yet) :-(
> 
>  
> 
> sigrok-cli recognized the USBee SX as "CWAV USBee SX with 8 probes: 0 1
> 2 3 4 5 6 7", but somehow the firmware upload failed.
> 
> What am I doing wrong?
> 
Did you install sigrok-firmware?

Alex

On 12/04/2012 12:52 PM, W. Ekkehard Blanz wrote:
>  
> 
> I tried connecting my USBee SX for the first time. It is listed as
> "supported" in http://www.sigrok.org/wiki/Supported_hardware, so I guess
> there must be a set of people who got it to work. Unfortunately, I don't
> seem to be a member of this set (yet) :-(
> 
>  
> 
> sigrok-cli recognized the USBee SX as "CWAV USBee SX with 8 probes: 0 1
> 2 3 4 5 6 7", but somehow the firmware upload failed.
> 
>  
> 
> Why do VID and PID not match the one from my device?
> 
>  
> 
> What is device -3?
>
>From what I can gather, the -3 is a libusb error:
/** Access denied (insufficient permissions) */
LIBUSB_ERROR_ACCESS = -3,

> 
> What am I doing wrong?

Did you set up permissions properly for the USB device? One quick test
is to try as root and see if that works.

Alex

Hi Ekkehard,

Did you install fx2lafw? - http://sigrok.org/wiki/Fx2lafw - our open firmware
for Fx2 based logic analysers. You need to build that and install it (you need
sdcc), and make sure you install the udev rules file as well.

Joel


On 04 December 2012 at 18:52 "W. Ekkehard Blanz" <ekkehard.blanz@...>
wrote:

> 
>  I tried connecting my USBee SX for the first time. It is listed as
> "supported" in http://www.sigrok.org/wiki/Supported_hardware, so I guess there
> must be a set of people who got it to work. Unfortunately, I don't seem to be
> a member of this set (yet) :-(
> 
>  sigrok-cli recognized the USBee SX as "CWAV USBee SX with 8 probes: 0 1 2 3 4
> 5 6 7", but somehow the firmware upload failed.
> 
>  Why do VID and PID not match the one from my device?
> 
>  What is device -3?
> 
>  What am I doing wrong?
> 
>  I am attaching the output of sigrok-cli, lsusb, and lsusb -v for the USBee
> SX. Note that the SX is the last device listed by lsusb (Bus 002 Device 006:
> ID 08a9:0009). Also, I have attached my system info.
> 
>  Cheers
> 
> 
>  $ sigrok-cli -l 5 -D
>  sr: libsigrok loglevel set to 5.
>  srd: libsigrokdecode loglevel set to 5.
>  sr: Sanity-checking all drivers.
>  sr: tondaj-sl-814: Couldn't determine connection options.
>  sr: la8: Probing for VID/PID 0403:6001.
>  sr: la8: Probing for VID/PID 0403:8867.
>  sr: ezusb: uploading firmware to device on 2.6
>  sr: ezusb: failed to open device: -3
>  sr: fx2lafw: Firmware upload failed for device 0.
>  sr: serial-dmm: Selected 'digitek-dt4000zc' subdriver.
>  sr: serial-dmm: Selected 'tekpower-tp4000zc' subdriver.
>  sr: serial-dmm: Selected 'metex-me31' subdriver.
>  sr: serial-dmm: Selected 'peaktech-3410' subdriver.
>  sr: serial-dmm: Selected 'mastech-mas345' subdriver.
>  sr: serial-dmm: Selected 'va-va18b' subdriver.
>  sr: serial-dmm: Selected 'metex-m3640d' subdriver.
>  sr: serial-dmm: Selected 'peaktech-4370' subdriver.
>  sr: serial-dmm: Selected 'pce-pce-dm32' subdriver.
>  sr: serial-dmm: Selected 'radioshack-22-168' subdriver.
>  sr: serial-dmm: Selected 'radioshack-22-812' subdriver.
>  sr: uni-t-dmm: Selected 'uni-t-ut61d' subdriver.
>  sr: usb: Extracted VID 0x1a86.
>  sr: usb: Extracted PID 0xe008.
>  sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>  sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>  sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>  sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>  sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>  sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>  sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>  sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>  sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>  sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>  sr: usb: VID:PID = 08a9:0009 (2.6) doesn't match.
>  sr: usb: Found 0 device(s).
>  sr: uni-t-dmm: Selected 'voltcraft-vc820' subdriver.
>  sr: usb: Extracted VID 0x1a86.
>  sr: usb: Extracted PID 0xe008.
>  sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>  sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>  sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>  sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>  sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>  sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>  sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>  sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>  sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>  sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>  sr: usb: VID:PID = 08a9:0009 (2.6) doesn't match.
>  sr: usb: Found 0 device(s).
>  The following devices were found:
>  Demo device with 8 probes: 0 1 2 3 4 5 6 7
>  CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
>  ~/USBee/sigrok/sigrok-cli
>  $ lsusb
>  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
>  Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>  Bus 001 Device 003: ID 046d:081b Logitech, Inc. Webcam C310
>  Bus 001 Device 004: ID 4971:ce17 SimpleTech 1TB SimpleDrive II USB External
> Hard Drive
>  Bus 002 Device 002: ID 04f9:002b Brother Industries, Ltd HL-5250DN Printer
>  Bus 004 Device 003: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
>  Bus 004 Device 004: ID 8054:0001
>  Bus 004 Device 005: ID 047d:2043 Kensington
>  Bus 004 Device 006: ID 045e:008c Microsoft Corp. Wireless Intellimouse
> Explorer 2.0
>  Bus 004 Device 007: ID 058f:9410 Alcor Micro Corp. Keyboard
>  Bus 002 Device 006: ID 08a9:0009
> 
>  $ lsusb -v -s 2:6
> 
>  Bus 002 Device 006: ID 08a9:0009
>  Couldn't open device, some information will be missing
>  Device Descriptor:
>  bLength 18
>  bDescriptorType 1
>  bcdUSB 2.00
>  bDeviceClass 255 Vendor Specific Class
>  bDeviceSubClass 255 Vendor Specific Subclass
>  bDeviceProtocol 255 Vendor Specific Protocol
>  bMaxPacketSize0 64
>  idVendor 0x08a9
>  idProduct 0x0009
>  bcdDevice 4.23
>  iManufacturer 0
>  iProduct 0
>  iSerial 0
>  bNumConfigurations 1
>  Configuration Descriptor:
>  bLength 9
>  bDescriptorType 2
>  wTotalLength 171
>  bNumInterfaces 1
>  bConfigurationValue 1
>  iConfiguration 0
>  bmAttributes 0x80
>  (Bus Powered)
>  MaxPower 100mA
>  Interface Descriptor:
>  bLength 9
>  bDescriptorType 4
>  bInterfaceNumber 0
>  bAlternateSetting 0
>  bNumEndpoints 0
>  bInterfaceClass 255 Vendor Specific Class
>  bInterfaceSubClass 255 Vendor Specific Subclass
>  bInterfaceProtocol 255 Vendor Specific Protocol
>  iInterface 0
>  Interface Descriptor:
>  bLength 9
>  bDescriptorType 4
>  bInterfaceNumber 0
>  bAlternateSetting 1
>  bNumEndpoints 6
>  bInterfaceClass 255 Vendor Specific Class
>  bInterfaceSubClass 255 Vendor Specific Subclass
>  bInterfaceProtocol 255 Vendor Specific Protocol
>  iInterface 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x01 EP 1 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x81 EP 1 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x02 EP 2 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x04 EP 4 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x86 EP 6 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x88 EP 8 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Interface Descriptor:
>  bLength 9
>  bDescriptorType 4
>  bInterfaceNumber 0
>  bAlternateSetting 2
>  bNumEndpoints 6
>  bInterfaceClass 255 Vendor Specific Class
>  bInterfaceSubClass 255 Vendor Specific Subclass
>  bInterfaceProtocol 255 Vendor Specific Protocol
>  iInterface 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x01 EP 1 OUT
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x81 EP 1 IN
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x02 EP 2 OUT
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x04 EP 4 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x86 EP 6 IN
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x88 EP 8 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Interface Descriptor:
>  bLength 9
>  bDescriptorType 4
>  bInterfaceNumber 0
>  bAlternateSetting 3
>  bNumEndpoints 6
>  bInterfaceClass 255 Vendor Specific Class
>  bInterfaceSubClass 255 Vendor Specific Subclass
>  bInterfaceProtocol 255 Vendor Specific Protocol
>  iInterface 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x01 EP 1 OUT
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x81 EP 1 IN
>  bmAttributes 3
>  Transfer Type Interrupt
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0040 1x 64 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x02 EP 2 OUT
>  bmAttributes 1
>  Transfer Type Isochronous
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x04 EP 4 OUT
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x86 EP 6 IN
>  bmAttributes 1
>  Transfer Type Isochronous
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 1
>  Endpoint Descriptor:
>  bLength 7
>  bDescriptorType 5
>  bEndpointAddress 0x88 EP 8 IN
>  bmAttributes 2
>  Transfer Type Bulk
>  Synch Type None
>  Usage Type Data
>  wMaxPacketSize 0x0200 1x 512 bytes
>  bInterval 0
>  ~/USBee/sigrok/sigrok-cli
>  $
> 
>  I am running an out-of-the-box (no kernel mods) Kubuntu 12.04 w/ kernel
> 3.2.0-34-generic with KDE 4.8.5 on a 64 bit machine with 6 AMD Phenom cores.
> gcc/g++ version 4.6.3, autoconf version 2.68, automake version 1.11.3,
> pkg-config version 0.26, libglib version 2.32.3, libzip version 0.10-1, zlib
> version 1:1.2.3.4, all from distro, and all fulfilling sigrok requirements.
> 
> 
> 
 ------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d_______________________________________________
sigrok-devel mailing list
sigrok-devel@...
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Nope - of course I did not install fx2lafw :-) - I'm a newbee - did not know I 
had to...

Did that now.

I also copied the udev rules file (thanks Joel and Alex!!).  Just a thought: 
Could the make install of e.g. sigrok-cli take care of that?  

Upon inspection of the rules file, I even made sure that I am a member of 
group plugdev ;-)

After that: Success!! :-) Well, sort of...

$ sigrok-cli --list-devices
sr: Failed to get device descriptor: -1. (Bug?)
The following devices were found:
Demo device with 8 probes: 0 1 2 3 4 5 6 7
CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
$

but the short form -D works better (not if executed right away though, see 
below):

$ sigrok-cli -D
The following devices were found:
Demo device with 8 probes: 0 1 2 3 4 5 6 7
CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
$

No more error messages.  One problem left here: The device ID is not printed 
as in the example output on the wiki page.  (Bug or Feature?)

That was cool - but only once :-(  When I tried it again, the process was 
"disk sleep" forever (I thought it had crashed), then came back after a minute 
or so and did not show the USBee SX anymore:

$ sigrok-cli -D
The following devices were found:
Demo device with 8 probes: 0 1 2 3 4 5 6 7
$ 

Turns out the USBee SX is gone from the list of USB devices after the first 
execution of sigrok-cli; in other words, lsusb doesn't show it anymore.

Unplugging and re-plugging the USBee SX fixes that - but only for one more 
execution of sigrok-cli.  Then I have to do the unplug/re-plug thing again.

To probe furhter: When I try to capture 10 samples while the SX is present as 
a USB device, I get

$ sigrok-cli -l 5 --samples 10
sr: libsigrok loglevel set to 5.
srd: libsigrokdecode loglevel set to 5.
sr: Sanity-checking all drivers.
sr: tondaj-sl-814: Couldn't determine connection options.
sr: la8: Probing for VID/PID 0403:6001.
sr: la8: Probing for VID/PID 0403:8867.
sr: ezusb: uploading firmware to device on 2.64
sr: ezusb: setting CPU reset mode on...
sr: ezusb: Uploading firmware at /usr/local/share/sigrok-firmware/fx2lafw-
cwav-usbeesx.fw
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4024 bytes
sr: ezusb: Firmware upload done
sr: ezusb: setting CPU reset mode off...
sr: serial-dmm: Selected 'digitek-dt4000zc' subdriver.
sr: serial-dmm: Selected 'tekpower-tp4000zc' subdriver.
sr: serial-dmm: Selected 'metex-me31' subdriver.
sr: serial-dmm: Selected 'peaktech-3410' subdriver.
sr: serial-dmm: Selected 'mastech-mas345' subdriver.
sr: serial-dmm: Selected 'va-va18b' subdriver.
sr: serial-dmm: Selected 'metex-m3640d' subdriver.
sr: serial-dmm: Selected 'peaktech-4370' subdriver.
sr: serial-dmm: Selected 'pce-pce-dm32' subdriver.
sr: serial-dmm: Selected 'radioshack-22-168' subdriver.
sr: serial-dmm: Selected 'radioshack-22-812' subdriver.
sr: uni-t-dmm: Selected 'uni-t-ut61d' subdriver.
sr: usb: Extracted VID 0x1a86.
sr: usb: Extracted PID 0xe008.
sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
sr: usb: Found 0 device(s).
sr: uni-t-dmm: Selected 'voltcraft-vc820' subdriver.
sr: usb: Extracted VID 0x1a86.
sr: usb: Extracted PID 0xe008.
sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
sr: usb: Found 0 device(s).
sigrok-cli only supports one device for capturing.
$

Am I reading that right?

It loses the device right after the firmware is loaded ("uploading firmware to 
device on 2.64" - 2.64 was the correct Bus/Device combination, BTW).  The 
sigrok-cli long output then shows that it is going through every single USB 
device on my machine, but the USBee SX appears to be already gone from that 
list by that time.  I cannot spot the VID:PID combination from the USBee SX 
(08a9:0009) anywhere in the output of sigrok-cli.

Please tell me what I am still missing...  Something else I didn't install???

Thanks for your patience!!!

Ekkehard

On 12/05/2012 04:24 PM, W. Ekkehard Blanz wrote:
> Turns out the USBee SX is gone from the list of USB devices after the
> first execution of sigrok-cli; in other words, lsusb doesn't show it
> anymore.
> 
>  
> 
> Unplugging and re-plugging the USBee SX fixes that - but only for one
> more execution of sigrok-cli. Then I have to do the unplug/re-plug thing
> again.
> 
I'm not sure if the firmware upload changes the VID:PID or not. Maybe
someone wiser can answer that.

> $ sigrok-cli -l 5 --samples 10
> 
Where's the --driver=fx2lafw option?

> Please tell me what I am still missing... Something else I didn't install???
> 
It looks like you got everything installed.

Hi Ekkehard,

What you're experiencing sounds odd. Last I knew the SX was easy to support. You
may be stumbling on bugs, at the very least our documentation needs to be
clearer I think.

My suggestion would be join us at #sigrok on freenode IRC channel. Then we can
try things more rapidly. If you're on europe time, there will probably be
intermittent chatter throughout the day. If you say hello, someone will probably
respond in less than 1hour.

biot, uwe_: Do either one of you have an SX that you could attempt to reproduce
this issue? I guess I could use my AX-clone, but I'm not going to have much time
for a few days.

Joel


On 05 December 2012 at 22:24 "W. Ekkehard Blanz" <ekkehard.blanz@...>
wrote:

>  Nope - of course I did not install fx2lafw :-) - I'm a newbee - did not know
> I had to...
> 
>  Did that now.
> 
>  I also copied the udev rules file (thanks Joel and Alex!!). Just a thought:
> Could the make install of e.g. sigrok-cli take care of that?
> 
>  Upon inspection of the rules file, I even made sure that I am a member of
> group plugdev ;-)
> 
>  After that: Success!! :-) Well, sort of...
> 
>  $ sigrok-cli --list-devices
>  sr: Failed to get device descriptor: -1. (Bug?)
>  The following devices were found:
>  Demo device with 8 probes: 0 1 2 3 4 5 6 7
>  CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
>  $
> 
>  but the short form -D works better (not if executed right away though, see
> below):
> 
>  $ sigrok-cli -D
>  The following devices were found:
>  Demo device with 8 probes: 0 1 2 3 4 5 6 7
>  CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
>  $
> 
>  No more error messages. One problem left here: The device ID is not printed
> as in the example output on the wiki page. (Bug or Feature?)
> 
>  That was cool - but only once :-( When I tried it again, the process was
> "disk sleep" forever (I thought it had crashed), then came back after a minute
> or so and did not show the USBee SX anymore:
> 
>  $ sigrok-cli -D
>  The following devices were found:
>  Demo device with 8 probes: 0 1 2 3 4 5 6 7
>  $
> 
>  Turns out the USBee SX is gone from the list of USB devices after the first
> execution of sigrok-cli; in other words, lsusb doesn't show it anymore.
> 
>  Unplugging and re-plugging the USBee SX fixes that - but only for one more
> execution of sigrok-cli. Then I have to do the unplug/re-plug thing again.
> 
>  To probe furhter: When I try to capture 10 samples while the SX is present as
> a USB device, I get
> 
>  $ sigrok-cli -l 5 --samples 10
>  sr: libsigrok loglevel set to 5.
>  srd: libsigrokdecode loglevel set to 5.
>  sr: Sanity-checking all drivers.
>  sr: tondaj-sl-814: Couldn't determine connection options.
>  sr: la8: Probing for VID/PID 0403:6001.
>  sr: la8: Probing for VID/PID 0403:8867.
>  sr: ezusb: uploading firmware to device on 2.64
>  sr: ezusb: setting CPU reset mode on...
>  sr: ezusb: Uploading firmware at
> /usr/local/share/sigrok-firmware/fx2lafw-cwav-usbeesx.fw
>  sr: ezusb: Uploaded 4096 bytes
>  sr: ezusb: Uploaded 4096 bytes
>  sr: ezusb: Uploaded 4096 bytes
>  sr: ezusb: Uploaded 4024 bytes
>  sr: ezusb: Firmware upload done
>  sr: ezusb: setting CPU reset mode off...
>  sr: serial-dmm: Selected 'digitek-dt4000zc' subdriver.
>  sr: serial-dmm: Selected 'tekpower-tp4000zc' subdriver.
>  sr: serial-dmm: Selected 'metex-me31' subdriver.
>  sr: serial-dmm: Selected 'peaktech-3410' subdriver.
>  sr: serial-dmm: Selected 'mastech-mas345' subdriver.
>  sr: serial-dmm: Selected 'va-va18b' subdriver.
>  sr: serial-dmm: Selected 'metex-m3640d' subdriver.
>  sr: serial-dmm: Selected 'peaktech-4370' subdriver.
>  sr: serial-dmm: Selected 'pce-pce-dm32' subdriver.
>  sr: serial-dmm: Selected 'radioshack-22-168' subdriver.
>  sr: serial-dmm: Selected 'radioshack-22-812' subdriver.
>  sr: uni-t-dmm: Selected 'uni-t-ut61d' subdriver.
>  sr: usb: Extracted VID 0x1a86.
>  sr: usb: Extracted PID 0xe008.
>  sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>  sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>  sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>  sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>  sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>  sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>  sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>  sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>  sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>  sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>  sr: usb: Found 0 device(s).
>  sr: uni-t-dmm: Selected 'voltcraft-vc820' subdriver.
>  sr: usb: Extracted VID 0x1a86.
>  sr: usb: Extracted PID 0xe008.
>  sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>  sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>  sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>  sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>  sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>  sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>  sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>  sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>  sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>  sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>  sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>  sr: usb: Found 0 device(s).
>  sigrok-cli only supports one device for capturing.
>  $
> 
>  Am I reading that right?
> 
>  It loses the device right after the firmware is loaded ("uploading firmware
> to device on 2.64" - 2.64 was the correct Bus/Device combination, BTW). The
> sigrok-cli long output then shows that it is going through every single USB
> device on my machine, but the USBee SX appears to be already gone from that
> list by that time. I cannot spot the VID:PID combination from the USBee SX
> (08a9:0009) anywhere in the output of sigrok-cli.
> 
>  Please tell me what I am still missing... Something else I didn't install???
> 
>  Thanks for your patience!!!
> 
>  Ekkehard
>

Sounds like this problem to me:
http://thread.gmane.org/gmane.comp.debugging.sigrok.devel/323/focus=327

The Asix Sigma2 is a little bit b0rked and stops other devices from working.

Am 06.12.2012 12:04, schrieb Joel Holdsworth:
> Hi Ekkehard,
>  
> What you're experiencing sounds odd. Last I knew the SX was easy to
> support. You may be stumbling on bugs, at the very least our
> documentation needs to be clearer I think.
>  
> My suggestion would be join us at #sigrok on freenode IRC channel. Then
> we can try things more rapidly. If you're on europe time, there will
> probably be intermittent chatter throughout the day. If you say hello,
> someone will probably respond in less than 1hour.
>  
> biot, uwe_: Do either one of you have an SX that you could attempt to
> reproduce this issue? I guess I could use my AX-clone, but I'm not going
> to have much time for a few days.
>  
> Joel
>  
> 
> On 05 December 2012 at 22:24 "W. Ekkehard Blanz"
> <ekkehard.blanz@...> wrote:
>>
>> Nope - of course I did not install fx2lafw :-) - I'm a newbee - did
>> not know I had to...
>>
>>  
>>
>> Did that now.
>>
>>  
>>
>> I also copied the udev rules file (thanks Joel and Alex!!). Just a
>> thought: Could the make install of e.g. sigrok-cli take care of that?
>>
>>  
>>
>> Upon inspection of the rules file, I even made sure that I am a member
>> of group plugdev ;-)
>>
>>  
>>
>> After that: Success!! :-) Well, sort of...
>>
>>  
>>
>> $ sigrok-cli --list-devices
>>
>> sr: Failed to get device descriptor: -1. (Bug?)
>>
>> The following devices were found:
>>
>> Demo device with 8 probes: 0 1 2 3 4 5 6 7
>>
>> CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
>>
>> $
>>
>>  
>>
>> but the short form -D works better (not if executed right away though,
>> see below):
>>
>>  
>>
>> $ sigrok-cli -D
>>
>> The following devices were found:
>>
>> Demo device with 8 probes: 0 1 2 3 4 5 6 7
>>
>> CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7
>>
>> $
>>
>>  
>>
>> No more error messages. One problem left here: The device ID is not
>> printed as in the example output on the wiki page. (Bug or Feature?)
>>
>>  
>>
>> That was cool - but only once :-( When I tried it again, the process
>> was "disk sleep" forever (I thought it had crashed), then came back
>> after a minute or so and did not show the USBee SX anymore:
>>
>>  
>>
>> $ sigrok-cli -D
>>
>> The following devices were found:
>>
>> Demo device with 8 probes: 0 1 2 3 4 5 6 7
>>
>> $
>>
>>  
>>
>> Turns out the USBee SX is gone from the list of USB devices after the
>> first execution of sigrok-cli; in other words, lsusb doesn't show it
>> anymore.
>>
>>  
>>
>> Unplugging and re-plugging the USBee SX fixes that - but only for one
>> more execution of sigrok-cli. Then I have to do the unplug/re-plug
>> thing again.
>>
>>  
>>
>> To probe furhter: When I try to capture 10 samples while the SX is
>> present as a USB device, I get
>>
>>  
>>
>> $ sigrok-cli -l 5 --samples 10
>>
>> sr: libsigrok loglevel set to 5.
>>
>> srd: libsigrokdecode loglevel set to 5.
>>
>> sr: Sanity-checking all drivers.
>>
>> sr: tondaj-sl-814: Couldn't determine connection options.
>>
>> sr: la8: Probing for VID/PID 0403:6001.
>>
>> sr: la8: Probing for VID/PID 0403:8867.
>>
>> sr: ezusb: uploading firmware to device on 2.64
>>
>> sr: ezusb: setting CPU reset mode on...
>>
>> sr: ezusb: Uploading firmware at
>> /usr/local/share/sigrok-firmware/fx2lafw-cwav-usbeesx.fw
>>
>> sr: ezusb: Uploaded 4096 bytes
>>
>> sr: ezusb: Uploaded 4096 bytes
>>
>> sr: ezusb: Uploaded 4096 bytes
>>
>> sr: ezusb: Uploaded 4024 bytes
>>
>> sr: ezusb: Firmware upload done
>>
>> sr: ezusb: setting CPU reset mode off...
>>
>> sr: serial-dmm: Selected 'digitek-dt4000zc' subdriver.
>>
>> sr: serial-dmm: Selected 'tekpower-tp4000zc' subdriver.
>>
>> sr: serial-dmm: Selected 'metex-me31' subdriver.
>>
>> sr: serial-dmm: Selected 'peaktech-3410' subdriver.
>>
>> sr: serial-dmm: Selected 'mastech-mas345' subdriver.
>>
>> sr: serial-dmm: Selected 'va-va18b' subdriver.
>>
>> sr: serial-dmm: Selected 'metex-m3640d' subdriver.
>>
>> sr: serial-dmm: Selected 'peaktech-4370' subdriver.
>>
>> sr: serial-dmm: Selected 'pce-pce-dm32' subdriver.
>>
>> sr: serial-dmm: Selected 'radioshack-22-168' subdriver.
>>
>> sr: serial-dmm: Selected 'radioshack-22-812' subdriver.
>>
>> sr: uni-t-dmm: Selected 'uni-t-ut61d' subdriver.
>>
>> sr: usb: Extracted VID 0x1a86.
>>
>> sr: usb: Extracted PID 0xe008.
>>
>> sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>>
>> sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>>
>> sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>>
>> sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>>
>> sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>>
>> sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>>
>> sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>>
>> sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>>
>> sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>>
>> sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>>
>> sr: usb: Found 0 device(s).
>>
>> sr: uni-t-dmm: Selected 'voltcraft-vc820' subdriver.
>>
>> sr: usb: Extracted VID 0x1a86.
>>
>> sr: usb: Extracted PID 0xe008.
>>
>> sr: usb: Trying to find USB device with VID:PID = 1a86:e008.
>>
>> sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match.
>>
>> sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match.
>>
>> sr: usb: VID:PID = 046d:081b (1.3) doesn't match.
>>
>> sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match.
>>
>> sr: usb: VID:PID = 04f9:002b (2.2) doesn't match.
>>
>> sr: usb: VID:PID = 046d:c215 (4.3) doesn't match.
>>
>> sr: usb: VID:PID = 8054:0001 (4.4) doesn't match.
>>
>> sr: usb: VID:PID = 047d:2043 (4.5) doesn't match.
>>
>> sr: usb: VID:PID = 045e:008c (4.6) doesn't match.
>>
>> sr: usb: VID:PID = 058f:9410 (4.7) doesn't match.
>>
>> sr: usb: Found 0 device(s).
>>
>> sigrok-cli only supports one device for capturing.
>>
>> $
>>
>>  
>>
>> Am I reading that right?
>>
>>  
>>
>> It loses the device right after the firmware is loaded ("uploading
>> firmware to device on 2.64" - 2.64 was the correct Bus/Device
>> combination, BTW). The sigrok-cli long output then shows that it is
>> going through every single USB device on my machine, but the USBee SX
>> appears to be already gone from that list by that time. I cannot spot
>> the VID:PID combination from the USBee SX (08a9:0009) anywhere in the
>> output of sigrok-cli.
>>
>>  
>>
>> Please tell me what I am still missing... Something else I didn't
>> install???
>>
>>  
>>
>> Thanks for your patience!!!
>>
>>  
>>
>> Ekkehard
>>
> 
>  
> 
> 
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> 
> 
> 
> _______________________________________________
> sigrok-devel mailing list
> sigrok-devel@...
> https://lists.sourceforge.net/lists/listinfo/sigrok-devel
>

Thanks a bunch Alex!

--driver=fx2lafw is another one of those things I just didn't know about...

Here's me knowing that a (Vendor ID : Product ID) pair describes the device 
uniquely, so me thinks that sigrok-cli must know which driver to use for that 
particular device much better than the average Joe User (i.e. me) would 
(unless some dummy did not install it, that'd be also me), and the --driver 
option should only be there to override that for whatever reason - right? 
(wrong, at least in current implementation - see below...)

BTW, you should not be able to change this VID:PID pair, like ever. Also, the 
device is gone good from the list, in other words, there is one less device on 
the list after sigrok-cli executes, which I'd consider a bug no matter which 
options get specified - sigrok-cli should leave the list of USB devices alone 
- it's not his/hers/whatever - right?

Be all that as it may, specifying the --driver=fx2lafw option does indeed lead 
to a different result - obviously sigrok-cli doesn't care whether I think it 
shouldn't ;-).  Now I know there is another bug as it now segfaults, which is 
always a bug, no matter what the circumstances - right?  

Oh, and the device is still gone from the list even with that new behavior and 
--driver=fx2lafw specified.  Which is very weird - I would not know how to 
take a device off that list...

But it looks as if I'm getting a little further every day - thanks to all your 
help!!

Ekkehard

$ sigrok-cli -l 5 -d 0 --samples 10 --driver=fx2lafw
sr: libsigrok loglevel set to 5.
srd: libsigrokdecode loglevel set to 5.
sr: Sanity-checking all drivers.
sr: ezusb: uploading firmware to device on 2.84
sr: ezusb: setting CPU reset mode on...
sr: ezusb: Uploading firmware at /usr/local/share/sigrok-firmware/fx2lafw-
cwav-usbeesx.fw
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4096 bytes
sr: ezusb: Uploaded 4024 bytes
sr: ezusb: Firmware upload done
sr: ezusb: setting CPU reset mode off...
sr: fx2lafw: Waiting for device to reset.
sr: fx2lafw: waited 403 ms
sr: fx2lafw: waited 506 ms
sr: fx2lafw: waited 610 ms
sr: fx2lafw: waited 713 ms
sr: fx2lafw: waited 817 ms
sr: fx2lafw: waited 920 ms
sr: fx2lafw: waited 1024 ms
sr: fx2lafw: waited 1127 ms
sr: fx2lafw: waited 1231 ms
sr: fx2lafw: waited 1334 ms
sr: fx2lafw: waited 1438 ms
sr: fx2lafw: waited 1539 ms
sr: fx2lafw: waited 1642 ms
sr: fx2lafw: waited 1745 ms
sr: fx2lafw: waited 1849 ms
sr: fx2lafw: waited 1952 ms
sr: fx2lafw: waited 2053 ms
sr: fx2lafw: waited 2156 ms
sr: fx2lafw: waited 2260 ms
sr: fx2lafw: waited 2363 ms
sr: fx2lafw: waited 2466 ms
sr: fx2lafw: waited 2567 ms
sr: fx2lafw: waited 2671 ms
sr: fx2lafw: waited 2774 ms
sr: fx2lafw: waited 2878 ms
sr: fx2lafw: waited 2979 ms
sr: fx2lafw: waited 3082 ms
sr: fx2lafw: Device came back after 3082 ms.
sr: fx2lafw: Unable to open device.
sr: session: sr_session_dev_add: dev_open failed (-1)
Failed to use device.
Segmentation fault (core dumped)
$

Thanks Joel,

I will give it a try - might take me a few minutes to get acquainted with it - 
never used it before.  However, I am not on European time (which I think most 
of you are, given E-mail addresses and names) - I am in California (PST = GMT 
- 8h).  So as far as you guys are concerned, I am pretty much nocturnal :-)

At any rate, please let me know how I can help you help me get that thing 
rolling.

Ekkehard


On Thursday, December 06, 2012 11:04:14 AM Joel Holdsworth wrote:

Hi Ekkehard, 
  
What you're experiencing sounds odd. Last I knew the SX was easy to support. 
You may be stumbling on bugs, at the very least our documentation needs to be 
clearer I think. 
  
My suggestion would be join us at #sigrok on freenode IRC channel. Then we can 
try things more rapidly. If you're on europe time, there will probably be 
intermittent chatter throughout the day. If you say hello, someone will 
probably respond in less than 1hour. 
  
biot, uwe_: Do either one of you have an SX that you could attempt to 
reproduce this issue? I guess I could use my AX-clone, but I'm not going to 
have much time for a few days. 
  
Joel 
  

On 05 December 2012 at 22:24 "W. Ekkehard Blanz" <ekkehard.blanz@...> 
wrote: 
Nope - of course I did not install fx2lafw :-) - I'm a newbee - did not know I 
had to... 
  
Did that now. 
  
I also copied the udev rules file (thanks Joel and Alex!!). Just a thought: 
Could the make install of e.g. sigrok-cli take care of that? 
  
Upon inspection of the rules file, I even made sure that I am a member of 
group plugdev ;-) 
  
After that: Success!! :-) Well, sort of... 
  
$ sigrok-cli --list-devices 
sr: Failed to get device descriptor: -1. (Bug?) 
The following devices were found: 
Demo device with 8 probes: 0 1 2 3 4 5 6 7 
CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7 
$ 
  
but the short form -D works better (not if executed right away though, see 
below): 
  
$ sigrok-cli -D 
The following devices were found: 
Demo device with 8 probes: 0 1 2 3 4 5 6 7 
CWAV USBee SX with 8 probes: 0 1 2 3 4 5 6 7 
$ 
  
No more error messages. One problem left here: The device ID is not printed as 
in the example output on the wiki page. (Bug or Feature?) 
  
That was cool - but only once :-( When I tried it again, the process was "disk 
sleep" forever (I thought it had crashed), then came back after a minute or so 
and did not show the USBee SX anymore: 
  
$ sigrok-cli -D 
The following devices were found: 
Demo device with 8 probes: 0 1 2 3 4 5 6 7 
$ 
  
Turns out the USBee SX is gone from the list of USB devices after the first 
execution of sigrok-cli; in other words, lsusb doesn't show it anymore. 
  
Unplugging and re-plugging the USBee SX fixes that - but only for one more 
execution of sigrok-cli. Then I have to do the unplug/re-plug thing again. 
  
To probe furhter: When I try to capture 10 samples while the SX is present as 
a USB device, I get 
  
$ sigrok-cli -l 5 --samples 10 
sr: libsigrok loglevel set to 5. 
srd: libsigrokdecode loglevel set to 5. 
sr: Sanity-checking all drivers. 
sr: tondaj-sl-814: Couldn't determine connection options. 
sr: la8: Probing for VID/PID 0403:6001. 
sr: la8: Probing for VID/PID 0403:8867. 
sr: ezusb: uploading firmware to device on 2.64 
sr: ezusb: setting CPU reset mode on... 
sr: ezusb: Uploading firmware at /usr/local/share/sigrok-firmware/fx2lafw-
cwav-usbeesx.fw 
sr: ezusb: Uploaded 4096 bytes 
sr: ezusb: Uploaded 4096 bytes 
sr: ezusb: Uploaded 4096 bytes 
sr: ezusb: Uploaded 4024 bytes 
sr: ezusb: Firmware upload done 
sr: ezusb: setting CPU reset mode off... 
sr: serial-dmm: Selected 'digitek-dt4000zc' subdriver. 
sr: serial-dmm: Selected 'tekpower-tp4000zc' subdriver. 
sr: serial-dmm: Selected 'metex-me31' subdriver. 
sr: serial-dmm: Selected 'peaktech-3410' subdriver. 
sr: serial-dmm: Selected 'mastech-mas345' subdriver. 
sr: serial-dmm: Selected 'va-va18b' subdriver. 
sr: serial-dmm: Selected 'metex-m3640d' subdriver. 
sr: serial-dmm: Selected 'peaktech-4370' subdriver. 
sr: serial-dmm: Selected 'pce-pce-dm32' subdriver. 
sr: serial-dmm: Selected 'radioshack-22-168' subdriver. 
sr: serial-dmm: Selected 'radioshack-22-812' subdriver. 
sr: uni-t-dmm: Selected 'uni-t-ut61d' subdriver. 
sr: usb: Extracted VID 0x1a86. 
sr: usb: Extracted PID 0xe008. 
sr: usb: Trying to find USB device with VID:PID = 1a86:e008. 
sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match. 
sr: usb: VID:PID = 046d:081b (1.3) doesn't match. 
sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match. 
sr: usb: VID:PID = 04f9:002b (2.2) doesn't match. 
sr: usb: VID:PID = 046d:c215 (4.3) doesn't match. 
sr: usb: VID:PID = 8054:0001 (4.4) doesn't match. 
sr: usb: VID:PID = 047d:2043 (4.5) doesn't match. 
sr: usb: VID:PID = 045e:008c (4.6) doesn't match. 
sr: usb: VID:PID = 058f:9410 (4.7) doesn't match. 
sr: usb: Found 0 device(s). 
sr: uni-t-dmm: Selected 'voltcraft-vc820' subdriver. 
sr: usb: Extracted VID 0x1a86. 
sr: usb: Extracted PID 0xe008. 
sr: usb: Trying to find USB device with VID:PID = 1a86:e008. 
sr: usb: VID:PID = 1d6b:0002 (1.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (2.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (3.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (4.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (5.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (6.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0001 (7.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0002 (8.1) doesn't match. 
sr: usb: VID:PID = 1d6b:0003 (9.1) doesn't match. 
sr: usb: VID:PID = 046d:081b (1.3) doesn't match. 
sr: usb: VID:PID = 4971:ce17 (1.4) doesn't match. 
sr: usb: VID:PID = 04f9:002b (2.2) doesn't match. 
sr: usb: VID:PID = 046d:c215 (4.3) doesn't match. 
sr: usb: VID:PID = 8054:0001 (4.4) doesn't match. 
sr: usb: VID:PID = 047d:2043 (4.5) doesn't match. 
sr: usb: VID:PID = 045e:008c (4.6) doesn't match. 
sr: usb: VID:PID = 058f:9410 (4.7) doesn't match. 
sr: usb: Found 0 device(s). 
sigrok-cli only supports one device for capturing. 
$ 
  
Am I reading that right? 
  
It loses the device right after the firmware is loaded ("uploading firmware to 
device on 2.64" - 2.64 was the correct Bus/Device combination, BTW). The 
sigrok-cli long output then shows that it is going through every single USB 
device on my machine, but the USBee SX appears to be already gone from that 
list by that time. I cannot spot the VID:PID combination from the USBee SX 
(08a9:0009) anywhere in the output of sigrok-cli. 
  
Please tell me what I am still missing... Something else I didn't install??? 
  
Thanks for your patience!!! 
  
Ekkehard

Here is a brief summary of all the actions I took based on your numerous 
suggestions last night. Thank you so much - you guys are amazing!!!
 
1) git commit 26be4eb of libsigrok fixed the segfault
   (if you had a bug tracking system you could close that now - sorry,
   couldn't resist :-)
 
2) AX clone works for Joel on current commit -
   he can officially fob me off now :-)
 
3) fx2lafw-cwav-usbeesx.fw built with sdcc 3.10 by Joel 
   (vs the one built by me using sdcc 2.9.0) 
   made no difference in outcome (the files diff, however!)
 
4) uwe_ also has a USBee SX, which works fine for him.
   His bcdDevice is 16.b5 - mine is 4.23
 
5) I have taken an image of the PCB of my device.  
   What is the best way to get it to you (it is 9 MB)?
 
6) I installed sigrok on a different PC (Kubuntu 12.04 32-bit) - same result
 
7) Tried to up #define MAX_RENUM_DELAY_MS 3000 in hardware/fx2lafw/fx2lafw.h
   a) this header file is in include/ in my installation, not in hw/
   b) this header file does not contain a #define MAX_RENUM_DELAY_MS
      in fact, I did a grep on the whole directory tree obtained from
      sigrok-firmware-fx2lafw-0.1.0.tar.gz -
      there was no MAX_RENUM_DELAY_MS anywhere -
      am I using a wrong version???
 
Thanks again for all your help!!!!!!!!!!
 
Ekkehard

On 12/06/2012 08:20 PM, W. Ekkehard Blanz wrote:
> Here is a brief summary of all the actions I took based on your numerous
> suggestions last night. Thank you so much - you guys are amazing!!!
> 
> 5) I have taken an image of the PCB of my device.
> 
> What is the best way to get it to you (it is 9 MB)?
> 
Upload it to somewhere public and give us a link. I would avoid services
like photobucket, or flickr, as they tend to scale down the image..

> in fact, I did a grep on the whole directory tree obtained from
> 
> sigrok-firmware-fx2lafw-0.1.0.tar.gz -
> 
> there was no MAX_RENUM_DELAY_MS anywhere -
> 
> am I using a wrong version???
> 
This is a libsigrok define, not a sigrok-firmware-fx2lafw one. You were
looking at the wrong subproject.

The problem seems pretty obvious: our fx2lafw firmware crashes on your
device. Uwe or Joel will have to get back to you on that one.

Alex

Correction on my last point.

I found MAX_RENUM_DELAY_MS in libsigrok (looked in the wrong place first).  
Increased it by a factor of 10 - now it just waits 30 seconds instead of 3 for 
the device to reset. Everything else is the same.

Is it officially time to give up on that particular device?  SW works for uwe_ 
on a (most likely much newer) USBee SX.  SW doesn't work with my (most likely 
much older) USBee SX on two different PCs => SW doesn't work with that 
particular USBee SX.

Oh well...  was worth trying.

Ekkehard

On 12/07/2012 12:15 PM, W. Ekkehard Blanz wrote:
> Is it officially time to give up on that particular device? SW works for
> uwe_ on a (most likely much newer) USBee SX. SW doesn't work with my
> (most likely much older) USBee SX on two different PCs => SW doesn't
> work with that particular USBee SX.
> 
No. We need to find out why fxlafw crashes on your device and fix it. As
I have previously stated, Uwe and/or Joel will have to get back to you
on that one.

In the meantime, please try to provide high resolution pictures of the
PCB, both front and back. The designers might have changed something in
the hardware.

Hi,

just a quick update for everyone on the list -- we found the issue on
IRC after checking the photos; those are available in the wiki now, too:

  http://sigrok.org/wiki/CWAV_USBee_SX

The problem is that this older USBee SX uses a Cypress CY7C68013 (FX2) chip,
not the more recent Cypress CY7C68013A (FX2LP). There are various
differences between these two chips/versions which I'll document in the
wiki soonish, which require fixes in libsigrok and fx2lafw.

A quick hack fix worked for both W. Ekkehard Blanz (USBee SX) and myself
on another FX2 (not FX2LP) based device. I'm currently working on the "proper"
fix for this, which should be available in git soonish, too.


Uwe.
-- 
http://hermann-uwe.de     | http://sigrok.org
http://randomprojects.org | http://unmaintained-free-software.org

I guess we can produce compile-time variants of fx2lafw. Do you think we can do
it in a single image, with some runtime checks to adapt to the host platform?


On 12 December 2012 at 22:12 Uwe Hermann <uwe@...> wrote:
> Hi,
>
> just a quick update for everyone on the list -- we found the issue on
> IRC after checking the photos; those are available in the wiki now, too:
>
> http://sigrok.org/wiki/CWAV_USBee_SX
>
> The problem is that this older USBee SX uses a Cypress CY7C68013 (FX2) chip,
> not the more recent Cypress CY7C68013A (FX2LP). There are various
> differences between these two chips/versions which I'll document in the
> wiki soonish, which require fixes in libsigrok and fx2lafw.
>
> A quick hack fix worked for both W. Ekkehard Blanz (USBee SX) and myself
> on another FX2 (not FX2LP) based device. I'm currently working on the "proper"
> fix for this, which should be available in git soonish, too.
>
>
> Uwe.
> --
> http://hermann-uwe.de | http://sigrok.org
> http://randomprojects.org | http://unmaintained-free-software.org
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> sigrok-devel mailing list
> sigrok-devel@...
> https://lists.sourceforge.net/lists/listinfo/sigrok-devel