WDT在低功耗模式下出现问题

1。锁定WDT类似于其他芯片上的锁定闪存；这样，您就不会意外地修改事物，而且当代码更改时，代码会更加慎重（尽管这也不是防火的）。有一点需要注意的是，它看起来也像是锁定了ILO时钟不被修改/改变……这可能是你的WDT无法工作/运行的原因吗？
2。如果你正在运行RTC时钟，也许它正在调用这个函数：CySysFlashClockConfig（Valy），它将改变IMO运行？
否则，我也不知道它会如何运行。我知道，当我第一次弄乱时钟设置时，IMO在尝试运行时禁用了这导致了问题…：3
三。RTC看起来像是要硬地使用WDTS中的一个：你应该阅读RTC时钟的数据表；特别是第4页提到你需要在时钟选择页面下配置时钟设置（在那里你启用/禁用ILO、IMO、WDT等），你可以把RTC设置给我们。是WDT时钟之一。通过阅读，RTC可能会在不处于休眠状态时发生火灾？（基于手动更新复选框，我想）



     以下为原文
  1. Locking the WDT is similar to locking flash on other chips; So that you don't accidently modify things, and the code is more deliberate when it changes it (although this isn't fireproof either). One thing to note, is that it looks like that function also locks the ILO clock from being modified/changed...Perhaps this is the cause of your WDT failing to work/run?
2. If you are running the RTC clock, perhaps it is calling this function: CySysFlashClockConfig(void) which will change the IMO to be running?
Otherwise, I don't understand how it would be running either. I know that when I first messed with the clock settings, having IMO disabled when trying to run that caused problems... :3
3. The RTC looks like you can hardwire one of the WDTs to be used: You should read the datasheet for the RTC clock; Specifically page 4 mentions that you need to configure the clock setting under the clock selection page (where you enable/disable the ILO,IMO,WDT, etc.) There, you can set the RTC to use one of the WDT clocks. Reading through this, the RTC might actually fire when not in sleep mode? (Based on the update manually checkbox I think)

我简化了我的代码，摆脱了RTC时钟。相反，我设置WDT每100毫秒开火，并增加一个滴答计数器。这就涵盖了我目前的时钟需求，而且似乎运转良好。
我想不出任何其他可能使IMO得以实现的原因，所以为什么这个序列不崩溃仍然是个谜。
CysScLyCuffelfCKDead（CythySyl CKYH-FFLKKY-ECO）；
CysSycLimoCo（）；
CysSpMySeLeP（）；
CysSLCKIMOSTART（）；
CysScLyCuffelfCKDead（CythySyl CkkHfCKKYMIO）；
哦，好吧。稍后将重访。继续前进…
非常感谢你的帮助。
更多问题要跟进



     以下为原文
  I simplified my code and got rid of the RTC clock. Instead I set the WDT to fire every 100 ms and increment a tick counter . That covers  my needs in terms of the clock for now and seems to be working well.
I can't think of anything else that may be enabling the IMO. so it still remains a mystery why this sequence does NOT crash
            CySysClkWriteHfclkDirect(CY_SYS_CLK_HFCLK_ECO);
            CySysClkImoStop();
            CySysPmSleep();         
            CySysClkImoStart();
            CySysClkWriteHfclkDirect(CY_SYS_CLK_HFCLK_IMO);
Oh well. will revisit later. moving on ..
Thank you so much for all your help
More questions  to follow