如何使用MPLABX和PM3验证器件？

他们删除了MPLabX的所有EPROM程序员特征，并将它们移到IPE。显然他们不理解井手的“我”是什么样子。你可以在MPlabX的IPE程序中做你想做的事情。



      以下为原文

    They removed all the Eprom Programmer features from MPLabX and moved them to IPE.
Apparently they do not understand what the 'I' stands fro in IDE.
You can do what you want in the IPE program included with MPlabX

因为重点是“D”和“P”代表什么！格林先生：说真的，客户对像IPE这样的工具有很多需求，这些工具有一个简单得多的用户界面（大概是低层编程技术人员）。因此，IPE诞生了。从IE中删除程序的功能似乎是有意义的，因为它们现在已经被IPE覆盖了。注意：我与这些决定无关，也不太在意。我只是在解释什么是推理。（我在走廊谈话中无意中听到的……）



      以下为原文

   


Because the focus is on what the 'D' and 'P' stand for!  mr green:
 
Seriously, there was a lot of demand from customers for a tool like IPE that had a substantially simpler user interface (presumably for low-level programming technicians).  Thus, IPE was born.  And it seemed to make sense to remove programming only features from the IDE as they were now covered in the IPE.

Note:  I had nothing to do with these decisions, and don't much care either way.  I'm just explaining what the reasoning was.  (As I overheard it in hallway conversations...)

我对IPE没有问题。我听到了关于MPLAB8从生产层使用有多困难的抱怨。我的问题是要运行两个程序，在它们之间来回切换来做IDE做了20年的事情。我记得DOS中编辑器、调试器和程序员之间的切换。我看到开发人员在从MPLABX中删除这些特性的零值仅仅是因为它们在另一个程序中可用。第一次IDE的人并不认为这是一个更好的解决方案。我猜测原因，是支持重复功能的成本。它当然不是帮助开发人员。



      以下为原文

    I do not have an issue with IPE. I have heard complaints about how hard Mplab8 was to use from the production floor. 
My Issue is having to run two programs, switching back an forth between them to do what IDEs did for 20 years.
I remember switching between Editor, Debugger,and Programmer in DOS.  I see zero value to Developers in removing the features from MPLabX just because they are available in another program.  The People that made the First IDE's did not think that was a better solution.
My guess on the reason, it was cost of supporting the duplicate features. It certainly was not to help developers.

一个像IPE这样的工具出现在MPLAB X之前。你还记得一个只使用MPLAB（非X）分布的编程工具“Visual PROMD”吗？IPE是Visual PROMD的继承者。



      以下为原文

   
 
A tool like IPE was present before MPLAB X. Do you remember a programming only tool called 'Visual PROCMD' distributed with MPLAB (non X)? IPE is the successor of Visual PROCMD.

“IDE”中没有“P”……（是的，我知道这是一个校园笑话的开始，关于P的去向），+ 1，从IDE中删除有用的功能是一个坏主意，仅仅因为它们在其他地方是可用的。



      以下为原文

   
There's no "P" in "IDE" ...
(Yes, I know that's the start of a schoolyard joke about where the "P" went ;) )
+1 for it being a bad idea to REMOVE useful features from the IDE, just because they are available elsewhere.

开发人员需要能够读写EEPROM，而开发程序有EEPROM。他们需要阅读，以确保它写（或写什么）。它们需要能够改变值来验证代码处理边缘条件。他们需要编写能够建立没有校准和配置软件的新部件，因为那些人在等你写固件。但是EES仍然需要测试，如果数据存储在Flash中也是如此。更是如此，因为Flash是更多的工作要使用。然后有引导加载程序。您需要从PIC中读取闪回，以查看引导加载程序是否工作，并查看它是否出错。这些能力在发展环境中不再是一体的。他们用什么来合理化他们想要做的事情就是理性化。它可能不影响所有的MPLABX用户。但它并不能帮助那些使用这些图片的人的生产力。



      以下为原文

    A Developer needs to be able to read and write to the EEPROM while developing Programs the Have EEPROM.
They need to read to be sure it wrote (or what it wrote).  They Need to be able to change values to verify the Code handles edge conditions.  They need to write to be able to set up new parts that do not have the calibration and configuration Software written, because those people are waiting for you to write them firmware.  But the EEs still need something to test with.
The same is true if the Data is stored in Flash.  Even more so since Flash is more work to use.
Then there are Bootloaders. You need to read the Flash back from the PIC to see if the Bootloader is working, and to see were it went wrong if it does not.  These ability is no longer Integrated in the Development Environment.
What ever reasons they used to Rationalize what they wanted to do are just that Rationalizations.  
It may not affect all MPlabX users.  But it does not help the Productivity of those that use those features of those PICs.

你仍然可以读取MPLAB X.的设备内存。



      以下为原文

    You can still read back the device memory from MPLAB X...
   Attached Image(s)

是的，你可以读回。但是你不能保存它或者编辑它。或者将它编程到不同的设备。MPLAB8在这方面更有用。



      以下为原文

    Yes you can read it back.  But then you can't save it or edit it. Or program it to a different device.  
MPLab8 was much more useful in this regard.