ICD3是否要求目标上电以从MPLAB v8.56连接？

如果我记得正确的话，ICD3可以为100mA的目标提供能量。除了这个，你还需要外部力量。在MPLAB 8中应该有一个选项来从ICD3上为设备供电。如果MPLAB 8没有找到您的ICD3，它可能是驱动程序的问题。您正在运行的机器是否安装了MPLAX？USB驱动程序根据使用的IDE不同。当您安装MPLAB XID/IPE时，它带有一个驱动器切换器，因此，如果您使用MPLAB 8或MPLAB X，则可以切换它们。确保安装了正确的驱动程序，MPLAB 8应该将其拾起。



      以下为原文

    The ICD3 can power a target up to 100mA if I'm remembering correctly.  Any more than that and you will need external power.  There should be an option in MPLAB 8 to power the device from the ICD3.
 
If MPLAB 8 is not finding your ICD3, it could be a driver problem.  Does the machine you are running this on also have MPLAB X installed?  The USB drivers are different depending on the IDE being used.  When you install the MPLAB X IDE/IPE it comes with a driver switcher so they can be switched depending on if you are using MPLAB 8 or MPLAB X.  Ensure the correct driver is installed and MPLAB 8 should pick it up.

来自http://www. McCys.com /论坛/ M1033569.ASPX 1010912，它有一些有用的上下文信息。



      以下为原文

    Comes from http://www.microchip.com/forums/m1033569.aspx#1033912
which has some useful context info.
 

回答你的前两个（重述）问题：Q1：ICD3是否需要目标功率在ICD3可以由MPLAB 8 IDE选择之前？A1：不，为什么ICD3不能从MPLAB 8 IDE.Q2中选择：可能需要什么其他的东西，这样我才能验证我的开发工具和环境是可靠的吗？A2：您可能需要安装MPLAB V892和MPLABX V4.05安装在真实硬件上的Windows 7。在A1上扩展：在安装MPLAB V853时，您可能没有选择对ICD3的支持。要修复这一点，您需要在自定义或修复模式下再次运行安装程序，并添加ICD3支持。我不记得如何点击这个点击为V853.3另一个可能出现的问题，如果你上次使用你的ICD3与MPLABX。当你做这个固件来支持MPLABX版本的USB设备驱动程序被编程到ICD3。您可能需要强制MPLAB V853重新加载所有的ICD3固件。Windows安装在ICD3上的驱动程序可能是错误的。使用设备管理器使用…中的文件更新ICD3驱动程序。MPLAIDIDICD3驱动程序文件夹。如果在WindowsVM中使用WindowsXP 64位，这些问题会变得更加复杂。并不是所有的MPLAB 8 Vrimes都有稳定的64位USB设备驱动程序。如果你还有一个PICTIT2，这可能是VM最快的工作方式。下一个选择将是一个PICTIT3，但是PICTIT3在使用MPLABX和MPLAB 8时也会有类似的问题。旧的软件和USB设备在一个新的OS和硬件环境下运行是一个挑战。



      以下为原文

    The answers for your first two (restated) questions:
Q1: Does the ICD3 require the target power to be on before the ICD3 can be selected by the MPLAB 8 IDE?
A1: No. There are other reasons why the ICD3 cannot be selected from the MPLAB 8 IDE.
 
Q2: What other things may be needed so I can validate my development tools and environment are reliable?
A2: You may need a Windows 7 installation on real hardware with MPLAB v8.92 and MPLABX v4.05 installed.
 
To expand on my A1:
It is possible that when you installed MPLAB v8.53 you did not select support for the ICD3. To fix this you would need to run the installer again in custom or repair mode and add ICD3 support. I do not remember how to do this click by click for V8.53.
 
Another possible issue can occur if you last used your ICD3 with MPLABX. When you do this firmware to support the MPLABX version of USB device driver is programmed in to the ICD3. You may need to force MPLAB v8.53 to reload all of the ICD3 firmware.
 
Also the driver that Windows installed for the ICD3 may be the wrong one. Use the Device Manager to update the ICD3 driver using the files in the ... MPLAB IDEICD3Drivers folder.
 
These issues can become even more convoluted if you are using WindowsXP 64-bit in your VM. Not all of the MPLAB 8 verisons had stable 64-bit drivers for USB devices.
 
If you still have a PICkit2 that may be the fastest way to get your VM working. Next choice would be a PICkit3, but the PICkit3 can have similar problems when used with both MPLABX and MPLAB 8.
 
Getting old software and USB devices to run right on a new OS and hardware environment is always a challenge.

