RC7620 with HL78xx-RC-WP DEV-KIT board

laa · March 13, 2024, 3:29pm

Hi.

I’m testing the RC7620 module with a HL78xx-RC-WP DEV-KIT board (blue pcb) and are trying to get the module to work by connected a Fedora 39 laptop running ModemManager to the main USB port on the dev kit.

First of all I can’t find any documentation for the dev kit. So maybe someone can provide a link for that.

My main issue is that I only get a ttyUSB0 port available, which doesn’t work for ModemManager and if I send the command “AT” to ttyUSB0 i get “00” back. So it probably isn’t a AT port.

If I look in the USB Driver Developer’s guide I can see that I might miss some USB endpoints (page 10). Is the RC7620 modules shipped with only bootloader code?

My goal is to get ModemManager to find the cdc-wdm0 (which is missing) and use the QMI interface.


kernel: qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
kernel: qcserial 1-1.1:1.0: device disconnected
kernel: usb 1-1.1: new high-speed USB device number 11 using ci_hdrc
kernel: usb 1-1.1: New USB device found, idVendor=1199, idProduct=68c0, bcdDevice= 0.00
kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-1.1: Product: Sierra Wireless RC7620
kernel: usb 1-1.1: Manufacturer: Sierra Wireless, Incorporated
kernel: usb 1-1.1: SerialNumber: CM4036250301B106
kernel: qcserial 1-1.1:1.0: Qualcomm USB modem converter detected
kernel: usb 1-1.1: Qualcomm USB modem converter now attached to ttyUSB0
ModemManager[248]: <info>  [device /sys/devices/platform/soc/30800000.bus/30b20000.usb/ci_hdrc.0/usb1/1-1/1-1.1] creating modem with plugin 'generic' and '1' ports
ModemManager[248]: <warn>  [plugin/generic] could not grab port ttyUSB0: Cannot add port 'tty/ttyUSB0', unhandled port type
ModemManager[248]: <warn>  [base-manager] couldn't create modem for device '/sys/devices/platform/soc/30800000.bus/30b20000.usb/ci_hdrc.0/usb1/1-1/1-1.1': Failed to find primary 
AT port

Bus 001 Device 010: ID 1199:68c0 Sierra Wireless, Inc. Sierra Wireless RC7620
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 [unknown]
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1199 Sierra Wireless, Inc.
  idProduct          0x68c0 Sierra Wireless RC7620
  bcdDevice            0.00
  iManufacturer           1 Sierra Wireless, Incorporated
  iProduct                2 Sierra Wireless RC7620
  iSerial                 3 CM4036250301B106
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)

:~ cd /dev/serial/by-id                                                                                         
:/dev/serial/by-id ll
total 0
drwxr-xr-x 2 root root 60 Mar 13 14:54 .
drwxr-xr-x 4 root root 80 Mar 13 14:54 ..
lrwxrwxrwx 1 root root 13 Mar 13 14:54 usb-Sierra_Wireless__Incorporated_Sierra_Wireless_RC7620_CM4036250301B106-if00-port0 -> ../../ttyUSB0

jyijyi · March 13, 2024, 3:35pm

Can you take a picture of your dev kit?
Did you put the boot pin switch to off?
Does it work in windows?

laa · March 13, 2024, 3:52pm

Think the boot switch is set to TP1.

I havn’t tested on a windows pc yet.

jyijyi · March 13, 2024, 4:06pm

How about setting the boot switch to off?

laa · March 14, 2024, 7:56am

Now it boot. thanks

Now I’m having issue with enabling power state(is low):

