Hi Christo,
The udev rules were not installed. I followed these instructions and
rebooted just to be safe:
https://sigrok.org/wiki/Fx2lafw#Install_the_udev_rules_file
I installed the 61-libsigrok-plugdev.rules because the user was already
a member of the plugdev group. These files came out of the git
repository of which I pulled within the last month. I should note I
"grep"ed for fluke and did not find an entry. As a test I also "grep"ed
for agilent and saw entries.
I should also note that the FTDI adapter I am using contains what
appears to be transmit and receive LEDs. Both of which are flashing
when using sigrok-cli w/the --continuous option. Just to verify, when I
use minicom and successfully obtain the current voltage reading from the
fluke-45. I see the transmit and receive LEDs flash while using minicom
as expected. So it would seam something is being sent to the fluke-45
and something is being returned from the fluke-45 while running sigrok.
But noting is printed out as expected at standard output.
-thanks again for your help.
On 5/31/21 3:43 PM, Christo Crause wrote:
Hi Stuart,
Regarding user access to the FT232R, can you check if the sigrok udev
rules [1,2] are installed? I guess you could run sigrok as root, but it
really should work for regular users too. I can use a FT232H as a
normal user, with the sigrok udev rules installed, on Linux Mint (so
quite similar to Ubuntu).
Not sure how to troubleshoot sigrok itself once it is connected to the
FTDI board.
1. https://sigrok.org/gitweb/?p=libsigrok.git;a=tree;f=contrib;hb=HEAD
<https://sigrok.org/gitweb/?p=libsigrok.git;a=tree;f=contrib;hb=HEAD>
2. https://sigrok.org/wiki/Fx2lafw#Install_the_udev_rules_file
<https://sigrok.org/wiki/Fx2lafw#Install_the_udev_rules_file>
On Mon, May 31, 2021 at 9:46 PM stuart <stu...@xnet.com
<mailto:stu...@xnet.com>> wrote:
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 <mailto: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 <mailto: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.
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
