• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 253 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.

TDA4VM: MMR lock proction

Zhihua Ding
Intellectual 460 points
Part Number: TDA4VM

Hi, TI

We met a strange problem during inplement safety mechanism "MMR-F2 - Partition locks" .

We first disable the lock interrupt for Wakeup (CTRLMMR_WKUP_INTR_STAT_CLR.EN_LOCK_ERR = 1; CTRLMMR_WKUP_INTR_EN_CLR.LOCK_ERR_EN_CLR = 1), and then lock all the partitions in wakeup. 

If we only do above, then it is fine. No lock error will be set. But if we disable the lock interrupt for MCU (CTRLMMR_MCU_INTR_STAT_CLR.EN_LOCK_ERR = 1, CTRLMMR_MCU_INTR_EN_CLR.LOCK_ERR_EN_CLR = 1), it will report lock error for wakeup. (CTRLMMR_WKUP_INTR_RAW_STAT.LOCK_ERR)

We are very confuse that why setting MCU lock registers will affect wakeup side. Could you give us some advise?

Thank you!

Zhihua

  • 0
    TI__Expert 4005 points

    Zhihua, 

    When you disable the lock interrupt for MCU and clear an errors, does WKUP_INTR_RAW_STAT immediately show an error?  Is this the correct sequence?

    1) Check WKUP_INTR_RAW_STAT--> No Error

    2) CTRLMMR_MCU_INTR_STAT_CLR.EN_LOCK_ERR = 1, CTRLMMR_MCU_INTR_EN_CLR.LOCK_ERR_EN_CLR = 1

    3) Immediately check  WKUP_INTR_RAW_STAT --> you see an error

    Are you sure you doing anything between steps 2 and 3?  This is because MCU_CTRL_MMR_ACCESS_ERR is connected to the WKUP domain, so if you are triggering an error an access error in MCU it may be forwarded to the WKUP domain.

  • 0 in reply to Y. Yang
    Intellectual 460 points

    Hi, Yang

    First 2 step is correct. For step3, we didn't check immediately, we check it cyclically, it reported error after 1.3s.

    Zhihua