Hi Ukhan717,
The AT commands of BG95 and BG96 are very similar.
We have tested on the BG95 EVB board with firmware version BG95M1LAR02A02_01.002.01.002.
After applying the patch below, the windows simulator demo project of BG96 can run with this BG95 EVB in our environment.
We suggest updating the BG95 firmware to the latest. In the past we did see more incompatibility between BG96 and BG95. But after updating firmware the difference narrowed, and we were able to make it work by just applying the patch below to the BG96 library.
You can run the BG96 demo (Lab-Project-FreeRTOS-Cellular-Demo/projects/bg96_mqtt_mutual_auth_demo at main · FreeRTOS/Lab-Project-FreeRTOS-Cellular-Demo · GitHub) after applying this patch:
$ git diff modules/bg96/cellular_bg96.c
diff --git a/modules/bg96/cellular_bg96.c b/modules/bg96/cellular_bg96.c
index 718d88a..b6b3e8e 100644
--- a/modules/bg96/cellular_bg96.c
+++ b/modules/bg96/cellular_bg96.c
@@ -233,6 +233,7 @@ CellularError_t Cellular_ModuleEnableUE( CellularContext_t * pContext )
cellularStatus = sendAtCommandWithRetryTimeout( pContext, &atReqGetNoResult );
}
+#if 0
if( cellularStatus == CELLULAR_SUCCESS )
{
/* Configure Band configuration to all bands. */
@@ -275,6 +276,7 @@ CellularError_t Cellular_ModuleEnableUE( CellularContext_t * pContext )
}
cellularStatus = sendAtCommandWithRetryTimeout( pContext, &atReqGetNoResult );
}
+#endif
if( cellularStatus == CELLULAR_SUCCESS )
{
The prvProcessReceivedCommands function is in the FreeRTOS kernel. It’s hard to root cause the problem by looking at the log you provided above.
We suggest you reuse the BG96 code with the patch first. If that doesn’t work, can you please enable the debug log in the cellular library, reproduce the issue then send us the log? Here is how to enable the log:
Change LOG_INFO to LOG_DEBUG.