NanoVNA V2 / Forum

Note: this page is a mirror of https://groups.io/g/NanoVNAV2.
Click here to join and see most recent posts.

NanoVNA V2 Linux no tty device #clones #nanovna-saver


ol2tmx 2021/06/16 03:34

Hi there,
I bought an NanoVNA V2 clone from Amazon. Today I tired to connect my NanoVNA v2 to my computer running Ubuntu 20.04 LTS for firmware upgrade. But I did not find any ttyUSB* device even I have pushed the DFU button and applied.

"DFU: Device Firmware Update Mode
To exit DFU mode, please reset device yourselfs"

lsusb:
--------
Bus 001 Device 009: ID 062a:4c01 MosArt Semiconductor Corp.
Bus 001 Device 005: ID 0c45:7409 Microdia  --> wireless keyboard
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 004: ID 0c45:6366 Microdia      --> this is my 2.4 Ghz wireless mouse
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub

dmesg:

~# dmesg | grep tty
0.116550] printk: console [tty0] enabled

root@anastasis:~# dmesg | grep tty*
0.005515] Found optimal setting for mtrr clean up
0.116550] printk: console [tty0] enabled
0.122170] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
0.262775] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
0.304266] pci 0000:01:00.0: vgaarb: setting as boot VGA device
0.304706] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti < giometti@linux.it >
0.537782] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
0.537805] ACPI: Power Button [PWRB]
0.537844] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
0.539041] ACPI: Power Button [PWRF]
0.900200] evm: Initialising EVM extended attributes:
0.900205] evm: HMAC attrs: 0x1
0.900954] rtc_cmos 00:01: setting system clock to 2021-06-16T05:13:39 UTC (1623820419)
1.619056] sr 0:0:0:0: Attached scsi CD-ROM sr0
1.619146] sr 0:0:0:0: Attached scsi generic sg0 type 5
2.117663] sd 1:0:0:0: Attached scsi generic sg1 type 0
2.142382] sd 1:0:0:0: [sda] Attached SCSI disk
28.862868] [drm] amdgpu kernel modesetting enabled.
28.863443] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1DA2:0xE367 0xC7).
83.534561] RTL8211B Gigabit Ethernet r8169-200:00: attached PHY driver [RTL8211B Gigabit Ethernet] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)

root:~# ls -l /dev/ttyUSB*

No ttyUSB* device found. Any suggestions, remarks, comments, experiences ?

best regards
ol2tmx

ol2tmx 2021/06/16 07:45

Hi guys,
by changing the contained usb cable and God-bless I am able to see the the tty-device:

[32731.481871] usb 6-2: new full-speed USB device number 7 using uhci_hcd
[32731.648028] usb 6-2: New USB device found, idVendor=04b4, idProduct=0008, bcdDevice= 0.01
[32731.648033] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32731.648036] usb 6-2: Product: CDC-ACM Demo
[32731.648039] usb 6-2: Manufacturer: Black Sphere Technologies
[32731.648041] usb 6-2: SerialNumber: DEMO
[32731.761875] cdc_acm 6-2:1.0: ttyACM0: USB ACM device
[32731.764527] usbcore: registered new interface driver cdc_acm
[32731.764529] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[32731.862892] usb usb6-port2: disabled by hub (EMI?), re-enabling...
[32731.862900] usb 6-2: USB disconnect, device number 7
[32732.085930] usb 6-2: new full-speed USB device number 8 using uhci_hcd
[32732.252053] usb 6-2: New USB device found, idVendor=04b4, idProduct=0008, bcdDevice= 0.01
[32732.252057] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32732.252060] usb 6-2: Product: CDC-ACM Demo
[32732.252062] usb 6-2: Manufacturer: Black Sphere Technologies
[32732.252064] usb 6-2: SerialNumber: DEMO
[32732.254093] *cdc_acm 6-2:1.0: ttyACM0: USB ACM device*

ol2tmx 2021/06/16 08:06

By exchanging the USB cable I could see the *USB ACM device ttyACM0*

[32731.481871] usb 6-2: new full-speed USB device number 7 using uhci_hcd
[32731.648028] usb 6-2: New USB device found, idVendor=04b4, idProduct=0008, bcdDevice= 0.01
[32731.648033] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32731.648036] usb 6-2: Product: CDC-ACM Demo
[32731.648039] usb 6-2: Manufacturer: Black Sphere Technologies
[32731.648041] usb 6-2: SerialNumber: DEMO
[32731.761875] cdc_acm 6-2:1.0: ttyACM0: USB ACM device
[32731.764527] usbcore: registered new interface driver cdc_acm
[32731.764529] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[32731.862892] usb usb6-port2: disabled by hub (EMI?), re-enabling...
[32731.862900] usb 6-2: USB disconnect, device number 7
[32732.085930] usb 6-2: new full-speed USB device number 8 using uhci_hcd
[32732.252053] usb 6-2: New USB device found, idVendor=04b4, idProduct=0008, bcdDevice= 0.01
[32732.252057] usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[32732.252060] usb 6-2: Product: CDC-ACM Demo
[32732.252062] usb 6-2: Manufacturer: Black Sphere Technologies
[32732.252064] usb 6-2: SerialNumber: DEMO
[ *32732.254093] cdc_acm 6-2:1.0: ttyACM0: USB ACM device*

The device is found but the kernel driver is probably not available yet or it needs some adaption in the modprobe system ???
Yep, we coming closer to a solution.

To reply to this topic, join https://groups.io/g/NanoVNAV2

View this thread on groups.io