RAK5010 stuck at AT+CREG?

olalonde · April 15, 2025, 3:35pm

Issue:

Hi, I just started testing my RAK5010. I’m in the Dominican Republic using a Claro SIM card. Both 2G and LTE networks (band 4) are available (but no LTE-M or nb-iot). The SIM card works in my Android phone and has data.

I tried running Zephyr’s “cellular modem” sample but it gets stuck in a timeout loop at “AT+CREG?”. I am new to embedded development and not sure how to debug this issue.

Setup:

Here’s what I did:

I connected the GPS and LTE antennas to corresponding ipex connectors.
I connected SEGGER debugger to corresponding pins.
Plugged in USB.

Using Nordic VS extension, I created a sample from Zephyr’s “cellular modem” sample, built and flashed it. Here are the RTT logs:

SEGGER J-Link V7.94i - Real time terminal output
SEGGER J-Link (unknown) V2.0, SN=802000342
Process: JLinkExe
*** Booting nRF Connect SDK v2.9.1-60d0d6c8d42d ***
*** Using Zephyr OS v3.7.99-ca954a6216c9 ***
Powering on modem
Bring up network interface
Waiting for L4 connected
[00:00:11.930,969] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_init_chat_script
[00:00:11.930,999] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 0
[00:00:11.931,030] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:00:11.952,270] <dbg> modem_chat: modem_chat_on_unknown_command_received: ATE0
[00:00:11.952,301] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:11.952,331] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 1
[00:00:11.952,362] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:00:12.103,302] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.103,332] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_in



[00:00:33.099,182] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:00:35.099,365] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:35.099,395] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:35.099,426] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:39.099,517] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:00:41.099,700] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:41.099,731] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:41.099,761] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:45.099,853] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:00:47.100,036] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:47.100,067] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:47.100,097] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:51.100,189] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:00:53.100,372] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:53.100,402] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:53.100,433] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:57.100,524] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:00:59.100,708] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:59.100,738] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:59.100,769] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:01:03.100,860] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:01:05.101,043] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:01:05.101,104] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:01:05.101,135] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?

I tried changing the APN in boards/rak5010_nrf52840.conf but I’m getting the same issue:

CONFIG_UART_ASYNC_API=y
# CONFIG_MODEM_CELLULAR_APN="internet"
CONFIG_MODEM_CELLULAR_APN="internet.ideasclaro.com.do"

It seems the modem is not able to connect to a network?

I tried re-flashing the default firmware and connecting via UART. Tried some AT commands and was able to get a list of networks the modem sees:

Serial terminal logs:

at+version
Firmware Version: RUI v3.0.0.15
OK

RDY

APP RDY

RDY

APP RDY

RDY
AT+COPS=?
+COPS: (1,"CLARO DOM","ClaroDOM","37002",0),(3,"Viva DO","Viva","37004",0),(1,"ALTICE","ALTICE","37001",0),,(0,1,2,3,4),(0,1,2)

OK

If ChatGPT is right, it seems those are all 2G networks. Which is weird since there should be LTE as well but still, even with just 2G the cellular modem sample should be able to connect…

What might be the issue?

olalonde · April 15, 2025, 3:56pm

Here are some logs from using UART with default firmware:

AT+CPIN?
ERROR:RUI_AT_UNSUPPORT 1
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
AT+CPIN?  
+CPIN: READY 
 
OK 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
AT+CSQ  
+CSQ: 99,99 
 
OK 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
AT+CREG?  
+CREG: 0,2 
 
OK 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
AT+COPS=?  
+COPS: (1,"CLARO DOM","ClaroDOM","37002",0),(3,"Viva DO","Viva","37004",0),(1,"ALTICE","ALTICE","37001",0),,(0,1,2,3,4),(0,1,2) 
 
OK 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY 
 
APP RDY 
 
RDY

I’m not sure why there are so many “APP RDY” and “RDY” messages. Example commands I sent:

at+set_config=cellular:(AT+CPIN?)
at+set_config=cellular:(AT+CSQ)

etc.

olalonde · April 15, 2025, 8:25pm

It seems it was a power issue. The timeout problem went away after connecting a rechargeable Lipo battery. As a follow up, is it not possible to power exclusively through the board USB port? I would like to avoid having to use a battery as I have a power source available (a 12v battery).

olalonde · April 16, 2025, 1:55am

Never mind, the AT+CREG? timeout issues are back, even with battery and USB plugged in… I’m wondering if there’s something wrong with the board. I swear it worked at least once today. Example log:

