TDA4VH-Q1: System does not auto-boot after Power-ON-Reset when >12 MCANs from Main domain mapped to MCU domain

Part Number: TDA4VH-Q1


Hi Team,

Posting on behalf of our customer.

Issue Description

The SoC has two domains:

  • MCU Domain (originally 2 MCAN controllers)

  • Main Domain (16 MCAN controllers)

We are adding MCAN controllers from the Main Domain to the MCU Domain.

Observed Behavior

  • With up to 12 MCAN controllers from Main domain moved to MCU Domain(Totally now 2 Mcu domain controllers + 12 Main domain controllers):

    • Flash via TFTP succeeds

    • After power-off / power-on reset, UART shows auto-boot logs (as expected)

    • System boots normally and CAN communication works

  • When any additional MCAN controller (13th or more) is added:

    • Flash via TFTP succeeds

    • After power cycle, no auto-boot output on UART (Tera Term)

    • System does not boot automatically

    • In debugger, an OS internal error (Os_ErrIsOsInternalException) is observed in stackframe view.

This occurs independent of which MCAN instance is added.

Questions

  1. Is there a limit on the number of MCAN controllers supported in each Domain?

  2. Are there additional configuration or resource constraints when moving MCANs from Main Domain to MCU Domain?

Regards,

Danilo

  • Hello,

    We are adding MCAN controllers from the Main Domain to the MCU Domain.

    I am sorry i did not understand ,what do you mean by above statement ?

    Accessing of Main Domain CAN can be done from MCU domain but what exactly is this adding of MCAN?

    No such limits to access MAIN CAN from Main domain and what is your SDK version ?

    Regards 

    Tarun Mukesh