模拟器速度

如果您在Linux环境中没有运行MPLABX模拟器，请检查您是否可以尝试。在我的经验中，MPLABX模拟器在Windows环境下与在相同的工作站上模拟相同代码的MPLAB V892模拟器相比非常慢。这很可能是M的结果。ICROCAMP重写MPLABX仿真工具。谣言是制造仿真工具MPLAB V892的工程师离开MPLABX项目之前的公司，而仿真工具组不想在没有创建者支持的情况下承担威廉希尔官方网站 债务。



      以下为原文

    If you are not running the MPLABX simulator in a Linux environment check out if you can try that.
 
In my experience the MPLABX simulator very slow in the Windows environment when compared to the MPLAB v8.92 simulator on the same workstation simulating the same code.
 
This is most likely the result of Microchip rewriting the simulation tools for MPLABX. The rumor is that the engineer that created the simulation tools MPLAB v8.92 left the company before the MPLABX project and the simulation tools group did not want to take on the technical debt without support from the creator.

丹，谢谢你的建议和信息。我的AWS实例目前已经运行Ubuntu 16.04，而我的个人机器正在运行MACOS（SIM对两者都很慢）。



      以下为原文

    Dan, thanks for the suggestion and info. My AWS instance is currently running Ubuntu 16.04 already, and my personal machine is running MacOS (sim is pretty slow on both of them).

你总是可以得到更大的处理器和更快的内存。然而，硬件进展并不是那么快，无法跟上正在进行的软件膨胀。



      以下为原文

    You always can get bigger processor and faster memory. However, hardware progress is not that fast anymore and cannot keep up with the ongoing software bloat.

在我看来，MPLABx是一个倒退。它在任何事情上都是如此的。在MPLB8上如此有用和快速的仿真器现在实际上是无用的。X花了大约30秒来跨过一个NOP（）；（这是没有任何监视窗口或活动的表，是的，多核进程被激活）。模拟痛苦，实际上是无用的。用真正的冰，加载调试代码是缓慢的，超越功能是徒步的。总之，我认为它至少花费我5倍的时间来开发PIC的代码。我已经用MPLBX工作了好几年，我随时都可以。回到MPLAB8，为了发展的速度。不幸的是，我能够越来越少，因为我们正在使用一些新的图片，MPLAB8没有支持。我也开发了使用Atmel SAMs的项目。Atmel Studio 7是一个极好的IDE。我只希望Microchip不要放弃它，因为它是一个臃肿的怪物，是的，在X中有一些不错的特性，但是对我来说，速度就是王者。



      以下为原文

    In my opinion, MPLABx is a step backwards.
It is so S-L-O-W at everything.
The simulator, that was so useful and fast on MPLB8, is now virtually useless.
X takes about 30 seconds to step over a NOP();
(And that is without any watch windows or active watches, and yes, multi - core processes is enabled).
Simulating  so painful, it is virtually useless.
With Real Ice, Loading the debug code is slow, stepping over functions is pedestrian.
All in all, i recon it is taking me at least 5x longer to develop code for PIC's.
I have been working with MPLBx for a couple of years now, and i whenever i can i port back to MPLAB8, for speed of development.
Unfortunately, i am able to this less and less, as we are working with some of the newer pics that mplab8 has no support.
I have also developed projects using ATMEL Sams.
Atemel Studio 7 is a superb IDE.. I just hope that Microchip  dont abandon this in favour of the netbeans IDE which is a bloated monster.
Yes, there are a couple of nice feature in X - but to me, speed is king.

通常病毒检查是罪魁祸首。但你不是在开窗户，所以我怀疑这是个问题。我们通常从Windows机器上的模拟器中得到1-2 MIPS。你可以切换到更高频率的真实硬件，但是有一个折衷的编程和连接时间，你没有经验的模拟器。需要多少指令，你需要运行来执行您的测试？



      以下为原文

    Normally virus checkers are the culprit.  But you're not running windows, so I doubt that is the issue.  We typically get 1-2 MIPS out of the simulator on our Windows machines.  You could switch to running real hardware at a higher frequency, but there is a trade off for programming and connect time that you don't experience with the simulator .
 
How many instructions are you needing to run to execute your tests?

乔治，我们希望通过模拟器实现接近实时的速度，我们在30 MIPS的生产中运行我们的PIC。幸运的是，我在Linux机器上碰到了4 MIPS，速度不够快。如果我能达到25 MIPS，这可能是足够的，但我明白，可能有限制模拟器的速度可以运行；请让我知道如果你认为我的期望是不合理的。



      以下为原文

    George, 
We were hoping to achieve near real-time speeds with the simulator, and we run our PIC at 30 MIPS in production. When lucky, I've been hitting ~4 MIPS on my linux machine, which isn't fast enough. If I could reach ~25 MIPS that'd probably be sufficient, but I understand that there may be limitations for how fast the simulator can run; please let me know if you think my expectation is unreasonable. 

听到你得到4个MIPS，我感到震惊和高兴！我不认为你可以实际地期望更快。我想知道如果你不能通过MdB而不是MPLAB X来运行模拟器的速度更快。MDB是命令行调试器（用MPLAB X来运行）。您将运行相同的模拟器，但没有所有的NETBeas开销。



      以下为原文

    I am shocked, and elated, to hear that you are getting 4 MIPS!  I don't think you can realistically expect any faster.
 
I do wonder if you might not get some faster speed running the simulator through MDB instead of MPLAB X.  MDB is a command line debugger (that ships with MPLAB X).  You'll run the same simulator, but without all the NetBeans overhead.