不能从MPLAB 5, 6, 7迁移到8版本

也许这对你来说很有趣：HTTP://MyCHIPCDeave/COM/MPLABX：工作在外部。



      以下为原文

    Maybe this is interesting to you http://microchipdeveloper.com/mplabx:work-outside

当你关闭“广告”的起始页面，不要使用配置器和和声，你会看到你不喜欢的东西吗？如果你想保持清醒，就可以使用CCS编译器的廉价版本，偶尔使用它，看看PIC编译器从技术角度写的是什么。我不认为CCS会填充You-Bill，并支持像Microchip这样的绝对最新的设备。



      以下为原文

     
After you close 'AD' start page and don't use Configuritor and Harmony what do
 
you see you don't like?
 
If you want to keep your sanity get a cheap version of CCS C Compiler and use it occasionally and
 
see what a PIC compiler written from a technical viewpoint is like.
 
I don't think CCS will fill yur bill and support absolutely positively latest devices like Microchip.

我很理解原始海报的挫折感。我终于完成了从MPLAB 8到MPLAB X的转换，这样我就可以用同样的方便，或者同时调试2个设备之间的通信。我仍然觉得它需要更多的挫败感。使用MPLAX X，开始使用MPLAB 8。我认为MPLAB X正在慢慢地变得更好。在我看来，MPLAB 8中的监视窗口仍然比X好，尽管MPLAB X在CPU寄存器中更好地遵循以下变量，但是与8位D无关。不管怎么说。迈西尔



      以下为原文

    I quite understand the frustration of the original poster.
 
I finally have made the transition from MPLAB 8 to MPLAB X,
such that I am able to use either with the same ease,
or both at the same time, to debug communication between 2 devices.
 
I still have the impression that it took more frustration and hairpulling to get into MPLAB X, 
than initially getting to use MPLAB 8.
I think MPLAB X is slowly getting better.
 
In my opinion, Watch window(s) in MPLAB 8 is still better than in X,
although MPLAB X is better at following variables that are located in CPU registers,
but that may not matter with 8 bit devices anyway.
 
   Mysil

我喜欢MPLABX比旧的多；-究竟什么是困难的？（我喜欢X比旧的多；）&编辑。好吧，看来你在汇编代码-我喜欢X的很多东西都不在那里工作。



      以下为原文

    I like MPLABX more than old one ;-)
What exactly is difficult?
(I like X more than the old one ;-)
 

OK, seems you are coding in assembly - many of the things that I like in X are not working there

MPLABX速度较慢，稳定性较差。-偶尔在手表上有错误的值。-不管调试器意味着什么，都会中断与调试器的通信。-将读取和编程分离为IPE。这迫使你使用快速编程、调试引导加载程序和设置EEPROM或Flash来测试值。-永恒的红色曲线线问题。-周期性高速缓存损坏，您仍然需要手动修复。-需要安装多个版本，以确定新版本是否比旧版本工作得更糟。双击跳转到一个定义是伟大的，当它工作。是的，它有许多漂亮和现代的改进。但它是一种生产力工具。它的工作是提高生产力。这是多次失败的惨败。它正在改进吗？很难说什么时候新版本比以前更糟糕。而新的特点则是错误和缓慢。老虫子溃烂了。在未能将调试会话保持到单个断点之后，在十次尝试中执行一次以上。如果在调试会话中犯了编辑代码的错误，必须重新启动MPLABX。我决定应该使用Prtff（）来调试我认为是坏的外部外围设备，但是其他时候它工作得很好。是的，我很抱歉，我没有回到MPLAB8来完成我的最后一个PIC16引导加载程序。这会节省一些时间。



      以下为原文

    MPLabX is
-Slower
-Less stable.
-Occasionally has the wrong value in the watches.
-Loses communication with the debugger constantly , whatever that means.
-Separated the read and Programing to IPE. That force you to use with allpications for quick Programing,debugging bootloader,and setting the eeprom or flash to test values.
- the eternal red squiggly line issue.
- the periodic cache corruption, that you still need to fix manually.
- the need to keep several versions installed to try to figure out if the new version is working worse than an old one.
- the double click to jump to a definition is great , when it works.

Yes it has many nice and modern Improvments. But it is a productivity tool. Its job is to increase productivity. There it is an abject failure at many times. Is it improving? It is hard to tell when new version often work worse than previous ones. And new features cuase crippling bug and slowness. While old bugs fester.

After it failing to maintain a debug session to a single breakpoint do more than one out of ten tries. And having to restart MPLabX if I committed the sin of editing code during a debug session. I decide that I should try to use printf() to debug what I think is a bad external peripheral.
But other times it works fine.
I
And yes I sorry I did not go back to mplab8 to finish my last pic16 bootloader. It would have saved some time.

