This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1352P: UART Overflow error bit set

Part Number: CC1352P


Hi,

I am using the collector example code and have build our application up on that. 

I am using SDK 4.40.04.04_s source code SDK I've got access to from TI. I am using the launchpad CC1352P2

I am using the source code SDK I've got access to from TI

Whenever i try to send data continuously on UART for a very long time the following things occur

1) The data is sent and response received, but in between at certain intervals i receive no response. But i receive further responses

2) The data sent  and response is received for about more than 10 mins and then i receive no response to further any data that i am sending.

When I checked the UART registers at this moment i found that the UART Over-run error bit is set.

 The OE bit is not getting reset back to 0.

Once it is set, i might lose the response to some bytes/would lose some data but after that is never reset back to 0

I have gone through the data sheet but can't figure out how to write to this register

Can you help me with how I can write/reset this register?

Why is it not setting back? 

With the same application I have on collector example code with SDK 4.40..04.04 , no changes in application. I find no response issues in between. But no continuous no response from the launchpad, that after that it doesn't recover. After one response lost. The next response does come.

With the same application I have on collector example code with SDK 3.40, no changes in application. I find no issue with UART there. No continuous no response/In between no response is not seen.

Regards,

Sameena Shaikh

  • Are you using the UART Driver provided in the SDK when you are experiencing these problems?

    You should not have to clear any overrun flags from the application as this should be taken care of by the driver.

    If you are not using our drivers, I strongly recommend that you start using it.

    If you are experiencing problems with our UART Driver, you will need to make a minimal code example that will trigger this problem so that we can reproduce it and debug it.

    You should use one of or simple code examples as a starting point, and only add the code necessary to reproduce the error.

    BR

    Siri

  • Hi Siri,

    I am using the SDK SDK 4.40.04.04.

    We are using UART drivers from this SDK.

    Yes i will try to reproduce this on collector example code with minimum application changes.

    Regards,

    Sameena Shaikh

  • Hi Sameena 

    Try first to reproduce it in an even simpler example (UART_ECHO for example) by just configuring the Usart the same way as you do in your application and using it the same way. If you are not able to reproduce it there, go ahead with the collector example and do minimal changes.

    BR

    SIri