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

    Quectel-CM error when Initializing a connection (SDK 1.5.0)

    Ask your questions right here!
    1
    2
    26
    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.
    • Matthew WellnerM
      Matthew Wellner
      last edited by

      Hi!

      I just updated to the newest VOXL SDK (1.5.0) to get support for the Hadron and Boson cameras and after the flash my Quectel 5G modem will no longer get an IP address from the cellular network. I ran through voxl-configure-modem again and I also ran the voxel-modem-start command manually. When I run voxel-modem-start manually, I get this error:

      qrb5165 based hardware detected...
      \Setting mode preference to LTE / 5G
      AT+QNWPREFCFG="mode_pref",LTE:NR5G
      OK
      
      Initalizing cellular connection...
      /usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error
      /usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error
      /usr/bin/voxl-modem-start: line 84: /usr/bin/quectel-CM: cannot execute binary file: Exec format error
      

      If I run "file /usr/bin/quectel-CM", I get this:

      /usr/bin/quectel-CM: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=22bb006a724be58f44e4eb6b7ed46f859144f314, for GNU/Linux 3.2.0, stripped
      

      Isn't this supposed to be "ARM aarch64"? I'm going to try copying the quectel-CM from a previous release to see if that fixes my issue, but let me know.

      1 Reply Last reply Reply Quote 0
      • Matthew WellnerM
        Matthew Wellner
        last edited by

        I grabbed the /usr/bin/quectel-CM from another VOXL2 on an older SDK (1.4.1) and swapped out the one that came with 1.5.0 and everything is working again...

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Powered by NodeBB | Contributors