How/where to enroll new P-L496-CELL02 development kit (see detail below)?

[KMurp.290]

Hello -

I recently acquired a new P-L496G-CELL02 development kit to evaluate cellular communication performance. Out of the box, when I first plug in the P-L496G-CELL02 development kit to my PC and open a terminal, it instructs me to "open a web browser and go to http://www.stm32-c2c.com". When I go to the http://www.stm32-c2c.com domain, its page says "The stm32.c2c.com web page to enroll P-L496-CELL02 is now moved to STMicroelectronics www.st.com. Please click here, to get more information." I have been unable to to find any page on the st.com domain for enrolling the P-L496-CELL02. So unfortunately I am stuck on step #1 with getting this demo running out of the box.

Please help. Thank you.

Regards,

Kevin

[Ronan GABOU]

Hello,

The stm32.c2c.com was mainly used to register the eSIM.

To achieve this use this URL : https://www.st.com/en/evaluation-tools/p-l496g-cell02.html#resource

and read/apply the following utility:

How to enable SIM MFF2 connectivity with P-L496G-CELL02

So at the end your eSIM will be activated so you can connect to cellular network.

Then you can use : https://www.st.com/en/embedded-software/x-cube-cellular.html

to get the cellular SW with examples.

Regards, Ronan,

[egoltzman]

Hello Ronan,

Can you please look at my question below and see if you can help?

Thanks

[egoltzman]

Hello,

I have this same board (P-L496G-CELL02) and I'm straggling for hours to try to start work with it and the X-CUBE-CELLULAR.

There is several getting started documents, non of them worked for me, the last thing I tried was your instruction above, I loaded l496_bg96_socket_v510.bin to the board as instructed by the "How to enable SIM MFF2 connectivity with P-L496G-CELL02" document and follow the steps, I faild to continue after issueing step 6 (See attached document and log.

Can you please advise?

Thanks

[egoltzman]

And this is the instruction doc

[Ronan GABOU]

Hello,

Please could you try to reboot the board and wait longer.

If there is still an issue can you provide the complete log.

Be sure at boot embedded SIM is selected.

In this topic you want to activate the eSIM on the BG96 STMod+ board, exact ?

I also got an email you sent to ST FAE.

Because in your email you stated modem FW update, not the same

Here is the MCU Wiki for cellular:

https://wiki.st.com/stm32mcu/wiki/Cellular_LTE_CatM_/_NBIoT_overview

Ronan,

[egoltzman]

Hello Ronan,

Sorry for late response.

I refer to this topic as indeed I was not able to activate the eSIM, but after I got your response and waited longer the connection was establish successfully.

So this issue is resolved at the moment and now I can continue with trying to run the MQTT demo, I want to try and to test it with the AWS IOT cloud, any input you can give me on that? I have experience with ST MCU to AWS IOT MQTT with other connection type s(Ethernet and WiFi)

You mention the question I asked my FAE about the modem FW update, I indeed tried this with no luck, any input you can give me on that? Link?

Thanks,

Eyal

[Ronan GABOU]

Hello Eyal,

Good to know :)

For AWS, I am not aware, as it is not included into X-CUBE-CELLULAR. Did you check X-CUBE-AWS ?

To flash BG96 you can find information in the X-CUBE-CELLULAR zip at the following location:

Utilities\Modem_FW\BG96\Pack_BG96MAR02A08M1G_01.012.01.012.zip

Ronan,

[Ronan GABOU]

Hello Eyal,

You're right. Quectel delete or move the tool.

We are going to contact them to reestablish the link.

I will let you know when available.

Ronan,

[Ronan GABOU]

Hello Eyal,

Flasher could be found here: www.quectel.com/ProductDownload/QFlash_V4.18.zip

Ronan,

[SGunn.1]

Hello,

I was hoping to piggyback off this forum since I am struggling to activate the eSim. I am at the point where I need to retrieve the BIC so that I can activate the esim on emnify. At step 8 of the instruction doc to register the BIC of emnify.com I was inputting the commands but when I input step 8.1.2 the command does not return anything and I cannot retrieve the BIC hex string. I have attached a the log from tera term.

I also noticed my log differs from egoltzman log when cst_mode_sim_init runs. Mine states:

SysCtrl_BG96:MODEM SIM ESIM SELECTED

   CST_modem_sim_init : check SIM First

   ATParser:*** SEND (size=12) ***

