UART k_fifo_get lose bytes of data from response

RE: UART k_fifo_get lose bytes of data from response

Vidar Berg — Wed, 24 Jan 2024 11:14:38 GMT

The only relevant setting I see here is the CONFIG_SERIAL option, which enables the serial driver. However, to pinpoint the root cause of the issue, it would be helpful to include more logging from the UART async callback to determine where it is failing. It might also be beneficial to use a debugger to read out the receive buffers and verify if any bytes are missing from them. Have you made any modifications to the orginal UART callback?

RE: UART k_fifo_get lose bytes of data from response

Mati — Tue, 23 Jan 2024 13:57:02 GMT

Differences in prj.config (the old one below):
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_MAIN_STACK_SIZE=1152
CONFIG_SERIAL=y
CONFIG_GPIO=y

RE: UART k_fifo_get lose bytes of data from response

Mati — Tue, 23 Jan 2024 13:53:38 GMT

... All data is basically gathered using code snippet above (with EOL data check to break loop faster)

With configuration line for anomaly 198 all data is received correctly as below (41 bytes, calculatec and compared CRC pass):
```
[00:01:58.116,760] <inf> QWERTY: Cells bytes read = 41
[00:01:58.116,790] <inf> QWERTY: Data: 22 02 08 21 10 0c ea 0d 06 0d
[00:01:58.116,790] <inf> QWERTY: Data: 0a 0d 02 0d 08 0d 09 0d 09 0d
[00:01:58.116,821] <inf> QWERTY: Data: 07 0d 05 0d 06 0d 07 0d 03 0d
[00:01:58.116,851] <inf> QWERTY: Data: 04 0d 04 0d 04 0d 03 bd af 0d
[00:01:58.116,851] <inf> QWERTY: Data: 0a 00 00 00 00 00 00 00 00 00
[00:01:58.116,973] <inf> QWERTY: CELLS CRC PASS: bdaf
```
Without CONFIG_NRF52_ANOMALY_198_WORKAROUND configuration line I got (al least previously - I specially get device with program writen previously and after uncommenting CONFIG_NRF52_ANOMALY_198_WORKAROUND it worked as below... I removed build, checked if it is same as previous configuration, configured it and it is working corerectly... after I made git checkout to the prevoius commit compiled and upload,there are missing bytes as below, yet CONFIG_NRF52_ANOMALY_198_WORKAROUND didnt made a change, thus it is (possibly) not this - I need to compare prj.conf and derive probable cause for loss of bytes...) data as below:
```
[00:00:12.108,978] <inf> QWERTY: Cells bytes read = 37
[00:00:12.109,008] <inf> QWERTY: Data: 22 02 08 21 10 0c ea 0d 06 0d
[00:00:12.109,039] <inf> QWERTY: Data: 0a 0d 02 08 0d 0a 0d 09 0d 08
[00:00:12.109,039] <inf> QWERTY: Data: 05 0d 05 0d 07 0d 03 04 0d 04
[00:00:12.109,100] <inf> QWERTY: Data: 0d 04 0d 02 ae 0d 0a 00 00 00
[00:00:12.109,130] <inf> QWERTY: Data: 00 00 00 00 00 00 00 00 00 00
[00:00:12.109,283] <inf> QWERTY: CELLS CRC ERROR: 9129 ;BMS CRC: 0000
```

RE: UART k_fifo_get lose bytes of data from response

Vidar Berg — Tue, 23 Jan 2024 13:24:29 GMT

Thanks for the update, but I'm not sure how this fixed the problem. This Kconfig symbol enables the workaround for [198] SPIM: SPIM3 transmit data might be corrupted.

CONFIG_NRF52_ANOMALY_198_WORKAROUND

RE: UART k_fifo_get lose bytes of data from response

Mati — Tue, 23 Jan 2024 13:19:53 GMT

... it seems that anomaly 198 is also on this chip (or whole line 52?) - after adding line below everything works fine

CONFIG_NRF52_ANOMALY_198_WORKAROUND=y

RE: UART k_fifo_get lose bytes of data from response

Vidar Berg — Mon, 22 Jan 2024 13:54:53 GMT

Hello,

I'm not able to spot any problems with the code snippet you posted. To further debug this issue, I recommend adding more logging to the code to help determine where the bytes are being lost.

Note: the debug logs are printed over RTT. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/peripheral_uart/README.html#debugging

Best regards,

Vidar