AM62A3: DM R5F access to MCAN0 or MCU_MCAN0/1

Hello Gunter,

As of now, we(TI) support the WKUP domain core for DM applications and  not opened DM R5F core for user applications in AM62A .

Why did you want to use MCAN or MCU_MCAN from DM R5F?

Regards,

S.Anil.

Hi Swargam Anil,

the customer is planning for additional usage beyond DM R5F typical FW. They would need 2x MCAN ports. What I would need is a theoretical confirmation that the MCAN and MCU_MCAN can be access from DM R5F. From looking at the TRM, the DM memory map can see the MCAN and MCU_MCAN ports, as well as interrupts from the peripherals can also be routed back to the DM core.

Can you confirm?

Thanks!

--Gunter

Hello Gunter,

Actually, there is one chapter on the interrupt connectivity table for the WAKE_UP_R5F core in which we can check what interrupts are routed to WKUP_R5F.

But this chapter is missing in the TRM. So, now that I have verified it in the MCU+SDK, there is one file named cslr_wkup_r5f_interrupt connevity.h. Typically, this file should be matched to the WKUP_R5F interrupt connectivity table of TRM. So, based on this, I assume that the user can access both MCAN's (MCU and MAIN) from the WKUP_R5F core, and there are no issues.

Please look at this file for your reference, and I can check internally with the design team as well whether we can use MCAN's from R5F or not.

cslr_intr_r5fss0_core0.h

Regards,

S.Anil.