[问答]

安装了Saleae Logic的MPLAB IPE 3.5x冻结

问答对人有帮助，内容完整，我也想知道答案 0 好的，这是一个奇怪的例子，但是我们看到它发生了两次，MPLAB 3.51和3.55。我们最初安装了MPLAB 3.51，安装在Windows 7, 64位机上，运行良好，使用IPE编程使用PICtiT3的PIC16设备。然后有一天，安装了SaleaLogic 16协议分析仪装置。在安装了驱动程序之后，当MPLAB-X IPE启动时，它的窗口要么完全是空白的，要么是被绘制出来的，但它只是冻结了。它的右上角说“校验和”只是说“计算”。MPLAB-X IDE仍然运行正常，所以我们使用它来编程设备。我们试图卸载3.51并重新安装。运气不好，3.55岁的时候我们试着安装。没有运气。我们在另一台电脑上安装了3.51台，并验证了它在第一台计算机上的运行。然后我们安装了SALEAE分析仪。IPE又坏了。安装了3.55个IPE仍然被打破。这是一个有趣的地方：IPE 3.40：工作非常好。所以，有人对这件事有什么想法吗？以上来自于百度翻译以下为原文 OK, this is a weird one, but we've seen it happen twice, with MPLAB 3.51 and 3.55. We initially had MPLAB 3.51 installed on a Windows 7, 64-bit machine, running just fine, and using IPE to program some PIC16 devices using a PICKIT3 just fine. Then one day a Saleae Logic 16 Protocol Analyzer device was installed. After the driver for that was installed, when MPLAB-X IPE was started, the window for it was either completely blank, or it got drawn, but it just froze. The upper right of it, where it says "Checksum" would just say "calculating". MPLAB-X IDE still ran OK, so we resorted to using that to program the devices. We tried to uninstall 3.51 and reinstall. No luck. When 3.55 came out we tried installing that. No luck. We installed 3.51 on another computer and verified it was working as it used to on the first computer. Then we installed the Saleae analyzer. IPE Broken again. Installed 3.55 IPE still broken. Here's the interesing bit: IPE 3.40: Works perfectly fine. So, has anybody got any wild ideas as to what the heck is going on? 0
2019-4-29 06:03:51　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × qun333 该类别下有 57 个回答。邀请回答技术发广告该类别下有 56 个回答。邀请回答 caoguiqun 该类别下有 56 个回答。邀请回答 psw30 该类别下有 44 个回答。邀请回答伊丹姿子该类别下有 41 个回答。邀请回答 uwufwjrw 该类别下有 39 个回答。邀请回答 hetao1111 该类别下有 38 个回答。邀请回答 lc123617 该类别下有 35 个回答。邀请回答欧阳大大该类别下有 32 个回答。邀请回答作死不止该类别下有 31 个回答。邀请回答 asd010 该类别下有 31 个回答。邀请回答 wy8719 该类别下有 29 个回答。邀请回答 60user92 该类别下有 29 个回答。邀请回答 ju978779 该类别下有 28 个回答。邀请回答嘻嘻爱哈哈该类别下有 28 个回答。邀请回答 haikitty 该类别下有 28 个回答。邀请回答 pol666 该类别下有 27 个回答。邀请回答 xiuzhen122 该类别下有 27 个回答。邀请回答 ueywyrsdfs 该类别下有 26 个回答。邀请回答 lhly23 该类别下有 25 个回答。邀请回答举报余小娟相关推荐 • MPLAB X IDE和MPLAB X IPE自动安装是正确的吗？ 3489 • MPLAB IPE启动没有反应 7854 • MPLAB IPE 5不在Win 10上发射 1969 • IPE 3.25无法在OS X 10.11.1的全新安装中启动 1384 • 无法使用MPLAB IPE 4.05在lvp中编程PIC16LF1459 1636 • MPLAB X IPE和dpi缩放工具无法使用 3243 • 无法找到JRE PK3CMD Windows 10 64位 1367 • Real Ice未在MPLAB X IDE中显示 1748 • MPLAB IPE 1.85认为ICD3的固件版本01.26.05太旧，因此无法正常工作 2151 • 怎么在4K屏幕上使用MPLAB X 3.5 2124 2个回答

