IWR6843AOP: IWR6843AOP high-speed UART's Rx configuration

Kai

Part Number: IWR6843AOP
Other Parts Discussed in Thread: IWR6843

Hello,

I’m using IWR6843AOP chip in my project and need to modify the original “overhead_3d_people_counting” project file, which is part of “mmwave_industrial_toolbox_4_7_0\labs\people_counting” lab package, to activate the Rx path of the high-speed UART.

In the project’s original code to map UART’s Tx (Pin E2), the GPIO is configured as in below,

Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINF14_PADAJ, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);

Pinmux_Set_FuncSel(SOC_XWR68XX_PINF14_PADAJ, SOC_XWR68XX_PINF14_PADAJ_MSS_UARTB_TX);

Apparently the configured pins in the original code are based on IWR6843 chip not IWR6843AOP.

So the question is if the below lines of code will map IWR6843AOP UART’s Rx to pin U12 in the same project,

Pinmux_Set_OverrideCtrl(SOC_XWR68XX_PINP4_PADBB, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);

Pinmux_Set_FuncSel(SOC_XWR68XX_PINP4_PADBB, SOC_XWR68XX_PINP4_PADBB_MSS_UARTB_RX);

Tanks,

Kai

over 4 years ago

+1 Alec May over 4 years ago

TI__Genius 17265 points

Kai,

You are correct with your evaluation of the normal 6843 pins vs the AOP pins. The values you chose appear to be correct.

Best Regards,
Alec

0 Kai over 4 years ago in reply to Alec May

Prodigy 100 points

Thank you Alec for the prompt reply.

Two more queries on this:

- Is there any GPIO mapping table for 6843 vs the AOP?

- I need to replace UartSci_Duplexity_TX_ONLY with UartSci_Duplexity_FULLin uart_xwr68xx.c source file inside mmwave_sdk_03_05_00_04 firmware package. Could you please let me know how could I recompile the modified library project? is there any way to do it in the CCS environment?

Cheers,

Kai

+1 Alec May over 4 years ago in reply to Kai

TI__Genius 17265 points

Kai,

The current pinmux driver does not have a mapping for the AOP package, this is something we are actively looking at. My recommendation is typically to use the pinmuxing values from the data sheet rather than relying on the macros from the pinmux driver.

In terms of rebuilding the UART library, you have 2 options.

Rebuild using the Make files provided in the SDK. You can see how to do this in the SDK user's guide under the section " Advanced build"
Import these files to your CCS project. This can require a bit of finese to do properly, but I will outline the steps to do so below.
1. Go to project->properties->ARM Linker(Assuming MSS)->file search path
2. From the top box, remove the library file that you want to remake.
3. Apply and close the properties window
4. Import the files that you will need to rebuild into CCS
  1. Copy and paste them into your project, and maintain the file path as best as possible so that the include paths match up.
  2. So if you are importing <ti/drivers/uart/uart.h>, you will want to make the folders in your CCS project ti/drivers/uart/ so that the path that other files are expecting is still maintained.
5. Build the project once to make sure nothing is broken
6. Check that CCS is using the correct files.
  1. Since CCS projects will check for files in your workspace before it checks in SDK, it will prioritize the ones you've added.
  2. You can test if the correct one is used by doing ctrl+left Click on something that will come from those files (Such as the line #include <ti/drivers/uart/UART.h>)
  3. CCS will then open the file that defines that value, and you can hover over the filename at the top and see what the path is
  4. If the path listed is still the one in the SDK, then your path in your workspace may have a mistake

Let me know if you have any further questions

Best Regards,
Alec

Sensors

Sensors forum

IWR6843AOP: IWR6843AOP high-speed UART's Rx configuration