在调试期间ICD 3或4无响应时必须杀死MPLABX

项目仪表板中的刷新调试工具状态不工作吗？



      以下为原文

    Does the Refresh Debug Tool Status, in the project dashboard, not work?

还是拔掉USB电缆并把它插回去？



      以下为原文

    Or unplugging the USB cable and Plugging it back in?

这可能是由于您在“Project Projts”下设置ICD3“冻结外围设备设置”。如果你试图读取一个冻结的外围标志，它将永远不会发生。当试图调试图形显示和等待For（Apple Tube）标志时，我发现了这一点。



      以下为原文

    It could be due to your settings for ICD3 "Freeze Peripherals settings" under "Project Properties". If you are trying to read a flag of a frozen peripheral it will never happen. I found this out when trying to debug Graphics display and waiting for while(_PUBUSY) flag to clear.

我试着拔掉ICD 4。唯一能让它反应的方法就是关闭程序。当调试器运行一段时间时发生。但不是所有的时间。我没有尝试过“刷新调试工具状态”。我要试一试。



      以下为原文

    I have tried to unplug the ICD 4. The only way to make it responsive is to close program. It happens when the debugger is running for a while. Not all the time though. I have not tried "Refresh Debug Tool Status". I will give that a shot.

你好，丹东尼，如果你愿意的话，你能提供以下信息吗？（1）使用MPLAB X IDE的版本是什么？2）当遇到这个问题时，你正在使用的MCU部件号是多少？3）当发生这种情况时，在“输出”窗口中可以看到哪些错误消息，可以在这个线程中发布？谢谢，肯。



      以下为原文

    Hello danthony,
 
If you are willing, could you provide the following information (with regard to when you experience this issue)?:
 
1) What version(s) of MPLAB X IDE are you using?
2) What is/are the MCU part number(s) you are working with when experiencing this issue?
3) When this happens are there any error messages you are seeing in the 'Output' window that you can post in this thread?
 
Thank you.
 
Best regards,
 
Ken

嗨，肯，1）MPLABX IDE 4.052）PIC32 MZ2048 ECH144 PH3）当我离开调试模式运行一段时间时发生。我试图停止调试，命令停止似乎没有影响。我会检查消息，当再次发生，但不记得任何。



      以下为原文

    Hi Ken,
 
1) MPLABX IDE 4.05
2) PIC32MZ2048ECH144 PH
3) It happens when I leave debug mode running for some time. I try to stop debug and the command to stop does not seem to take affect. I will check for messages when in happens again but do not recall any.

嗨，我和ICD4有同样的问题。只有重新启动MPLABX才有帮助。



      以下为原文

    Hi,
 
I have the same problem with ICD4. Only restart of mplabx helps.

你好，丹东尼，非常感谢你花时间为你所面临的问题提供额外的细节。我想现在我对你的问题有了更好的了解：你有一个调试会话正在运行，你的目标正在运行，并且在X次的时间之后你试图停止（MPLAB X IDE）暂停按钮。你被锁起来了，对吗？对不起，如果你不介意的话，我忘了问你几个问题：1）你能告诉我你在运行MPLAB X IDE吗？2）这是笔记本电脑还是PC机？3）你的代码是否在PIC32 MZ2048 EC144上运行，在任何时候都能进入睡眠模式？（我不是积极的，但如果这样，它可能会杀死调试会话。我没有亲自做这个实验，所以我在这一点上动摇了。）你有没有像PIC32 MZ2048 ECH144在这个问题发生时仍然在运行的视觉指示？4）当这个问题发生的时间窗口足够长，你的PC /笔记本电脑可能进入电源休眠模式，或者可能是USB选择性暂停（在高级电源设置下）？（再次，我不是100%肯定如果USB选择性暂停将是一个怀疑或不涉及您的问题。）我抛出一些潜在的想法，以消除罪魁祸首，帮助解决这个问题。我想弄清楚，根本原因可能是PIC32 MZ2048 ECH144侧（它仍然在运行代码，还是在睡觉？）或者在PC端，最好的问候，肯



      以下为原文

    Hello danthony,
 
Thank you very much for taking the time to provide the extra details about the issue you are facing.
 
I think I understand your issue much better now:
You have a debug session running and your target is running, and after X amount of time you try to halt (MPLAB X IDE 'Pause' button) and you get locked up, correct?
 
Sorry, I forgot to ask you several more questions if you don't mind:
 
1) Could you also let me know what OS you are running MPLAB X IDE on?
 
2) Is this a laptop or PC?
 
3) Is your code running on your PIC32MZ2048ECH144 putting it into Sleep mode at any point?
(I am not positive but if so it might kill a Debug session. I have not run this experiment personally so I am shaky on this point.)
Do you have for example visual indication that the PIC32MZ2048ECH144 is still running when this issue happens?
 
4) Is the time period window when this issue happens long enough that your PC/laptop perhaps goes into power sleep mode or perhaps USB selective suspend (under advanced power settings)?
(Again, I am not 100% certain if USB selective suspend would be a suspect or not with regard to your issue.)
 
I'm throwing out some potential ideas to eliminate from being the culprit to help troubleshoot this. I'm trying to figure out if the root cause is perhaps on the PIC32MZ2048ECH144 side (is it still running code or perhaps sleeping?) or on the PC side.
 
Best regards,
 
