cancel
Showing results for 
Search instead for 
Did you mean: 

simple project work on P-NUCLEO-WB55 but not on custom pcb

oga
Associate III

I've prepared a small device firmware for a STM32WB35CEU7A

it's only providing battery service and debug infos on serial

I've tested it on a P-NUCLEO-WB55 loaded with stm32wb5x_BLE_Stack_full_fw.bin1.19.02 stack loaded @0x080CE000 and it works wonderfully even if .ioc file is based on STM32WB35CEU7A and not on WB55

on debug serial all startup is complete :

[app_entry.c][APPE_SysUserEvtRx][362] Wireless Firmware version 1.19.0
[app_entry.c][APPE_SysUserEvtRx][363] Wireless Firmware build 2
[app_entry.c][APPE_SysUserEvtRx][364] FUS version 1.2.0
[app_entry.c][APPE_SysUserEvtRx][366] >>== SHCI_SUB_EVT_CODE_READY
[app_entry.c][APPE_SysEvtReadyProcessing][452] >>== WIRELESS_FW_RUNNING
[app_entry.c][APPE_SysEvtReadyProcessing][476] >>== DBGMCU_GetRevisionID= 2003
[app_entry.c][APPE_SysEvtReadyProcessing][481] >>== DBGMCU_GetDeviceID= 495
[app_ble.c][APP_BLE_Init][333] Success: SHCI_C2_BLE_Init command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][715] ==>> Start Ble_Hci_Gap_Gatt_Init function
[app_ble.c][Ble_Hci_Gap_Gatt_Init][728] Success: hci_reset command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][742] Success: aci_hal_write_config_data command - CONFIG_DATA_PUBADDR_OFFSET
[app_ble.c][Ble_Hci_Gap_Gatt_Init][743] Public Bluetooth Address: 00:80:e1:27:a3:ce
[app_ble.c][Ble_Hci_Gap_Gatt_Init][821] Success: aci_hal_write_config_data command - CONFIG_DATA_IR_OFFSET
[app_ble.c][Ble_Hci_Gap_Gatt_Init][834] Success: aci_hal_write_config_data command - CONFIG_DATA_ER_OFFSET
[app_ble.c][Ble_Hci_Gap_Gatt_Init][847] Success: aci_hal_set_tx_power_level command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][860] Success: aci_gatt_init command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][896] Success: aci_gap_init command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][934] Success: hci_le_set_default_phy command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][948] Success: aci_gap_set_io_capability command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][979] Success: aci_gap_set_authentication_requirement command
[app_ble.c][Ble_Hci_Gap_Gatt_Init][997] ==>> End Ble_Hci_Gap_Gatt_Init function
[custom_stm.c][SVCCTL_InitCustomSvc][298] Success: aci_gatt_add_service command: Batt
[custom_stm.c][SVCCTL_InitCustomSvc][320] Success: aci_gatt_add_char command : LVL
[app_ble.c][APP_BLE_Init][373] Success: aci_hal_set_radio_activity_mask command
[app_ble.c][Adv_Request][1023] ==>> aci_gap_set_discoverable - Success
[app_ble.c][Adv_Request][1038] ==>> Success: Start Fast Advertising

and I can connect / notify characteristics etc ....


on our custom design PCB we have put a WB35 and co-processor is filled with stm32wb3x_BLE_Stack_full_fw.bin 1.19.02 @0x0805A000

exactly same firmware is fitted, unfortunately it looks that something don't match between both processor because it stays at FUS level.

[app_entry.c][APPE_SysUserEvtRx][362] Wireless Firmware version 1.19.0
[app_entry.c][APPE_SysUserEvtRx][363] Wireless Firmware build 2
[app_entry.c][APPE_SysUserEvtRx][364] FUS version 1.2.0
[app_entry.c][APPE_SysUserEvtRx][366] >>== SHCI_SUB_EVT_CODE_READY
[app_entry.c][APPE_SysEvtReadyProcessing][494] >>== SHCI_SUB_EVT_CODE_READY - FUS_FW_RUNNING

Even if main processor loop continue to run, it act as if no HCI event come back from co-processor ...

tank's for any idea and/or debugging process

1 ACCEPTED SOLUTION

Accepted Solutions
oga
Associate III

I did finally getting it to work on custom pcb too but after many stack reset and reflash even if nothing changed I dont explain realy good how it turns to works or not I ve try to fill WB3 stack on P nucleo and other configuration that dosen't work and after coming back to good stack and good flash adress I got the same error on P-Nucleo wb55 and after many stack reset it falls into works also ... I can't explain

View solution in original post

1 REPLY 1
oga
Associate III

I did finally getting it to work on custom pcb too but after many stack reset and reflash even if nothing changed I dont explain realy good how it turns to works or not I ve try to fill WB3 stack on P nucleo and other configuration that dosen't work and after coming back to good stack and good flash adress I got the same error on P-Nucleo wb55 and after many stack reset it falls into works also ... I can't explain