ula icon indicating copy to clipboard operation
ula copied to clipboard

Cannot connect

Open darkbox opened this issue 2 years ago • 9 comments

Hi, I am new to pulseview and logic analyzers for that matter. I've uploaded the latest firmware to a rp2040 zero board but is not detected by pulseview and the "choose driver" dropdown is empty.

I need to install something else?

lsusb shows the device conected as:

Bus 003 Device 011: ID 16c0:27dd Van Ooijen Technische Informatica CDC-ACM class devices (modems)

using Ubuntu 23.04

darkbox avatar Jul 20 '23 15:07 darkbox

Hey @darkbox Could you please run ls /dev/tty*?

dotcypress avatar Jul 21 '23 15:07 dotcypress

The output is:

/dev/tty    /dev/tty23  /dev/tty39  /dev/tty54      /dev/ttyS1   /dev/ttyS25
/dev/tty0   /dev/tty24  /dev/tty4   /dev/tty55      /dev/ttyS10  /dev/ttyS26
/dev/tty1   /dev/tty25  /dev/tty40  /dev/tty56      /dev/ttyS11  /dev/ttyS27
/dev/tty10  /dev/tty26  /dev/tty41  /dev/tty57      /dev/ttyS12  /dev/ttyS28
/dev/tty11  /dev/tty27  /dev/tty42  /dev/tty58      /dev/ttyS13  /dev/ttyS29
/dev/tty12  /dev/tty28  /dev/tty43  /dev/tty59      /dev/ttyS14  /dev/ttyS3
/dev/tty13  /dev/tty29  /dev/tty44  /dev/tty6       /dev/ttyS15  /dev/ttyS30
/dev/tty14  /dev/tty3   /dev/tty45  /dev/tty60      /dev/ttyS16  /dev/ttyS31
/dev/tty15  /dev/tty30  /dev/tty46  /dev/tty61      /dev/ttyS17  /dev/ttyS4
/dev/tty16  /dev/tty31  /dev/tty47  /dev/tty62      /dev/ttyS18  /dev/ttyS5
/dev/tty17  /dev/tty32  /dev/tty48  /dev/tty63      /dev/ttyS19  /dev/ttyS6
/dev/tty18  /dev/tty33  /dev/tty49  /dev/tty7       /dev/ttyS2   /dev/ttyS7
/dev/tty19  /dev/tty34  /dev/tty5   /dev/tty8       /dev/ttyS20  /dev/ttyS8
/dev/tty2   /dev/tty35  /dev/tty50  /dev/tty9       /dev/ttyS21  /dev/ttyS9
/dev/tty20  /dev/tty36  /dev/tty51  /dev/ttyACM0    /dev/ttyS22
/dev/tty21  /dev/tty37  /dev/tty52  /dev/ttyprintk  /dev/ttyS23
/dev/tty22  /dev/tty38  /dev/tty53  /dev/ttyS0      /dev/ttyS24

I guess it is this one: /dev/ttyACM0

darkbox avatar Jul 21 '23 19:07 darkbox

Is this /dev/ttyACM0 disappear when disconnecting Pico? Also could you try following command: sigrok-cli -d ols:conn=/dev/ttyACM0 --scan?

dotcypress avatar Jul 21 '23 20:07 dotcypress

Is this /dev/ttyACM0 disappear when disconnecting Pico?

yes

Also could you try following command: sigrok-cli -d ols:conn=/dev/ttyACM0 --scan?

sigrok-cli -d ols:conn=/dev/ttyACM0  --scan
Driver ols not found.

darkbox avatar Jul 21 '23 20:07 darkbox

I've been looking for a solution on the Sigrok web but didn't find anything related. For what I understood, all the drivers are on share library called libsigrok which looks like is installed already. This are the packages installed on my system (apt list --installed | grep "sigrok"):

libsigrok4/lunar,now 0.5.2-4 amd64 [installed]
libsigrokcxx4/lunar,now 0.5.2-4 amd64 [installed]
libsigrokdecode4/lunar,now 0.5.3-4 amd64 [installed,automatic]
sigrok-cli/lunar,now 0.7.2-1 amd64 [installed]
sigrok-firmware-fx2lafw/lunar,lunar,now 0.1.7-1 all [installed]
sigrok/lunar,lunar,now 0.3 all [installed]
pulseview/lunar,now 0.4.2-3 amd64 [installed,automatic]

darkbox avatar Jul 22 '23 09:07 darkbox

Update: I've tested it in Windows 10 and works. So maybe there is some problem with the builds of Pulseview for Ubuntu. Meanwhile I'll use Windows and if I found a solution in the future, I'll post it here.

darkbox avatar Aug 02 '23 13:08 darkbox

I had the same problem on Ubuntu and Manjaro but it works if run pulseview with sudo: sudo pulseview The problem is the permission to acces to /dev/ttyACM0. https://stackoverflow.com/questions/49063139/why-do-i-need-to-execute-sudo-chmod-arw-dev-ttyacm0-command-again-after-every

Loc15 avatar Nov 13 '23 20:11 Loc15

I have the same issue even with sudo :

sudo sigrok-cli -d ols:conn=/dev/tty.usbmodem_ula_1 --scan
Driver ols not found.

FathiMahdi avatar Apr 07 '24 12:04 FathiMahdi

Driver ols not found This suggests that whilst you do have sigrok-cli and libsigrok installed, the version (or package) you have doesn't support the ols driver.

You can see a list of supported drivers by running:

sigrok-cli --list-supported

UPDATE:

Seems to be an Ubuntu bug where libsigrok supports no hardware at all.

If you're brave, you could install the Debian versions as they don't seem to be effected. It should work but I've not tried it as I don't use Ubuntu.

krayon avatar Dec 31 '24 14:12 krayon