❯ mmcli -m any
  ----------------------------------
  General  |                   path: /org/freedesktop/ModemManager1/Modem/0
           |              device id: 838cb1e115e3a02df2cd05f5560b18832696681f
  ----------------------------------
  Hardware |           manufacturer: Sierra Wireless, Incorporated
           |                  model: RC7620
           |      firmware revision: SWI9X07H_00.09.10.00 85890e jenkins 2023/09/25 03:16:56
           |         carrier config: default
           |           h/w revision: 1.0
           |              supported: gsm-umts, lte
           |                current: gsm-umts, lte
           |           equipment id: 353634110876389
  ----------------------------------
  System   |                 device: /sys/devices/pci0000:00/0000:00:08.3/0000:e4:00.3/usb7/7-1/7-1.4/7-1.4.1
           |                drivers: qmi_wwan, qcserial
           |                 plugin: sierra
           |           primary port: cdc-wdm0
           |                  ports: cdc-wdm0 (qmi), ttyUSB0 (qcdm), ttyUSB2 (at), wwan0 (net)
  ----------------------------------
  Numbers  |                    own: +4549321248
  ----------------------------------
  Status   |                   lock: sim-pin2
           |         unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
           |                  state: disabled
           |            power state: low
  ----------------------------------
  Modes    |              supported: allowed: 2g; preferred: none
           |                         allowed: 3g; preferred: none
           |                         allowed: 4g; preferred: none
           |                         allowed: 2g, 3g; preferred: 3g
           |                         allowed: 2g, 3g; preferred: 2g
           |                         allowed: 2g, 4g; preferred: 4g
           |                         allowed: 2g, 4g; preferred: 2g
           |                         allowed: 3g, 4g; preferred: 4g
           |                         allowed: 3g, 4g; preferred: 3g
           |                         allowed: 2g, 3g, 4g; preferred: 4g
           |                         allowed: 2g, 3g, 4g; preferred: 3g
           |                         allowed: 2g, 3g, 4g; preferred: 2g
           |                current: allowed: 2g, 3g, 4g; preferred: 4g
  ----------------------------------
  Bands    |              supported: egsm, dcs, utran-1, utran-8, eutran-1, eutran-3, eutran-7, 
           |                         eutran-8, eutran-20, eutran-28
           |                current: egsm, dcs, utran-1, utran-8, eutran-1, eutran-3, eutran-7, 
           |                         eutran-8, eutran-20, eutran-28
  ----------------------------------
  IP       |              supported: ipv4, ipv6, ipv4v6
  ----------------------------------
  3GPP     |                   imei: 353634110876389
           |          enabled locks: fixed-dialing
           |   packet service state: detached
  ----------------------------------
  3GPP EPS |   ue mode of operation: csps-1
           | initial bearer ip type: ipv4v6
  ----------------------------------
  SIM      |       primary sim path: /org/freedesktop/ModemManager1/SIM/0
           |         sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active)
           |                         slot 2: none

In basic modemmanger log i get:

