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.

CC2642R-Q1: UART cannot enter callback with busy transmitting

Part Number: CC2642R-Q1

Hi Engineers

I'm facing a 100% reproducible issue when using UART driver in SDK 5.20

1. use a external MCU to transmit a particular packet to 2642 via UART

2. 2642 will UART_close after receiving this packet

3. MCU will wait for 2s then pull low RX of UART of 2642

4. 2642 will open UART again and toggle  via UART TX to MCU

5. after receiving this toggle, MCU will pull high RX of UART of 2642

6. then repeat step1-2. we can see that UART_close is not entered, register show that UART is still busy transmitting data.

could you share some insight what may cause this issue?

  • Hello Simon,

    I need some time to look into this issue. I will give feedback till 9/28/2023 latest.

    In the meantime, would it be possible to try if the issue still exists with the latest SDK?

    It would be also helpful to see some code spinets of the toggling process. Is it done as GPIO functionality or with some UART commands?

    If it is done with the UART then maybe it would help to close and open the UART again after the toggling.

    Which driver are used, UART or UART2?

    Which mode is the UART used in, blocking, non-blocking or callback mode?

    Best regards,

    Andreas.

  • Hello Simon,

    I checked the UART and UART2 driver of SDK 5.20.

    Since the thread title is mentioning call back mode, I assume UART2 drivers are used.

    I still do not understand how the sequence of toggling is implemented.

    I assume the issue might be related to that sequence.

    But I really need more details on the implementation before I can proceed.

    Best regards,

    Andreas.