同意所有丹点。只需扩展其中两个。如果你必须使用MPLAB 8，获得版本8.92，这是“最新的和最伟大的”。同意。它不会是驱动程序的问题（因为两者都使用内置的Windows HID驱动程序），但是用MPLABX加载固件的PK3将与MPLAB8不兼容。如果MPLAB8已与MPLABX一起使用，则必须强制MPLAB8更新所有PK3固件。



      以下为原文

    Agree with all Dan points.
Just expanding on a couple of them.

If you must use MPLAB 8, get version 8.92, which was the "latest and greatest".
 

Agree. It won't be a driver issue (as both use the built in Windows HID driver),
but a PK3 loaded with firmware by MPLABX will be incompatible with MPLAB8. You have to force MPLAB8 to update all the PK3 firmware if it has been used with MPLABX.

谢谢，KTrenholm。我忘了开关了。我把它换了，但没用。谢谢，“DAN1138和@ QYB。请注意，我正在尝试我的WiXP VM以及我的WI10物理机。他们似乎都表现出同样的问题。也就是说，ICD 3菜单选项是灰色的。在安装问题期间，我将调查ICD 3的支持。我不认为我有一个PICTIT2，但我的客户拥有这个IP或构建房子，我们有一个长期的关系。但是，请允许我跳到底游戏：我真的可以重新编译现在的VM，正如在其他帖子中提到的@ QYB指出。现在，我需要做的更改是足够复杂的，我需要实时调试。请注意，我很久以前就设计了这些东西，并且已经忘记了我所知道的一半。该特定产品使用具有外部存储芯片的PIC18C601。问：我能用MPLAB 8和ICD 3实时调试吗？我想这意味着我需要同时编程和（JTAG？）控制处理器。编程必须通过处理器到外部存储器。我必须在很久以前就这样做过。我只是不记得。如果我不能让ICD 3工作，房子有我的旧ICD 2，我可以试试。无论是客户还是构建室都可能有一个PACKIT2。最后，就生产而言，只要我能构建HEX文件，如果我不能从VM中获得任何程序员/调试器，至少我仍然可以从真正的Win 10机编程。然后，不管怎样，我不做生产编程，构建室直接把它直接移植到嵌存的内存芯片上（（这个客户和他们几十年的IP）。他们负担不起新IP。所有的IP都是旧的，在固件和主机PC上。原来的DEV计算机已经很长时间了，所以我已经采取了VM策略。我想有一个虚拟机来编译他们所有的软件和固件。对于在没有调试的现场硬件中可以测试的微小变化来说，这是很好的。我很少需要实时调试，因为这只是为了更大的变化。但目前我有这个需求。如果我必须这么做，我想我的MPLAB + HETECH安装方法将在我的真正的计算机上工作，就目前而言。我只是不想在这台电脑死后10年内再做一次，还有新的OS和不存在的驱动程序。）（非常感谢）赫尔穆特



      以下为原文

    Thanks, @KTrenholm.  I forgot about the switch.  I switched it, but that didn't help.
 
Thanks, @dan1138 and @qyb.  Please note that I am trying BOTH my WinXP VM as well as my Win10 physical machine.  They both *seem* to exhibit the same problem.  That is, the ICD 3 menu option is grayed out.
 
I will investigate the ICD 3 support during install question.  I don't think I have a pickit2, but my client who owns this IP or the build house with whom we have a long relationship might.
 
HOWEVER, PLEASE ALLOW ME TO JUMP TO THE END GAME:  I can indeed recompile now on the VM, as mentioned in the other post that @qyb pointed out.  Now, the change I need to make is complicated enough that I need to REAL TIME DEBUG.  Note that I designed this stuff EONS ago, and have forgotten half of what I ever knew.  This particular product uses a PIC18C601 with an external memory chip.  QUESTION: Will I be able to real time debug with MPLAB 8 and the ICD 3?  I think this means I need to both program and (is it JTAG?) control the processor.  The programming must go *through* the processor to the external memory.  I *must* have been doing this before, a long time ago.  I just don't remember.
 
If I can't get the ICD 3 working, the build house has my old ICD 2 and I could try it.  Either the customer or the build house might have a pickit2.
 
Finally, just for production, as long as I can build the hex file, if I can never get any programmer/debugger working form the VM, at least I can still program from a real Win10 machine.  And then, I don't do production programming anyway, the build house does that directly to the socketed memory chip.
 
