Part Number: TDA4VM
Hello Team,
We're developing a domain controller powered by 2 TDA4VM SOCs in a same PCB, where the 1st SOC's USB1 connects to the 2nd SOC's USB0. The controller boot scenarios are as follows:
- The 1st SOC boots from the EMMC first, running to the A72 HLOS <QNX>. Then the 1st SOC servers as USB Host.
- The 2nd SOC as device boots from the DFU, receiving the firmware from the Host one by one, and then starts the firmware.
Now we have a problem that when the MCU_RESETz or MCU_PORz reset signals are asserted to the SOCs, the 1st SOC comes up from eMMC as expected but the 2nd SOC's MCU_ROM occasionally CANNOT enumerate itself as DFU device. Then the 2nd SOC will always stays at MCU_ROM stage. At this stage, we attach the JTAG to the 2nd SOC and we confirms:
- The 2nd SOC is not dead -- still running the MCU_ROM code.
- The 2nd SOC's boot strap pin is correct -- by reading the CTRLMMR_WKUP_DEVSTAT and CTRLMMR_MAIN_DEVSTAT registers which shows it boots from DFU.
- The USB peripheral circuit are also checked all OK.
Moreover, when it comes to this case, no matter how many MCU_PORz signals are triggered to the 2nd SOC, it cannot recovery to normal state unless completely power down and on.
Could you please check and help us confirm what's going on?
Thanks and Regards,
Raymond.
