RM520N-GL only ttyUSB0 and ttyUSB1 enumerate on a linux device running linux kernel 5.4.223. This kernel seem to have the needed patches for the 520 to be supported. However as you can see in the dmesg output below, it seems like the VID and PID are for the generic EC25 0x0125 instead of for the rm520, which would be 0x0801.
dmesg:
[ 12.114487] usb 2-1.4: new SuperSpeed Gen 1 USB device number 4 using xhci-hcd
[ 12.145943] usb 2-1.4: LPM exit latency is zeroed, disabling LPM.
[ 12.157302] usb 2-1.4: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 5.04
[ 12.169792] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 12.169793] usb 2-1.4: Product: RM520N-GL
[ 12.169794] usb 2-1.4: Manufacturer: Quectel
[ 12.169795] usb 2-1.4: SerialNumber: 52ddb378
[ 12.333418] usb_bam_dt_to_data: bam type is missing in device tree
[ 12.339800] usb_bam: probe of a704000.qcom,usbbam failed with error -22
[ 12.339802] usb 2-1.4: New USB device found, VID=2c7c, PID=0125
[ 12.349669] msm-usb-ssphy-qmp 88e8000.ssphy: USB DP QMP PHY: Update TYPEC CTRL(2)
[ 12.369566] usb 2-1.4: GSM modem (1-port) converter now attached to ttyUSB0
[ 12.401604] usb 2-1.4: GSM modem (1-port) converter now attached to ttyUSB1
ttyUSB1 does seem to be AT, but there should be many more ports enumerating. With the cdc_wdm and qmi_wwan drivers loaded, quectel-CM also does not work properly
After looking at it more, I can now see that ttyUSB1 is the AT port, with ttyUSB0 probably being USBDM. So now the question is why is the NMEA port not showing up? I nmea port should be outputing over usb, after checking +QGPSCFG: “outport”,usbnmea.
While not actually a problem anymore, does anyone have any idea why the VID and PID aren’t in line with what a RM520 should be?
I did see something about usbcfg elsewhere. Makes sense. Also not a necessity, but do you know where I can find info on the other fields of the usbcfg AT command? The RM520N AT Command doc doesn’t have anything on that one.
I set the PID to 0x0801 as it should be and that worked! Thanks! Not sure why the PID was wrong, maybe Quectel wanted to support older kernel’s before they patched it in mainline.