Device not accepting address 6, error -71

suen · December 24, 2020, 11:26am

hi everyone,i have plug a usb device(a 5G modules evm board for N510M from Neoway) to jetson nx board but i can not get messages frome usb serial.
when i plug the device,the dmesg shows:

root@nvidia-desktop:/home/nvidia# dmesg --follow
[  312.337656] usb 1-2.4: new high-speed USB device number 6 using tegra-xusb
[  313.350158] usb 1-2.4: Device not responding to setup address.
[  313.557825] usb 1-2.4: Device not responding to setup address.
[  313.765620] usb 1-2.4: device not accepting address 6, error -71
[  313.845592] usb 1-2.4: new high-speed USB device number 7 using tegra-xusb
[  313.867004] usb 1-2.4: New USB device found, idVendor=2949, idProduct=8800
[  313.867015] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  313.867023] usb 1-2.4: Product: N510M
[  313.867029] usb 1-2.4: Manufacturer: Neoway
[  313.867035] usb 1-2.4: SerialNumber: 92718392204285
[  314.165602] rndis_host 1-2.4:1.0: RNDIS_MSG_QUERY(0x00010202) failed, -110
[  314.165890] rndis_host 1-2.4:1.0: RNDIS_MSG_QUERY(0x01010101) failed, -71
[  314.166051] rndis_host 1-2.4:1.0: rndis get ethaddr, -71
[  314.166273] rndis_host: probe of 1-2.4:1.0 failed with error -71
[  314.167641] option 1-2.4:1.2: GSM modem (1-port) converter detected
[  314.170846] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB0
[  314.171074] option 1-2.4:1.3: GSM modem (1-port) converter detected
[  314.171400] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB1
[  314.171641] option 1-2.4:1.4: GSM modem (1-port) converter detected
[  314.171939] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB2
[  314.172165] option 1-2.4:1.5: GSM modem (1-port) converter detected
[  314.172395] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB3
[  314.172976] option 1-2.4:1.6: GSM modem (1-port) converter detected
[  314.173288] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB4
[  314.174823] usb 1-2.4: USB disconnect, device number 7
[  314.176969] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  314.177015] option 1-2.4:1.2: device disconnected
[  314.178056] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  314.178159] option 1-2.4:1.3: device disconnected
[  314.178495] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  314.178535] option 1-2.4:1.4: device disconnected
[  314.178918] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  314.178991] option 1-2.4:1.5: device disconnected
[  314.179392] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[  314.179424] option 1-2.4:1.6: device disconnected
[  314.401566] usb 1-2.4: new high-speed USB device number 8 using tegra-xusb
[  314.423007] usb 1-2.4: New USB device found, idVendor=2949, idProduct=8800
[  314.423019] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  314.423026] usb 1-2.4: Product: N510M
[  314.423032] usb 1-2.4: Manufacturer: Neoway
[  314.423039] usb 1-2.4: SerialNumber: 92718392204285
[  314.443632] rndis_host 1-2.4:1.0 usb1: register 'rndis_host' at usb-3610000.xhci-2.4, RNDIS device, 9a:39:72:48:6c:b2
[  314.444469] option 1-2.4:1.2: GSM modem (1-port) converter detected
[  314.445034] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB0
[  314.445306] option 1-2.4:1.3: GSM modem (1-port) converter detected
[  314.446062] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB1
[  314.446442] option 1-2.4:1.4: GSM modem (1-port) converter detected
[  314.446720] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB2
[  314.446949] option 1-2.4:1.5: GSM modem (1-port) converter detected
[  314.447136] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB3
[  314.452871] option 1-2.4:1.6: GSM modem (1-port) converter detected
[  314.453118] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB4
[  314.903864] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[  462.382454] NETDEV WATCHDOG: usb1 (rndis_host): transmit queue 0 timed out
[  462.382538] ------------[ cut here ]------------
[  462.382690] WARNING: CPU: 1 PID: 7106 at /home/ub/nx_r32.4.4/Linux_for_Tegra/source/kernel/kernel-4.9/net/sched/sch_generic.c:316 dev_watchdog+0x2c8/0x2d0
[  462.382922] Modules linked in: rndis_host bnep fuse rtl8812au cfg80211 zram overlay spidev userspace_alert nvgpu bluedroid_pm ip_tables x_tables

