EC800MCN Modules Failing to Return RDY After Power-On

Hi Quectel Support Team,

We are experiencing an issue with some of our EC800MCN modules. After power-on, the affected modules do not return the expected RDY indication. Instead, we receive the following boot log:

** PC      : 0x80022000
Version: SDK_1.010.087 Dec  9 2024 12:20:29
Ac 4, Board 2, DKB 1
0
Cinit 2
Flash type: nvm 0, factory 0, fota 0
0 silentreset, don't need to dump
Phase1Inits
diag Phase1 Init
SVT 128
profile num = 2
CRNL_SVC_FP[0] = 0x18
CRNL_SVC_FP[1] = 0x19
CRNL_SVC_FP[2] = 0x1b
CRNL_SVC_FP[3] = 0x21
PSRAM fuse: 13
Bootup not silent
0 [MPU][RGN][      BASE][       END][      SIZE][  PERMISSION][CACHE][SHARE][N_EXE]
0 [MPU][  0][0x00000000][0xffffffff][0xffffffff][   NO_ACCESS][    0][    1][    1]
0 [MPU][  1][0x00000000][0x0000ffff][0x0000ffff][   READ_ONLY][    0][    0][    0]
0 [MPU][  2][0xb0020000][0xb002ffff][0x0000ffff][ FULL_ACCESS][    0][    0][    1]
0 [MPU][  3][0x80000000][0x81ffffff][0x01ffffff][ FULL_ACCESS][    0][    0][    0]
0 [MPU][  4][0x7e000000][0x7e3fffff][0x003fffff][ FULL_ACCESS][    1][    0][    0]
0 [MPU][  5][0x7e330000][0x7e33ffff][0x0000ffff][ FULL_ACCESS][    0][    1][    0]
0 [MPU][  6][0x7e340000][0x7e37ffff][0x0003ffff][ FULL_ACCESS][    0][    1][    0]
0 [MPU][  7][0x7e380000][0x7e3fffff][0x0007ffff][ FULL_ACCESS][    0][    1][    0]
0 [MPU][  8][0xc0000000][0xffffffff][0x3fffffff][ FULL_ACCESS][    0][    0][    1]
0 [MPU][  9][0xd1000000][0xd100ffff][0x0000ffff][ FULL_ACCESS][    0][    1][    1]
0 [MPU][ 10][0x80000000][0x801fffff][0x001fffff][ FULL_ACCESS][    1][    0][    0]
0 [MPU][ 11][0x80200000][0x802fffff][0x000fffff][ FULL_ACCESS][    1][    0][    0]
0 [MPU][ 12][0x00000000][0x00000001][0x00000001][   NO_ACCESS][    1][    0][    0]
0 [MPU][ 13][0x00000000][0x00000001][0x00000001][   NO_ACCESS][    1][    0][    0]
0 [MPU][ 14][0x00000000][0x00000001][0x00000001][   NO_ACCESS][    1][    0][    0]
0 [MPU][ 15][0x80000000][0x80000001][0x00000001][   NO_ACCESS][    1][    0][    1]
0 crane_set_fbp:reserved_start_addr[0x35d000],reserved_end_addr[0x38e000]
1 qspi_nor_find_fbp:flash size is 0x400000, name is GD25LE32E
2 qspi_nor_find_fbp:find type is 24, protect area=0x0~0x37ffff
3 qspi_nor_set_fbp:org status1[0x0],status2[0x2].
4 qspi_nor_set_fbp:new status1[0x10],status2[0x42].
5 qspi_nor_set_fbp:read back,n_status1[0x10],n_status2[0x42].
117d usbinfo trace to uart debugfail
14e5 quec usb nema cfg nv init: value 0 read failed
22 [Egan]usb_device_init,usb_mode=69
22 Usb mode 0, descriptor 69
24 power_up_reason: 0x2, power_down_reason: 0x2
17e6 read g_quec_nat_flag=0 fail
17ea mifi mode
25 lwip: lwip_init_all done!
27 ######## quec_system_init ok ########
27 EC800MCNGDR06A07M04 V01
28 Application Start...
28 ATCmdSvrRdy
20f4 usb get ifc value fail rts_control=0,cts_control=0
217a read remoteip=0,ret=5
218b remoteip read fail
2227 cts value=0 not need init
22de debounce timer read fail,use default value
2439 usim wakeup flag read fail,use default value=0
68 quec_modem_channel_init: done
68 modem_msgq_init: done
69 modem_if_init: done
69 modem_router_create: done
6a modem_init_internal: done
6a AT command server ready!
6c Booting done
4a2b dsss sim2 read_cfg=1,dftcid=1
78 quec_transmission_rate_config!!!
7b SW restart reason: Charging in powering off

The firmware version reported by the module is:

EC800MCNGDR06A07M04 V01

Could you please help us determine the root cause of this behavior and advise on the recommended troubleshooting or corrective action?

Best regards,
Vu

Hi @minhvunguyen
I would not identify the root cause as a firmware boot failure yet. The module reaches AT command server ready! and Booting done, which means the main firmware initialization completes. i have few question on this issue:

  1. Does the module reboot repeatedly?
    Your current log ends with:

7b SW restart reason: Charging in powering off

  1. Could you please help to test the AT interface through UART instead of USB? If you are currently using USB, connect directly to the module’s main UART and send “AT”

If UART works normally but USB does not, the problem is most likely related to the USB interface/configuration, rather than the modem firmware itself.

  1. Do you have any good module? if you have, you can capture the logs for both modules and compare.
  2. May i know what driver are you using?