Skip to main content
PDeng
PDeng
Associate II
October 23, 2019
Question

WB55 Nucleo always drops to Default_Handler() -> infinite loop

  • October 23, 2019
  • 5 replies
  • 1963 views

Hey guys,

now that the problem with the linker table is finally fixes with FW1.3.0 I have encountered another problem:

If I create a new project in CubeIDE using the standard pin configuration for the WB55 Nucleo board and start debugging after the init sequence the mcu jumps to the Default_handler (startup_....s).

Anybody knows how to fix this?

Best regards,

Philipp

This topic has been closed for replies.

5 replies

PDeng
PDengAuthor
Associate II
October 23, 2019

Quick update:

This could be related to CPU2 boot. This never happens. If the transport layer is enabled the Default_Handler is called.

PDeng
PDengAuthor
Associate II
October 24, 2019

Another update:

Did a clean install on WIN10. CubeIDE 1.1.0 and WB Firmware 1.3.0. Can anyone confirm this is working?

Thank you.

PDeng
PDengAuthor
Associate II
October 24, 2019

Flashed BLE_Stack_fw.bin (1.3.1) to the Nucleo board with no problems. Still the minimal running example keeps jumping to the default_handler as soon as the transport layer is enabled. I tried another WB55 board with the same results while the older projects (like examples or FW_WB 1.2.0) are running fine.

I'd really appreciate any help, this is urgend (as it is an actual product development).

PDeng
PDengAuthor
Associate II
October 24, 2019

Ok, so I tracked the source of the interrupt down (at one point I obviously knew my setup routine). If you encounter a similar problem add the following to your stm32wbxx_it.c:

void RTC_WKUP_IRQHandler(void)
{
 HW_TS_RTC_Wakeup_Handler();
}
 
void IPCC_C1_TX_IRQHandler(void)
{
 HW_IPCC_Tx_Handler();
}
 
void IPCC_C1_RX_IRQHandler(void)
{
 HW_IPCC_Rx_Handler();
}

Maybe this is helpful to someone.

    Ozone
    Ozone
    Principal
    October 24, 2019

    Enabling interrupts without providing a handler will get you into the hardfault handler, yes.

    This is a bug in your project. Providing the respective code upfront would have helped.

    > I'd really appreciate any help, this is urgend (as it is an actual product development).

    This is an open forum with mostly volunteers, not affiliated with ST. Most have a dayjob of their own.

    You can't expect others to solve your problems immediately, for free. And neither hold them responsible.

    PMark.1
    PMark.1
    Visitor II
    March 2, 2020

    Thank you PDeng, had the same error with automatic generated code from STM32CubeMX.

    Terms & ConditionsAccessibility statement