ICD3不会编程或执行自检， PGC和PGD保持不活动状态

几年前我遇到了一个问题，MMC免费更换了一个。我认为这不是保修。没有问题问？文斯



      以下为原文

    I had a problem a few years ago and MC replaced one at no charge. I don't think it was in warranty. No questions asked?
Vince

谢谢文斯，但是我已经有很多年了。我怀疑我和他们在一起。我可以看到这两条线到SN7LVC1T45收发器，所以我会看看信号是否达到这个，如果它的引脚有电源。如果这就是全部的话，我很有可能修理它。



      以下为原文

    Thanks Vince, but I've had these for years. I suspect I'm on my own with them.
 
I can see the two lines go to a SN74LVC1T45 transceiver so I'll see if the signals are reaching that and if there's power to its pins. If that's all it is, I can probably fix it.

好的，从头开始PGC和PGD不切换，我现在可以看到他们输出一个突发时，我把它连接到我的目标，并尝试编程它。我正在看我正在编程的IC的腿，我尝试了一个新芯片，只是为了证明它不是死的。我想，自我测试不足以切换到示波器上，而不需要数字存储范围。所以我可以看到那些线在做它们的事情，但它不知道。像MCLR这样的OKS仍然很高。我不知道这是不是正确的。如果PGC和PGD都干净地切换，还有什么会引起这个问题？这到底是软件问题吗？这不是我第一次把ICD3变成一个不连接或自我测试的状态，只是为了奇迹般地重新开始工作。是否有某种重置，我可以做或迫使固件重新加载？



      以下为原文

    Ok, scratch PGC and PGD not toggling, I can now see that they do output a burst when I connect it to my target and try to program it. I'm looking right onto the legs of the IC I'm trying to program and I've tried a new chip just to prove that it's not a dead one.
I guess the self test doesn't toggle the lines enough to see them on the oscilloscope without a digital storage scope.
 
So I can see those lines doing their thing but it looks like MCLR remains high throughout. I don't know if that's right or not.
 
If both PGC and PGD are cleanly switching, what else can be causing the issue? Is this a software issue after all? 
 
This wouldn't be the first time that I've got the ICD3 into a state where it just wouldn't connect or self test, only for it to magically start working again. Is there some sort of reset that I can do or force the firmware to reload?
 

每个新版本的MPLABX似乎加载新的固件到ICD3。也许尝试一下MPLABX的早期版本。也改变部分似乎更新固件，以及文斯。



      以下为原文

    Each new version of MPLabX seems to load new firmware to the ICD3. Maybe try an earlier version fo MPLabX. Also changing parts seems to update the firmware as well.
Vince

好的，我刚换到另一个目标板上，有一个不同的处理器，编程好可以切换回到原来的板上。我现在得到这些错误。在端点2上传输失败连接失败。如果问题仍然存在，请断开并重新连接ICD 3到USB电缆。如果没有解决这个问题，验证是否安装了适当的MPLAB X USB驱动程序。端点1上的接收失败（Err＝- 10121）连接失败。如果问题仍然存在，请将ICD 3断开并重新连接到USB电缆。如果这不能解决问题，验证是否安装了适当的MPLAB X USB驱动程序。如果它能编程一种类型而不是另一种类型，它就开始看起来像是软件中的东西。



      以下为原文

    Ok, I've just changed to another target board with a different processor and that programmed ok Switching back to the original board I get these errors now...
 
Transmission on endpoint 2 failed
Connection Failed.
If the problem persists, please disconnect and reconnect the ICD 3 to the USB cable. If this does not fix the problem verify that the proper MPLAB X USB drivers have been installed.
 
 
Reception on endpoint 1 failed (err = -10121)
Connection Failed.
If the problem persists, please disconnect and reconnect the ICD 3 to the USB cable. If this does not fix the problem verify that the proper MPLAB X USB drivers have been installed.
 
It's beginning to look like it's something in the software if it can program one type and not another.

过载，或者接地不良，也许？



      以下为原文

    Overload, or bad grounding, maybe?

请继续使用这些单元，我们将替换它们。这里有一个链接来帮助SAR.HTPP//www. McCHIP.COM/CISAR/HOM.ASPX。



      以下为原文

    Please go ahead and SAR these units, we will replace them.
Here is a link to help with the SAR.
 
http://www.microchip.com/cisar/Home.aspx
 

不，我已经尝试了两个ICD3模块，有两个不同的目标，还有自测试模块和使用不同的电缆。固件似乎下载OK，输出PGC和PGD都切换，所以我不知道为什么这些不编程的芯片。我可以看到在芯片的引脚上切换的线路。我认为ICD3硬件存在问题。



      以下为原文

    No, I've tried both ICD3 modules with two different targets and also the self test module and used different cables.
 