whereas theirs states:

SysCtrl_BG96:MODEM SIM ESIM SELECTED

   CST_modem_sim_init : CST_modem_define_pdn

BG96:user cid = 1, modem cid = 1

   ATParser:*** SEND (size=27) ***

if you have a direction or solution for me that would be great thanks

ÿ-----> New State: BOOT_STATE <-----
BG96 UART config: BaudRate=115200 / HW flow ctrl=1
 
 
=============================
 X-CUBE-CELLULAR
 Version: V5.2.0
=============================
Select the application to run:
 
1: Setup configuration Menu
2: FAQ display
3: Modem power on (without application)
 
Or type any key to start
 
 
 
--------SETUP Configuration ----------
 Cellular Service from FEEPROM
 Echoclt from DEFAULT
 Grovestreams from DEFAULT
 Ping from DEFAULT
------------------------------------------
<< Status Begin >>
GlobalHeap : 28632=>3400 (init:28632) (480 SA usage)
Task number:13
StartDefaultTh n: 1 FreeHeap: 384=> 205 (init:384) Prio:4 State:X
IDLE n: 2 FreeHeap: 128=> 117 (init:128) Prio:0 State:R
Tmr Svc n: 3 FreeHeap: 256=> 245 (init:256) Prio:2 State:R
CMD_THREAD_DEF n: 4 FreeHeap: 600=> 589 (init:600) Prio:2 State:R
BoardButtonsTh n: 5 FreeHeap: 256=> 245 (init:256) Prio:3 State:R
atcoreTask n: 6 FreeHeap: 384=> 373 (init:384) Prio:3 State:R
cellularServic n: 7 FreeHeap: 512=> 501 (init:512) Prio:3 State:R
UICltThread n: 8 FreeHeap: 576=> 565 (init:576) Prio:3 State:R
EchoCltThread n: 9 FreeHeap: 448=> 437 (init:448) Prio:3 State:R
HttpCltThread n:10 FreeHeap: 448=> 437 (init:448) Prio:3 State:R
PingCltThread n:11 FreeHeap: 448=> 437 (init:448) Prio:3 State:R
ComCltThread n:12 FreeHeap: 448=> 437 (init:448) Prio:3 State:R
memsDclibTask n:13 FreeHeap: 320=> 309 (init:320) Prio:3 State:R
<< Status End >>
AUTOM TASK: BOOT_STATE - BOOT_EVENT
*********** CST_boot_event_mngt ********
-----> New State: MODEM_INIT_STATE <-----
AUTOM TASK: MODEM_INIT_STATE - MODEM_INIT_EVENT
*********** CST_init_state_mngt ********
SysCtrl_BG96:Waiting 5500 millisec for modem running...
SysCtrl_BG96:...done
 ATParser:*** SEND (size=11) ***
AT+IFC=2,2<CR>
 AT+IFC=2,2<CR><CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=3) ***
AT<CR>
 AT<CR><CR><LF>
 OK<CR><LF>
BG96:modem synchro established, proceed to normal power sequence
 ATParser:*** SEND (size=5) ***
ATE0<CR>
 ATE0<CR><CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=10) ***
AT+CMEE=2<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=5) ***
ATV1<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=6) ***
AT&D0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=8) ***
AT+CGMR<CR>
 <CR><LF>
 BG96MAR02A06M1G<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=12) ***
AT+CFUN=0,0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=11) ***
AT+CPSMS=0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=15) ***
AT+QCFG="band"<CR>
 <CR><LF>
 +QCFG: "band",0xf,0x400a0e189f,0xa0e189f<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=20) ***
AT+QCFG="iotopmode"<CR>
 <CR><LF>
 +QCFG: "iotopmode",0<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=20) ***
AT+QCFG="nwscanseq"<CR>
 <CR><LF>
 +QCFG: "nwscanseq",020301<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=21) ***
AT+QCFG="nwscanmode"<CR>
 <CR><LF>
 +QCFG: "nwscanmode",0<CR><LF>
 <CR><LF>
 OK<CR><LF>