我不明白为什么MPLAX X会有这么多的仇恨，我认为它与MPLAB8相比很棒，而且我没有任何问题。也许是时候升级你的电脑，如果它运行缓慢。



      以下为原文

    I don't get why MPLAB X gets so much hate, I think it's great compared to MPLAB8 and I haven't had any issue. Maybe it's time to upgrade your PC if it runs slow.

PC不慢，MPLAX X仍处于beta版本。



      以下为原文

    PC not slow, MPLab X is still in beta version.

也不接受回车键作为对话框的确认，是不好的。这比缓慢更糟糕；



      以下为原文

    Also not accepting Enter key as a confirmation of a dialog box, is not nice. And this is even worse than slowness ;)

我仍然没有得到“MPLAB X是那么慢”的东西…



      以下为原文

    I still don't get the "MPLAB X IS SO SLOW" thing...

与旧IDE相比，它在某些方面绝对慢一些。构建，编程芯片…需要花费更多的时间。没有人考虑到由于新特性而获得的速度优势。（代码中的导航，调用图，查找用法……）



      以下为原文

   
Compared to the old IDE it is definitely slower in some things. Build, program the chip... takes much more time.
No one takes into account the speed advantage you get because of new features.
(Navigation in code, call graph, find usage.... )

当新的特性工作时，它们会起作用。但它们并不总是有效的。我担心的是，如果一个产品是旧的仍然是马车和不稳定，它会是什么？新的特性需要大量的RAM和CPU电源。移动存储器读/写/程序只是简单的懒惰。没有人使用它的合理化是自私的。他们做了我错过的民意调查吗？事实上，版本3到3.10不能打开堆栈，并且经常报告手表的错误值，这仍然让我警惕。9个月来修复基本特征，同时添加新的bug。他们在追逐什么产品？我有一个i7，8个游戏，16或32帮助？PIC16比PIC 32更好，我知道这个项目更大，但是它并不是ARM和微软视觉产品的问题。是的。但它是脆弱的。并不能加快发展。这只是生活的目的。它是有用的，但这不是一个响亮的背书。



      以下为原文

    When the new features work they help. But they don't always work. My concern is that if a product that is this old is still buggy and unstable will it ever be? The new features apperently require a lot of RAM and CPU power. The moving the memory read/ write/ program was just plain lazy. The posted rationalzation that no one uses it is self serving. Did they do a poll I missed?
The fact the versions 3.00 to 3.10 could not unroll the stack and often reported incorrect values for watches still makes me wary. 9 month to fix base features while adding new features with new bugs. What product are they chasing?
I have an i7 with 8 gigs , would 16 or 32 help?
It is better on pic16 than pic 32 yes I understand the project is bigger, but it does not appear to be an issue with ARM and Microsoft Visual products.

Yes it works. But it is weak. And does not speed up development. It's only purpose in life. It usable, but that's not a ringing endorsement.

作为一个业余爱好者，我已经接受了我必须生活在输出窗口中的红色墨水消息。在我的旧PC Wi7 PC和只有4G RAM，我不认为MPLABX慢（回到3.50），（我关闭网络）。我发现手表窗口有问题，也有断点和“建立调试，然后运行设置”。我更喜欢“停止在主”，我已经贴上了便笺，提醒我“停止”调试之前，我触摸KB…似乎减少了“PK3卸载繁忙的时候…”胡说八道



      以下为原文

    Just as a hobbyist, I have accepted I have to live with the red ink messages in the output window. On my old pc win7 PC and only 4G ram I don't consider MPLABX slow (went back to 3.50), ( I turn off the network ). I have found the watch window has issues, also the break points and 'build debug then run setting'. I prefer to be 'halt at main'   And I have put up sticky notes up to remind me to 'Halt' the debug before I touch the KB...seems to reduce the "PK3 unloaded while busy ..." nonsense    

现在，一切都需要大量的RAM，看看所有新的智能手机和App.MPLAB X并不完美，但地狱每个程序员有时都有bug：P无论如何，我有一个很好的经验与X



      以下为原文

    Well, nowadays everything requires huge amounts of RAM, look at all the new smartphones and APPs.
 
MPLAB X is not perfect, but hell every programmer has bugs sometimes :P anyways I've had a very good experience with X

但是，MPLAX X需要异常大的内存量和CPU时间，异常缓慢，而且异常不稳定。与它的任务相比，与任何其他（正常）IDE相比。刚才发生了：MPLAB xV3.60运行，项目打开，但没有调试，没有活动很长时间。R台，但是我听说CPU风扇开始高速旋转一段时间。我启动任务管理器。JavaW.EXE不断消耗25%的CPU时间。为什么？他到底在干什么？在我使用MPLAB X的两个实例之前几天，我击落了一个，但是几分钟后，我发现在任务管理器中仍然有两个JavaW.exe实例，它们都消耗了大量的内存和CPU时间。850 MByte，“活着的一个”消耗了CCA，1，1字节，我没有长时间地触摸键盘，没有调试，只有待机，而且需要1，95字节。这是不正常的。这是无法解释的。为了开发一个200 KB的微控制器程序，我想问一下美国宇航局的超级计算机。



      以下为原文

   

