tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

RE: tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

Maria Gilje — Thu, 15 Jun 2023 11:40:05 GMT

Hi Brad,

I am following up on this ticket while Raoul is on vacation.

Does replacing line 60 with

#define MSG_TO_SEND {'U'}

work for you?

Best regards,

Maria

RE: tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

rockerderek — Mon, 12 Jun 2023 16:55:31 GMT

Hi Raoul,

I can't set it to a char due to the error in the attached picture. The path to this example code is:

modules\hal\nordic\nrfx\samples\src\nrfx_uarte\tx_rx_non_blocking

RE: tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

Raoul — Mon, 12 Jun 2023 12:28:21 GMT

Hi Brad,

Could you try replacing "U" with 'U' on line 68?

I think the double quotes make "U" into a string literal, with an implicit /0 at the end. Single quotes would make it a char literal. I think this explanation is relevant: https://stackoverflow.com/questions/31179386/difference-between-char-and-strings-in-c

I wanted to try this in your code, but for some reason I'm not able to build the project you uploaded.

[quote user="rockerderek"]Since this is the example code from the latest nRF Connect SDK[/quote]

Where did you take this from? Just curious, since this is definitely no ordinary Zephyr setup.

Let me know if the fix works!

Best regards,

Raoul

RE: tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

rockerderek — Sun, 11 Jun 2023 23:07:39 GMT

Hi Raoul,

Since this is the example code from the latest nRF Connect SDK, I'm not familiar with which part of the HAL is causing the string terminator. Could you take a look at what is causing the string terminator to be sent so I can remove it? Then the code will meet our needs.

Thanks,

Brad

RE: tx_rx_non_blocking example sends extra byte of zeros (nRF5340)

Raoul — Thu, 08 Jun 2023 19:05:40 GMT

Hi Brad,

If I'm not mistaken, the second transmission is simply the string terminator which in C is just NUL.

Instead of sending a single char, your code is sending a string that consist of "U" (0x55) and then "\0" (0x00).

I don't have time today to dig into the code you've shared (although I appreciate you sharing it, it often makes things easier), but if you're still stuck after this I'll gladly take a look.

Best regards,

Raoul