(((Darn this customer and their decades old IP.  They can't afford new IP.  All there IP is old, on both firmware and host PC.  The original dev computers are long dead, so I've taken up the VM strategy.  I want to have one VM to compile all their software and firmware.  That's fine for minor changes that can be tested in live hardware without debugging.  I should rarely have a need for real-time debugging, because that's only for bigger changes.  But I have that need at the moment.  If I have to, I think my install method for MPLAB+HITECH will work on my real computer, just for now.  I just don't want to have to do it all again in 10 years after this computer dies, and new OS with drivers that don't exist.)))
 
Thanks VERY much,
Helmut

PIC18C601需要一个ICE2000或更旧的调试。它是一个基于EPROM的PIC，而不是Flash。它与ICD3兼容吗？那也许是你的灰色。做一个新的测试项目，选择一个新的PIC，看看这是否有助于灰色。



      以下为原文

    PIC18C601  You would need an ICE2000, or older to debug that.  It is an EPROM based PIC, not Flash. Is it compatible with the ICD3?  That maybe your Gray.  Make a New Test project and select a Newer PIC, see if that helps the Gray.

啊哈，你可能是对的，ICD3不支持PIC18C601。我可以去检查支持的名单。但是，我刚刚和我的客户谈了很久。没有关系！调试调试程序的投资太高。无论如何，这个遗留产品的剩余寿命有限。我们将以旧的方式来做：（a）在我的状态下，我仔细地进行源代码更改，然后（b）他使用半生产来重新编程，然后测试他的状态下的行为。它不会像实时调试那样快，但这对他的四个改变需求来说是可以的。对于更困难的变革需求，我必须非常明智地选择跟踪输出来找出问题所在。换句话说，回到那些我们甚至没有源码调试的超级旧时代。（我猜我们几乎总是有汇编代码调试。我不记得40年前有什么不同。也许我们之前没有汇编代码调试。无论如何，谢谢赫尔穆特。



      以下为原文

    Ah ha, you might be right that ICD3 doesn't support PIC18C601.  I could go check the supported list.
 
HOWEVER, I just had a long talk with my customer.  NEVERMIND!  The investment in getting programming for debugging going is too high.  This legacy product does have a limited remaining lifetime, anyway.  We will do it the old way of (A) I make careful sourcecode changes in my state, then (B) he uses semi-production to reprogram and then tests behavior in his state.  It won't be as fast as real time debugging, but that will be OK for two of his four change needs.  For the more difficult change needs, I'll just have to be very judicious in picking trace outputs to figure out what's up.  In other words, back to the super old days where we didn't even have source code debugging.  (I guess we almost always had assembly code debugging.  I don't remember anything different going back 40 years.  Maybe we didn't have assembly code debugging before that.)
 
Thanks anyway,
Helmut

如果没有窗口部分，则需要一堆OTP部件。我认为他们不再制造窗户零件了。



      以下为原文

    If you do not have a windowed part you will need a pile of OTP parts.
I do not think they make window parts anymore.

18C601是ROMLASE——它需要外部存储器来存储代码。



      以下为原文

    18c601 is romless - it requires external memory to store code.

外部存储器？那是在我拍照片之前，我不知道拍了什么。



      以下为原文

   
external memory ?
That is before my time with PICs.
I did not know the made any.
 
 

在深入了解了这一点后，我发现PIC18C601有一个演示板，DM16300 6- PicDEM 18R。它附带的软件在微芯片网站上仍然可用。它也似乎支持D16166继续到MPLAB V810版本，并可能仍然在V892版本，没有看到。底线是只有ICD2曾经有ICSP支持这些无罗盘PIC18C设备。这种支持要求用户提供ICD2调试会话的功能来读取和写入PIC18C设备的外部存储器。结论是MPLAB V8XXX IDE和ICD2是支持PIC18C601目标的调试的唯一工具。没有其他工具能起作用。



      以下为原文

    After looking in to this a bit deeper I have found that the PIC18C601 had a demo board, DM163006 - PICDEM 18R. The software that it comes with is still available on the Microchip web site. It also appears that support for the DM163006 continued up to the MPLAB v8.10 release and may still be in the v8.92 release, have not looked.

The bottom line is that only the ICD2 has ever had ICSP support for these ROMless PIC18C devices. This support requires the user to provided functions for the ICD2 debug session to read and write the external memory of the PIC18C device.

The conclusion is that the MPLAB v8.xx IDE and the ICD2 are the only tools that supported debug for the PIC18C601 target. No other tools will work.

它仍然在那里，在992年，绿色灯的“亲二”，“PM3”和“ICD 2”程序员。



      以下为原文

   
It's still there in 8.92.
That has green lights for the "PRO MATE II", "PM3", and "ICD 2" programmers.