LP-AM263P: MCAN

Hi,

To add more context we are using a custom board build with AM263P.

Hello Arjun,

Thanks for providing this information. Can you confirm which SDK examples you tested with both the old and new part numbers?

I also wanted to confirm that you are using the latest version of the AM263Px SDK (Version: 10.01.00.31 - Release date: 19 Dec 2024).

Link here for easy access: https://www.ti.com/tool/download/MCU-PLUS-SDK-AM263PX/10.01.00.31

I reviewed the part number options to determine if there is any issue with using AM263P4ACOLF vs original AM263P4ACOMF, but both L and M options support CAN-FD.

Best Regards,

Zackary Fleenor

Hi Fleenor,

Thanks for the reply.

1. We have tested both SDK 10.01 and 10.0.35 . In earlier part number we could run code build with both SDK examples succesfully.

2. Regarding part numbers we have been using experimental part num (prefix x) XAM263P4ACOMF until now. is there any change due to this?

3. We will try to debug hardware as well, is there any power supply to MCAN module that we can check to see if all is well.

Thanks,

Arjun

Hello Arjun,

1) Understood, Can you please test with the latest MCU_PLUS_SDK (v10.01.00.31)?

2) No, both part numbers support full CAN-FD functions from MCAN module.

3) There are dedicated 5.0V rails for the CAN Transceiver on the launchpad. These are controlled by the PMIC which can be programmed by the SoC. The latest SDK should include all the necessary code to properly configure the PMIC to enable necessary power rails for CAN Transceiver. Let me loop in another engineer to provide more precise details here.

Best Regards,

Zackary Fleenor

Hello Fleenor,

1. Yes, we have tested with v 10.01.00.31. 

2. Understood

3. I want to be clear here, we are not using EVAL-CC or LP boards, we are using our custom boards where we verified MCAN functionality with the transceiver circuit posted in this thread. The schematics was verified by TI earlier. Please loop in HW expert as well to address this.

Thanks,

Arjun

Arjun,

To clarify, you are using an identical PCB as you were using with the previous device XAM263P4ACOMF. You dropped in the new device, AM263P4ACOLFZCZ, and it is not working?

Which AM263P4 device pins are the MCAN0 signals connected to?

Regards,

Brennan

Hi Brennan,

This is correct.

We are using MCAN0 on Pin numbers E16,F16.

Thanks,

Arjun

Arjun,

Understood. And I assume you have your SysConfig correctly configured for mux mode 1 on both E16 and F16 to enable the MCAN0? 

When you run the software on the device, are you getting an output error? Or does the software properly execute, and you are not seeing any data transmission on the lines when probing the CAN output?

If you are using a TI provided SDK example, please let me know which example you are using.

Regards,

Brennan

Hi Brennan,

Attaching relevant parts of sysconfig here.

TI SDK examples tried : "canfd_external_read_write", "mcan_external_read_write" with some modifications to send frames repeatedly.

Brennan Hartigan said:

When you run the software on the device, are you getting an output error? Or does the software properly execute, and you are not seeing any data transmission on the lines when probing the CAN output?

Software properly executes, but we cannot see any activity on TX,RX lines from MCU (before transceiver). To ensure the pins are not short during manufacture we tried configuring them as GPOs and toggled them and it works properly in GPIO mode.

Thanks,

Arjun

Arjun,

In your previous setup with the XAM263P4ACOMF device, did you have a receiver connected to the on-board CAN PHY, such as a CAN-USB module or a different board with a CAN transceiver?

What is the part # of the on-board CAN PHY?

When you probe CAN_H and CAN_L are you able to see the CAN message?

Regards,

Brennan

Hi Brennan,

We have connected to PCAN-USB device from PEAK connected to PC as the other node to test setup with XAM263P4ACOMF. 

CAN transceiver part # TCAN1051VDRQ1.

CAN_H and CAN_L pins on Transceiver are not showing any activity.  

Arjun,

From a HW perspective, everything looks to be ok - especially since you say that this configuration worked with the old part number.

I am going to check the SDK example history to see if any of the SW configuration has changed, apologies I do not have a clear answer for you yet.

Regards,

Brennan

Hey Arjun,

Can you verify & provide the IOMUX CTRLMMR configuration for the MCAN0_TX and MCAN0_RX pins in question here?

Best Regards,

Zackary Fleenor

Arjun, 

Could you also send over the software you are attempting to run on the AM263P4? I will run the code on a TI evaluation platform with known working HW.

Regards,

Brennan