完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
我正在尝试使用Curioti板编程设备，使用PIC16F1708 MCU。该项目是单一的.C文件，主要功能是空while循环。在MPLABX 3.65中，所有的工作都是预期的。这个操作需要一分钟，主要是因为固件更新。虽然在MPLABX 4，事情变得怪异，它永远呆在这里。IDE右下角的进度条消失了。随后尝试执行相同的动作，只会永远留在这里。关闭MPLABX 4和打开MPLABX 3.65 -所有的工作，我可以编程MCU如预期再次。我检查的行为与PACTIT3，它工作如预期。其他人有类似的经验吗？
以上来自于百度翻译 以下为原文 I'm trying to program device using Curiosty board, using PIC16F1708 MCU. The project is single .c file with empty while loop in main function. In MPLABX 3.65, everything works as expected ***************************************************** Connecting to Starter Kit on Board... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 Firmware type..............Enhanced Midrange Now Downloading new Firmware for target device: PIC16F1708 Downloading bootloader Bootloader download complete Programming download... Downloading RS... RS download complete Programming download... Downloading AP... AP download complete Programming download... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 Firmware type..............Enhanced Midrange Target voltage detected Target device PIC16F1708 found. Device ID Revision = 2004 Device Erased... Programming... The following memory area(s) will be programmed: program memory: start address = 0x0, end address = 0x7ff configuration memory Programming/Verify complete This operation takes a minute, mainly because of firmware update. Though in MPLABX 4.00, things get weird ***************************************************** Connecting to Starter Kit on Board... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 * Firmware type..............Enhanced Midrange Now Downloading new Firmware for target device: PIC16F1708 Downloading bootloader Bootloader download complete Programming download... Downloading RS... RS download complete Programming download... Downloading AP... AP download complete Programming download... And it stays here forever. The progres***ar in right bottom corner of IDE disappears. Subsequent attempts to perform the same action yield only ***************************************************** Connecting to Starter Kit on Board... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 * Firmware type..............Enhanced Midrange And it stays here forever. Closing MPLABX 4.00 and opening MPLABX 3.65 - everything works, I can program the MCU as expected again. I checked the behavior with PicKit3, it works as expected. Does anybody else have similar experience? 
0
|
|
相关推荐
13个回答
|
|
|
我用Linux MINT 18.2在不同的计算机上尝试了同样的结果。嗯，看起来像是一张支持票的候选人。
以上来自于百度翻译 以下为原文 I tried the same on different computer with Linux Mint 18.2 - exactly the same result. IMHO it looks like a candidate for a support ticket. |
|
|
|
|
|
我已经看到了这样的问题，IDE在某个时候挂起了设备编程工具的更新。在我的例子中，它是PICTIT3，我用MPLAB V892和MPLABX V3.50.0使用它，这似乎导致更新挂起与加载到设备编程工具的固件部分之间的不兼容性有关。这个固件看起来有两个部分，首先是IDE用来与工具通信的部分，第二个是目标特定的部分。我发现，当我的PICTIT3已经用MPLAB V892工作得很好时，我切换到MPLABX V3.50。MPLABX更新了PICTIT3通信固件。然后，将挂起目标特定固件更新，而PICTIT3似乎是砖块。当发生这种情况时，我使用PACKIT3上的按钮强制PICTIT3进入Bootloader模式，并强制对所有PICTIT3固件进行完全更新。一旦PICTIT3是健全的，我强迫目标特定固件更新，通过选择一个PIC目标在一个不同的家庭比目标，我将编程。您的问题可能与此可能的不兼容性。因此，尝试使用IPE编程一个PIC从一个不同的家庭与您的好奇心板，然后切换回您的目标目标PIC。
以上来自于百度翻译 以下为原文 I have seen issues like this where the IDE hangs at some point during the update of a device programming tool. In my case it was the PICkit3 and I was using it with MPLAB v8.92 and MPLABX v3.50. What seems to cause the update to hang has something to do with an incompatibility between parts of the firmware loaded in to the device programming tool. This firmware seems to come in two parts, first is the part that the IDE uses to communicate with the tool, second is the target specific part. I have found that when my PICkit3 has been working fine with MPLAB v8.92 then I switch to MPLABX v3.50 the MPLABX updates the PICkit3 communications firmware and then will hang doing the target specific firmware update and the PICkit3 seems to be bricked. When this happens I use the button on the PICkit3 to force the PICkit3 in to bootloader mode and force a complete update of all the PICkit3 firmware. Once the PICkit3 is sane I force the target specific firmware to update by selecting a PIC target in a different family than the target I will be programming. Your problem may be related to this possible incompatibility. So try using the IPE to program a PIC from a different family with your curiosity board then switch it back to your intended target PIC. |
|
|
|
|
|
是的，当我从V3.65切换到V.4.00时，我的好奇心20PIN和PIC16F1619也遇到了同样的问题。这是好奇实验室的输出：从C:/Microchip / PicroStudio / QualoStudiabLabBLink。X/Dista/Debug / Puthaly/QualoSosiy实验室建立成功的（总时间：17S）加载代码。程序完成后，无法连接到工具硬件：PKOBSKEDPPLAMFIRTOOL，COM。Microchip。MPLAB。在板上连接起动器工具箱……当前加载的固件在Boad固件套件版本…01.4909固件类型……增强的中程…等待增强…等待…等待……一个眨眼的装配：连接到板上的启动工具箱……在Boad固件套件版本的启动工具包上当前加载的固件…01.4909 *固件类型……未知固件类型为目标设备下载新固件：PIC16F1619下载AP…AP下载完成程序下载…等…等……（（**********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************。我决定做一个V4.00的新安装，但没有任何意义。参见http://www. McCyp.com….MS/M99330.ASPX当做，
以上来自于百度翻译 以下为原文 Yes, I got the same problem with my Curiosity 20pins and the PIC16F1619 when I switched from v3.65 to v.4.00 This is the output of the Blink from the Curiosity Labs: BUILD SUCCESSFUL (total time: 17s) Loading code from C:/microchip/PIC_Projects/CuriosityLab_Blink.X/dist/default/production/CuriosityLab_Blink.X.production.hex... Loading completed Connecting to programmer... The programmer could not be started: Could not connect to tool hardware: PKOBSKDEPlatformTool, com.microchip.mplab.mdbcore.pkobskde.PKOBSKDEDbgToolManager ******************************************************** ***************************************************** Connecting to Starter Kit on Board... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 * Firmware type..............Enhanced Midrange .....waiting...waiting....waiting..;-(( ***************************************************** And with a Blink assembly: ************************************* Connecting to Starter Kit on Board... Currently loaded firmware on Starter Kit on Board Firmware Suite Version.....01.49.09 * Firmware type..............Unknown Firmware Type Now Downloading new Firmware for target device: PIC16F1619 Downloading AP... AP download complete Programming download .....waiting....waiting....;-(( *********************************************** Costed me a lot of hours and I decided to do a fresh install of v.4.00 but that didn't make any sense. See alsomy post on http://www.microchip.com/..ms/m979330.aspx#1009517 Kind regards, |
|
|
|
|
|
丹1138：谢谢你的建议。我尝试用不同的编程算法切换到不同的PIC设备（如PIC16F1887，它与E.1708有很大的不同），但是每次重复地、一致地停止在同一个SPOT中。MPLABX似乎与其他调试工具工作得很好，但是用好奇板失败了。这似乎是皮克特3，但是，我打开票，让我们看看会发生什么。
以上来自于百度翻译 以下为原文 dan1138: Thanks for suggestion. I tried to switch to different PIC devices with different programming algorithms (like PIC16F18877 which is significantly different from eg. 1708), but everytime, repeatedly and consistently it stops in the same spot. MPLABX seems to work fine with other debug tools, but fails with curiosity board - which seems to be PicKit3 based, though. I opened ticket, let's see what happens. |
|
|
|
|
|
当我的目标是PIC16F时，我的PICTIT3需要为一个非常不同的家庭选择一个目标设备，基线、中档或增强的中档似乎并没有“不同”。使用PIC18F为我工作，这是一个多年的问题，并已被报道。可能没有一个支持请求足够明确，迫使微芯片找到这个bug。对于MPLABX的发行来说，这是一个显而易见的问题。这可能是基于Microchip的Java工具与各种开发者Windows系统上安装的反病毒保护系统的一个问题。祝你好运，但不要屏息。我认为这个问题会让人过于执着，用一种清晰而愚笨的方法来重现故障，然后微芯片会做很多事情。
以上来自于百度翻译 以下为原文 With my PICkit3 I needed to select a target device for a vastly different family when my target is a PIC16F, base-line, mid-range or enhanced mid-range did not seem "different" enough. Using the PIC18F works for me. This has been an issue for years, and has been reported. It's possible that none of the support requests have been clear enough to compel Microchip to find this bug. This is an obvious problem for developers that no release of MPLABX has been able to fix so far. It's likely an issue with the Microchip Java based tools interacting with anti-virus protection installed on the various developers Windows systems. Good luck but don't hold your breath. I think this problem will take someone being excessively persistent with a clear and fool proof way to reproduce the fault before Microchip will do much about it. |
|
|
|
|
|
所有，我们确实看到了这一点，目前正在研究它。请继续使用V3.65直到我们能够达成一个决议。感谢反馈，问候，霍华德
以上来自于百度翻译 以下为原文 All, We do see this as well and currently looking into it. Please continue to use v3.65 until we can reach a resolution. Appreciate the feedback. Regards, Howard |
|
|
|
|
|
MPLAB X和IPE V4，即使在列表中，也不重新排序皮卡3。回到V3.65。
以上来自于百度翻译 以下为原文 mplab x and ipe v4, both do no regonize pickit 3 even though it is listed. Back to v3.65 |
|
|
|
|
|
令人惊异的是，那些做得很好的事情，在每一个后续版本中都会变得更糟…
以上来自于百度翻译 以下为原文 Amazing how something that did work pretty well, can get worse on each subsequent version... |
|
|
|
|
|
这个问题与MPLABX V4.0更复杂，你知道。我的系统是一个WiNoS7 Pro 64位，英特尔Xeon处理器，4GB RAM和每一个带有MPLABX V4.0的Work.Realice，Explorer 16/32 PigTigBand，PACKIT3都已经更新了BMPLABX，没有挂起。我的公司提出了一些相当令人讨厌的AN。TI病毒在我们的系统中。安全策略不允许本地管理员注册服务，所以每一个XC8更新需要获得域管理员来注册MPLABXC8DLL，所以MPLAB V892可以使用XC8编译器。那么，您的问题可能涉及Windows 10？我知道有WixOS10的PACKIT3问题，参见：HTTP://www. McCHIP.COM/FUMMS/FUNDSPE/83106
以上来自于百度翻译 以下为原文 This issue with MPLABX v4.0 is more complex that you know. My system is a Windows7-pro 64-bit, intel xeon processor, 4GB ram and every with MPLABX v4.0 has worked. RealICE, Explorer 16/32 PICkitOnBoard, and PICkit3 have all been updated bu MPLABX with no hangs. My company puts some fairly obnoxious anti-virus stuff on our systems. The security policies do not allow a local administrator to register a service so every XC8 update I need to get the domain admin to register the MPLABXC8.dll so MPLAB v8.92 can use the XC8 compiler. So perhaps your issues involve Windows10? I do know that there are PICkit3 issues with Windows10, see: http://www.microchip.com/forums/FindPost/883106 |
|
|
|
|
|
|
|
|
|
|
|
我现在是如何工作的。在V3.65，我有3个插入到UBS3端口，没有问题，工作很好，已经老化。现在用V4，它工作在USB2，但不是USB3。我知道PACKIT2只在USB2上工作，但它就像V4已经落后。USB2接近它的结束在现代主板上。
以上来自于百度翻译 以下为原文 I now how it working. On v3.65 I had pickit 3 plugged into a ubs3 port, no problem, works fine and has been ages. Now with v4, it works on u***2 but not u***3. I know pickit2 only works on u***2 but it's like v4 has gone backwards. u***2 is nearing it's end on modern motherboards. |
|
|
|
|
|
我从Microchip的支持得到响应-确认错误，不幸的是，没有4的解决办法，下一个版本应该是好的，或者至少这个bug应该消失了。
以上来自于百度翻译 以下为原文 I got response from Microchip support - the bug is confirmed and unfortunately there is no workaround for 4.00, next release should be OK - or at least this bug should be gone. |
|
|
|
|
|
嘿，Jarin，我好像找到了一个可以帮你解决问题的办法。问题似乎是在MPLAB上升级MPLAB X 4固件。我所做的是手动升级固件使用MPLAB X IDE 3.65，但使用固件从MPLAB X IDE 4。在固件从3.65 IDE升级到4之后，您可以使用MPLAB X IDE 4进行连接，并且不会看到任何问题，因为固件已经是最新的。
以上来自于百度翻译 以下为原文 Hey Jarin, I seem to have found a workaround that might help you. The problem seems to be with upgrading firmware on MPLAB X 4.00 on the curiosity board. What I did was manually upgrade the firmware using MPLAB X IDE 3.65, but using the firmware from MPLAB X IDE 4.00. After the firmware is upgraded to 4.00 from within the 3.65 IDE, you can then connect using the MPLAB X IDE 4.00 and won't see any issues, because the firmware is already up to date. |
|
|
|
|
只有小组成员才能发言，加入小组>>
4986 浏览 9 评论
1904 浏览 8 评论
1837 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3052 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2131 浏览 5 评论
560浏览 1评论
408浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
461浏览 0评论
352浏览 0评论
IPECMD命令烧录AVR128DA48芯片，报找不到芯片错误
837浏览 0评论
/6 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
1687
评论
淘帖
1008
