# VOXL2 USB Host Port J18 Not initializing Source: https://forum.modalai.com/topic/5240/voxl2-usb-host-port-j18-not-initializing Category: General Questions (https://forum.modalai.com/category/2/general-questions) Posted: 2026-06-04 00:12:46 UTC by nickanick Replies: 8 · Views: 744 ## nickanick · 2026-06-04 00:12:46 UTC We bought the parts to build our own Blue UAS drone. When trying to connect the Wifi dongle (AWUS036ACS) using the MCBL-00009-01 cable in the VOXL 2 port J18, nothing is shown in lsusb. voxl-suite version 1.6.3 kernel 4.19.125 Error message dmesg | grep -i -B2 -A8 ssusb [ 1.862118] msm-usb-hsphy 88e4000.hsphy: Linked as a consumer to regulator.10 [ 1.862129] msm-usb-hsphy 88e4000.hsphy: Linked as a consumer to regulator.21 [ 1.862704] msm-dwc3 a600000.ssusb: Linked as a consumer to 15000000.apps-smmu [ 1.862915] iommu: Adding device a600000.ssusb to group 13 [ 1.863060] msm-dwc3 a600000.ssusb: Linked as a consumer to regulator.66 [ 1.863558] dwc3 a600000.dwc3: Failed to get clk 'ref': -2 [ 1.863615] dwc3 a600000.dwc3: changing max_speed on rev 00000000 [ 1.864445] msm-dwc3 a600000.ssusb: unable to get ssphy device [ 1.865469] msm-dwc3 a600000.ssusb: Dropping the link to regulator.66 [ 1.865524] msm-dwc3 a800000.ssusb: Linked as a consumer to 15000000.apps-smmu [ 1.865730] iommu: Adding device a800000.ssusb to group 14 [ 1.865884] msm-dwc3 a800000.ssusb: Linked as a consumer to regulator.67 [ 1.866435] dwc3 a800000.dwc3: Failed to get clk 'ref': -2 [ 1.866578] register_client_adhoc:find path.src 101 dest 512 [ 1.866718] register_client_adhoc:find path.src 101 dest 676 [ 1.866828] register_client_adhoc:find path.src 1 dest 751 [ 1.866893] register_client_adhoc:Client handle 36 usb1 [ 1.867145] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.867149] ehci-pci: EHCI PCI platform driver [ 1.867158] ehci-platform: EHCI generic platform driver -- [ 1.869969] i2c_geni a88000.i2c: Bus frequency is set to 400000Hz [ 1.870203] i2c_geni 884000.i2c: Bus frequency is set to 400000Hz [ 1.875097] ssusb redriver 3-001c: Could not get usb power_supply [ 1.875103] ssusb redriver 3-001c: failed to get phandle for redriver [ 1.875396] i2c_geni 884000.i2c: i2c error :-107 [ 1.875491] i2c_geni 884000.i2c: i2c error :-107 [ 1.875584] i2c_geni 884000.i2c: i2c error :-107 [ 1.875678] i2c_geni 884000.i2c: i2c error :-107 [ 1.875681] I2C PMIC: i2c_pmic_read: i2c_pmic_read failed for 3 retries, rc = -107 [ 1.875683] I2C PMIC: i2c_pmic_determine_initial_status: Couldn't read irq data rc=-107 [ 1.875686] I2C PMIC: i2c_pmic_probe: Couldn't determine initial status rc=-107 [ 1.875699] i2c_pmic: probe of 3-0010 failed with error -107 -- [ 1.924143] register_client_adhoc:Client handle 57 cam_ahb [ 1.924194] register_client_adhoc:find path.src 170 dest 512 [ 1.924203] msm-dwc3 a800000.ssusb: DWC3 exited from low power mode [ 1.924258] register_client_adhoc:Client handle 58 cam_hf_0_mnoc [ 1.924310] register_client_adhoc:find path.src 137 dest 512 [ 1.924371] register_client_adhoc:Client handle 59 cam_sf_0_mnoc [ 1.924417] register_client_adhoc:find path.src 171 dest 512 [ 1.924449] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.924474] register_client_adhoc:Client handle 60 cam_sf_icp_mnoc [ 1.924479] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [ 1.924696] xhci-hcd xhci-hcd.0.auto: hcc params 0x0230ffe5 hci version 0x110 quirks 0x0000000000010810 -- [ 1.962399] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.18 [ 1.962410] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.32 [ 1.962484] msm-dwc3 a600000.ssusb: Linked as a consumer to regulator.66 [ 1.962839] dwc3 a600000.dwc3: Failed to get clk 'ref': -2 [ 1.962874] dwc3 a600000.dwc3: changing max_speed on rev 00000000 [ 1.963402] usb_bam_init: setting SPS_BAM_SMMU_EN flag with (a704000.qcom,usbbam) [ 1.963465] sps:BAM 0x000000000a704000 is registered. [ 1.963510] msm-dwc3 a600000.ssusb: unable to get ssphy device [ 1.964159] msm-dwc3 a600000.ssusb: Dropping the link to regulator.66 [ 1.964223] qpnp-pdphy c440000.qcom,spmi:qcom,pm8150b@2:qcom,usb-pdphy@1700: Linked as a consumer to regulator.10 [ 1.964711] qpnp-pdphy c440000.qcom,spmi:qcom,pm8150b@2:qcom,usb-pdphy@1700: usbpd_create failed: -517 [ 1.964765] qpnp-pdphy c440000.qcom,spmi:qcom,pm8150b@2:qcom,usb-pdphy@1700: Dropping the link to regulator.10 [ 1.964834] qcom,haptics c440000.qcom,spmi:qcom,pm8150b@3:qcom,haptics@c000: Linked as a consumer to regulator.89 [ 1.965191] input: qti-haptics as /devices/platform/soc/c440000.qcom,spmi/spmi-0/spmi0-03/c440000.qcom,spmi:qcom,pm8150b@3:qcom,haptics@c000/input/input2 [ 1.969082] ufshcd-qcom 1d84000.ufshc: ufshcd_needs_reinit: Re-init UFS host to use proper PHY settings for the UFS device. This can be avoided by setting the force-g4 in DT [ 1.969742] ssusb redriver 3-001c: Could not get usb power_supply [ 1.969746] ssusb redriver 3-001c: failed to get phandle for redriver [ 1.971209] Input suspended: Fake battery [ 1.971249] qcom,qpnp-smb5 c440000.qcom,spmi:qcom,pm8150b@2:qcom,qpnp-smb5: Linked as a consumer to regulator.86 [ 1.973079] of_batterydata_get_best_profile: No battery data found [ 1.973102] pm8150b_charger: jeita_update_work: Incorrect fastchg-current-ma or max-voltage-uv [ 1.979101] SMB5 status - usb:present=0 type=0 batt:present = 1 health = 1 charge = 1 [ 1.979118] QPNP SMB5 probed successfully [ 1.984394] Error registering TZ zone:-19 for dt_ch:77 [ 1.987232] Error registering TZ zone:-19 for dt_ch:77 -- [ 1.991538] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.18 [ 1.991547] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.32 [ 1.991616] msm-dwc3 a600000.ssusb: Linked as a consumer to regulator.66 [ 1.991965] dwc3 a600000.dwc3: Failed to get clk 'ref': -2 [ 1.991997] dwc3 a600000.dwc3: changing max_speed on rev 00000000 [ 1.992493] usb_bam_init: setting SPS_BAM_SMMU_EN flag with (a704000.qcom,usbbam) [ 1.992545] sps:BAM 0x000000000a704000 is registered. [ 1.992586] msm-dwc3 a600000.ssusb: unable to get ssphy device [ 1.993223] msm-dwc3 a600000.ssusb: Dropping the link to regulator.66 [ 1.993290] qpnp-pdphy c440000.qcom,spmi:qcom,pm8150b@2:qcom,usb-pdphy@1700: Linked as a consumer to regulator.10 [ 1.994031] i2c_geni 884000.i2c: i2c error :-107 [ 1.994117] i2c_geni 884000.i2c: i2c error :-107 [ 1.994202] i2c_geni 884000.i2c: i2c error :-107 [ 1.994287] i2c_geni 884000.i2c: i2c error :-107 [ 1.994372] i2c_geni 884000.i2c: i2c error :-107 [ 1.994457] i2c_geni 884000.i2c: i2c error :-107 [ 1.994541] i2c_geni 884000.i2c: i2c error :-107 -- [ 1.999438] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.18 [ 1.999442] msm-usb-ssphy-qmp 88e8000.ssphy: No separate ID extcon device [ 1.999485] msm-dwc3 a600000.ssusb: Linked as a consumer to regulator.66 [ 1.999803] dwc3 a600000.dwc3: Failed to get clk 'ref': -2 [ 1.999828] dwc3 a600000.dwc3: changing max_speed on rev 00000000 [ 2.000352] usb_bam_init: setting SPS_BAM_SMMU_EN flag with (a704000.qcom,usbbam) [ 2.000397] sps:BAM 0x000000000a704000 is registered. [ 2.000458] register_client_adhoc:find path.src 61 dest 512 [ 2.000574] register_client_adhoc:find path.src 61 dest 676 [ 2.000679] register_client_adhoc:find path.src 1 dest 583 [ 2.000742] register_client_adhoc:Client handle 63 usb0 [ 2.000777] msm-dwc3 a600000.ssusb: Linked as a consumer to regulator.86 [ 2.000925] core_ctl: Creating CPU group 0 [ 2.000928] core_ctl: Init CPU0 state [ 2.000930] core_ctl: Init CPU1 state [ 2.000931] core_ctl: Init CPU2 state [ 2.000932] core_ctl: Init CPU3 state [ 2.000997] core_ctl: Creating CPU group 4 [ 2.000999] core_ctl: Init CPU4 state [ 2.001000] core_ctl: Init CPU5 state -- [ 2.045080] ALSA device list: [ 2.045082] No soundcards found. [ 2.060174] msm-dwc3 a600000.ssusb: DWC3 exited from low power mode [ 2.060764] msm-dwc3 a600000.ssusb: DWC3 in low power mode [ 2.063630] ufshcd-qcom 1d84000.ufshc: ufshcd_print_pwr_info:[RX, TX]: gear=[4, 4], lane[2, 2], pwr[FAST MODE, FAST MODE], rate = 1 [ 2.067524] ufshcd-qcom 1d84000.ufshc: ufshcd_wb_config: Write Booster Configured [ 2.068150] scsi 0:0:0:49488: Well-known LUN KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 [ 2.069714] scsi 0:0:0:49476: Well-known LUN KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 [ 2.070390] scsi 0:0:0:49456: Well-known LUN KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 [ 2.079698] scsi 0:0:0:0: Direct-Access KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 [ 2.081517] scsi 0:0:0:1: Direct-Access KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 [ 2.083544] scsi 0:0:0:2: Direct-Access KINGSTON CY14-128 0002 PQ: 0 ANSI: 6 -- [ 2.727663] kona-pinctrl f000000.pinctrl: invalid function func2 in map table [ 3.130934] msm-usb-ssphy-qmp 88e8000.ssphy: USB DP QMP PHY: Update TYPEC CTRL(2) [ 3.188278] msm-dwc3 a600000.ssusb: DWC3 exited from low power mode [ 3.968038] of_batterydata_get_best_profile: No battery data found [ 3.968047] QCOM-STEPCHG: get_step_chg_jeita_setting_from_profile: Couldn't find profile [ 4.740943] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! [ 4.741012] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! [ 4.741615] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! [ 4.746196] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! [ 4.749797] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! [ 4.750167] ufshcd-qcom 1d84000.ufshc: ufshcd_ioctl: User buffer is NULL! Please assist. ## Reply by nickanick · 2026-06-04 14:37:19 UTC @nickanick Do I need the VOXL 2 WiFi Add-on and I/O Breakout to use the WIFI Dongle? ## Reply by nickanick · 2026-06-04 14:50:16 UTC Second question: Can I use the USB to connect to QGroundControl instead? ## Reply by Eric Katzfey (ModalAI staff) · 2026-06-04 16:29:29 UTC (in reply to nickanick) @nickanick It's best if you ask each question in a separate post. For QGC over the ADB USB: https://docs.modalai.com/qgc-via-adb/ ## Reply by nickanick · 2026-06-04 19:50:06 UTC (in reply to Eric Katzfey) @Eric-Katzfey Thanks Eric. I have posted the WIFI Dongle question in another post. ## Reply by nickanick · 2026-06-04 20:16:08 UTC (in reply to Eric Katzfey) @Eric-Katzfey can use the VOXL2 USB-C port to connect to QGroundControl, or do I need an extra component? ## Reply by Eric Katzfey (ModalAI staff) · 2026-06-04 20:49:02 UTC (in reply to nickanick) @nickanick That was what I responded with previously. Did that documentation not address your question? ## Reply by nickanick · 2026-06-05 01:32:30 UTC (in reply to Eric Katzfey) @Eric-Katzfey Appreciate your help! ## Reply by nickanick · 2026-06-10 04:42:14 UTC (in reply to Eric Katzfey) @Eric-Katzfey We are experiencing connection issues between VOXL2 and QGC. QGroundControl is showing disconnected after inputting the comms link with 192.168.7.2:14550 in UDP. mavlink_to_gcs and mavlink_from_gcs are both reporting data. voxl-px4 and voxl-mavlink-server are running. voxl-my-ip 192.168.7.2 (usb0)