[  462.383020] CPU: 1 PID: 7106 Comm: compiz Not tainted 4.9.140-tegra #4
[  462.383026] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[  462.383034] task: ffffffc1cc474600 task.stack: ffffffc1c54b8000
[  462.383041] PC is at dev_watchdog+0x2c8/0x2d0
[  462.383047] LR is at dev_watchdog+0x2c8/0x2d0
[  462.383054] pc : [<ffffff8008ddf818>] lr : [<ffffff8008ddf818>] pstate: 00400045
[  462.383058] sp : ffffffc1ffd20db0
[  462.383063] x29: ffffffc1ffd20db0 x28: 0000000000000002
[  462.383077] x27: ffffff8009e750c8 x26: 00000000ffffffff
[  462.383089] x25: 0000000000000001 x24: 0000000000000140
[  462.383101] x23: ffffff8009e76000 x22: ffffffc1e91fa460
[  462.383113] x21: 0000000000000000 x20: ffffffc1e91fa000
[  462.383124] x19: ffffffc1e4add000 x18: 0000000000000000
[  462.383136] x17: 0000007f91aa0170 x16: 0000007f88b84738
[  462.383148] x15: ffffffffffffffff x14: ffffff800a15a1e0
[  462.383160] x13: 0000000000000000 x12: 0000000000000006
[  462.383171] x11: 0000000000000006 x10: 00000000000003e6
[  462.383184] x9 : 0000000000000001 x8 : ffffffc1ffcd95a4
[  462.383197] x7 : 0000000000000000 x6 : ffffffc1ffd21bf0
[  462.383208] x5 : ffffffc1ffd21bf0 x4 : 0000000000000000
[  462.383220] x3 : ffffffc1ffd277f8 x2 : ffffffc1ffd21bf0
[  462.383232] x1 : ffffffc1cc474600 x0 : 000000000000003e

the source code has been modisied as follow:

~/nx_r32.4.4/Linux_for_Tegra/source$ diff -Naur  kernel/kernel-4.9/drivers/usb/serial/option.c source_orig/kernel/kernel-4.9/drivers/usb/serial/option.c
--- kernel/kernel-4.9/drivers/usb/serial/option.c       2020-12-24 18:16:28.567202066 +0800
+++ source_orig/kernel/kernel-4.9/drivers/usb/serial/option.c   2020-10-17 03:12:13.000000000 +0800
@@ -566,8 +566,6 @@


 static const struct usb_device_id option_ids[] = {
-       { USB_DEVICE(0x2949, 0x8800),
-               .driver_info = RSVD(0)|RSVD(1)},
        { USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_COLT) },
        { USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_RICOLA) },
        { USB_DEVICE(OPTION_VENDOR_ID, OPTION_PRODUCT_RICOLA_LIGHT) },

DaneLLL · December 28, 2020, 2:09am

Hi,
Please share more information about the patch. What is the purpose of applying the patch? And what is the behavior of using default kernel driver?

And please share release version for reference( $ head -1 /etc/nv_tegra_release ).

suen · December 28, 2020, 3:08am

the patch just add the PID & VID of the 5G modules .
here is the version info:

nvidia@nvidia-desktop:~$ head -1 /etc/nv_tegra_release
# R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t186ref, EABI: aarch64, DATE: Fri Oct 16 19:37:08 UTC 2020
nvidia@nvidia-desktop:~$

DaneLLL · December 28, 2020, 11:32pm

Hi,
Do you use custom board or default developer board? For using custom board, you would need to run compliance test and tune the signal.

suen · December 29, 2020, 12:53am

i have test with our carrier board and the developer board,they all didn’t work.

DaneLLL · December 29, 2020, 5:31am

Hi,
In http://www.neoway.com/details/product_en/837.html the interface looks to be PCIe M2. Would like to confirm you connect to USB type-A port or M2 Key E, key M on developer kit?

suen · December 29, 2020, 5:36am

our own carrier board has PCIE M.2 KEY B with usb3.0 from a usb 3.0 hub (rts5411s),and we also have a EVM (with usb c,micro usb,)from Neoway,

DaneLLL · December 30, 2020, 2:19am

Hi,
The 5G module seems not stable to be enumerated. The log shows the 5G module is connected, disconnected, and then connected. And it is enumerated HS while its spec says it’s USB3.1 capable. It seems to be an issue in power. Please try