Ken
 
 
 
 
 
 

1）我在Windows 7上运行。2）它是PC英特尔I7 7000 K处理器，16 GB RAM3）在这个项目中，我根本不使用睡眠模式。需要验证下一次是否运行。我可以尝试访问处理器中的网页，并且尝试使用我已经连接的按钮。4）所有的电源管理（睡眠模式）都在我的桌面上被禁用。USB选择性挂起被禁用。谢谢您的帮助。戴维



      以下为原文

    1) I am running on Windows 7 Ultimate.
2) It is PC Intel I7 2700K processor, 16 GB ram
3) I do not use sleep mode at all in this project. Will need to verify if it is running next time. I can try to access webpages in processor and also try to use buttons I have connected.
4)  All power management (sleep modes) are disabled on my desktop. USB selective suspend is disabled.
 
Thanks for your help.
 
David

当发生这种情况时，应用程序正在PIC32上运行。PIC正在服务网页，运行良好。



      以下为原文

    The application is running on PIC32 when this occurs. PIC is serving webpages and is functioning fine.
 
 

从监视列表中删除所有变量，并查看调试会话是否稳定。



      以下为原文

    Remove all variables from your watch list and see if your debugging session stabilizes. 
 
 

你好，戴维，非常感谢你挖掘和提供这些额外的细节-非常感谢。至少在你刚才描述的情况下，我们知道目标MCU仍然正常运行正常的代码。我认为最好的做法是打开一个支持票通过适当的。微芯片通道使得这个问题可以通过微芯片进行研究。如果这可以可靠地复制（有时是最困难的部分），它可以被固定。请务必参考这个微芯片论坛线程，以便他们会得到一些额外的细节，你的问题。你可以打电话或如果你有一个帐户提交和电子机票：HTTP://www. MicroPC.COM/Sputp/HoTopopics.ASPXI我想看看我是否可以复制这个。在我的办公桌（通过调试会话运行一夜），但我不能作出任何承诺，因为我的工作时间表（因此我建议你打开一个支持票）。对不起，你遇到这种麻烦。我希望这个消息有点帮助。最好的问候，肯



      以下为原文

     
Hello David,
 
Thanks very much for digging in and for providing these extra details -- it is greatly appreciated.
At least in the case you just described we know that the target MCU is still running proper code as normal.
 
I think the best thing to do would be to open a Support Ticket through the proper Microchip channels so that this issue can be investigated by Microchip. If this can be reliably reproduced (sometimes the toughest part) it can be fixed. Make sure you reference this Microchip Forum thread so that they will get some extra details regarding your issue.
 
You could call on the phone or if you have an account submit and electronic ticket:
http://www.microchip.com/support/hottopics.aspx
 
Personally I would like to see if I can reproduce this at my desk (by having a debug session run overnight) but I cannot make any promises due to my work schedule (hence me suggesting you open a support ticket).
 
I'm sorry you are experiencing this trouble. I hope this message helps somewhat.
 
Best regards,
 
Ken
 
 
 

你好，KLMEA，客户应该能够在没有经历锁定调试会话的情况下调试会话长时间运行。把这一点吸引到微芯片上（通过支持通道）是找到根本原因的第一步。我对戴维的建议（关于用Microchip打开一张支持票）也适用于你。如果你的情况有所不同，那么我建议创建一个新的微卡。P论坛线程（如果你想），如果你仍然需要从微芯片论坛社区获得帮助或想法。这将有助于保持事情的焦点。不过，我觉得最好的做法是打开官方的支持票，这样资源就可以被分配来查看整个调试问题（不管是什么根本原因）。最好的问候，肯。



      以下为原文

    Hello Klema,
 
Customers should be able to have debug sessions run for extended periods of time without experiencing locked up debugging sessions. Bringing this to Microchip's attention (via the support channel) is the first step in finding the root cause.
 
My advice to David (regarding opening up a support ticket with Microchip) would also apply to you as well.
If your situation is somewhat different then I would suggest creating a new Microchip Forum thread (if you want to) if you still need to get help or ideas from the Microchip Forum Community. This will help keep things focused. However, I feel the best course of action would be to open up an official support ticket so resources can be allocated to look into this overall debugging issue (whatever the root cause).
 
Best regards,
 
Ken

你好，戴维，当您运行最后一个测试并证明PIC32 MZ2048 ECH144仍然运行良好（仍然服务网页和响应交换机）是您的调试工具MPLAB ICD 3还是MPLAB ICD 4？（我从你的标题中了解到这两个工具都有问题，但我希望从一个分类的角度来看，哪个工具可能会给你带来更多的问题。）谢谢。肯，最好的问候。



      以下为原文

     
Hello David,
 
When you ran your last test and proved that the PIC32MZ2048ECH144 was still running fine (still serving web pages and responding to the switches) was your debug tool the MPLAB ICD 3 or MPLAB ICD 4?
 
(I realize from your title of this thread that you are having problems with both tools in this regard, but I hoping to know, from a triage point of view, which tool may be giving you more problems.)
 
Thank you.
 
Best regards,
 
Ken 

我用的是ICD4。如果我没记错的话，我认为我最好在ICD3上成功。我使用ICD3已经几个月了。



      以下为原文

    I was using ICD4. I think I had better success with the ICD3 if I remember correctly. It has been a few months since I have used ICD3.