• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 99 subscribers
  • Views 517 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM6442: Power OK module behavior at UV detection

Koichiro Tashiro
Mastermind 22945 points
Part Number: AM6442


Hi,

My customer is asking Power OK module behavior when UV is detected by VMON_VSYS.
Below is TRM description.

It seems the status is updated STAT register or an interrupt is sent to ESM.
But there is no detailed information available. Where can I find it?

The customer wants to know:
a) Where is the STAT register?
b) What is a result of the interrupt to ESM?
c) any other details.

Thanks and regards,
Koichiro Tashiro
 

  • 0
    TI__Mastermind 28235 points

    Tashiro-san

    Someone should be able to respond to this early next. week.  Thank you for your patience 

    -Paul 

  • 0
    TI__Genius 9530 points

    Tashiro-san,

    a) Refrain from using the stat register as it has been proven to have unstable behavior. The ESM should be used to get status.

    b) The result is software configurable. Please refer to section 12.6.2.4 ESM Functional Description for how ESM behaves when an interrupt is received. There are also status registers that can be monitored in the ESM to determine if a specific interrupt has been received.

    c) The ESM interrupt mapping has generic naming for the input interrupts which will not be helpful in determining which POK module is tied to which interrupt input. I am pasting the interrupt map table below so it can be derived which interrupt is linked to which POK module.

    ESM Interrupt Input POK Module
    MCU_ESM0_PLS_IN_64 pok_vddshv_main_3p3_ov
    MCU_ESM0_PLS_IN_65 pok_vddshv_main_1p8_ov
    MCU_ESM0_PLS_IN_66 pok_vmon_cap_mcu_general_ov
    MCU_ESM0_PLS_IN_67 pok_vddshv_mcu_3p3_ov
    MCU_ESM0_PLS_IN_68 pok_vddshv_mcu_1p8_ov
    MCU_ESM0_PLS_IN_69 pok_vddr_core_ov
    MCU_ESM0_PLS_IN_70 pok_vdds_ddrio_ov
    MCU_ESM0_PLS_IN_71 pok_vddshv_main_3p3_uv
    MCU_ESM0_PLS_IN_72 pok_vddshv_main_1p8_uv
    MCU_ESM0_PLS_IN_73 pok_vmon_cap_mcu_general_uv
    MCU_ESM0_PLS_IN_74 pok_vddshv_mcu_3p3_uv
    MCU_ESM0_PLS_IN_75 pok_vddshv_mcu_1p8_uv
    MCU_ESM0_PLS_IN_76 pok_vddr_core_uv
    MCU_ESM0_PLS_IN_77 pok_vdds_ddrio_uv
    MCU_ESM0_PLS_IN_78 pok_vdd_mcu_uv
    MCU_ESM0_PLS_IN_79 pok_vdda_mcu_ov
    MCU_ESM0_PLS_IN_80 pok_vdda_mcu_uv
    MCU_ESM0_PLS_IN_81 pok_vdda_pmic_in_uv
    MCU_ESM0_PLS_IN_82 pok_vdd_mcu_ov

    Thanks,

    Chris

  • 0 in reply to Christopher Roberts
    TI__Mastermind 22945 points

    Hi Chris,

    Thanks for your reply.
    Customer will look into it and let you know if he has further questions.

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Mastermind 22945 points

    Hi Chris,

    It seems the interrupt map table you provided does not use the same signal names as TRM uses.

    Below understanding is correct?
    VMON_VSYS => IPOK_VDDA_PMIC_IN = pok_vdda_pmic_in_uv => MCU_ESM0_PLS_IN_81

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Genius 9530 points

    Tashiro-san,

    That is correct. Table 9-90 for the MCU_ESM0 interrupt map in the TRM only provides generic information as to the source interrupt and therefore is ambiguous as to which POK is sourcing the interrupt.

    I provided the table in the early post to clear up this ambiguity. We will fix this in a future release of the TRM.

    Thanks,

    Chris