Connect a self-powered USB 3.1 hub to Jetson NX board, make sure the self-powered USB 3.1 hub is enumerated as SuperSpeed
Connect the 5G module to the self-powered USB 3.1 hub

suen · December 30, 2020, 9:00am

i plug a usb 3.1 hub to nx board.

root@nvidia-desktop:/home/nvidia# dmesg --follow
[  479.342442] usb 2-3.4: new SuperSpeed USB device number 7 using tegra-xusb
[  479.367155] usb 2-3.4: New USB device found, idVendor=05e3, idProduct=0612
[  479.367167] usb 2-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  479.367176] usb 2-3.4: Product: USB3.1 Hub
[  479.367183] usb 2-3.4: Manufacturer: GenesysLogic
[  479.368631] hub 2-3.4:1.0: USB hub found
[  479.368958] hub 2-3.4:1.0: 4 ports detected
[  479.446146] usb 1-2.4: new high-speed USB device number 13 using tegra-xusb
[  479.469522] usb 1-2.4: New USB device found, idVendor=05e3, idProduct=0610
[  479.469533] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  479.469540] usb 1-2.4: Product: USB2.0 Hub
[  479.469547] usb 1-2.4: Manufacturer: GenesysLogic
[  479.470657] hub 1-2.4:1.0: USB hub found
[  479.470938] hub 1-2.4:1.0: 4 ports detected
[  479.498202] usb 2-3.4: usb_suspend_both: status 0
[  480.530564] usb 1-2.4-port1: Cannot enable. Maybe the USB cable is bad?
[  482.601997] usb 1-2.4: usb_suspend_both: status 0

and then plug 5G module to usb3.1 hub:

[  651.857090] usb 1-2.4: usb_suspend_both: status 0
[  669.584177] usb 1-2.4.1: new full-speed USB device number 28 using tegra-xusb
[  669.604550] usb 1-2.4.1: not running at top speed; connect to a high speed hub
[  669.605297] usb 1-2.4.1: New USB device found, idVendor=1782, idProduct=4d00
[  669.605307] usb 1-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  669.605338] usb 1-2.4.1: Product: Gadget Serial
[  669.605344] usb 1-2.4.1: Manufacturer: spreadtrum with dwc3-gadget
[  672.961472] usb 1-2.4.1: USB disconnect, device number 28
[  673.123978] usb 1-2.4: usb_suspend_both: status 0
[  684.431410] usb 1-2.4.1: new high-speed USB device number 29 using tegra-xusb
[  684.458384] usb 1-2.4.1: New USB device found, idVendor=2949, idProduct=8800
[  684.458395] usb 1-2.4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  684.458401] usb 1-2.4.1: Product: N510M
[  684.458414] usb 1-2.4.1: Manufacturer: Neoway
[  684.458420] usb 1-2.4.1: SerialNumber: 92718392204285
[  684.550872] rndis_host 1-2.4.1:1.0 usb1: register 'rndis_host' at usb-3610000.xhci-2.4.1, RNDIS device, ce:08:10:3d:17:27
[  684.551548] option 1-2.4.1:1.2: GSM modem (1-port) converter detected
[  684.551974] usb 1-2.4.1: GSM modem (1-port) converter now attached to ttyUSB0
[  684.552284] option 1-2.4.1:1.3: GSM modem (1-port) converter detected
[  684.552674] usb 1-2.4.1: GSM modem (1-port) converter now attached to ttyUSB1
[  684.552885] option 1-2.4.1:1.4: GSM modem (1-port) converter detected
[  684.553166] usb 1-2.4.1: GSM modem (1-port) converter now attached to ttyUSB2
[  684.553391] option 1-2.4.1:1.5: GSM modem (1-port) converter detected
[  684.553731] usb 1-2.4.1: GSM modem (1-port) converter now attached to ttyUSB3
[  684.554221] option 1-2.4.1:1.6: GSM modem (1-port) converter detected
[  684.554656] usb 1-2.4.1: GSM modem (1-port) converter now attached to ttyUSB4
[  684.675578] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready

it’s same as before.

DaneLLL · December 30, 2020, 11:15pm

Hi,
It looks like the error is not seen:

