Getting UART transmitted data length

RE: Getting UART transmitted data length

ovrebekk — Tue, 05 Oct 2021 09:09:30 GMT

Hi Spencer

[quote user="SpencerEtn"]If i send a frame of data of [1,2,3,4,5,6,7] after the buffer would then become [7,2,3,4,5,6].[/quote]

You mean the next one would be [7,1,2,3,4,5] right?

Otherwise it looks like you have lost a byte, which would definitely be a problem.

Do you know how much of a delay there would be between each transaction?

If the delay is relatively large you could always set a shorter timeout, so that the UART RX times out between each message.
This doesn't make the buffers align like you request, but it would ensure that receive a complete message before the next one starts.

Message one would be received as: [1,2,3,4,5,6] followed by [7]

Then the second message would be [1,2,3,4,5] (with offset 1) followed by [6,7]

Third message [1,2,3,4] (offset 2) followed by [5,6,7]

And so on...

[quote user="SpencerEtn"]It may be more headache than it is worth but thanks for the help anyways![/quote]

I think so, yes.

It is also risky to trust too much in the exact behavior of the UART driver, as this might change between SDK versions, or depending on which chip you are using.

Best regards
Torbjørn

RE: Getting UART transmitted data length

SpencerEtn — Mon, 04 Oct 2021 13:48:46 GMT

For instance, if I send [1,2,3,4,5,6,7] and the buffer is [1,2,3,4,5,6] after I send another the first frame. If i send a frame of data of [1,2,3,4,5,6,7] after the buffer would then become [7,2,3,4,5,6].

We do have a header byte to mark the beginning of a new message but this would have just been an extra form of validation. It may be more headache than it is worth but thanks for the help anyways!

RE: Getting UART transmitted data length

ovrebekk — Mon, 04 Oct 2021 08:11:51 GMT

Hi Spencer

What do you mean by putting them in the wrong locations?

Are the bytes printed in the while loop not the same as the bytes that you expect to receive?

The incoming bytes will be placed at different offsets in the UART RX buffers, that is true, but you can compile them as you wish once you receive them.

If you are implementing some form of message based UART communication I would strongly recommend using a header byte or similar to mark the start of a new message.

Best regards
Torbjørn

RE: Getting UART transmitted data length

SpencerEtn — Fri, 01 Oct 2021 18:00:24 GMT

Hi Torbjørn,

Following your example it does seem to work the first time I try to send more than the buffer size. However, the next time I send 7 bytes again it would start putting them in wrong locations. Is there a way i'd be able to count the evt->data rx/tx buf length before it gets manipulated in the callbacks? I think it'd be easier overall if I could just detect if say 7 bytes were received and to ignore them all and wait for a new set of bytes.

Thanks,

Spencer

RE: Getting UART transmitted data length

ovrebekk — Fri, 01 Oct 2021 10:45:16 GMT

Hi Spencer

Have you looked into using the UART async driver?

Then you can define a timeout on the receiver, and get a callback from the driver as soon as either one or the buffers have filled up, or the timeout period has passed.

I made a small example showing how to implement this here.

In your case this should lead to a first interrupt with a length of 6 bytes, followed by another interrupt some time later with the length of 1 containing the last byte.

Best regards
Torbjørn