AWR1843AOP: AWR1843AOP: CANFD Pinmux Configuration Change – No CAN Messages on Alternate Pins

HI,

Let me review your question and get back to you next week.

thank you
Cesar

Hello Cesar,

I have added the suggested pinmux header file for the AWR1843AOP at the following path:
C:\ti\mmwave_sdk_03_05_00_04\packages\ti\drivers\pinmux\include

In my application, I attempted to use Ball B4 as CANFD_TX and Ball A4 as CANFD_RX. I configured the pins using the following code:

// modified codes 

Pinmux_Set_OverrideCtrl(SOC_XWR1843AOP_PINB4_PADBR, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
Pinmux_Set_FuncSel(SOC_XWR1843AOP_PINB4_PADBR, SOC_XWR1843AOP_PINB4_PADBR_CANFD_TX);

Pinmux_Set_OverrideCtrl(SOC_XWR1843AOP_PINA4_PADBS, PINMUX_OUTEN_RETAIN_HW_CTRL, PINMUX_INPEN_RETAIN_HW_CTRL);
Pinmux_Set_FuncSel(SOC_XWR1843AOP_PINA4_PADBS, SOC_XWR1843AOP_PINA4_PADBS_CANFD_RX);

However, after applying these changes, the CAN interface does not receive any messages when using these pins (A4 and B4).

Could you please confirm if these pins are valid for CANFD functionality on the AWR1843AOP and whether any additional configuration is required?

Thank you for your support.

Thank you for your response.

I configured the pins A4 and B4 (GPIO_44 and GPIO_43) as GPIO outputs. After setting and resetting these pins, I observed the following behavior:

• When set, the pins output approximately 3.3V

• When reset, the pins output approximately 0.3V

This confirms that I am successfully able to configure and control these pins as GPIOs. and it means my hardware is correct.

However, I noticed that the macros defined for configuring these pins for CANFD functionality (CANTX and CANRX) both have the same value: in the file pinmux_xwr1843AOP.h

#define SOC_XWR1843AOP_PINB4_PADBR_CANFD_TX             5U    /*< */
#define SOC_XWR1843AOP_PINA4_PADBS_CANFD_RX            5U    /*<*/

Could you please confirm whether these macro definitions for CANFD configuration are correct?

Thanks
Mitesh Singh

Hi,

Yes this information is what is available.

Could you run the CAN-FD unit test to check if it works?

C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\drivers\canfd\test\xwr18xx\main.c

You would need to select "MCAN_APP_TEST_EXTERNAL_LOOPBACK"

What application are you working on?

Thank you

Cesar

Hi,

I have successfully received CAN-FD messages using the default pins D1 and F2, as configured in the example project located at:
C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\drivers\canfd\test\xwr18xx\main.c
This setup is currently working within the MRR application.

 I have configured A4 and B4 pins using the same Pinmux_Set_OverrideCtrl and Pinmux_Set_FuncSel function as shown in the above example, and I’ve already shared the relevant code for this setup in my previous reply.

but I did not get message on these pins (A4/B4).

Regarding your question — I am working on the Medium Range Radar (MRR) application on the AWR1843AOP, with only the MRR mode enabled.

I would appreciate your guidance on how to proceed with enabling CAN-FD communication over the A4 and B4 pins in this context.

Thanks
Mitesh

Hello Cesar,

i found this thread "(+) AWR1843AOP: CAN-FD pinmux on pins A4/B4: datasheet inaccuracy? - Sensors forum - Sensors - TI E2E support forums"

related to same problem for the PIN A4 /B4. 

you are in the chain of the message. I think you have the solution for this.

Thanks
Mitesh

Hi,

I reviewed the message. 

It just provides the following pins for CAN-FD but it still does not confirm if A4/B4 can be used for CAN-FD.

I have seen other older threads that seem to indicate that A4/B4 are not working with CAN-FD.

I need to check with design team. This will take some time. Will get back to you next week

thank you
Cesar

1. CAN Instance #1 – CAN-FD
   1. TX – D1
   2. RX – F2

Hi,

I talked with the Design Team and it seems that the Datasheet is not correct.

The A4/B4 pins are not for CAN-FD but CAN only.

This is consistent with the behavior you have noticed.

thank you
Cesar