如果INTCON.PEIE=1，MiWi堆栈将无限循环

如果你不需要花很多时间调试它，我希望你能有任何见解。我有一个MC TS的案例。我没有收到来自MC摘要的确认和决议：我使用MIWI演示工具包（DM182016-1）和MLA V2017Y03Y06的代码来开发MiWi网格。我加载了SW，让演示板按原样工作。我修改了我自己的PanCo和EngDead板的代码。我可以成功地在ED和PANCO之间传输数据。然后，当我在PANCO代码的Syc中加上“ItNo.Peee＝1”时，MiWi堆栈将无限地循环大约5分钟到2HRS。用“InCON.Peee＝1”，数据在PanCo和ED.之间传输OK，这个问题将发生在5分钟到2小时之后。调试表明，在一次故障中，主机被卡住，如果（MippuxUnaseTalk（ListSoist.Boad，NULL，FALSE）＝TRUE）和空隙中断HISISR（无效），我添加了“ItNCON.PEI= 1”；对于MIWI Demo KIT PANCO板的代码，同样的问题发生了。这意味着低优先级中断不能用MiWi启用。栈。



以下为原文

I post this so if you don't have to spend much time debugging it, and hope to hear from you if you have any insight. I have a case with MC TS on this. I have not received confirmation and resolution from MC.

Summary:
I'm using MiWi Demo kit (DM182016-1) and code from MLA v2017_03_06 to develop a MiWi mesh. I loaded the sw and got the demo boards working as-is. I modified the code for my own PanCo and EndDevice boards. I can transfer data between my ED and PanCo successfully. Then when I added "INTCON.PEIE = 1;" in system.c of PanCo code, MiWi stack will get in a loop infinitely about 5 minutes to 2hrs later.

With "INTCON.PEIE = 1;", data were transferred OK between PanCo and ED. The issue would occur about 5 minutes to 2hrs later. Debugging shows that in one failure, host is stuck in if(MiApp_UnicastAddress(lastSource.bytes,NULL,false)==true) and void interrupt HighISR(void)

I added "INTCON.PEIE = 1;" to the code for MiWI-Demo-kit PanCo board, the same issue occurred.

This means low-priority interrupt can't be enable with MiWi stack.