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.
Hi All,
We are using DM3725 and working on power management on RTOS with our own BSP.
We are able to go to retention and SYS_CLKREQ pin in going low and 26MHz system clocking switching off, also wakeup is also working fine.
But as per our design we need to GP timer 5 to be active which is configured for 32KHz clock, in this we are not switching off GPtimer 5 functional clock because GP timer5 wakeup is required for our system.
So with this PER active state(other all power domains are in retention) SYS_CLKREQ is not going low and 26MHz clock is active.
Can you please let us know how we can switch off system clock in GPtimer5 wakeup enable state?
Is system clock to switch off all domains required to go in retention?
What is this Sleep state and how we can configure PER in sleep state where we can wakeup from GP timer 5.
Please add your suggestions/comments to resolve this issue.
Thanks,
Raviraj
Raviraj Somnache1 said:We tried with both TIOCP_CFG register CLOCKACTIVITY value 0 and 2 but in both this is not working.
CM_IDLEST_PER register ST_GPT5 bit is 0.
This unfortunately is what I was expecting, but I wanted to be absolutely sure...
Raviraj Somnache1 said:Is it possible to configure GPtimer5 on 32KHz clock and put PER and CORE in retention and switch off system clock. And GPtimer can wakeup system after wakeup timeout.
If you keep the GPTimer5 functional clock alive then that means the peripheral module is still active, and as a result you cannot transition the PER domain to retention. For example, here's a snippet from the TRM discussing power domain transitions:
Raviraj Somnache1 said:Currently we are using GPtimer 1 for MCU and this is working fine for MCU to wakeup and same we required one more timer GPtimer5 which can run on 32KHz and wakeup IVA.
I suggest getting an external timer that can wakeup the DSP through a pin associated with GPIO1. Since GPIO1 is part of the WKUP domain that would enable you to completely disable the PER domain and still wake up.
Raviraj Somnache1 said:I am just thinking GPtimer5 is configured on 32KHz then why system clock is required and not cutting off also why PER and system is not going into retention.
If the GPTimer5 functional clock is enabled (32k clock) then by definition GPTimer5 is active. The PER domain cannot achieve any low power modes while any modules are active. It's a cascading effect, i.e. GPTimer5 active causes PER to stay on which causes the system clock to stay on.
Raviraj Somnache1 said:We have already tested with external TCXO chip which is running on 32KHz clock and able to wakeup on GPIO1 bank gpio.
Raviraj Somnache1 said:With your input it is confirmed that it is not supported and now we can go with external 32KHz chip wakeup design for next Spin production.
I'm glad to hear you can spin the board quickly to get passed the issue!