AWR1843AOP: UARTB RX - UART Driver "Capable of only sending data"

EMRE ÖZDEMİR

Part Number: AWR1843AOP

Hello ,

UART B is not capable of receive data. But we can configure pinmux as receive.

Is it possible if we change the "UartSci_Duplexity_TX_ONLY" to "UartSci_Duplexity_FULL" from the driver to use UARTB Recive data.,

Regards

EMRE

over 2 years ago

0 Kaushik Gowda over 2 years ago

TI__Mastermind 20605 points

Hi EMRE,

Can you please point to the exact place in the code that you are referring to?

Regards,

Kaushik

0 EMRE ÖZDEMİR over 2 years ago in reply to Kaushik Gowda

Intellectual 505 points

UART driver use this c file "uart_xwr18xx.c file ."

under this location "C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\drivers\uart\platform"

/**

* @brief This is the XWR18xx MSS specific UART configuration. There are

* 2 UART instances available on the MSS. UART1 is tied to SCI-A and UART3 is

* tied to SCI-B. This should *NOT* be modified by the customer.

UartSci_HwCfg gUartSciHwCfg[2] =

{

/* UART1 Hardware configuration:

* - Capable of sending and receiving data

* - PIN MUX is required */

{

((volatile SCIRegs*)SOC_XWR18XX_MSS_SCI_A_BASE_ADDRESS),

UartSci_Duplexity_FULL,

UartSci_PinMux_REQUIRED,

SOC_XWR18XX_MSS_SCIA_LVL0_INT,

SOC_XWR18XX_MSS_SCIA_TX_DMA_REQ,

SOC_XWR18XX_MSS_SCIA_RX_DMA_REQ,

&UartSci_openDMA,

&UartSci_closeDMA,

&UartSci_isDMAEnabled,

&UartSci_initiateRxDMA,

&UartSci_initiateTxDMA

/* UART3 Hardware configuration:

* - Capable of only sending data

* - PIN MUX is required */

{

((volatile SCIRegs*)SOC_XWR18XX_MSS_SCI_B_BASE_ADDRESS),

UartSci_Duplexity_TX_ONLY,

UartSci_PinMux_REQUIRED,

SOC_XWR18XX_MSS_SCIB_LVL0_INT,

SOC_XWR18XX_MSS_SCIB_TX_DMA_REQ,

SOC_XWR18XX_MSS_SCIB_RX_DMA_REQ,

&UartSci_openDMA,

&UartSci_closeDMA,

&UartSci_isDMAEnabled,

&UartSci_initiateRxDMA,

&UartSci_initiateTxDMA

}

};

if I change UART3 configuration to "UartSci_Duplexity_FULL" does it able to work like UART1

Best regards.

EMRE

0 Kaushik Gowda over 2 years ago in reply to EMRE ÖZDEMİR

TI__Mastermind 20605 points

Hi EMRE,

Both are UART SCI modules are capable of fully duplex transfers. Please follow the driver sequence as done for the 1st instance and you should be able to achieve the same. Here is another thread where the same was discussed in detail.

(+) AWR1843BOOST: Tx/Rx data through 2nd UART interface on AWR1843BOOST EVM - Sensors forum - Sensors - TI E2E support forums

Regards,

Kaushik

0 EMRE ÖZDEMİR over 2 years ago in reply to Kaushik Gowda

Intellectual 505 points

Hi Kaushik ,

Thank you for your answer.

I have reviewed your post and it explains the need to connect the pins. We have provided this connection in the design of our board, and we are confident that the signal is being transmitted to the processor. We can see this on the oscilloscope.

However, we realized that there are also some necessary actions to be taken in the driver section for UART3. This is because the driver section has been written only for tx.

Therefore, the structure mentioned in the first post for UART 3 is defined as "UartSci_Duplexity_TX_ONLY." If I change this definition to "UartSci_Duplexity_FULL" like in UART1, will the rx become active?

If not, how else can I solve this issue?

Thank you very much.

EMRE

0 Kaushik Gowda over 2 years ago in reply to EMRE ÖZDEMİR

TI__Mastermind 20605 points

Hi Emre,

There might be more changes required in addition to the change you mentioned. Therefore, as I mentioned earlier, please follow the driver sequence similar to the other UART instance and you should be able to achieve full duplexity.

Regards,

Kaushik

0 EMRE ÖZDEMİR over 2 years ago in reply to Kaushik Gowda

Intellectual 505 points

UART 3 is changed as "UartSci_Duplexity_FULL", and followed the driver sequence similar to the other UART instance. but I could not any specific code for other uart so ı could not find anything to change. ıf you have ready code please share with me. the situation is urgent.

0 Kaushik Gowda over 2 years ago in reply to EMRE ÖZDEMİR

TI__Mastermind 20605 points

Hi Emre,

I am extremely sorry to inform you that we do not have a code ready to share. Can you please elaborate your current issue and appropriate support will be provided if possible?

Regards,

Kaushik