Hi,
In VF5xx/wakeup sources of WKPU_WISR thread, I got the following answer.
・One of them, WKPU_M4IF (source - PIT), appears to be incorrect (to be removed in the next Reference Manual revision).
When I stop PIT, I do not LPSTOP3 cancellation. And, when PIT moves, I do LPSTOP3 cancellation.
From the above, I doubt that I do wakeup from LPSTOP3 in PIT.
I confirmed that I removed LPSTOP3 in wakeup trigger of PIT.Then it contradicts this answer.
WKPU register is abnormal, too.The WKPU register after the LPSTOP3 cancellation is follows.
WKPU_WISR = 0x00400000
WKPU_IRER = 0x00013006
WKPU_WRER = 0x00013006
WKPU_NCR = 0x00000000
WKPU_NSR = 0x00000000
Wakeup becomes the factor of WKPU_WISR = 0x00400000, but is a bit not to exist.
Q1)
Is PIT wakeup trigger of WKUP?
Q2)
What WAKEUP source does WKPU_WISR = 0x00400000 mean?
Q3)
Please tell me the method to mask PIT wakeup trigger.
Best Regards,
soichi
Dear Soichi,
Let me rephrase your question: are you questioning the statement from the earlier thread that WKPU_M4IF (source - PIT) does not exist, please?
If so, may you describe all your actions leading to this assumption literally step-by-step, please?
Sincerely, Naoum Gitnik.
Dear Naoum,
Thank you for reply.
Sorry.
> If so, may you describe all your actions leading to this assumption literally step-by-step, please?
That's right!
Please give me a little time because I will confirm that.
I have one question .
Q)
Please comment on WKPU_WISR = 0x00400000.
I cannot understand me.
Best Regards,
soichi
Dear Soichi,
Regarding WKPU_WISR and its 0x00400000 value: based on the Reference Manual, fields 0 to 23 are reserved, meaning not used by the Vybrid design (you know, it often happens when the same block is used for various ICs...). Unless there is a real problem requiring deep IC behavior analysis, they are ignored.
Regards, Naoum Gitnik.