Hi Christo,
The output of:
"sudo lsusb -v -d 0403:6001"
Bus 001 Device 005: ID 0403:6001 Future Technology Devices International, Ltd
FT232 Serial (UART) IC
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0403 Future Technology Devices International, Ltd
idProduct 0x6001 FT232 Serial (UART) IC
bcdDevice 6.00
iManufacturer 1 FTDI
iProduct 2 FT232R USB UART
iSerial 3 A9028SGB
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 90mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 2 FT232R USB UART
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 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 0x0040 1x 64 bytes
bInterval 0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)
That looks fine. So, here's the output to:
ftdi_eeprom --read-eeprom ftdi_conf.txt
...where ftdi_conf.txt is:
# Filename of the EE file to be generated. Leave empty to skip file writing.
filename=habr.bin
# Vendor ID. FT4232H factory default 0x0403.
vendor_id=0x0403
# Product ID. FT4232H factory default 0x6011.
product_id=0x6001
FTDI eeprom generator v0.17
(c) Intra2net AG and the libftdi developers <opensou...@intra2net.com>
Unable to find FTDI devices under given vendor/product id: 0x403/0x6001
Error code: -4 (usb_open() failed)
Retrying with default FTDI pid=0x6001.
Error: usb_open() failed
... well, that's strange. Why couldn't it open it? Trying again as root.
FTDI eeprom generator v0.17
(c) Intra2net AG and the libftdi developers <opensou...@intra2net.com>
FTDI read eeprom: 0
EEPROM size: 128
FTDI close: 0
That's better. So maybe it is permissions?
> ls -lat /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 May 31 14:41 /dev/ttyUSB0
> groups
... ... dialout ... ... ...
So, shouldn't be a problem. But just in case:
sudo sigrok-cli --driver fluke-45:conn=/dev/ttyUSB0:serialcomm=9600/8n1
--continuous
Still no output. But plenty of activity on the serial adapter LEDs!
I'm really confused at this point.
-thanks again for your help.
On 5/31/21 12:31 PM, Christo Crause wrote:
Hi Stuart,
That error seems to originate from libftdi, suggesting that libusb_open
failed
(http://developer.intra2net.com/git/?p=libftdi;a=blob;f=src/ftdi.c;hb=HEAD#l407
<http://developer.intra2net.com/git/?p=libftdi;a=blob;f=src/ftdi.c;hb=HEAD#l407>).
If so it cannot be fixed on sigrok's side since it relies on the
underlying drivers to communicate with the devices.
Can you list the output of:
sudo lsusb -v -d0x0403 (or whatever your device id is)
Another test of the libftdi/libusb stack is to run e.g. the ftdi_eeprom
utility
(http://manpages.ubuntu.com/manpages/impish/man1/ftdi_eeprom.1.html
<http://manpages.ubuntu.com/manpages/impish/man1/ftdi_eeprom.1.html>),
just to see if that driver stack can access the device.
Best regards
On Mon, May 31, 2021 at 4:49 PM stuart <stu...@xnet.com
<mailto:stu...@xnet.com>> wrote:
Hi,
I know this is the dev mail list. If there is a user mail list please
let me know. (I've dropped in on the IRC twice and asked but I didn't
see any responses.)
On an up to date Ubuntu box, if I can run:
"minicom -D /dev/ttyUSB0 -b 9600"
... and get the voltage from my FLUKE 45 then why doesn't:
"sigrok-cli --driver fluke-45:conn=/dev/ttyUSB0:serialcomm=9600/8n1
--continuous"
... return anything at all?
-thanks for any help.
More info in case it is useful:
> ./sigrok-cli --version
> sigrok-cli 0.8.0-git-dded02f
>
> Libraries and features:
> - libsigrok 0.6.0-git-955ab604/4:0:0 (rt: 0.6.0-git-955ab604/4:0:0).
> - Libs:
> - glib 2.64.6 (rt: 2.64.6/6406:6)
> - libzip 1.5.1
> - libserialport 0.1.1/1:0:1 (rt: 0.1.1/1:0:1)
> - libusb-1.0 1.0.23.11397 API 0x01000107
> - libftdi 1.4
> - librevisa 0.0.20130812
> - Host: x86_64-pc-linux-gnu, little-endian.
> - SCPI backends: TCP, RPC, serial, VISA, USBTMC.
> ./sigrok-cli --scan
> sr: ftdi-la: Failed to get the FTDI strings: -4
> sr: serial-libsp: Attempt to open serial port with invalid
parameters.
> sr: serial-libsp: Attempt to open serial port with invalid
parameters.
> sr: serial-libsp: Attempt to open serial port with invalid
parameters.
> sr: serial-libsp: Attempt to open serial port with invalid
parameters.
> The following devices were found:
> demo - Demo device with 13 channels: D0 D1 D2 D3 D4 D5 D6 D7 A0
A1 A2 A3 A4
> minicom -D /dev/ttyUSB0 -b 9600
> Welcome to minicom 2.7.1
>
> OPTIONS: I18n
> Compiled on Dec 23 2019, 02:06:26.
> Port /dev/ttyUSB0, 09:45:07
>
> Press CTRL-A Z for help on special keys
>
> VAL?
> -0.28E-3
> =>
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
<mailto:sigrok-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
<https://lists.sourceforge.net/lists/listinfo/sigrok-devel>
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