BG96:>>>>> BG96 mode and bands configuration <<<<<
BG96:LTE Cat.M1 band active (scan rank = 1)
BG96:Cat.M1 BANDS config = 0x40a0e189f
BG96:CatM1_B1
BG96:CatM1_B2
BG96:CatM1_B3
BG96:CatM1_B4
BG96:CatM1_B5
BG96:CatM1_B8
BG96:CatM1_B12
BG96:CatM1_B13
BG96:CatM1_B18
BG96:CatM1_B19
BG96:CatM1_B20
BG96:CatM1_B26
BG96:CatM1_B28
BG96:CatM1_B39
BG96:GSM band active (scan rank = 2)
BG96:GSM BANDS config = 0xf
BG96:GSM_900
BG96:GSM_1800
BG96:GSM_850
BG96:GSM_1900
BG96:>>>>> ................................. <<<<<
*********** CST_modem_sim_init ********
SysCtrl_BG96:MODEM SIM ESIM SELECTED
 CST_modem_sim_init : check SIM First
 ATParser:*** SEND (size=12) ***
AT+CFUN=4,0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=9) ***
AT+QCCID<CR>
 <CR><LF>
 +CME ERROR: SIM failure<CR><LF>
ATCore ERROR:AT_sendcmd error
ATCore ERROR:AT_sendcmd error: parse from rsp
LOG ERROR #1: channel=2 / errorId=11 / gravity=2
LOG ERROR #2: channel=2 / errorId=14 / gravity=2
CST_modem_powered_on_state : No SIM found
=== CST_modem_sim_init Fail !!! ===
LOG ERROR #3: channel=11 / errorId=1 / gravity=2
-----> New State: MODEM_RESET_STATE <-----
Subscribe modems events
 AUTOM TASK: MODEM_RESET_STATE - MODEM_INIT_EVENT
*********** CST_modem_reset_mngt ********
 -----> New State: MODEM_INIT_STATE <-----
AUTOM TASK: MODEM_INIT_STATE - MODEM_INIT_EVENT
*********** CST_init_state_mngt ********

[Ronan GABOU]

It is no more possible to activate the Emnify eSIM, even if you get the BIC.

This was an added temporary option, Emnify does not support it anymore.

Solution is to use a plastic SIM card instead.

[TomC]

Hi Ronan,

I am using a plastic SIM however when running the project l496_bg96_socket_v601.bin in

STM32CubeExpansion_CELLULAR_V6.0.1\Projects\32L496GDISCOVERY\Demonstrations\Cellular\Binaries\l496_bg96_socket_v601.bin

I receive the output below notably containing "CME ERROR: SIM failure". This SIM card has been activated and successfully used with the QUECTELBG96 UMTS&LTE EVB development board. I was wondering if you knew of any obvious reason that the SIM card may not be working with the example code. Thank you

SysCtrl_BG96:Waiting 5500 millisec for modem running...
SysCtrl_BG96:...done
 ATParser:*** SEND (size=11) ***
AT+IFC=2,2<CR>
 AT+IFC=2,2<CR><CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=3) ***
AT<CR>
 AT<CR><CR><LF>
 OK<CR><LF>
BG96:modem synchro established, proceed to normal power sequence
 ATParser:*** SEND (size=5) ***
ATE0<CR>
 ATE0<CR><CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=10) ***
AT+CMEE=2<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=5) ***
ATV1<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=6) ***
AT&D0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=8) ***
AT+CGMR<CR>
 <CR><LF>
 BG96MAR02A06M1G<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=12) ***
AT+CFUN=0,0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=11) ***
AT+CPSMS=0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=15) ***
AT+QCFG="band"<CR>
 <CR><LF>
 +QCFG: "band",0xf,0x400a0e189f,0xa0e189f<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=20) ***
AT+QCFG="iotopmode"<CR>
 <CR><LF>
 +QCFG: "iotopmode",0<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=20) ***
AT+QCFG="nwscanseq"<CR>
 <CR><LF>
 +QCFG: "nwscanseq",020301<CR><LF>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=21) ***
AT+QCFG="nwscanmode"<CR>
 <CR><LF>
 +QCFG: "nwscanmode",0<CR><LF>
 <CR><LF>
 OK<CR><LF>
