nrf_serial_read() stops receiving data after about 300 bytes with SDK V16

[dannyhacker1]

I have taken the examples\peripheral\serial example and made minor changes (NRF_UART_HWFC_ENABLED to NRF_UART_HWFC_DISABLED, commented out bsp_board_init).

I have a USB chip directly wired to nRF52840's pin P0.06 and P0.08.

I able to connect to a terminal program (Tera Term) and when I type manually, it works as expected.

However, when I send an ASCII file, it seems to choke at about 330 bytes.  (When I run the serial_uartes example with 2 USB chips connected to nRF52840, I can send about 2 to 8 bytes before it chokes).

Read errors are returning timeouts but it seems that no events are being generated.  What can be done to fix this?  I saw a post about resetting via user defined event handler (nrf_serial_read() stops receiving data after some time.), but I was hoping to keep this as simple as possible (like maybe check for error status and reset appropriately?).

Thanks!

[Vidar Berg]

Hi,

The Serial port library must be re-initialized to recover from UART communications errors such as framing errors. Libuarte - advanced UARTE driver may be a better option if the goal is to receive data fast without flow control, or have you considered it already? There is a separate example for it located in the peripheral folder: Libuarte Example.