pix-elated和失真），并且一些项目不旋转。有没有关于这方面的工作？在Harmony屏幕编辑器中，它看起来是正确的，但是一旦在屏幕上绘制，它看起来就非常奇怪（如果屏幕正常地绘制而不旋转，则看起来很好
2020-04-03 10:56
大家好，我一直在模拟MPLABX模拟器上的PIC24大约一个月，并且已经取得了很大的进步！（检查一下ZIPCAR GITHUB，如果你想看看我一直在做的开源软件：）不幸的是，模拟器的速度使我的开发速度相当缓慢。我在AWS上运行C4.xBug的模拟器，并且仅用新的Relic报告了大约70%的CPU使用最大值。有什么方法可以给MPLABX一个小推* *，所以它试图拉更多的系统资源，以提高我的模拟器速度？如果需要的话，我可以把我的例子扩展成更丰富的东西，但是当模拟器不想使用更多的资源时，我不知道该去哪里。 以上来自于百度翻译 以下为原文 Hi all, I've been working on simulating a PIC24 in the MPLABX simulator for about a month, and have been making great progress! (Check out the Zipcar Github if you want to take a look at the open source stuff I've been working on wink: ) Unfortunately, the speed of the simulator has been causing my development to slow pretty significantly. I'm running the simulator on a c4.xlarge in AWS, and have only been hitting around 70% CPU usage max, as reported by New Relic. Is there any way I can give MPLABX a little *push* so it tries to pull more system resources, in order to increase my simulator speed? I can scale up my instance to something more beefy if need be, but seeing as the simulator isn't trying to use more resources, I'm not sure where to turn.
2018-09-06 16:23
[到] GeorgePauley，错误的模拟器指令循环，3月9日我打开了案例00282543，Mel回应了我的请求，似乎他没有足够的经验来帮助。请看看你能帮他什么忙。工具：MPLABX V4.05XC8 V1.45 WORDOWS7 X64目标设备：PIC18F2520在DM164130-3，28引脚LIN演示板。模拟指令循环计数与实际目标硬件中执行的指令周期数目不匹配。附上的项目可以用来查看差异。示例应用程序的描述：本应用程序的目的是在16位模式中使用Time0来断言每隔2000个指令周期中断一次。Time1用于计算中断之间的指令周期。Time0通过中断服务程序重新加载。Time0再装入值被调整为写入Time0计数寄存器的结果所发生的未计数的指令周期，使得下一个Time0中断在当前中断之后完全不漂移地断言2000个指令周期。这意味着在任何数量的Time0中断下累积计数误差总是小于±2计数。不管该实现是否正确，模拟中的计数与实际硬件的计数不匹配。你能解释为什么模拟和真实硬件的计数不匹配吗？注意，MPLAB V892模拟器正确地计数指令周期。谢谢，CEA。18F2520xSimulasBug x.Zip（83.81 KB）-下载51次 以上来自于百度翻译 以下为原文 [TO]GeorgePauley, Wrong simulator instruction cycle countOn March 9 I opened case 00282543 and Mel has responded to my request it seems he may not have enough experience to help.Please see if there is any thing you could do to help him.Tools:MPLABX v4.05XC8 v1.45Windows7 x64Target device: PIC18F2520 in the DM164130-3, 28 Pin LIN Demo Board.Simulated instruction cycle count does not match the number of instruction cycles executed in the real target hardware.Attached projects can be used to see the difference.Description of the sample application:The purpose of this application is to use TIMER0 in 16-bit mode to assert an interrupt every 2000 instruction cycles. TIMER1 is used to count the instruction cycles between interrupts. TIMER0 is reloaded by the interrupt service routine. The TIMER0 reload value is adjusted for the uncounted instruction cycles that occur as a result of writing the TIMER0 count register such that the next TIMER0 interrupt asserts exactly 2000 instruction cycles after the current interrupt without drifting. This means that the accumulated count error over any number of TIMER0 interrupts is always less than ±2 counts. Regardless of whether this implementation is correct or not the count from the simulation does not match the count from the real hardware.Can you explain why the counts from the simulation and real hardware do not match?Note that the MPLAB v8.92 simulator counts the instruction cycles correctly.Thanks,cea. Attachment(s)18F2520_SimulatorBug.8.zip (94.09 KB) - downloaded 47 times18F2520_SimulatorBug.X.zip (83.81 KB) - downloaded 51 times
2018-10-24 16:51
