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.

CC2340R5: UART Communication

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

Hello I am using cc2340 for UART communication, i have configured pin 12 and pin 13  for RX and TX, i am not able to send or recieve data.
after ble connection succees  i want transmit data on uart. 

  • Hello Prashant,

    If you are using a BLE example such as basic_ble then the one UART peripheral is already reserved for the terminal Display.  If you are not using the LP-EM-CC2340R5 XDS110 backchannel UART or do not desire the Display feature then you should pre-define Display_DISABLE_ALL in your project and make necessary Custom Hardware changes in the SysConfig file.  You can use a logic analyzer or oscilloscope to confirm that transmissions are being sent our successfully.

    Regards,
    Ryan

  • yes ,i have disable the display still having the same issue

  • its stucked in fault isr

  • Thus you will need to address the other suggestions:

    • Ensuring SysConfig settings do not have the Display module added (TX only) and there is only one UART2 configuration with the correct PinMux
    • Observing the RX and TX UART pins with external hardware (oscilloscope or logic analyzer recommended)

    Since you are able to debug the code, I suggest stepping through the code and establishing breakpoints to determine the API which precedes the device entering the fault ISR.  This will allow you to address the problem directly.

    Regards,
    Ryan

  • we have already kept external pins only for RX and TX... i am takjing one thread then only tx and rx is working whenever i take outside from thread its not working for uart.

  • Please be more descriptive with your responses.  If you have a setup in which UART does work then you should further clarify the change which causes the UART to break.  There are plenty of Debugging Tools available for which you can identify the issue or adequately describe its symptoms on this E2E thread.  This would also be a beneficial time to list the F3 SDK version and direct example name you are referencing, alongside the changes which have been implemented so far (with code snippets provided).

    Regards,
    Ryan