Communication error "can't set config #1, error -32" (USB) when plugging in nrf52840 dongle (PCA10059) into nvidia xavier

[A.St.]

Hi,

as stated in the title, we have a nrf52840 dongle (PCA10059) which does not come up normally on a Nvidia xavier devboard. Output of dmesg:

[  112.940331] usb 1-3.1: New USB device found, idVendor=1915, idProduct=c00a
[  112.940335] usb 1-3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  112.940338] usb 1-3.1: Product: nRF52 Connectivity
[  112.940341] usb 1-3.1: Manufacturer: Nordic Semiconductor
[  112.940343] usb 1-3.1: SerialNumber: EE54BF5A789B
[ 112.948394] usb 1-3.1: can't set config #1, error -32

We tried different OS and SW (bootloader/softdevice/application) versions all with the same outcome.

After a lot of testing and tracing we found out, that when we pull out the usb-dongle ot of the usb-socket just that far that the power-pins are still connected and only the connection-pins are disconnected and then plug it back, the device will be detected just fine. Also when using a external usb-hub it will come up normally.

So it seems the problem comes from a timing issue between the xavier-usb (tegra-xusb) driver and the dongle. Probably the dongle delivers the usb-config too slow so that the kernel has no config to select the further loading of cdc_acm.

Is there anything we can do in the bootloader/softdevice/app to somehow fix this problem, so that no external usb-hub is needed?

[ovrebekk]

Hi 

This is not an known issue, but we haven't done any testing on this platform either. I assume you don't have this issue on a regular PC platform?

Do you have any means to sniff the USB communication between the dongle and the Nvidia host, so you can see what is going on?

Best regards
Torbjørn

[A.St.]

Hi Torbjørn,

we've send you a PM regarding USB sniffing.

We also posted this problem on the nvidia forums, where they asked if the device (the dongle) has a USB compliance test, see https://developer.nvidia.com/embedded/dlc/agx-xavier-3-1-compliance-test-guide

Has it?

[ovrebekk]

Hi

As I mentioned in the message it should be possible to drag drop attachments into your reply. 

In the mean time I will check what USB compliance testing we have done for the dongle. 

Best regards
Torbjørn

[A.St.]

Hi,

sent you the USB sniff, any updates?

[ovrebekk]

Hi

Is there anything happening in the application startup sequence that could delay the processing of USB events?

I assume the USB events are polled from the main loop, like in most of the standard examples?

Talking of standard examples, have you tried the CDC ACM example unmodified to see if it exhibits the same issue?

Do you have an nRF52840DK to test with, to see if the issue is the same?

Best regards
Torbjørn

[A.St.]

Hi,

we are flashing the softdevice and app from here https://github.com/NordicSemiconductor/pc-ble-driver/tree/v4.0.0/hex/sd_api_v6 (note: we currently have to use tag v4.0.0). If i recall correctly we flash "s140_nrf52_6.1.0_softdevice.hex" and "connectivity_4.0.0_usb_for_s140_6.1.0.hex" when flashing with jtag and "connectivity_4.0.0_usb_with_s140_6.1.0_dfu_pkg.zip" when flashing with nrfutil. But no matter what method we use (jtag or nrfutil) the problem is the same.

Unfortunately we dont have the nRF52840DK but we have a dongle and a custom board with two bt-chips and a usb-hub where both (dongle and custom) have the same behavior.

Best regards,

[ovrebekk]

Hi 

Any chance you could try the latest version of the connectivity example, available in SDK v17.1.0? 

I have included the precompiled hex below:

ble_connectivity_s140_usb_hci_pca10059.hex

6165.s140_nrf52_7.2.0_softdevice.hex

Best regards
Torbjørn

[A.St.]

Hi,

currently i cant flash the device with a JTAG-device. Is it possible to get those two files as a .zip file so that i can flash it with nrfutil?

For testing purposes i flashed the latest .zip from here https://github.com/NordicSemiconductor/pc-ble-driver/blob/v4.1.4-hex/hex/sd_api_v6/connectivity_4.1.4_usb_with_s140_6.1.1_dfu_pkg.zip but this already ended in the same config error.