SEGGER J-Link V7.94i - Real time terminal output
SEGGER J-Link (unknown) V2.0, SN=802000342
Process: JLinkExe
*** Booting nRF Connect SDK v2.9.1-60d0d6c8d42d ***
*** Using Zephyr OS v3.7.99-ca954a6216c9 ***
Powering on modem
Bring up network interface
Waiting for L4 connected
[00:00:11.895,416] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_init_chat_script
[00:00:11.895,446] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 0
[00:00:11.895,477] <dbg> modem_chat: modem_chat_script_next: sending: ATE0
[00:00:11.916,656] <dbg> modem_chat: modem_chat_on_unknown_command_received: ATE0
[00:00:11.916,717] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:11.916,748] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 1
[00:00:11.916,778] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=4
[00:00:12.053,802] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.053,833] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 2
[00:00:12.053,863] <dbg> modem_chat: modem_chat_script_next: sending: AT+CMEE=1
[00:00:12.075,561] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.075,622] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 3
[00:00:12.075,653] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG=1
[00:00:12.097,290] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.097,320] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 4
[00:00:12.097,351] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGREG=1
[00:00:12.119,049] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.119,079] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 5
[00:00:12.119,110] <dbg> modem_chat: modem_chat_script_next: sending: AT+CEREG=1
[00:00:12.140,777] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.140,808] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 6
[00:00:12.140,838] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:12.162,445] <dbg> modem_chat: modem_chat_log_received_command: +CREG:  1 0
[00:00:12.162,506] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.162,536] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 7
[00:00:12.162,567] <dbg> modem_chat: modem_chat_script_next: sending: AT+CEREG?
[00:00:12.184,234] <dbg> modem_chat: modem_chat_log_received_command: +CEREG:  1 4
[00:00:12.184,295] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.184,326] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 8
[00:00:12.184,356] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGREG?
[00:00:12.206,054] <dbg> modem_chat: modem_chat_log_received_command: +CGREG:  1 0
[00:00:12.206,115] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.206,146] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 9
[00:00:12.206,176] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGSN
[00:00:12.227,935] <dbg> modem_chat: modem_chat_log_received_command:  864593056768822
[00:00:12.227,966] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 10
[00:00:12.228,027] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.228,027] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 11
[00:00:12.228,088] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGMM
[00:00:12.249,542] <dbg> modem_chat: modem_chat_log_received_command:  BG95-M3
[00:00:12.249,603] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 12
[00:00:12.249,664] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.249,664] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 13
[00:00:12.249,694] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGMI
[00:00:12.271,179] <dbg> modem_chat: modem_chat_log_received_command:  Quectel
[00:00:12.271,209] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 14
[00:00:12.271,270] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.271,301] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 15
[00:00:12.271,331] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGMR
[00:00:12.292,816] <dbg> modem_chat: modem_chat_log_received_command:  BG95M3LAR02A03
[00:00:12.292,846] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 16
[00:00:12.292,907] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.292,938] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 17
[00:00:12.292,968] <dbg> modem_chat: modem_chat_script_next: sending: AT+CIMI
[00:00:12.314,636] <dbg> modem_chat: modem_chat_log_received_command:  370021201019608
[00:00:12.314,666] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 18
[00:00:12.314,758] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.314,758] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 19
[00:00:12.314,788] <dbg> modem_chat: modem_chat_script_next: sending: AT+QCCID
[00:00:12.336,517] <dbg> modem_chat: modem_chat_log_received_command: +QCCID:  89010210524010196085
[00:00:12.336,547] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 20
[00:00:12.336,608] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.336,639] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_init_chat_script: step: 21
[00:00:12.336,669] <dbg> modem_chat: modem_chat_script_next: sending: AT+CMUX=0,0,5,127
[00:00:12.359,008] <dbg> modem_chat: modem_chat_on_unknown_command_received: OK
[00:00:12.636,840] <dbg> modem_chat: modem_chat_script_stop: quectel_bg95_init_chat_script: complete
[00:00:12.758,483] <inf> modem_at_shell: pipe connected
[00:00:12.758,544] <inf> modem_at_shell: opening pipe
[00:00:12.780,395] <inf> modem_at_shell: pipe opened
[00:00:12.780,456] <inf> modem_at_shell: chat attached
[00:00:12.901,947] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_dial_chat_script
[00:00:12.901,977] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_dial_chat_script: step: 0
[00:00:12.902,008] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGACT=0,1
[00:00:12.925,231] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.925,262] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_dial_chat_script: step: 1
[00:00:12.925,292] <dbg> modem_chat: modem_chat_script_next: sending: AT+CGDCONT=1,"IP","internet.ideasclaro.com.do"
[00:00:12.952,423] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.952,484] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_dial_chat_script: step: 2
[00:00:12.952,514] <dbg> modem_chat: modem_chat_script_next: sending: AT+CFUN=1
[00:00:12.976,684] <dbg> modem_chat: modem_chat_log_received_command: OK
[00:00:12.976,715] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_dial_chat_script: step: 3
[00:00:12.976,776] <dbg> modem_chat: modem_chat_script_next: sending: ATD*99***1#
[00:00:12.976,898] <dbg> modem_chat: modem_chat_script_stop: quectel_bg95_dial_chat_script: complete
[00:00:13.000,549] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x0d because 0x7e was expected.
[00:00:13.000,579] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x0a because 0x7e was expected.
[00:00:13.000,610] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x43 because 0x7e was expected.
[00:00:13.000,610] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x4f because 0x7e was expected.
[00:00:13.000,640] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x4e because 0x7e was expected.
[00:00:13.000,640] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x4e because 0x7e was expected.
[00:00:13.000,671] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x45 because 0x7e was expected.
[00:00:13.000,671] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x43 because 0x7e was expected.
[00:00:13.000,701] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x54 because 0x7e was expected.
[00:00:13.000,701] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x20 because 0x7e was expected.
[00:00:13.000,732] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x31 because 0x7e was expected.
[00:00:13.000,732] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x35 because 0x7e was expected.
[00:00:13.000,762] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,793] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,793] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,823] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,823] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,854] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,854] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x30 because 0x7e was expected.
[00:00:13.000,885] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x0d because 0x7e was expected.
[00:00:13.000,885] <dbg> modem_ppp: modem_ppp_is_byte_expected: Dropping byte 0x0a because 0x7e was expected.
[00:00:13.421,081] <dbg> modem_chat: modem_chat_on_unknown_command_received: APP RDY
[00:00:13.421,173] <dbg> modem_chat: modem_chat_on_unknown_command_received: APP RDY
[00:00:16.148,773] <dbg> modem_chat: modem_chat_log_received_command: +CREG:  2
[00:00:16.148,895] <dbg> modem_chat: modem_chat_log_received_command: +CGREG:  2
[00:00:16.176,696] <dbg> modem_chat: modem_chat_log_received_command: +CREG:  1
[00:00:16.200,958] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.201,171] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 29)
[00:00:16.201,599] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.201,690] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 12)
[00:00:16.228,027] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.228,118] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 13)
[00:00:16.251,983] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.252,105] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 12)
[00:00:16.279,937] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.280,029] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 12)
[00:00:16.280,090] <dbg> modem_ppp: modem_ppp_process_received_byte: Receiving PPP frame
[00:00:16.280,181] <dbg> modem_ppp: modem_ppp_process_received_byte: Received PPP frame (len 9)
[00:00:46.176,940] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:00:46.176,971] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:00:46.177,001] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:00:50.177,093] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:01:20.177,276] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:01:20.177,337] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:01:20.177,368] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:01:24.177,429] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
[00:01:54.177,612] <dbg> modem_chat: modem_chat_script_start: running script: quectel_bg95_periodic_chat_script
[00:01:54.177,673] <dbg> modem_chat: modem_chat_script_next: quectel_bg95_periodic_chat_script: step: 0
[00:01:54.177,703] <dbg> modem_chat: modem_chat_script_next: sending: AT+CREG?
[00:01:58.177,764] <wrn> modem_chat: quectel_bg95_periodic_chat_script: timed out
L4 was not connected in time

Any advice? Did anyone manage to run the Zephyr cellular modem sample on the RAK5010 board? I tried tuning some config variables like CONFIG_MODEM_CELLULAR_PERIODIC_SCRIPT_MS but it didn’t help.

sercan · April 16, 2025, 10:03pm

Hello @olalonde,

Firstly, RAK5010 uses BG95-M3 modem which supports LTE Cat M1/Cat NB2/EGPRS. So, it is not possible to connect/search LTE cell tower. Your region must support LTE-M/NB-IOT, or you can only use 2G(EGPRS).

I tested to connect LTE-M network with attached project on Zephyr RTOS. I am able to connect.

bg95_modem.zip (7.1 KB)

What I understand from your message is there is no LTE-M support at your area. So, you can only use 2G(EGPRS) network. To be honest, I am not so sure that Zephyr’s modem api supports only LTE-M, or it is possible to connect 2G network. I tried to force modem to connect 2G networks but there is no successful connection on my side. If you also want to try it, please edit modem_cellular.c file like screenshot.

I will continue to search how I can setup modem for 2G network on my side.

Best regards,
Sercan.