Rm520n-glap adb

IoT Modules 5G Module
1

Trying to get ADB shell to my RM520N-GLAP and am hitting an issue. Got the modem unlocked, and it is detected, but in a constant “offline” status. Is it a driver issue? It picked up default WinUSB driver and Windows 10 won’t let me update it to anything else as “Windows has determined that the best driver for this device is already installed”

ATI
Quectel
RM520N-GL
Revision: RM520NGLAPR01A03M4G
OK

AT+QADBKEY?
+QADBKEY: 25816482
OK

AT+QADBKEY=“MPdpWAU6C.BL9Eq”
OK

at+qcfg=“usbcfg”
+QCFG: “usbcfg”,0x2C7C,0x0801,1,1,1,1,1,1,1
OK

adb devices
List of devices attached
90abcdef offline

image
image2390×682 69.2 KB

2

It will take effect after reboot.

3

Please also check the AT command

AT+QCFG=“usbnet”
AT+QCFG=“data_interface”

4

Yes, I’ve tried both “AT+CFUN=1,1” and hardware reboot.

AT+QCFG=“usbnet”
+QCFG: “usbnet”,2
OK

AT+QCFG=“data_interface”
+QCFG: “data_interface”,1,0
OK

I’ve tried “AT+QCFG=“data_interface”,1,1” but it did not change anything.

By the way, this is the PCIe only AP variant. Is there maybe a separate procedure for unlocking the ADB that is exposed over PCIe? Or maybe a separate “usbcfg” command, as the PID returned by “usbcfg” (0x0801) doesn’t match the PID of UDE Client ADB Device (0x0802)?

5

What’s the firmware version?

6

Please don’t change the PID of the device.
It seems that you have changed the USB PID.

7

AT+CVERSION
VERSION: RM520NGLAPR01A03M4G
Mar 24 2022 03:18:54
Authors: Quectel

AT+QGMR
RM520NGLAPR01A03M4G_01.001.01.001

I never changed the PID. It was mismatched like that out of the box. “usbcfg” even now still returns 0x0801 even though the UDE Client ADB Device is enumerating with 0x0802. What PID should I have?

Is there a way to contact you directly? I have to wait 45 minutes for each reply…

8

It should only be 0x0801.
Do you have a Linux PC? Could you try it on Ubuntu?

9

RM520NGLAP R01A03M4G_01.001.01.001

OK. yes it is PCIe only. And it do not support USB. You cannot login with adb.

10

The ADB device that is already enumerated via the USB Device Emulation (UDE) over PCIe is good enough for me. I don’t need nor am I trying to use the USB one. The PCIe ADB Device already shows up in “adb devices”. The problem I am having is it is always shown as “offline” in adb. It seems as if the approval/unlock didn’t go through.

11

Sorry I have never seen any try the adb over PCIe.
If you must login in the modem it is better to try the AT version but not the PCIe only version.
Otherwise you can login in the modem via debug uart.

12

How do I do that? Does the debug UART provide root shell?

13

image
image1413×730 84.6 KB

You can login with the debug uart.

DBG_RXD
DBG_TXD

14

Thank you. This only being available on testpoints is less than ideal of course, but hopefully I’ll just be able to unlock the PCIe ADB via it and use that as planned moving forward.

Oh, last question before I forget, the logic level on the debug uart is 1v8, correct?

15

Yes. 1.8V.
Normally Quectel will not provide the solution for non VIP customer to login the STD modem

16

Got it connected, but it is password protected. Can you please provide root password for the following module:

QTI Linux reference nogplv3 distro targeting performance builds. r00223.1 sdxlemur ttyMSM0
 quectel-v : v1.0
 quectel-ID : 25816482
17

username: root
passwd:BIosnVFS7ChXoAWUAKZb3/

1 Like
18

@Bean.Wang-Q
Got ADB working over PCIe. all you need is AT+QPCIE="adb",1
I am assuming it needs ADB to be unlocked first with +QADBKEY but I have no way to test it as mine is already unlocked with +QADBKEY.
Removing /data/.adb_enable has no effect on it though, but I suspect that is simply not enough to re-lock ADB.