But, the MPLAB X requires abnormally huge amount of memory and CPU time,
abnormally slow, and abnormally instable. 
Compared to it's task, and compared to any other (normal) IDE.

Just now happened: MPLAB X v3.60 runs, project open, but no debug, nothing activity for long minutes.
I am soldering at another desk, but I hear, the CPU fan begin to spin on higher speed for a while.
I start the task manager. javaw.exe consumes 25% CPU time constantly. Why? What the hell is it doing?


Few days before I used two instance of MPLAB X. Later I shot down one, but minutes later I saw,
in the task manager, still there are two javaw.exe instances,
and both of them consumes lot of memory and CPU time. 
The "dead" exe consumed cca. 850 MByte, the "living one" consumed cca 1,1 GBytes. 
I did not touched the keyboard for long time, no debug, only standby.
And it is require 1,95 GBytes. It is abnormal. This can not be explained.
To develop a 200kB microcontroller program, I would ask a supercomputer from NASA?

lt；3



      以下为原文

    <3

我发现，MPLABX在运行时间越长，速度越慢，有时甚至变得不可用。这个问题在很大程度上影响编辑器，这样当我编辑一行并点击“输入”时，在添加或编辑另一行之前，会延迟几到几秒钟。如果我关闭应用程序（这也需要相当长的时间），然后重新打开它（这也很慢），相同的编辑和其他功能正常工作，几乎没有明显的延迟。我认为它与Java内存管理和垃圾收集有关。我注意到，在做其他事情之后，将焦点设置在MPLABX应用程序上的时间相当长，主要是“扫描外部更改”。一些问题可能与我的计算机有关，这是ALMO。ST 4岁，运行Windows 8。我有一台Win 10的机器，但是我拒绝了安装和微调我在这台机器上的许多应用的艰巨任务，尽管我没有很多可用。



      以下为原文

    I have found that MPLABX gets progressively slower the longer it runs, sometimes to the point of unusability. The problem affects the editor to a large degree, such that when I edit a line and hit "Enter", there is a delay of several to many seconds before another line can be added or edited. If I close the application (which also takes considerable time), and then re-open it (which is also slow), the same edits and other functions work "normally", with almost no noticeable delay. I think it has to do with Java memory management and garbage collection.
 
Another thing I noticed is that there is considerable delay when setting focus on the MPLABX application after doing other things - mostly "scanning for external changes".
 
Some issues may be related to my computer, which is almost 4 years old and running Windows 8. I have a Win10 machine but I am resisting the Herculean task of installing and fine-tuning the many applications I have on this machine, although I can get by without many of them.

u应该尝试SSD或PCIe NVME（这就是我使用的）。我的MPLAB X（V3.60）在空闲时@为1%-1181MB RAM。说到神秘的RAM使用，我的WI10系统在空闲时使用5.3GB，这是疯狂的，但我仍然有58GB可用：PU不需要NASA计算机，但你必须知道你的计算机的速度和限制。我不知道经验是否改进了IDE内存中的IDE内存。Ile。



      以下为原文

    U guys should try an SSD or a PCIe NVMe (which is what I use).
 
My MPLAB X (v3.60) does 0-1% when idling @1181MB ram. And speaking of mysterious RAM usage, my win10 system uses 5.3GB when idle, which is crazy, but still I've got 58GB available :P
 
You don't need a NASA computer, but you have to be aware of your computer's speed and limits.
 
I don't know if experience improves changing the ide memory inside the .conf file.
 

或者你可以使用旧的程序，这些程序不仅运行得快得多（有些闪电快），而且还有更少的bug。这就是我所做的。对于所有的新玩意儿，我有一个Windows 8-1系统，其中MPLAX X可以与Vivado在“谁是较慢的开始”比赛中摩擦。不打扰我很多，因为我的主要活动是在我的Windows 7 PC。



      以下为原文

   
 
Or you can use older programs, which not only run much faster (some of them lightning fast), but also have much less bugs. That's what I do.
 
For all the new stuff, I have a Windows 8.1 system where MPLAB X can rub shoulders with Vivado in the "who's slower to start" contest. Doesn't bother me much because my main activity is on my Windows 7 PC.
 

或者有一台快速的电脑，运行新的和现代的程序闪电般快我的情况。哦，顺便说一下，摆脱Win8



      以下为原文

    Or have a fast computer and run new and modern programs lightning fast like my case. Oh, and BTW get rid of win8