[  313.765620] usb 1-2.4: device not accepting address 6, error -71

You probably need to apply the patch like this:
Jetson/L4T/r32.3.x patches - eLinux.org
USB tethering does not work

Add the device into the list for enabling USB tethering.

suen · December 31, 2020, 1:18am

i have apply the patch and update the Image:

root@nvidia-desktop:/home/nvidia# dmesg --follow
[  934.998424] usb 1-2.4: new full-speed USB device number 6 using tegra-xusb
[  935.018918] usb 1-2.4: not running at top speed; connect to a high speed hub
[  935.019628] usb 1-2.4: New USB device found, idVendor=1782, idProduct=4d00
[  935.019638] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  935.019645] usb 1-2.4: Product: Gadget Serial
[  935.019651] usb 1-2.4: Manufacturer: spreadtrum with dwc3-gadget
[  938.361126] usb 1-2.4: USB disconnect, device number 6
[  950.101409] usb 1-2.4: new high-speed USB device number 7 using tegra-xusb
[  950.130642] usb 1-2.4: New USB device found, idVendor=2949, idProduct=8800
[  950.130655] usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  950.130662] usb 1-2.4: Product: N510M
[  950.130693] usb 1-2.4: Manufacturer: Neoway
[  950.130699] usb 1-2.4: SerialNumber: 92718392204285
[  950.218946] rndis_host 1-2.4:1.0 usb1: register 'rndis_host' at usb-3610000.xhci-2.4, RNDIS device, d2:66:73:60:c7:bd
[  950.219564] option 1-2.4:1.2: GSM modem (1-port) converter detected
[  950.219816] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB0
[  950.220027] option 1-2.4:1.3: GSM modem (1-port) converter detected
[  950.220294] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB1
[  950.220527] option 1-2.4:1.4: GSM modem (1-port) converter detected
[  950.220789] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB2
[  950.220960] option 1-2.4:1.5: GSM modem (1-port) converter detected
[  950.221188] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB3
[  950.221636] option 1-2.4:1.6: GSM modem (1-port) converter detected
[  950.222014] usb 1-2.4: GSM modem (1-port) converter now attached to ttyUSB4
[  950.347252] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready

but still can not work.

DaneLLL · December 31, 2020, 1:45am

Hi,
Looks like the device is detected:

[  950.218946] rndis_host 1-2.4:1.0 usb1: register 'rndis_host' at usb-3610000.xhci-2.4, RNDIS device, d2:66:73:60:c7:bd

You should see it present in ifconfig and can access internet after executing sudo dhclient DEVICE_NAME.

suen · December 31, 2020, 2:00am

yes the usb ethernet can be detected,but the usbserial has no reply.

root@nvidia-desktop:/home/nvidia# ls /dev/ttyUSB*
/dev/ttyUSB0  /dev/ttyUSB1  /dev/ttyUSB2  /dev/ttyUSB3  /dev/ttyUSB4

ttyUSB2 is usbserial for AT command,but usb serial has no replay.

DaneLLL · December 31, 2020, 3:14am

Hi,
Probably it requires additional driver. Could you check with the vendor?

Maybe need to enable

USB driver for GSM and CDMA modems （CONFIG_USB_SERIAL_OPTION=y）

There is a public N720 pdf mentioning this:
Testing At Commands - Neoway N720 User Manual [Page 9] | ManualsLib
Might be similar to N510M.

suen · December 31, 2020, 3:22am

I have checked with the FAE,just enable the COMFIG_USB_SERIAL_OPTION=y,then will get devices:ttyUSB0~4,and ttyUSB2 is usbserial for AT command,but there is no replay when i type AT command.
but it works well when i plug the EVM to Host PC(Linux 4.15.0-128-generic #131~16.04.1-Ubuntu )

DaneLLL · January 4, 2021, 2:38am

Hi,
Looks like the host PC is K4.15. Probably CONFIG_USB_SERIAL_OPTION=y is required for K4.9?

suen · January 4, 2021, 4:20am

yes,i have enabled the config,COMFIG_USB_SERIAL_OPTION=y

DaneLLL · January 5, 2021, 2:34am

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Hi,
Since the device is detected and enumerated, it is more like an issue that certain driver is missing.

We don’t have experience in the case, could you share information about there is no reply when i type AT command? What command is executed and what reply is expected?