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.

LAUNCHXL-CC26X2R1: Trying to access the second UART on dual UART device

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSCONFIG

I have a design which utilises a CC2652R1 multi protocol bluetooth controller.  

The was chosen because the device datasheet states that it has TWO UARTs  , I need one for the PTM and a second for communication with my sensor (9600:N,8,1) , data packets are once a second and are 28 bytes long.

I am using the  simple peripheral as base for my development linking to my target via the jumper ports.

Communication with the sensor is the final part of the development, but when I used the UART2 demo to add my port configuration and read the data - the pins are set to DIO2 and 3.  Modifying them is a simple task and going into the SYSCONFIG I can see TWO UART on the device - but there is a conflict because both UARTs want to access DMA channels 1 and 2.

I then used the UART emulator for the sensor controller and generated the files successfully - but it does not recognise the incoming data stream.  This was tracked to the device being able to accept up to two stop bits before going idle and looking for the next set of incoming data.   The sensor has a 2 bit gap, (208us) . I have changed the configuration for the device (as much as I am able ) and reducing the idle counts down to 1 still had no impact.

I need a solution that will either get the second UART functioning or the sensor controller emulation runnning.

Regards

De an 

  • Hi,

    Thank you for reaching out,

    First thing first can you provide your sdk and a screenshot of the conflict on sysconfig.

    On my side I'm able to add 2 UART directly from sysconfig without any conflicts, what are the pins for both ones? DMA channel should be 0 and 1, you can double check it in the generate files changes in sysconfig.

    regards,

  • This is the error I get when using sys config,  the error is not on the pin allocation but on the DMA access.    My application needs a slow secondary UART which can easily be polled.

  • Hi Brynley,

    Can you provide me your SDK and your Sysconfig version, it could be related to that.

    regards,

  • Having received the response earlier, I have gone through the implementation in the simple peripheral sysconfig.

    Primary UART was linked to the XDS100 and thus the onboard UART was free - whereas I was creating my own project and thus the DMA was initially in conflict

    I have updated my code and added a loopback and the result is that the serial data in is being echoed to the output, though I still need to check the data is 100% correct, my problem has been resolved

    Many thanks

    I have updated the