Receiving only one char through uart interrupt in Serial_uartes

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Wed, 05 May 2021 08:33:13 GMT

Hi Susheel,

I have checked with the code with Serial terminal software and its working fine for even multi byte reading.

after that i have also checked this same peer and code by increasing the timeout_us=10000;

then this code is also working with multibyte reading.

finally i can say that its working fine as i intended to.

Thanks for your help.

Best Regards,

Raj.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Wed, 05 May 2021 06:56:25 GMT

Have you tested your project again any other UART peer? If not, I suggest you test that. I have used your project unedited and it works OK with the peer that is doing a multibyte transfer.

Could it be possible that your peer serial device is having spaces between each byte transfers? Do you have a logic analyzer or an oscilloscope to see the incoming transactions? Can you test your project against the peer I tested with (attached project in my previous reply tested on pca10040?

The reason I am asking you to test this because I think your product/project handles reception correctly and it looks to me that the peer serial device does not transmit data continuously If there are spaces between characters then the UART RX will get an interrupt for every single char it gets and the RX seems to be processed before the next char is received. Just my theory, since nothing else explains this behavior when i see different results with your unedited project

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Tue, 04 May 2021 17:51:18 GMT

Hi Susheel,

i have again tested my code with timeout_us=1000 as suggested by "Dmitry", and still i can receive only one byte at a time.

i'm currently receiving this data from a energy meter using RS-485(UART) and i can see only 1st byte(one byte) when interrupts triggers.

please guide us to come out of this issue

Best Regards,

Raj.

RE: Receiving only one char through uart interrupt in Serial_uartes

Dmitry — Tue, 27 Apr 2021 08:44:43 GMT

I could guess that rx timeout is too short:

    nrf_libuarte_async_config_t nrf_libuarte_async_config = {
            ...
            .timeout_us = 100,
    };

Maybe increasing it to 1000 will help.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Tue, 27 Apr 2021 08:15:39 GMT

I used a simple setup as below

PCA10056 DK is running your project and the PCA10040 (nrf52832) is running below project

devzone.nordicsemi.com/.../6457.libuarte.zip

So, I do not know why you are receiving only one character when the single transaction tested on your project without any changes shows that the RX event has multiple chars in it.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Tue, 27 Apr 2021 08:12:41 GMT

Rajender,

I have now tested your latest project where you are testing nrf_libuarte.

I have connected the pins for the uarte0 to the peer board that is transmitting this below thing in a loopback

"Testing this exampple with UART example started.\r\n Loopback:\r\n";

I have breakpoint where the uart_event_handle processes the data.

Looking into the memory pointer of the received event, I can see that the length and data are correct and not a single char.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Tue, 27 Apr 2021 07:25:31 GMT

Rajender,

Sorry for the late reply, i am trying to replicate the issue by setting up a peer uart. I am able to build and flash your code. Most likely i will have some more insights today

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Mon, 26 Apr 2021 12:49:19 GMT

Hi Susheel,

This replay is for formal remainder for the replay to solve our problem, we are awaiting for your replay.

please give the replay asap, since we have to solve this problem asap, and our development on this project is on hold because of this issue,

so please help us

Best Regards,

Raj

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Fri, 23 Apr 2021 11:22:58 GMT

devzone.nordicsemi.com/.../libuarte-_2D00_-GSM_2800_sms_2900_.zip

Hi susheel,

Yes, i found out SERIAL_BUFF_TX_SIZE in the man.c, but if i use the libuarte example then also im getting only one byte at a time, and i didn't find any buf size specified in the main.c

please suggest the changes in the libuartes example also

PFA for the libuarte project file in this library also im getting only one byte at a time

and this example is from SDKv17.0.2

best Regards

Raj

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Wed, 21 Apr 2021 08:23:55 GMT

Looking at your code you have

#define SERIAL_BUFF_TX_SIZE 1
#define SERIAL_BUFF_RX_SIZE 1

You clearly have set the TX_SIZE/RX_SIZE to 1 limiting the amount of rx transaction to 1 char.

Please check to see if you can increase it to a bigger number.

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Tue, 20 Apr 2021 06:10:57 GMT

devzone.nordicsemi.com/.../serial_5F00_uartes-_2D00_-GSM_2800_sms_2900_.zip

Hi Susheel,

Thanks for the reply,

Here i am attaching zip file of my project, i think you can work around with this,

and my problem in this project are,1) taking bunch of data at single shot only, 2)Response of GSM module was not catching completely (ex: if it should say, "\r\nOK\r\nCONNECT\r\n", Its saying "\r\nOK\r\nCONN"

Please check on the issue for data loss alos

Best Regards,

Raj.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Mon, 19 Apr 2021 08:08:57 GMT

Hi Rajender.

I have now looked into the nrf_serial implementation and it is possible that you are using UART configuration instead of UARTE. Can you please attach your sdk_config.h (best would be to attach your project here) so that i can quickly review the peripheral configuration you are using?

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Sat, 17 Apr 2021 09:12:32 GMT

Hi susheel,

I know i have given very late replay last time, im sory for that but i need to solve this issue ASAP, this issue effecting the complete project development so please replay soon.

Please understand the urgency.....

Best Regards,

Raj

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Thu, 15 Apr 2021 17:01:58 GMT

Hi Susheel,

1) GSM Interrupt occurs when we request the data from gsm like sending any AT command to the GSM (most likely around 1 second)

2) RX Characters on the RX line --> i dont have the Logic analyser(CRO) in with me but i can say minimum RX characters are "OK"-2 characters, MAX characters are around 255 characters.

3)If we talk about any interrupt priority, i have not changed any interrupt priority its default as the example only (Mostly Priority 7)

I am not sure my answers are correct as you expected but please help and correct me.

Best Regards

Raj.

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Thu, 08 Apr 2021 12:15:56 GMT

Hi Rajender, I am back from vacation and will look into this tomorrow. I suspect that the issue is that GSM_InterruptHandler might have higher priority than UART interrupt and is triggering faster than the byte received inthe UART RX FIFO. Or the uart traffic is slower than the frequency of the GSM interrupt frequency?

if none is the case, then we need to debug as to why you are not able to receive multiple received bytes from FIFO.

Before i can try to dig more into the nrf_serial library, could you tell me

1) GSM interrupt frequency
2) UART characters on the RX line in single transaction (logic analyzer snapshots would be helful)
3) UART and GSM interrupt priority

RE: Receiving only one char through uart interrupt in Serial_uartes

umrsraj — Thu, 01 Apr 2021 08:11:32 GMT

Hi susheel,

ok we can wait till next weeek, but please make sure to complete ASAP

Best Regards,

Raj

RE: Receiving only one char through uart interrupt in Serial_uartes

Susheel Nuguru — Wed, 31 Mar 2021 13:47:26 GMT

I could not take a look at this before the easter holiday, i will take a look at this early next week when i come back to office.