2025-07-16 1:48 PM - last edited on 2025-07-21 5:03 AM by Andrew Neil
Ever since being forced to update STM32CubeIde, every time a change is made to the .ioc file and the code is regenerated the following errors show up.
app_ble.c
/**
* Write the BD Address
*/
p_bd_addr = BleGetBdAddress();
ret = aci_hal_write_config_data(CONFIG_DATA_PUBLIC_ADDRESS_OFFSET, CONFIG_DATA_PUBLIC_ADDRESS_LEN, (uint8_t*) p_bd_addr);
if (ret != BLE_STATUS_SUCCESS)
{
APP_DBG_MSG(" Fail : aci_hal_write_config_data command - CONFIG_DATA_PUBLIC_ADDRESS_OFFSET, result: 0x%x \n", ret);
}
else
{
APP_DBG_MSG(" Success: aci_hal_write_config_data command - CONFIG_DATA_PUBLIC_ADDRESS_OFFSET\n");
APP_DBG_MSG(" Public Bluetooth Address: %02x:%02x:%02x:%02x:%02x:%02x\n",p_bd_addr[5],p_bd_addr[4],p_bd_addr[3],p_bd_addr[2],p_bd_addr[1],p_bd_addr[0]);
}
CONFIG_DATA_PUBLIC_* needs to be changed to CONFIG_DATA_RANDOM_*
case ACI_HAL_WARNING_VSEVT_CODE:
{
aci_hal_warning_event_rp0 *p_warning_event;
p_warning_event = (aci_hal_warning_event_rp0 *)p_blecore_evt->data;
UNUSED(p_warning_event);
APP_DBG_MSG(">>== ACI_HAL_WARNING_VSEVT_CODE\n");
APP_DBG_MSG("Warning Type = 0x%02X\n", p_warning_event->Warning_Type);
/* USER CODE BEGIN ACI_HAL_WARNING_VSEVT_CODE */
//
/* USER CODE END ACI_HAL_WARNING_VSEVT_CODE */
break;
}
Apparently, ACI_HAL_WARNING_VSEVT_CODE is no longer a thing.
../STM32_WPAN/App/app_ble.c: In function 'SVCCTL_App_Notification':
../STM32_WPAN/App/app_ble.c:673:14: error: 'ACI_HAL_WARNING_VSEVT_CODE' undeclared (first use in this function); did you mean 'ACI_HAL_FW_ERROR_VSEVT_CODE'?
673 | case ACI_HAL_WARNING_VSEVT_CODE:
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
| ACI_HAL_FW_ERROR_VSEVT_CODE
../STM32_WPAN/App/app_ble.c:673:14: note: each undeclared identifier is reported only once for each function it appears in
../STM32_WPAN/App/app_ble.c:675:11: error: unknown type name 'aci_hal_warning_event_rp0'; did you mean 'aci_hal_fw_error_event_rp0'?
675 | aci_hal_warning_event_rp0 *p_warning_event;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| aci_hal_fw_error_event_rp0
../STM32_WPAN/App/app_ble.c:677:34: error: 'aci_hal_warning_event_rp0' undeclared (first use in this function); did you mean 'aci_hal_fw_error_event_rp0'?
677 | p_warning_event = (aci_hal_warning_event_rp0 *)p_blecore_evt->data;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
| aci_hal_fw_error_event_rp0
../STM32_WPAN/App/app_ble.c:677:61: error: expected expression before ')' token
677 | p_warning_event = (aci_hal_warning_event_rp0 *)p_blecore_evt->data;
#define CFG_BLE_MAX_ADD_EATT_BEARERS (4)
../STM32_WPAN/App/app_ble.c: In function 'APP_BLE_Init':
../Core/Inc/app_conf.h:360:49: warning: excess elements in struct initializer
360 | #define CFG_BLE_MAX_ADD_EATT_BEARERS (4)
| ^
../STM32_WPAN/App/app_ble.c:302:10: note: in expansion of macro 'CFG_BLE_MAX_ADD_EATT_BEARERS'
302 | CFG_BLE_MAX_ADD_EATT_BEARERS
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
../Core/Inc/app_conf.h:360:49: note: (near initialization for 'ble_init_cmd_packet.Param')
360 | #define CFG_BLE_MAX_ADD_EATT_BEARERS (4)
| ^
../STM32_WPAN/App/app_ble.c:302:10: note: in expansion of macro 'CFG_BLE_MAX_ADD_EATT_BEARERS'
302 | CFG_BLE_MAX_ADD_EATT_BEARERS
What am I doing wrong, do I need to do something, so it generates the code correctly?
Kindest regards
2025-08-12 6:51 AM
Opening .ioc file directly in STM32CubeIDE can be buggy sometimes.
I recommend opening the .ioc file in standalone version STM32CubeMX.
Please try the older version as I mentioned before.
Could you please tell me what system do you use (OS)?
Thank you.
Best regards,
Filip Kremen
2025-08-12 6:54 AM
On some projects, when trying to open a .ioc, I get this:
Why is this so broken :(?
2025-08-12 6:58 AM - edited 2025-08-12 6:58 AM
I don't see where a specific version of STM32CubeMX was recommended. Can you please let me know which version you'd like me to try? Installing the latest version is what has created the situation of not being able to open any of my existing .ioc files.
I'm using Windows 10.
Kindest regards.
2025-08-12 7:05 AM
I tried installing an older version of STM32CubeMX and I get this error:
I guess there's no going back now :(.
Kindest regards.
2025-08-12 6:38 PM
As per your suggestion, I also installed STM32CubeIDE v1.18.1 and get the same error I get from STM32CubeMX.
Kindest regards.
2025-08-13 12:10 AM
Hello,
please try to open the .ioc file in standalone version of STM32CubeMX.
You can download the standalone version here.
STM32CubeMX | Software - STMicroelectronics
Best regards,
ST support