BG96:>>>>> BG96 mode and bands configuration <<<<<
BG96:LTE Cat.M1 band active (scan rank = 1)
BG96:Cat.M1 BANDS config = 0x40a0e189f
BG96:CatM1_B1
BG96:CatM1_B2
BG96:CatM1_B3
BG96:CatM1_B4
BG96:CatM1_B5
BG96:CatM1_B8
BG96:CatM1_B12
BG96:CatM1_B13
BG96:CatM1_B18
BG96:CatM1_B19
BG96:CatM1_B20
BG96:CatM1_B26
BG96:CatM1_B28
BG96:CatM1_B39
BG96:GSM band active (scan rank = 2)
BG96:GSM BANDS config = 0xf
BG96:GSM_900
BG96:GSM_1800
BG96:GSM_850
BG96:GSM_1900
BG96:>>>>> ................................. <<<<<
=====>CST_notif_callback (Data Cache event=0)
=====>CST_notif_callback (Data Cache event=0)
*********** modem state : CA_MODEM_STATE_POWERED_ON
*********** CST_modem_sim_init ********
Modem Boot OK
CST_modem_sim_init : CS_sim_select sim slot nb 0
SysCtrl_BG96:MODEM SIM SOCKET SELECTED
 CST_modem_sim_init : check SIM First
 ATParser:*** SEND (size=12) ***
AT+CFUN=4,0<CR>
 <CR><LF>
 OK<CR><LF>
 ATParser:*** SEND (size=9) ***
AT+QCCID<CR>
 <CR><LF>
 +CME ERROR: SIM failure<CR><LF>
ATCore ERROR:AT_sendcmd error
ATCore ERROR:AT_sendcmd error: parse from rsp
LOG ERROR #10: channel=1 / errorId=11 / gravity=2
LOG ERROR #11: channel=1 / errorId=14 / gravity=2
CST_modem_sim_init : Can't find sim on current slot. Increment sim slot.
CST_modem_sim_init : No more sim slot, no SIM found. Retry...
CST_modem_sim_init : Reboot modem.
=== CST_modem_sim_init Fail !!! ===
LOG ERROR #12: channel=2 / errorId=1 / gravity=2
-----> New State: MODEM_REBOOT_STATE <-----
Subscribe modems events
 AUTOM TASK: MODEM_REBOOT_STATE - PPP_OPENED_EVENT
*********** CST_modem_reboot_mngt ********
CST_modem_power_off
 Power off modem

[Ronan GABOU]

Hello,

The "SIM" issue is due to wrong BG96 modem FW

You have (from factory) : 02A06, I know because of the provided trace :

1. AT+CGMR<CR>
2. <CR><LF>
3. BG96MAR02A06M1G<CR><LF>
4. <CR><LF>
5. OK<CR><LF>

As mentioned in modem RN you must use : BG96MAR02A08M1G_01.012.01.012

STM32CubeExpansion_CELLULAR_V6.0.1\Drivers\BSP\X_STMOD_PLUS_MODEMS\Release_Notes.html (see 6.0.0 part)

See : STM32CubeExpansion_CELLULAR_V6.0.1\Utilities\Modem_FW\BG96\Pack_BG96MAR02A08M1G_01.012.01.012.zip\Pack_BG96MAR02A08M1G_01.012.01.012\How to flash BG96 board.pdf

to be able to upgrade your BG96 FW.

however Quectel removed links listed in the pdf, so you must go to quectel.com create an account an download the QFlash tool and the windows driver.

Then follow instructions.

Once you will have move BG96 FW from 06 to 08 version your application should be up & running

Ronan,

[TomC]

Hi Ronan,

Thank you for your response, the BG96 firmware version was indeed causing the problem and was noted in the release notes as you said. I was not able to successfully flash the BG96 with QFlash ver 5.3 receiving the QFlash error "at+qmbncfg=list FAIL" but I was able to use QFlash ver 4.12 successfully.

I was wondering also if there was a software expansion package that would allow me to demonstrate uploading data from the P-L496G-Cell02 to the cloud. I have flashed the "l496_bg96_lwip_v600.bin" example from the CELLULAR_V6.0.0 package however I believe it does not have the functionality I am after.

I have acquired the "STM32CubeFunctionPack_LTE1_V1.1.0" package however do not have a X-NUCLEO-IKS01A3 which I believe is required to run the "SBSFU_STM32L496G_AssetTracker.bin" example. Would it be reasonable for me to modify the example's source code to run it without the X-NUCLEO-IKS01A3 and upload data to the AWS dashboard detailed in this document.

I believe originally the P-L496G-Cell02 was meant to be demonstrated using ST's c2c infrastructure however it seems this infrastructure no longer exists or is not supported. The c2c infrastructure is meant to be used with the example program that comes loaded with the P-L496G-Cell02.

