Skip to main content
DNumk
DNumk
Associate
February 7, 2024
Question

assert_failed() called inside BleStack_Init() with USE_FULL_ASSERT

  • February 7, 2024
  • 2 replies
  • 1144 views

assert_failed() is being called inside BleStack_Init() with USE_FULL_ASSERT defined.  By default, Stm32CubeMx does not define USE_FULL_ASSERT so assert_failed() would have never been called.  

Either way, BleStack_Init() returns zero causing APP_BLE_Init() to initialize gapp and gatt.  No problems.

Question: Is the call to assert_failed() by design?  Should I ignore assert_failed() during a call to BleStack_Init().

I am using Nucleo-WBA52CG, STM32Cube_FW_WBA_V1.2.0, arm-gnu-toolchain-13.2.Rel1-x86_64-arm-none-eabi and Ubuntu 22.

 

 

This topic has been closed for replies.

2 replies

Pavel A.
Pavel A.
February 7, 2024

> Should I ignore assert_failed() 

No, you should understand why it is called and why the developer placed the assert statement at that place. Yes, it can be mistake or bug, but more likely it is not.

 

DNumk
DNumkAuthor
Associate
March 8, 2024

I am still getting an assert failure while calling BleStack_Init().  I get the failure in both stm32wba_ble_stack_basic.a and stm32wba_ble_stack_full.a.

Here is the call stack at the time of failure using stm32wba_ble_stack_basic.a and LinkLayer_BLE_Basic_lib.a.

DNumk_1-1709932008270.png

The failure occurs in mem_pool_init().  Unfortunately, the assert doesn't come with an error code or a cause.

Any idea what the cause might be and how to fix the failure?

 

 

Terms & ConditionsAccessibility statement