ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Trouble with EM7565 startup...

    Ask your questions right here!
    3
    24
    1424
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Ed SutterE
      Ed Sutter @tom
      last edited by

      @tom One thing I just noticed...
      If I boot up without an LTE modem, then /etc/resolv.conf is:

      # Generated by dhcpcd from wlan0
      # /etc/resolv.conf.head can replace this line
      domain myfiosgateway.com
      nameserver 192.168.1.1
      # /etc/resolv.conf.tail can replace this line
      

      That (above) makes sense. That's my ISP (Fios) and wifi subnet in my home.
      If I boot up with the LTE modem, then /etc/resolve.conf is:

      nameserver 172.26.38.1
      

      Looks like something in the modem startup overwrites /etc/resolv.conf. The script "enable-dns.sh" is called by voxl-modem-start.sh, but it only writes to /etc/resolve.conf if it doesn't already exist (plus it writes 8.8.8.8, which apparently is Google dns).
      Any idea how this is being written?

      1 Reply Last reply Reply Quote 0
      • Ed SutterE
        Ed Sutter @tom
        last edited by

        @tom I'm starting a new thread on this...

        1 Reply Last reply Reply Quote 0
        • Ed SutterE
          Ed Sutter @Eric Katzfey
          last edited by Ed Sutter

          @Eric-Katzfey Somehow this slipped through the cracks... I just looked in that file and I don't see the VID/PID of the EM7565 listed. So a couple of questions:

          1. What does this mean?
          2. Do you know what is involved in getting it listed?

          I have the latest driver files from Sierra Wireless, and they do have what I need. Is this a module that I can update on VOXL?
          Ed

          1 Reply Last reply Reply Quote 0
          • Ed SutterE
            Ed Sutter @Eric Katzfey
            last edited by

            @Eric-Katzfey @tom Digging a bit deeper into this, I see that the voxl-build procedure does patch the qmi_wwan.c file, and after the patch, the VID/PID for EM7565 is in there. On one hand this is good news because it implies that the kernel does have support for the modem I'm trying to use; however, its not-so-good news for me because running with that modem has not reliable on VOXL. 😞
            Aside from verifying that I am actually running the same version on my VOXL-Flight-Deck as is being built in voxl-build (see below), I'm at a loss regarding other things to do to debug this. Any thoughts on this?
            Following is the output of voxl-version on my board:

            / # voxl-version
            cat: /etc/modalai/voxl-software-bundle-version.txt: No such file or directory
            --------------------------------------------------------------------------------
            system-image:    ModalAI 3.3.0 BUILDER: ekatzfey BUILD_TIME: 2021-06-06_19:28
            kernel:          #1 SMP PREEMPT Sun Jun 6 19:41:01 UTC 2021 3.18.71-perf
            factory-bundle:  1.0.1 (Yocto installation)
            --------------------------------------------------------------------------------
            architecture:    aarch64
            processor:       apq8096
            os:              GNU/Linux
            --------------------------------------------------------------------------------
            voxl-suite:
            Package: voxl-suite
            Version: 0.5.0
            Depends: libjpeg_turbo (>= 9.0.4), libmodal_exposure (>= 0.0.2), libmodal_json (>= 0.3.6), libmodal_pipe (>= 2.1.1), lib
            rc_math (>= 1.1.5), libvoxl_cutils (>= 0.0.2), libvoxl_io (>= 0.5.4), mavlink-camera-manager (>= 0.0.2), mongoose (>= 7.
            3.0), opencv (>= 4.5.2-2), openmp (>= 10.0.2), voxl-camera-calibration (>= 0.1.1), voxl-camera-server (>= 0.8.1), voxl-c
            pu-monitor (>= 0.2.0), voxl-dfs-server (>= 0.2.2), voxl-docker-support (>= 1.1.3), voxl-gphoto2 (>= 0.0.5), voxl-imu-ser
            ver (>= 0.9.1), voxl-mavlink (>= 0.0.2), voxl-modem (>= 0.12.0), voxl-mpa-tools (>= 0.3.6), voxl-nodes (>= 0.2.0), voxl-
            portal (>= 0.1.2), voxl-qvio-server (>= 0.3.4), voxl-streamer (>= 0.2.6), voxl-tag-detector (>= 0.0.2), voxl-tflite (>=
            2.2.3), voxl-tflite-server (>= 0.1.5), voxl-utils (>= 0.8.4), voxl-vision-px4 (>= 0.9.5), voxl-vpn (>= 0.0.3)
            Status: install user installed
            Section: base
            Architecture: all
            Maintainer: james@modalai.com
            MD5Sum: 172dd2541a4b01ec415651b5ded3afab
            Size: 1956
            Filename: voxl-suite_0.5.0_202111041852.ipk
            Description: meta-package for voxl-suite software collection
            Installed-Time: 144
            
            --------------------------------------------------------------------------------
            
            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Powered by NodeBB | Contributors