睡眠唤醒程序进入一个未知的状态

嗨，克里斯汀，
1）ISR中的任何一个都操纵变量“状态”的值吗？
2）在与PICU中断相关的ISR中做了什么？恢复ISR中的时钟似乎更直观。
3）当设备处于休眠模式时，关闭IMO。因此，在调试模式下运行该设备是不可能的。请验证芯片功能是否正常运行（如果不在“调试”模式下运行）。



     以下为原文
  Hi kristen,
     
    1) Does any of the ISR manipulate the value of the variable "state"?
    2) What is done in the ISR associated with the PICU interrupt? Restoring the clocks in that ISR seems more intuitive.
    3) When the device is in Sleep mode, the IMO is turned off. So, running the device in Debug mode is not possible while in sleep. Please verify if the chip functionality is as expected when it is run normally (without running in "Debug" mode).

我看了一下附件的代码。虽然在这一点上我找不到确切的问题，但我建议你尝试以下几点。
我看到您在使用CypSaveCuxScript（）API保存时钟后启用ISR并调用while循环。建议CyPmSleep（）在节电后不久，不要做任何其他功能，因为所有的费时时钟都关闭，可能会导致不理想的结果。当部件醒来时，也会恢复时钟。
CyPultStasuSUE（）不是必需的，因为部分没有从CTW事件中醒来。
尝试将所有组件唤醒API都放在中断例程之外（在主C中恢复时钟后立即写入）
从而利用ISR常规只有明确中断状态位/设置标志等。
如果可能的话，你可以将项目在这里让我可以重新审视其走错在哪里？
谢谢，
SRIM



     以下为原文
  I had a glance at the attached code. Although I could not find the exact issue at this point, I would suggest you to try the following things.
    I see that you are enabling the ISR and calling a while loop after saving clocks using CyPmSaveClocks() API. It is advisable to call CyPmSleep( ) soon after saving clocks and not to do any other functions as all the pheripheral clocks are off and could result in undesirable results. Also restore clocks as soon as the part wakes up.
    CyPmReadStatus() is not necessary as the part is not waking from a CTW event.
    Try keeping all component wake-up APIs outside the interrupt routine (writing soon after the restore clocks in main.c) and 
    thereby using ISR rotine only to clear interrup status bits/ setting flag etc..
    If possible, can you attach the project here so that I can relook where exactly its goin wrong?
     
    Thanks,
    SRIM

我建议你把你的项目上传到这里，这样我们就可以完整地看到你的照片了。我们可以怀疑很少的事情，但我们不能没有根本原因没有你的完整项目。



     以下为原文
  I would suggest you to upload your project here, so that we get a complete poicture of your picture. We can suspect few things but we can not zero in on the root cause without your complete project.