STM32WL55 DEBUG MODE ISSUE
Hello,
I have a project on STM32WL55 which runs on dual core CM0+ and CM4.
When i put it in debug mode using the development board STM32WL55 Nuleo-64 (NUCLEO-WL55JC1), it goes into debug mode without any issue. Both the cores are getting debugged.
Procedure :
Launching the configurations
Launch the Cortex®‑M4 configuration to download both the Cortex®‑M0+ and Cortex®‑M4 images.
Resume the Cortex®‑M4 core until the C2BOOT bit is set in power control register 4 (PWR_CR4) to enable
the Cortex®‑M0+.
Launch the Cortex®‑M0+ configuration using the arrow next to the debug icon. The Cortex®‑M0+ is in the
running mode and the user can halt it after the debugger is started.
Now, I want to debug the same code in a customized PC having STM32WL55CCU6. It is not going in debug mode which means it gets stuck here :
void MBMUXIF_SystemSendCmd(FEAT_INFO_IdTypeDef SystemPrioFeat)
{
/* USER CODE BEGIN MBMUXIF_SystemSendCmd_1 */
/* USER CODE END MBMUXIF_SystemSendCmd_1 */
if (SystemPrioFeat == FEAT_INFO_SYSTEM_ID)
{
MbSystemRespRcvFlag = 0; /* To avoid using Sequencer during Init sequence for SysCmd */
if (MBMUX_CommandSnd(FEAT_INFO_SYSTEM_ID) == 0)
{
if (AllowSequencerForSysCmd)
{
UTIL_SEQ_WaitEvt(1 << CFG_SEQ_Evt_MbSystemRespRcv);
}
else
{
/* To avoid using Sequencer (& LowPower) during Init sequence for SysCmd */
while (!MbSystemRespRcvFlag) {}
}
}
else
{
Error_Handler();
}
}
else
{
/* USER CODE BEGIN MBMUXIF_SystemSendCmd_2 */
/* USER CODE END MBMUXIF_SystemSendCmd_2 */
}
/* USER CODE BEGIN MBMUXIF_SystemSendCmd_Last */
/* USER CODE END MBMUXIF_SystemSendCmd_Last */
}In the above code MbSystemRespRcvFlag never becomes 1 from 0 due to which it gets stuck in
while (!MbSystemRespRcvFlag) {} loop forever.
But the above issue does not occur with NUCLEO-WL55JC1 development board.
It displays the msg :
STM32WL55 DUAL CORE DEBUG ERROR MSG : Failed to execute MI Command: - exec-next 1 Error message from debugger backend: Cannot find bounds of current function.
I have tried all possible solutions but unable to figure out the issue.
Please help me to find where is the issue.
Thanks.