softdevice enable +usbd - deadbeef error

Question

Hi, 
 I'm working on a project using BLE via s140, everything was working fine until I wanted to implement usb. 
 I created a blank project in order to validate the usbd then once validated, I implemented it to my BLE project. 
 when the code enable the softdevice, I'm redirected to app_error_fault_handler. You can see below id's error and p_info who tell me that err_code equal to 0xdeadbeef 
 
 Sometime I get 0x165 for the line_num. 
 
 It's noted that I'm using freeRTOS for my program and here is the memory mapping:

I also oversized freeRTOS heap's size to rule out any related problem. 
 
thanks for your support

Susheel Nuguru · Accepted Answer

This is an SDK error 
 
 And looking at the p_info structure, it gives the file name and line number

looking at nrf_drv_power.c line 0x165 which is deciman 357 
 
 It looks to me that this function is called without the nrf_drv_power being initialized. Setting a breakpoint here and running again shows the call stack 
 
 The nrf_drv_power_init is called in app_usbd_init which is called in your usbd_thread. But this thread does not start until the scheduler starts later on. 
 Cleaner way would be just call this below before ble_stack_init 
 #if APP_USBD_CONFIG_POWER_EVENTS_PROCESS
 uint32_t ret = nrf_drv_power_init(NULL);
 if ((ret != NRF_SUCCESS) && (ret != NRF_ERROR_MODULE_ALREADY_INITIALIZED))
 {
 /* This should never happen */
 APP_ERROR_HANDLER(ret);
 }
#endif 
 I see that later you ble_advertising_init is failing with a wrong data size but that is a different error and seems like the data you are trying to fit into your advertising packet does not fit the legacy adv packet.

Susheel Nuguru · Answer

It seems like you verified this thread and hence it comes out of my queue. I opened it again to be able to watch it. 
 
 Pegaze said: ret_code = sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler); 
 This is strange, but possible to happen if you have given the clock configuration wrong? 
 It looks like you have set the NRF_SDH_CLOCK_LF_SRC in the sdk_config.h to XTAL. The softdevice might stall waiting for the XTAL to start if there is no XTAL or if your XTAL is not starting up as it should. Please check if this setting is right for you?

Pegaze · Answer

Thanks again! 
 
 That's exactly it, I don't have an XTAL so changing the configuration to use RC makes everything work. 
 
 Thank you for your responsiveness and invaluable support.

softdevice enable +usbd -> deadbeef error

Top Replies