NRF_SERIAL_EVENT_DRV_ERR on disconnect

[rodriguise]

I am using nrf_serial in IRQ mode to communicate with an AT based device. When I reset the device using ATZ, I get NRF_SERIAL_EVENT_DRV_ERR -- likely because the pins go into an undefined state.

Is there anyway to recover from this state? After this happens nrf_serial_read always returns NRF_ERROR_TIMEOUT.

Thanks

PC10040 SDK 14 ARMGCC toolchain

[Jørgen Holmefjord]

This looks similar to this issue. Could you check if the suggestions in the comment from @hungbui helps on the issue?

[rodriguise]

It is not. My FIFOs are at 64 bytes the timeout is 1000ms. Those recommendations did not solve the problem. I believe the serial port is in a bad state because when the the MCU resets it drives the pins low. I can't find anything in the SDK to solve this.

[Jørgen Holmefjord]

nrf_serial does not start RX again after an error. Could you try calling nrf_serial_uninit() and then nrf_serial_init() again when the error occurs? This should start RX again.

[rodriguise]

I have tried this, however nrf_serial_uninit() for some reason is return NRF_ERROR_FEATURE_NOT_ENABLED. Which makes no sense what soever because a subsequent call to nrf_serial_init() returns NRF_ERROR_MODULE_ALREADY_INITIALIZED.

[Jørgen Holmefjord]

I cannot find the error code NRF_ERROR_FEATURE_NOT_ENABLED anywhere in the nrf_serial library. nrf_serial_uninit can only return NRF_SUCCESS, NRF_ERROR_BUSY, NRF_ERROR_NOT_SUPPORTED, or NRF_ERROR_MODULE_NOT_INITIALZED. Are you sure this is the error you are seeing?