The firmware seems to download ok, and the outputs PGC and PGD both toggle so I'm at a loss to know why these don't program the chips. I can see the lines switching right on the pins of the chip.
 
I think there's an issue with the ICD3 hardware.

这里是Microchip故障排除指南：HTTPS://www. MicroPC.COM/CISAR/HOM.ASPXAT，它会让你知道他们是否会把它调换出来。



      以下为原文

    Here is the Microchip trouble shooting guide:
 
https://www.microchip.com/cisar/Home.aspx
 
At the end it will let you know if they will swap it out.

HiWoW与“自我测试板”一起使用吗？自我测试具体检查PGC/PGD谱线。



      以下为原文

    Hi
 
How does it go with the "self-test board"?
The self-test specifically check the PGC/PGD lines.
 

太好了，我刚刚完成了表格，这似乎是一个很好的服务。但我不得不做两次，系统无法应付多个设备。



      以下为原文

    That's great, I've just completed the form and that seems to be a good service. I'll have to do it twice though, the system can't cope with multiple devices.
 

它没有自我测试与各种不同的错误。我要把它换成50美元的费用，这是一个很好的交易，比购买价格过高的ICD4便宜很多。



      以下为原文

    It fails the self test with a variety of different errors. I'm going to get it replaced for the $50 fee, that's a good deal and a lot cheaper than buying the overpriced ICD4
 

ICD4比大图片上的ICD3快（即PIC32 MZ），我假设它不太明显，PICSI小猜想你应该在一个时间内打破一个：



      以下为原文

    The ICD4 is Faster than the ICD3 on Bigger PICs (ie PIC32MZ)
I assume it is less noticeable with smaller PICs
 
I guess you are on supposed to break one at a time Smile:

我刚买了一个ICD4，但我认为它定价过高。我确信以前的ICD版本比以前便宜得多，我想这就是为什么阿迪尼斯现在这么受欢迎的原因。Microchip应该仔细考虑这些成本，他们不应该试图从他们那里赚那么多钱，在我看来，它使人们不再使用他们的产品。



      以下为原文

    I would have just bought an ICD4, but I think it's over priced. I'm sure it used to be much cheaper to get the old ICD versions, I think this is why Arduinos are so popular these days. Microchip ought to take a long hard look at the cost of these, they shouldn't be trying to make as much money from them in my opinion, it puts people off using their products.

这是什么比较呢？ARDUNO与ICD3／4？ARDUINO是一个非常好的平台，可以让爱好者们在没有硬件专业知识和经验的情况下，得到微控制器的游戏。OTHH程序员、调试器和ICE是面向专业级用户的开发工具。不仅开发了固件，还开发了微软周围的硬件。我可以接受ICD4有点定价过高，但当我们得到终身保修，让我们在几年后免费更换，有时滥用……只是我的2美分。



      以下为原文

    Hi

What kind of comparision is this?
Arduino versus ICD3/4?
 
They are not the same kind of tools.
Arduino is a quite nice platform for hobbyists to get a play with microcontrollers without needing professional level knowledge and experience on the hardware details.
OTOH programmers, debuggers and ICEs are development tools targeted at professional level users developing not only the firmware but also the hardware around the micro.
 
I can accept that the ICD4 is a bit overpriced, but when we get a lifetime warranty that gets us a free replacement after several years of use, and sometimes abuse....
 
Just my 2 cents of it....

ARDUIONS是一个带有引导程序的ATMEL CPU。这是解决不同问题的零硬件解决方案。Atmel也销售调试器模块。你认为ToDuNooBootloader是如何开发的？



      以下为原文

    Arduinos are an Atmel CPU with a Bootloader programmed in.  That is a zero hardware solution to a different Problem.  Atmel sells Debugger modules too.  How do you think the Arduino bootloader was developed?