答案对人有帮助，有参考价值 0 它是为我与Windows 10 以上来自于百度翻译以下为原文 It is working for me with Windows 10 Attached Image(s)

2019-4-29 06:16:14 评论举报陈杰

答案对人有帮助，有参考价值 0 I（现在）在具有SaleAE逻辑8的Windows 10 X64系统上没有MPLABX（包括IPE和ICD3）3.45、3.51、3.55的问题。PC是相当新的，它使用MPLABX 3.45和Salea逻辑和ICD 3（USB 2）都很好。在安装3.51之后，我可能有类似或相同的问题。刚安装后，我第一次意识到打开“Project Projts”（例如从DasBoots）会冻结一些线程（在GUI中，您可以看到硬件工具的列表没有被正确填写）。对于IPE，在启动过程中会发生某种冻结。我今天的结论是，MPLABX或IPE都通过USB来检测/连接到ICD3，这导致了冻结/故障。我有很多假设如何与MPLABX版本相关，但没有一个是真的，因为在很多安装和D之后的某个时间点。这个问题突然出现在我的3.45个版本中，以前工作过。此外，Windows系统恢复到3.51安装之前的时间没有帮助。HTTP://www. McCHIP.COM/FUMMS/FINDPOST/969570I也尝试使用不同的USB端口从我的（内部）USB集线器等。最后，在与马克从SaleAe讨论后，我可以解决这个问题。对我来说，问题是（最有可能）与我的华硕内部USB集线器（3和3.1）的驱动有关，使用华硕USB 3.1的最新驱动程序，用于我的华硕Z170主板。在返回到微软USB 3.1驱动程序（ASMICE USB 3.1可扩展主机控制器1.10）（微软）之后，问题消失了，到现在为止一个月都没有出现过。由于其他USB设备的其他问题，我认为SaleaAuthor设备不是罪魁祸首，可能是它。放大现有的问题。验证需要更多的测试。但这需要大量的清洁设施。我也在我的许多测试中卸载了SaleAE驱动程序（和其他），这并没有解决我的问题。总之：肯定有很多原因，为什么IPE（或MPLABX）冻结。你也应该考虑一个不稳定的Windows USB驱动系统。以上来自于百度翻译以下为原文 I (now) have no problems with MplabX (incl. IPE and ICD3) 3.45, 3.51, 3.55 on a Windows 10 x64 system with Saleae Logic 8. The PC is rather new and it worked fine with MpLabx 3.45 and Salea Logic and ICD 3 (both USB 2.0). Immediately after installation of 3.51 I had possibly similar or same problems as you have. Just after installation I first realized that opening the 'Project Properties' (e.g. from Da**oard) would freeze some thread (in the GUI you could see that the list with Hardware Tools was not filled correctly). For IPE some kind of freeze would happen during start. My conclusion today is that both MpLabX or IPE then try via USB to detect / connect to the ICD3. which results in the freeze / malfunction. I had a lot of assumptions how that could be related to the version of MPLABx, but none of them was true, because at some point after lots of installations and deinstallations the problem suddenly also was there in my 3.45 version, which worked before. Also a Windows system restore to a time before the 3.51 installation did not help. http://www.microchip.com/forums/FindPost/969570 I also tried to use different USB Ports from my (internal) USB Hubs etc. Finally, after discussion with Mark from Saleae I could solve the problem. For me the problem was (most likely) related to the driver of my ASUS internal USB Hubs (both 3.0 and 3.1) using Asus USB 3.1 latest drivers for my ASUS Z170 main board ).* After reverting to the Microsoft USB 3.1 drivers (ASMedia USB 3.1 eXtensible Host Controller - 1.10 (Microsoft), the problem was gone and did not appear again so far for a month now. Due to other problems with other USB devices, I think that the Saleae driver / device was not the culprit, may be it amplifies existing problems. Verifying would require many more tests. But that would require a lot of clean installations. I also deinstalled the Saleae driver (and others) in one of my many tests,- this did not fix my problems. To sum up: there certainly may be lots of reasons, why the IPE (or MPLabx) freezes. You should also consider an instable Windows USB driver system.

2019-4-29 06:32:55 评论举报李雨晨