Mar 14 08:34:17 laped ModemManager[63014]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:02.2/0000:01:00.0': not supported by any plugin
Mar 14 08:34:17 laped ModemManager[63014]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:03.1/0000:03:00.0/0000:04:04.0/0000:72:00.0': not supported by any plugin
Mar 14 08:34:29 laped cherrytree.desktop[53262]: [2024-03-14 08:34:29.717] [   ] [debug] autosave no need
Mar 14 08:34:35 laped ModemManager[63014]: <info>  [device /sys/devices/pci0000:00/0000:00:08.3/0000:e4:00.3/usb7/7-1/7-1.4/7-1.4.1] creating modem with plugin 'sierra' and '5' ports
Mar 14 08:34:35 laped ModemManager[63014]: <warn>  [plugin/sierra] could not grab port ttyUSB1: Cannot add port 'tty/ttyUSB1', unhandled port type
Mar 14 08:34:35 laped ModemManager[63014]: <info>  [base-manager] modem for device '/sys/devices/pci0000:00/0000:00:08.3/0000:e4:00.3/usb7/7-1/7-1.4/7-1.4.1' successfully created
Mar 14 08:34:35 laped ModemManager[63014]: <warn>  [modem0/sim0] couldn't load GID1: Couldn't read data from UIM: QMI protocol error (16): 'NotProvisioned'
Mar 14 08:34:35 laped ModemManager[63014]: <warn>  [modem0/sim0] couldn't load GID2: Couldn't read data from UIM: QMI protocol error (16): 'NotProvisioned'
Mar 14 08:34:36 laped ModemManager[63014]: <warn>  [modem0] couldn't load supported assistance data types: LOC service: general failure
Mar 14 08:34:36 laped ModemManager[63014]: <info>  [modem0] state changed (unknown -> disabled)
Mar 14 08:34:36 laped NetworkManager[2659]: <info>  [1710401676.0953] manager: (cdc-wdm0): new Broadband device (/org/freedesktop/NetworkManager/Devices/18)
Mar 14 08:34:36 laped NetworkManager[2659]: <info>  [1710401676.0957] device (cdc-wdm0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 14 08:34:36 laped NetworkManager[2659]: <info>  [1710401676.0959] device (cdc-wdm0): modem state 'enabling'
Mar 14 08:34:36 laped NetworkManager[2659]: <info>  [1710401676.0961] device (cdc-wdm0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Mar 14 08:34:36 laped ModemManager[63014]: <info>  [modem0] state changed (disabled -> enabling)
Mar 14 08:34:36 laped ModemManager[63014]: <warn>  [modem0] couldn't enable interface: 'Invalid transition'
Mar 14 08:34:36 laped ModemManager[63014]: <info>  [modem0] 3GPP registration state changed (unknown -> unknown)
Mar 14 08:34:36 laped ModemManager[63014]: <info>  [modem0] state changed (enabling -> disabled)
Mar 14 08:34:36 laped NetworkManager[2659]: <warn>  [1710401676.1322] modem-broadband[cdc-wdm0]: failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition

Could it be something like FCC unlock?

I tried calling:

❯ sudo qmicli -d /dev/cdc-wdm0 --dms-set-fcc-authentication
error: couldn't set FCC authentication: QMI protocol error (94): 'NotSupported'

Also tried to enable the fcc unlock scripts as mentioned in the modemmanager docs.

/etc/ModemManager/fcc-unlock.d🔒 
❯ ll
lrwxrwxrwx@   - root root 14 Mar 08:16  03f0:4e1d -> /usr/share/ModemManager/fcc-unlock.available.d/03f0:4e1d
lrwxrwxrwx@   - root root 14 Mar 08:16  1eac -> /usr/share/ModemManager/fcc-unlock.available.d/1eac
lrwxrwxrwx@   - root root 14 Mar 08:16  1eac:1001 -> /usr/share/ModemManager/fcc-unlock.available.d/1eac:1001
lrwxrwxrwx@   - root root 14 Mar 08:16  2c7c -> /usr/share/ModemManager/fcc-unlock.available.d/2c7c
lrwxrwxrwx@   - root root 14 Mar 08:16  2c7c:030a -> /usr/share/ModemManager/fcc-unlock.available.d/2c7c:030a
lrwxrwxrwx@   - root root 14 Mar 08:16  105b -> /usr/share/ModemManager/fcc-unlock.available.d/105b
lrwxrwxrwx@   - root root 14 Mar 08:16  105b:e0ab -> /usr/share/ModemManager/fcc-unlock.available.d/105b:e0ab
lrwxrwxrwx@   - root root 14 Mar 08:16  413c:81a3 -> /usr/share/ModemManager/fcc-unlock.available.d/413c:81a3
lrwxrwxrwx@   - root root 14 Mar 08:16  413c:81a8 -> /usr/share/ModemManager/fcc-unlock.available.d/413c:81a8
lrwxrwxrwx@   - root root 14 Mar 08:16  1199 -> /usr/share/ModemManager/fcc-unlock.available.d/1199
.rwx------@ 775 root root 14 Mar 08:39  1199:68c0
lrwxrwxrwx@   - root root 14 Mar 08:16  1199:9079 -> /usr/share/ModemManager/fcc-unlock.available.d/1199:9079

ModemManager debug log in QMI shows:

ModemManager[64755]: <debug> [1710402289.938396] [modem0] autoconnect is already disabled
ModemManager[64755]: <debug> [1710402289.938426] [modem0] getting device operating mode...
ModemManager[64755]: <debug> [1710402289.938445] [/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<<   length = 13
<<<<<<   data   = 01:0C:00:00:02:03:00:0B:00:2D:00:00...
 
ModemManager[64755]: <debug> [1710402289.938465] [/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<<   length  = 12
<<<<<<   flags   = 0x00
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 11
<<<<<<   tlv_length  = 0
<<<<<<   message     = "Get Operating Mode" (0x002D)
 
ModemManager[64755]: <debug> [1710402289.940388] [/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 24
<<<<<<   data   = 01:17:00:80:02:03:02:0B:00:2D:00:0B...
 
ModemManager[64755]: <debug> [1710402289.940418] [/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<<   length  = 23
<<<<<<   flags   = 0x80
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "response"
<<<<<<   transaction = 11
<<<<<<   tlv_length  = 11
<<<<<<   message     = "Get Operating Mode" (0x002D)
<<<<<< TLV:
<<<<<<   type       = "Result" (0x02)
<<<<<<   length     = 4
<<<<<<   value      = 00:00:00:00
<<<<<<   translated = SUCCESS
<<<<<< TLV:
<<<<<<   type       = "Mode" (0x01)
<<<<<<   length     = 1
<<<<<<   value      = 01
<<<<<<   translated = low-power
 
ModemManager[64755]: <debug> [1710402289.940463] [modem0] updating power state: 'on'...
ModemManager[64755]: <debug> [1710402289.940483] [modem0] Power indication registration request is sent
ModemManager[64755]: <debug> [1710402289.940503] [/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<<   length = 17
<<<<<<   data   = 01:10:00:00:02:03:00:0C:00:01:00:04...
 
ModemManager[64755]: <debug> [1710402289.940526] [/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<<   length  = 16
<<<<<<   flags   = 0x00
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 12
<<<<<<   tlv_length  = 4
<<<<<<   message     = "Set Event Report" (0x0001)
<<<<<< TLV:
<<<<<<   type       = "Operating Mode Reporting" (0x14)
<<<<<<   length     = 1
<<<<<<   value      = 01
<<<<<<   translated = yes
 
ModemManager[64755]: <debug> [1710402289.943212] [ttyUSB2/at] <-- '<CR><LF>OK<CR><LF>'
ModemManager[64755]: <debug> [1710402289.943267] [ttyUSB2/at] --> 'ATV1<CR>'
ModemManager[64755]: <debug> [1710402289.944205] [/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 20
<<<<<<   data   = 01:13:00:80:02:03:02:0C:00:01:00:07...
 
ModemManager[64755]: <debug> [1710402289.944217] [/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<<   length  = 19
<<<<<<   flags   = 0x80
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "response"
<<<<<<   transaction = 12
<<<<<<   tlv_length  = 7
<<<<<<   message     = "Set Event Report" (0x0001)
<<<<<< TLV:
<<<<<<   type       = "Result" (0x02)
<<<<<<   length     = 4
<<<<<<   value      = 00:00:00:00
<<<<<<   translated = SUCCESS
 
ModemManager[64755]: <debug> [1710402289.944241] [modem0] Power operation is pending
ModemManager[64755]: <debug> [1710402289.944252] [/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<<   length = 17
<<<<<<   data   = 01:10:00:00:02:03:00:0D:00:2E:00:04...
 
ModemManager[64755]: <debug> [1710402289.944263] [/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<<   length  = 16
<<<<<<   flags   = 0x00
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 13
<<<<<<   tlv_length  = 4
<<<<<<   message     = "Set Operating Mode" (0x002E)
<<<<<< TLV:
<<<<<<   type       = "Mode" (0x01)
<<<<<<   length     = 1
<<<<<<   value      = 00
<<<<<<   translated = online
 
ModemManager[64755]: <debug> [1710402289.944277] [modem0] Starting timeout for indication receiving for 10 seconds
ModemManager[64755]: <debug> [1710402289.948297] [/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 20
<<<<<<   data   = 01:13:00:80:02:03:02:0D:00:2E:00:07...
 
ModemManager[64755]: <debug> [1710402289.948339] [/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<<   length  = 19
<<<<<<   flags   = 0x80
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "response"
<<<<<<   transaction = 13
<<<<<<   tlv_length  = 7
<<<<<<   message     = "Set Operating Mode" (0x002E)
<<<<<< TLV:
<<<<<<   type       = "Result" (0x02)
<<<<<<   length     = 4
<<<<<<   value      = 01:00:3C:00
<<<<<<   translated = FAILURE: InvalidTransition
 
ModemManager[64755]: <debug> [1710402289.948399] [/dev/cdc-wdm0] sent message...
<<<<<< RAW:
<<<<<<   length = 17
<<<<<<   data   = 01:10:00:00:02:03:00:0E:00:01:00:04...
 
ModemManager[64755]: <debug> [1710402289.948420] [/dev/cdc-wdm0] sent generic request (translated)...
<<<<<< QMUX:
<<<<<<   length  = 16
<<<<<<   flags   = 0x00
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "none"
<<<<<<   transaction = 14
<<<<<<   tlv_length  = 4
<<<<<<   message     = "Set Event Report" (0x0001)
<<<<<< TLV:
<<<<<<   type       = "Operating Mode Reporting" (0x14)
<<<<<<   length     = 1
<<<<<<   value      = 00
<<<<<<   translated = no
 
ModemManager[64755]: <debug> [1710402289.948452] [modem0] couldn't update power state: Invalid transition
ModemManager[64755]: <debug> [1710402289.948464] [modem0] attempting fcc unlock...
ModemManager[64755]: <debug> [1710402289.948542] [fcc unlock dispatcher] singleton created
ModemManager[64755]: <debug> [1710402289.950821] [/dev/cdc-wdm0] received message...
<<<<<< RAW:
<<<<<<   length = 20
<<<<<<   data   = 01:13:00:80:02:03:02:0E:00:01:00:07...
 
ModemManager[64755]: <debug> [1710402289.950855] [/dev/cdc-wdm0] received generic response (translated)...
<<<<<< QMUX:
<<<<<<   length  = 19
<<<<<<   flags   = 0x80
<<<<<<   service = "dms"
<<<<<<   client  = 3
<<<<<< QMI:
<<<<<<   flags       = "response"
<<<<<<   transaction = 14
<<<<<<   tlv_length  = 7
<<<<<<   message     = "Set Event Report" (0x0001)
<<<<<< TLV:
<<<<<<   type       = "Result" (0x02)
<<<<<<   length     = 4
<<<<<<   value      = 00:00:00:00
<<<<<<   translated = SUCCESS
 
ModemManager[64755]: <debug> [1710402289.952920] [ttyUSB2/at] <-- '<CR><LF>OK<CR><LF>'
ModemManager[64755]: <debug> [1710402289.952997] [ttyUSB2/at] --> 'AT+CMEE=1<CR>'
ModemManager[64755]: <debug> [1710402289.967595] [ttyUSB2/at] <-- '<CR><LF>OK<CR><LF>'
ModemManager[64755]: <debug> [1710402289.967672] [ttyUSB2/at] --> 'ATX4<CR>'
ModemManager[64755]: <debug> [1710402289.969553] [modem0] couldn't run FCC unlock: fcc unlock operation finished with status 1
ModemManager[64755]: <debug> [1710402289.969565] [modem0] updating power state: 'on'...
ModemManager[64755]: <debug> [1710402289.969578] [modem0] Power indication registration request is sent
ModemManager[64755]: <debug> [1710402289.969594] [/dev/cdc-wdm0] sent message...

So do you also have any ideas on this subject?

jyijyi · March 14, 2024, 8:08am

what are the return of the following AT commands?

ATI3
AT!ENTERCND="A710"
at!IMAGE?
aT!IMPREF?
AT+cpin?
aT!GSTATUS?
at+cfun?
aT!PCINFO?

laa · March 14, 2024, 8:36am

❯ mmcli -m any --command="ATI3"
response: 'Manufacturer: Sierra Wireless, Incorporated
Model: RC7620
Revision: SWI9X07H_00.09.10.00 85890e jenkins 2023/09/25 03:16:56
IMEI: 353634110876389
IMEI SV: 29
FSN: CM4036250301B1
+GCAP: +CGSM'

❯ mmcli -m any --command='AT!ENTERCND="A710"'
response: ''

❯ mmcli -m any --command='AT!IMAGE?'
response: 'TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    EMPTY  0   0 0                  
FW   2    EMPTY  0   0 0                  
FW   3    EMPTY  0   0 0                  
Max FW images: 1
Active FW image is at slot 255

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
PRI  FF   GOOD   0   0 0      001.164_000 00.09.10.00_GENERIC
Max PRI images: 50'

❯ mmcli -m any --command='AT!IMPREF?'
response: '!IMPREF: 
 preferred fw version:    00.09.10.00
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_001.164_000
 preferred subpri index:  000
 current fw version:      00.09.10.00
 current carrier name:    GENERIC
 current config name:     GENERIC_001.164_000
 current subpri index:    000'

❯ mmcli -m any --command='AT+cpin?'
response: '+CPIN: READY'

❯ mmcli -m any --command='!GSTATUS?'
response: '!GSTATUS: 
Current Time:  230		Temperature: 28
Modem Mitigate Level: 0		ModemProc Mitigate Level: 0	
Reset Counter: 1		Mode:        LOW POWER MODE '

❯ mmcli -m any --command='AT!GSTATUS?'
response: '!GSTATUS: 
Current Time:  233		Temperature: 29
Modem Mitigate Level: 0		ModemProc Mitigate Level: 0	
Reset Counter: 1		Mode:        LOW POWER MODE '

❯ mmcli -m any --command='AT+cfun?'
response: '+CFUN: 0'

❯ mmcli -m any --command='AT!PCINFO?'
response: 'State: Low Power Mode
LPM voters - Temp:0, Volt:1, User:0, W_DISABLE:0, IMSWITCH:0, BIOS:0, LWM2M:0, OMADM:0, FOTA:0, RFCAL:0, AVMS:0
LPM persistence - None'

jyijyi · March 14, 2024, 8:43am

the “Volt:1” in AT!PCINFO shows there is abnormal voltage problem on your board.

Not sure if you should use the same jumper as my picture on right bottom corner, you can give a try

laa · March 14, 2024, 9:07am

Actually I’m not sure what the input voltage should be. I’m using 5V DC on the banana plugs. Is that correct?

jyijyi · March 14, 2024, 9:10am

you can just use the USB power to supply power to the board

laa · March 14, 2024, 9:14am

Okay thanks. It works now by removing the power via the banana plugs and moving the jumper to USB_VBUS and connecting the dev kit board via main USB.

Topic		Replies	Views
Q2698 usb serial issue Legacy AirPrime modules	9	2785	February 7, 2019
MC7710 only ttyISB0 available MC/EM Series	3	1042	June 25, 2014
RC7620 unresponsive to QMI (sometimes) RC76	2	323	August 24, 2023
After power problem, new ID USB on 05C6:9008. Why? IoT Modules	5	352	December 18, 2023
OpenWRT QMI - HL7588 issues	3	4935	February 20, 2019

RC7620 with HL78xx-RC-WP DEV-KIT board

Related Topics