Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

L

linus777

@linus777
Unfollow Follow
About
Posts
7
Topics
5
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • USB network interface
    L linus777

    I'm trying to communicate between Voxl2 and Voxl2 mini via USB by using the USB network interface. However, when I use the command below, the g_ether.ko module is not found. I want to know what options I should include when building the kernel.

    e0e32a43-1472-4e9a-93ec-fd107d4d27fc-image.png

    Looking forward to a quick answer.
    Thanks,
    Linus

    Ask your questions right here! missing gether

  • MSU-M0107 IMX412 I2C address selection
    L linus777

    @Alex-Kushleyev
    Please, see below.

    The M0061 had an I2C address selection pin.

    Thanks,
    Linus

    ffa6d782-5482-4ead-bbb6-d2f6b327ec30-image.png

    Image Sensors

  • MSU-M0107 IMX412 I2C address selection
    L linus777

    Is there an option on the board to change I2C address selection? If so, how can I change it?

    797c93a2-57a1-4e5a-91d0-aa39c707b722-image.png

    Image Sensors

  • MSU-M0107 IMX412 I2C address selection
    L linus777

    Is there an option on the board to change I2C address selection? If so, how can I change it?

    2dc6156a-bb9d-483b-8684-e0dbf0108c73-image.png

    Ask your questions right here!

  • 5G Quectel modem device-initiated U1 failed.
    L linus777

    Hello,

    Please analyze this issue.
    It seems like the usb device initialization failed.

    voxl2:/$ lsusb
    Bus 002 Device 003: ID 2c7c:0800
    Bus 002 Device 002: ID 0424:5744 Standard Microsystems Corp.
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 0424:2740 Standard Microsystems Corp.
    Bus 001 Device 002: ID 0424:2744 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    Please, see below syslog.
    [ 12.409758] usb 2-1.1: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
    [ 12.428493] usb 2-1.1: New USB device found, idVendor=2c7c, idProduct=0800, bcdDevice= 4.14
    [ 12.428509] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 12.428558] usb 2-1.1: Product: RM502Q-AE
    [ 12.428568] usb 2-1.1: Manufacturer: Quectel
    [ 12.428576] usb 2-1.1: SerialNumber: c647888b
    [ 12.610617] usb 2-1.1: Enable of device-initiated U1 failed.
    [ 12.677598] usb 2-1.1: Enable of device-initiated U2 failed.
    [ 12.706636] option 2-1.1:1.0: GSM modem (1-port) converter detected
    [ 12.707026] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB0
    [ 12.707447] option 2-1.1:1.2: GSM modem (1-port) converter detected
    [ 12.708677] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB1
    [ 12.708999] option 2-1.1:1.3: GSM modem (1-port) converter detected
    [ 12.710240] usb 2-1.1: GSM modem (1-port) converter now attached to ttyUSB2
    [ 12.772496] qmi_wwan 2-1.1:1.4: cdc-wdm0: USB WDM device
    [ 12.773496] qmi_wwan 2-1.1:1.4: Quectel EC25&EC21&EG91&EG95&EG06&EP06&EM06&BG96&AG35 work on RawIP mode
    [ 12.774739] qmi_wwan 2-1.1:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1.1, WWAN/QMI device, fa:7d:65:32:e0:aa
    [ 12.802569] usb 2-1.1: Enable of device-initiated U1 failed.
    [ 12.870466] usb 2-1.1: Enable of device-initiated U2 failed.

    voxl2:/etc$ systemctl status -l voxl-modem
    ● voxl-modem.service - Modem Initialization
    Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2023-03-02 12:58:06 UTC; 1min 9s ago
    Process: 1360 ExecStartPre=/bin/sleep 2 (code=exited, status=0/SUCCESS)
    Main PID: 1842 (voxl-modem-star)
    Tasks: 3 (limit: 4915)
    CGroup: /system.slice/voxl-modem.service
    ├─1842 /bin/bash /usr/bin/voxl-modem-start
    └─3820 quectel-CM -s 5g.vodafone.iot

    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:883] network interface '' or qmidev '' is not exist
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:883] qmidevice_detect failed
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:885] Quectel_QConnectManager_Linux_V1.6.0.24
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:886] network interface '' or qmidev '' is not exist
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:886] qmidevice_detect failed
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:887] Quectel_QConnectManager_Linux_V1.6.0.24
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:888] network interface '' or qmidev '' is not exist
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:888] qmidevice_detect failed
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:890] Quectel_QConnectManager_Linux_V1.6.0.24
    Mar 02 12:58:08 m0054 voxl-modem-start[1842]: [03-02_12:58:08:892] network interface '' or qmidev '' is not exist

    In case of LTE modem's lsusb

    voxl2:/etc$ lsusb
    Bus 002 Device 002: ID 0424:5744 Standard Microsystems Corp.
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 0424:2740 Standard Microsystems Corp.
    Bus 001 Device 004: ID 1199:68c0 Sierra Wireless, Inc.
    Bus 001 Device 002: ID 0424:2744 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    voxl2:/$ voxl-version

    system-image: 1.7.6-M0054-14.1a-perf
    kernel: #1 SMP PREEMPT Wed Mar 20 19:48:52 UTC 2024 4.19.125

    hw platform: M0054
    mach.var: 1.0

    voxl-suite: 1.2.0

    Thanks,
    Linus

    Cellular Modems

  • Recording and Receiving Videos
    L linus777

    @WineVirus
    @Moderator What part do I need to modify to automatically save it to the QGC area?

    Ask your questions right here!

  • How to bring-up new camera module.
    L linus777

    I'm developing OV64B camera module which was provided by the FLIR for the RB5.The com.qti.sensormodule.sunny_ov64b40.bin and com.qti.sensor.ov64b40.so are build in qrb5165-ubun-1-0_amss_oem-r00023.1 release.
    I want to know how to integrate this module in the VOXL SDK(voxl-camera-server and voxl-configure-cameras).
    Is it possible to release the VOXL2 Platform which are included with RB5 system image and VOXL SDK integrated in OV64B?

    Thanks,
    Linus

    Feature Requests camera module
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups