RE: How do I recover from a failed I2C write?

zhwzh308 — Wed, 18 May 2016 14:14:01 GMT

Then you will have to uninit nrf_drv_twi, and init again. Do this in the error handler.

RE: How do I recover from a failed I2C write?

olduvai — Wed, 18 May 2016 02:14:02 GMT

Thanks but that doesn't help. ALL successive writes fail with NRF_ERROR_INTERNAL after the initial problem.

RE: How do I recover from a failed I2C write?

zhwzh308 — Wed, 18 May 2016 00:27:25 GMT

Just skip APP_ERROR_CHECK and replace it with if statement, or if you really want to do this properly, define your own fault handler in this form: void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info). This essentially overrides the weakly defined app_error_fault_handler so you can define routine to handle specific error from your code.

For example:

/**
 * Function is implemented as weak so that it can be overwritten by custom application error handler
 * when needed.
 */
void app_error_fault_handler(uint32_t id, uint32_t pc, uint32_t info)
{
    // On assert, the system can only recover with a reset.
#ifndef DEBUG
    NVIC_SystemReset(); // Override this if you like, so it does not reboot
#else

#ifdef BSP_DEFINES_ONLY
    LEDS_ON(LEDS_MASK); // Only runs if you have Board Support Package with LEDs configured
#else
    UNUSED_VARIABLE(bsp_indication_set(BSP_INDICATE_FATAL_ERROR));
    // This call can be used for debug purposes during application development.
    // @note CAUTION: Activating this code will write the stack to flash on an error.
    //                This function should NOT be used in a final product.
    //                It is intended STRICTLY for development/debugging purposes.
    //                The flash write will happen EVEN if the radio is active, thus interrupting
    //                any communication.
    //                Use with care. Uncomment the line below to use.
    //ble_debug_assert_handler(error_code, line_num, p_file_name);
#endif // BSP_DEFINES_ONLY

    app_error_log(id, pc, info);
//    app_error_save_and_stop(id, pc, info); // You may want to continue your code execution.

#endif // DEBUG
}