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

    How do I issue an AT command (to modem) and get response?

    Ask your questions right here!
    3
    17
    1079
    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 There is definitely different dmesg output when using the two different modems.
      For the RC7611...

      [   19.303681] usb 1-1.1: New USB device found, idVendor=1199, idProduct=68c0
      [   19.303716] usb 1-1.1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
      [   19.303743] usb 1-1.1: Product: Qualcomm CDMA Technologies MSM
      [   19.303766] usb 1-1.1: Manufacturer: Qualcomm, Incorporated
      [   19.303788] usb 1-1.1: SerialNumber: 7e7dbded
      [   19.343459] option 1-1.1:1.0: GSM modem (1-port) converter detected
      [   19.345574] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB0
      [   19.347060] option 1-1.1:1.2: GSM modem (1-port) converter detected
      [   19.349603] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB1
      [   19.351815] option 1-1.1:1.3: GSM modem (1-port) converter detected
      [   19.353829] usb 1-1.1: GSM modem (1-port) converter now attached to ttyUSB2
      [   19.362619] mdss_register_panel: mdss mdp resource not initialized yet
      [   19.362665] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [   19.373309] qmi_wwan 1-1.1:1.8: cdc-wdm0: USB WDM device
      [   19.377024] qmi_wwan 1-1.1:1.8 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1.1, WWAN/QMI device, ffffffc06c1ebd10
      [   19.383161] mdss_register_panel: mdss mdp resource not initialized yet
      [   19.383184] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [   22.285452] usb 1-1.1: USB disconnect, device number 3
      [   22.287788] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
      [   22.287966] option 1-1.1:1.0: device disconnected
      [   22.289656] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
      [   22.289854] option 1-1.1:1.2: device disconnected
      [   22.294800] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
      [   22.295177] option 1-1.1:1.3: device disconnected
      [   22.296485] qmi_wwan 1-1.1:1.8 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.0.auto-1.1, WWAN/QMI device
      [   22.297369] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister wwan0
      [   22.350081] [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister wwan0
      [   24.045813] msm-dwc3 7600000.hsusb: DWC3 in low power mode
      [   30.455740] msm-dwc3 7600000.hsusb: DWC3 exited from low power mode
      [   30.711346] usb 1-1.1: new high-speed USB device number 4 using xhci-hcd
      [   30.812657] usb 1-1.1: config 1 has an invalid interface number: 8 but max is 3
      [   30.812706] usb 1-1.1: config 1 has no interface number 1
      

      then for the EM7565...

      [    3.882936] usb 1-1.2: New USB device found, idVendor=1199, idProduct=9091
      [    3.882948] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [    3.882955] usb 1-1.2: Product: Sierra Wireless EM7565 Qualcomm\xffffffc2\xffffffae Snapdragon\xffffffe2\xffffff84\xffffffa2 X16 LTE-A
      [    3.882961] usb 1-1.2: Manufacturer: Sierra Wireless, Incorporated
      [    3.882969] usb 1-1.2: SerialNumber: UF92358533041506
      [    3.893106] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    3.908035] qcserial 1-1.2:1.0: Qualcomm USB modem converter detected
      [    3.908701] usb 1-1.2: Qualcomm USB modem converter now attached to ttyUSB0
      [    3.911484] mdss_register_panel: mdss mdp resource not initialized yet
      [    3.911493] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [    3.933495] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    3.938487] qcserial 1-1.2:1.2: Qualcomm USB modem converter detected
      [    3.938850] usb 1-1.2: Qualcomm USB modem converter now attached to ttyUSB1
      [    3.941502] mdss_register_panel: mdss mdp resource not initialized yet
      [    3.941513] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [    3.961700] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    3.962458] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    3.964776] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    3.970480] qcserial 1-1.2:1.3: Qualcomm USB modem converter detected
      [    3.970849] usb 1-1.2: Qualcomm USB modem converter now attached to ttyUSB2
      [    3.973775] mdss_register_panel: mdss mdp resource not initialized yet
      [    3.973786] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [    4.003719] qmi_wwan 1-1.2:1.8: cdc-wdm0: USB WDM device
      [    4.004200] qmi_wwan 1-1.2:1.8 wwan0: register 'qmi_wwan' at usb-xhci-hcd.0.auto-1.2, WWAN/QMI device, ffffffc0f080c390
      [    4.006956] mdss_register_panel: mdss mdp resource not initialized yet
      [    4.006966] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
      [    4.017858] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      [    4.019045] ufshcd 624000.ufshc: ufshcd_ioctl: User buffer is NULL!
      

      Do those errors on the EM7565 make any sense to you?

      1 Reply Last reply Reply Quote 0
      • tomT
        tom admin
        last edited by

        @Ed-Sutter I'm not sure whether those errors are related to the Sierra modem or not. It might be worth reaching out to Sierra themselves about the issue? They may be able to provide any missing kernel patches if there are any.

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

          @tom I have been, see here. They claim I'm using an old kernel, and running without their driver so they can't really help much.
          I just updated to the 0.9 platform to see if that helps any. My guess is it won't, but we'll see.

          1 Reply Last reply Reply Quote 0
          • Chad SweetC
            Chad Sweet ModalAI Team
            last edited by

            usually you just need to tell the kernel to associate the USB id with a driver. Has that been done where you have built your own kernel with the new USB device ID?

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

              @Chad-Sweet I forget the name of the file at the moment, but I did look into this a while back and the VID/PID for the EM7565 was already in your build, so I didn't do anything beyond that.

              1 Reply Last reply Reply Quote 0
              • Chad SweetC
                Chad Sweet ModalAI Team
                last edited by

                ah, shoot. that's an easy one 🙂

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

                  @Chad-Sweet LOL, well I do have to go back now and "remember" what I did 'cause I just updated to the latest package and the wwan0 interface isn't coming up at all. 😞 Yikes! I hope I took good notes. 😞

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

                    @Chad-Sweet FYI... to be clear, its only a problem with the EM7565 over USB, your modem card with the RC7611 works fine.

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

                      @Chad-Sweet Yet another update... after rebooting, and re-installing the EM7565, wwan0 did come up this time. 🙂 But I still have the problem that I can't communicate with /dev/ttyUSB2. 😞

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

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB | Contributors