好的，更新一下…尽管Microchip已经在我的50美元的非保修更换方案下给我两个替换单元，但我仍然没有进一步前进。我一直抵制第二个替换单元，直到我知道发生了什么。第一个替换单元的行为完全和我发送的一样。必须是一个软件问题。我第一次尝试自我测试失败，“不能连接到选定的硬件工具。请确保MPLAB X中的另一个项目没有使用该工具。它还显示了测试每一行的失败。然后，我决定尝试对我的目标进行编程，因为ICD3测试接口模块可能会有问题。“目标电压检测目标设备ID（0x0）是一个无效的设备ID。请检查您的连接到目标设备。设备擦除…编程…以下存储器区域将被编程：程序存储器：起始地址＝0x0，结束地址＝0x191fCON。形状记忆程序存储器地址：0预期值：3180接收值：程序设备失败：“我改变了USB电缆，未安装的MPLAB-X V4.15，并尝试了V4.2和V3.65，所有的结果都相同。我已经卸载了微芯片WiUSB设备，现在它被重新安装了。V1.0.0.8，但这并不工作，我注意到Windows最近更新，我开始怀疑最新的更新是否与ICD3模块不工作。这个模块很高兴地下载了所选芯片的固件，只有当它真的被编程到芯片上时，它才会遇到麻烦。还有其他人有这个问题吗？当我什么也没变的时候，它突然出现了。



      以下为原文

    Ok, an update on this... I'm still no further forward even though Microchip have sent me two replacement units under their $50 non-warranty replacement scheme.
 
I've resisted plugging in the second one until I know what's going on.
 
The first replacement unit behaves exactly in the same way as the ones I've sent back, so this has to be a software issue.
I first tried the self test which fails with
 
"Could not connect to the selected hardware tool. Please make sure the tool is not being used by another project in MPLAB X."
It also shows the failure to test each line.
 
I then decided to try to program my target since the ICD3 Test Interface Module could possibly have an issue. That fails with the following error...
 
"Target voltage detected
Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.
Device Erased...
Programming...
The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x191f
configuration memory
program memory
Address: 0 Expected Value: 3180 Received Value: 0
Failed to program device"
 
I've changed the USB cable, uninstalled MPLAB-X V4.15 and tried it with V4.2 and also V3.65, all with the same result.
I've uninstalled the Microchip WinUSB Device and it now is re-installed with V1.0.0.8 but that doesn't work
 
I noticed that Windows updated very recently, and I'm beginning to wonder if the latest updates don't work with the ICD3 module. The module happily downloads the firmware for the selected chip, it's only when it actually goes to program the chip that it runs into trouble.
 
Has anyone else got this problem? It just came out of the blue when I'd changed nothing.
 

我放弃了主计算机，尝试了运行Windows 7和MPLAB-X V4.05i的笔记本电脑，首先编程了PIC18F2480项目，它是在该系统上运行的最后一个产品，它在新的ICD3上运行良好，即使在ICD3测试接口模块F上进行自测试。然后，我用PIC16F18345芯片切换到我的新项目，它在没有下载任何新固件的情况下用生产构建程序。用调试版本再次尝试它不起作用，大概是因为它下载了一个新的有bug的固件。我换了一个新的芯片，这没什么区别。切换到另一个项目，它又是快乐的。所以看起来固件有问题。每次它改变到PIC16F18345固件，它将无法连接。奇怪的是，它成功地在不改变固件的情况下对芯片进行了一次编程，但是这可能是因为两台计算机通过Dropbox共享相同的文件，它可能会被弄糊涂了。有没有其他人在PIC16F18345固件上遇到问题？奇怪的是，这是一分钟，然后没有。这就像是在Microchip上的人对固件进行了更改，一旦它被自动下载，它就出问题了。有没有办法回滚固件，所以我可以在没有最新更改的情况下尝试它？



      以下为原文

    I gave up on the main computer and tried my Laptop which is running Windows 7 and MPLAB-X V4.05
I first programmed a PIC18F2480 project which was the last one run on that system as a production build and that worked fine with the new ICD3 even though the self test on the ICD3 Test Interface Module failed.
I then switched to my new project with the PIC16F18345 chip and it programmed it with the Production build without downloading any new firmware. Trying it again with a debug build doesn't work, presumably because it downloaded new firmware that has a bug. I changed to a new chip and that makes no difference.
Switching back to the other project it's happy again.
 
So it would appear that there's something wrong in the firmware. Every time it changes to the PIC16F18345 firmware it won't connect. It's odd that it managed to program the chip once without changing the firmware, but that might just be because the two computers share the same files via Dropbox and it might have got confused.
 
Has anyone else got an issue with the PIC16F18345 firmware? It's strange that this was working one minute and then not. It's almost as if someone at Microchip made a change to the firmware and as soon as that was automatically downloaded it all went wrong.
 
Is there any way to roll back the firmware so I can try it without the latest changes?

MPLABX需要软件附带。为了恢复固件，你需要使用一个旧版本的MPLABX。我假设你只使用MPLABX而不使用MPLAB 8。



      以下为原文

    MPLabX needs the Software is comes with.  To Rool Back the Firmware you need to use an older version of MPlabX.
And I am assuming you are Only Using MplabX and Not using MPlab 8 at all.