Why mesh sdk goes to app_error_fault_handler before softdevice being inited?

[zzzh]

Hi,

I am testing the light switch sample in mesh sdk 2.2, in server part I need to drive an I2C slave device, which may take some time to init, so I put the init code after this line:

__LOG(LOG_SRC_APP, LOG_LEVEL_INFO, "----- BLE Mesh Light Switch Server Demo -----\n");

where is before softdevice being inited, so that it would not influence the sofdevice work.

But, the code always goes to app_error_fault_handler before the init code being finished, the error is Mesh error 17 at 0x00000000.

The init code is just some twi operation and nrf_delay, which should be good because sometimes by running from breakpoint to next breakpoint, the device can work correctly.

I also tried it in nRF5_SDK_15.0.0_a53641a, where it can last longer but also goes to app_error_fault_handler at last.

So why this is happening and how to solve it?

[Hung Bui]

Hi, 

Could you send a screen short of the RTT log ? The address at 0x000000 sounds strange . Error 0x17 is NRF_ERROR_BUSY , maybe you trying to do something that is underway ?  

[zzzh]

Hi, Hung,

It's error 17, not 0x17.

[zzzh]

So, no one can reply this?

[zzzh]

Used nrf_drv_twi_tx in send_cmd, confirm twi_tx is done when get NRF_DRV_TWI_EVT_DONE in event_handler.

Nothing underway.

[Hung Bui]

Hi Bob, 

I'm sorry for the late response, it was due to the New Year holiday. 

Could you post what inside your send_cmd()  function ? I would suspect that nrf_drv_twi_tx() was throwing the error. Are you sure you give enough time for the TWI to send the data ? If you increase the delay would it work ?