beaglebone and R404


#1

I’m having an issue with getting the R404 Nova to work on beaglebone. With the following at startup:

[ 17.151707] usb0: HOST MAC f4:5e:ab:f8:f6:7e
[ 17.156082] usb0: MAC f4:5e:ab:f8:f6:7f
[ 17.167160] usb1: HOST MAC f4:5e:ab:f8:f6:81
[ 17.168118] usb1: MAC f4:5e:ab:f8:f6:82
[ 17.463661] configfs-gadget gadget: high-speed config #1: c
[ 17.848108] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 18.035743] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 18.189402] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[ 19.630510] usbcore: registered new interface driver usbserial
[ 19.630597] usbcore: registered new interface driver usbserial_generic
[ 19.630665] usbserial: USB Serial support registered for generic
[ 20.056070] usbcore: registered new interface driver cdc_wdm
[ 20.161548] usbcore: registered new interface driver option
[ 20.161643] usbserial: USB Serial support registered for GSM modem (1-port)
[ 20.162047] option 1-1:1.0: GSM modem (1-port) converter detected
[ 20.199668] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 20.200415] option 1-1:1.2: GSM modem (1-port) converter detected
[ 20.201065] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 20.228068] qmi_wwan 1-1:1.3: cdc-wdm0: USB WDM device
[ 20.249901] qmi_wwan 1-1:1.3 wwan0: register ‘qmi_wwan’ at usb-musb-hdrc.1-1, WWAN/QMI device, c6:97:b8:f1:58:f4
[ 20.250238] usbcore: registered new interface driver qmi_wwan
[ 25.942769] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 28.346221] pruss 4a300000.pruss: creating PRU cores and other child platform devices
[ 28.558364] remoteproc remoteproc1: 4a334000.pru is available
[ 28.558492] pru-rproc 4a334000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
[ 28.583035] remoteproc remoteproc2: 4a338000.pru is available
[ 28.583164] pru-rproc 4a338000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
[ 32.077631] Bluetooth: Core ver 2.22
[ 32.077772] NET: Registered protocol family 31
[ 32.077782] Bluetooth: HCI device and connection manager initialized
[ 32.077813] Bluetooth: HCI socket layer initialized
[ 32.077829] Bluetooth: L2CAP socket layer initialized
[ 32.077880] Bluetooth: SCO socket layer initialized
[ 32.158618] Bluetooth: HCI UART driver ver 2.3
[ 32.158640] Bluetooth: HCI UART protocol H4 registered
[ 32.158646] Bluetooth: HCI UART protocol BCSP registered
[ 32.163703] Bluetooth: HCI UART protocol LL registered
[ 32.163721] Bluetooth: HCI UART protocol ATH3K registered
[ 32.163728] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 32.163734] Bluetooth: HCI UART protocol QCA registered
[ 33.293990] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 33.294008] Bluetooth: BNEP filters: protocol multicast
[ 33.294039] Bluetooth: BNEP socket layer initialized
[ 34.948538] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[ 34.976269] wlcore: loaded
[ 35.451017] wlcore: PHY firmware version: Rev 8.2.0.0.236
[ 35.468648] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_host (89, <AValid), retry #1, port1 00000507
[ 35.495308] wlcore: firmware booted (Rev 8.9.0.0.69)
[ 35.516950] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 35.641365] usb 1-1: USB disconnect, device number 3
[ 35.643152] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[ 35.644459] option 1-1:1.0: device disconnected
[ 35.652173] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[ 35.652377] option 1-1:1.2: device disconnected
[ 35.656138] qmi_wwan 1-1:1.3 wwan0: unregister ‘qmi_wwan’ usb-musb-hdrc.1-1, WWAN/QMI device
[ 35.851832] IPv6: ADDRCONF(NETDEV_UP): SoftAp0: link is not ready
[ 35.955565] usb 1-1: new high-speed USB device number 4 using musb-hdrc
[ 36.107522] usb 1-1: New USB device found, idVendor=05c6, idProduct=90b2
[ 36.107545] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 36.107554] usb 1-1: Product: Qualcomm CDMA Technologies MSM
[ 36.107561] usb 1-1: Manufacturer: Qualcomm, Incorporated
[ 36.107569] usb 1-1: SerialNumber: 23a5066d
[ 36.110479] option 1-1:1.0: GSM modem (1-port) converter detected
[ 36.111047] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 36.116752] option 1-1:1.2: GSM modem (1-port) converter detected
[ 36.117354] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 36.127042] qmi_wwan 1-1:1.3: cdc-wdm0: USB WDM device
[ 36.131900] qmi_wwan 1-1:1.3 wwan0: register ‘qmi_wwan’ at usb-musb-hdrc.1-1, WWAN/QMI device, c6:97:b8:f1:58:f4
[ 36.151617] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_host (89, <AValid), retry #1, port1 00000507
[ 36.208481] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <AValid), retry #2, port1 00000507
[ 36.260990] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (89, <AValid), retry #3, port1 00000507
[ 36.352670] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_vrise (88, <AValid), retry #3, port1 0008050f
[ 37.101313] wlan0: authenticate with 30:85:a9:e6:c3:78
[ 37.129241] wlan0: send auth to 30:85:a9:e6:c3:78 (try 1/3)
[ 37.155276] wlan0: authenticated
[ 37.167589] wlan0: associate with 30:85:a9:e6:c3:78 (try 1/3)
[ 37.172592] wlan0: RX AssocResp from 30:85:a9:e6:c3:78 (capab=0x411 status=0 aid=7)
[ 37.242278] wlan0: associated
[ 38.138547] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 38.190144] wlcore: Association completed.
[ 39.561811] wlcore: down
[ 39.793793] IPv6: ADDRCONF(NETDEV_CHANGE): SoftAp0: link becomes ready

It looks like it’s connected but there is the VBUS error… It does show the two ttyUSBx in the /dev so maybe the python hologram isn’t reading the modem correct?

Any suggestions on checking it ?

Thanks,
Travis


#2

I figured it out, not enough power to the beaglebone. I used a 12V 2.5A adapter and it’s working now, but I had to unplug it a few times.


#3

Hey @travlytle,

Thanks for the follow up!

We definitely recommend using a power source of at-least 2.4amps when powering a beaglebone, RPI, etc with a Nova.

Cheers,
Maiky


#4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.