Many thanks,

Tom

EDIT: Hi Ronan, since my original post I have been trying to use the "STM32CubeExpansion_Cloud GenericV1.0.0" example package but in both the MQTT and Grovestreams example have not been in successful in proceeding beyond entering the SIM's APN, user and password, please see below the output from the Grovestream application. From the SIM providers web site:

"What is the Truphone IoT APN configuration?

The default Truphone IoT APN is: iot.truphone.com (without authentication).

Please refer to the SIM card information page on the IoT Connectivity Management Platform for specific customer APN configurations."

EDIT 2: I believe the reason the application is not proceeding is because I am loading a binary generated without #define USE_BG96. I am unsure how to relink the source file, drivers, utilities and middleware to rebuild with this macro defined. Thanks

(Example from: STM32CubeExpansion_Cloud GenericV1.0.0\Projects\STM32L496G-Discovery\Applications\Cloud\Grovestreams\Binary\STM32L496G-Discovery_Cloud_CLD_GEN_V1.0.0.bin)

*************************************************************
*** STM32 IoT Discovery kit for
*** STM32F413/STM32F769/STM32L475/STM32L496 MCU
*** X-CUBE-CLD-GEN Cloud Connectivity Demonstration
*** FW version 1.0.0 - 28-March-2018 02:18:56 PM
*************************************************************
 
*** Board personalization ***
 
 
*** C2C connection ***
 
Push the User button (Blue) within the next 5 seconds if you want to update the C2C configuration.
 
Your C2C parameters need to be entered to proceed.
 
Enter Sim Operator Access Point Code (e.g. EM or ESEYE1 etc): truphone.com
You have entered <iot.truphone.com> as the Sim Operator Access Point Code.
 
Enter the username (it can be NULL) (max 16 char):
You have entered <> as the username.
 
Enter the password (it can be NULL) (max 16 char):
You have entered <> as the password.
 
Initializing the C2C module
Trying to connect with the external SIM
C2C AT comunication error with the C2C device
C2C device might be disconnected or wrongly connected
Trying to connect with the embedded SIM
C2C AT comunication error with the C2C device
C2C device might be disconnected or wrongly connected
Error initializing the module!

[Ronan GABOU]

Hello Tom,

Good for modem FW update.

Yes X-CUBE-CELLULAR V6 example is a basic Echo TCP/UDP and Ping example.

Yes in previous version we had a connection to cloud (with HTTP) to Grovestrream cloud), it is no more provided because customer need to create a Grovestream account ... and it was no straight forward.

In another version we also supported MQTT that allow to connect to cloud, but you must start a MQTT broker reachable on Internet.

From V6 onward we decided to focus only on Cellular middleware that is the reason why we only had basic example.

We try to improve user experience in coming deliveries.

STM32CubeExpansion_Cloud GenericV1.0.0 is a very old package base on very old X-CUBE-CELLULAR.

I don't understand why Truphone because the MVNO used in CELL02 kits was Emnify (note it is no more activated so impossible to use eSIM on BG96). For those Kits you must use a plastic SIM.

[TomC]

Thanks Ronan,
I was ultimately able to get the Grove streams and generic MQTT example working using an external plastic SIM with Truphone in Australia. I will focus future efforts on understanding and integrating the middleware for driving the BG96. Is it necessary to use RTOS for applications that use the BG96 middleware?

[Ronan GABOU]

Hello Tom,

Great achievement :)

Yes the RTOS is mandatory to use Cellular Middleware.

Is it an issue for you ? Flash or RAM memories constraints ?

Ronan,

[TomC]

No I don't believe there will be constraints that prevent using RTOS, thank you

[BillB]

Gee, I wish I would have read over the community questions more carefully on the P-L496-CELL02 before I purchased it. I was expecting an out-of-the-box demo on cellular capabilities. What I instead encountered was a miserable journey hunting through various out-of-date documents describing features that don't exist then having to dig through community threads only to find out that the out-of-the-box experience has been deprecated.

There are three revisions of X-CUBE-CELLULAR. How do they evolve? Don't know. Why are there completely different demos in each one? Don't know. Do I need to update the modem firmware? If so, how do I do it? Don't know. Now that the eSIM can't be activated, what is the simplest alternative to demonstrate the dev kit? Don't know.

ST, you need to work on keeping up-to-date, coherent documents for your products, especially your dev kits.