Hi Felipe !
Could you clarify dependencies between cores in case of power management.
Looks like cores are dependant and power management APIs can be called from Core0 only and wakeup sources affects both cores some how.
In make case I should RUN Core0 at 150Mhz for some short times and RTOS will put it to SleepMode sometimes and at known time to Power-down mode to conserve power.
Due Flexcomm 3 and few GPIO pins what are part of GINT0 , Core0 will wakeup sometimes to RUN mode from Power-Down mode.
Looks like it should work .
But what about Core1 behaviour while Core0 change power states ? Does it follow ?
I really expect that Core1 will be clocked by FRO1Mhz ( or FRO12Mhz) and can RUN or Sleep mode only.
It can poll some I2C interface sometimes and serve output of some individual pins.
But looks like it will be go to powerdown mode due Core0.
But it is written that Core1 can go to Sleep mode only.
So basically when I would like to run Core1 I should keep Core0 at list in Deep-sleep mode.
So all wakeup sources wakeup both Cores to RUN mode and I should put Core0 to Deep-Sleep asap and continue my operation on Core1 if need.
And if I need scheduled wakeup for Core1 and I can use RTC, OS event or other timers. What is recommended.
Core1 communicate to Core0 by using MAILBOX and it should always work becouse Core0 can't be in Powerdown if Core1 send interrupts.
Could you suggest what is the best power model in this case ?
How wakeup sources can wakeup both cores if GINT0 routed to Core0 and GINT1 to Core1 for example.
Regards,
Eugene