TDA4VM: TDA4VM HW Reset implementation

Part Number: TDA4VM

Hi, on TDA4 there are two reset input pins for MCU and Main domain. Would you please support me on answering the following questions:

MCU/Main_PORz is used for cold resets and MCU/Main_RESETz is used for warm resets.

- What is the expected electrical implementation between MCU/Main_PORz and MCU/Main_RESETz? 

Currently, intended application is using only MCU/Main_PORz connected to TDA4, MCU/Main_RESETz pin is left unconnected. Is this an acceptable configuration?

Or should both signals, MCU/Main_PORz and MCU/Main_RESETz tied together to the Power supply PGOOD/Reset line?

- MCU_RESETz specifies that some TDA4 subparts are not being affected by the reset and other ones are partially reset. 

What is the meaning of partially reset? 

  • Here is a description of each reset:

    MCU_PORz:  MCU domain Power On reset input, driven from PMIC (can also be combined with other resources) (Note MCU domain also controls Main domain, so MCU_PORz will reset both MCU and Main domains)

    MCU_RESETz:  input for MCU warm reset.  Connect to PU resistor if unused.

    MCU_PORz_OUT:  Buffered version of MCU_PORz input.  Can optionally drive MCU peripheral reset inputs with this signal (only reset with PORz)

    MCU_RESETSTATz:  Output version of MCU domain reset.  Is asserted for both MCU_PORz and software initiated resets.  Can optionally drive MCU peripheral reset inputs with this signal (reset for both cold and warm reset conditions)

     

    PORz :  Main domain power on reset, sourced from PMIC

    RESET_REQ:  Input for main domain warm reset.  Connect to PU resistor if unused.

    PORz_OUT:  Buffered version of PORz input.  Can optionally drive main domain peripheral reset inputs with this signal (only reset with PORz)

    RESETSTATz:  Output version of main domain reset.  Is asserted for both PORz and software initiated resets.  Can optionally drive main domain peripheral reset inputs with this signal (reset for both cold and warm reset conditions)