Apalis TK1 USB RNDIS Not Enumerating

Technical Support
, , ,
1

I’ve updated my Linux kernel sources to 2.7b2 and I’ve now discovered that the USB fails to enumerate as an RNDIS device when connected to the USBO1 OTG port. This has previously been working very well until just upgrading to the 2.72b sources.

Has anything changed around this area? I also no longer seen any kernel messages showing the USB bus going from SUSPEND → PERIPHERAL mode.

I can confirm the USB device is configured correctly and enabled.

2

I’m not aware of any changes in that area of late. At least with stock 2.7b2 that works just fine:

root@apalis-tk1:~# dmesg | grep android
[    6.111635] android_usb gadget: Mass Storage Function, version: 2009/09/11
[    6.121635] android_usb gadget: Number of LUNs=1
[    6.137671] android_maxim14675_set_voltage: max_voltage (vbus) = 5000
[    6.147234] android_usb gadget: android_usb ready
[    6.155034] tegra-udc: bind to driver android_usb
[    8.795720] android_usb: already disabled
[    8.818301] android_usb gadget: using random self ethernet address
[    8.831273] android_usb gadget: using random host ethernet address
[    9.011152] android_work: did not send uevent (0 0   (null))
[    9.073759] android_work: sent uevent USB_STATE=CONNECTED
[    9.081236] android_work: sent uevent USB_STATE=DISCONNECTED
[    9.156013] android_usb gadget: high-speed config #1: android
[    9.199915] android_work: sent uevent USB_STATE=CONNECTED
[    9.216149] android_work: sent uevent USB_STATE=CONFIGURED
root@apalis-tk1:~# ip addr show rndis0
6: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2a:6e:b6:94:99:f2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 brd 192.168.11.255 scope global rndis0
       valid_lft forever preferred_lft forever
    inet6 fe80::286e:b6ff:fe94:99f2/64 scope link 
       valid_lft forever preferred_lft forever
3

If you’re using ixora make sure that there is no jumper on JP2.

4

Hmm, that’s strange. I downloaded stock 2.7b2 but tweaked the kernel to for ADV7280 and also compiled the Wi-Fi backports modules. No changes to USB subsystems were made. I will check on Wednesday when I’m back in the office but I find it odd that I don’t get any USB enumeration messages - even for failure events.

5

Using our own custom carrier board. To confirm though, USB RNDIS has been working perfectly on other builds on our board, moving to 2.7b2 seems to have broken something.

6

Hi @marcel.tx, I’ve just tried the USB again and still, I am not able to access the TK1 via RNDIS:

root@apalis-tk1:~# dmesg | grep android
[    5.578431] android_usb gadget: Mass Storage Function, version: 2009/09/11
[    5.586651] android_usb gadget: Number of LUNs=1
[    5.598949] android_maxim14675_set_voltage: max_voltage (vbus) = 5000
[    5.606635] android_usb gadget: android_usb ready
[    5.612559] tegra-udc: bind to driver android_usb
[    9.591919] android_usb: already disabled
[    9.610306] android_usb gadget: using random self ethernet address
[    9.621122] android_usb gadget: using random host ethernet address
root@apalis-tk1:~# ip addr show rndis0
7: rndis0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether fa:c6:60:78:6d:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 brd 192.168.11.255 scope global rndis0
       valid_lft forever preferred_lft forever
root@apalis-tk1:~#
7

Can you please provide full boot log of this. Plus maybe you could test the same module on an Ixora as well just to make sure it would work with RNDIS there.