mplabx 3.61挂起

事实上，我没有试过1.43次。你知道它是否解决了这个问题？



      以下为原文

    Actually, No I haven't tried 1.43.  Do you know if it fixes this issue?
 
 

现在我开始尝试IDE中的其他特性，我认为这可能是IDE问题。



      以下为原文

    Now that I'm starting to try other features in the IDE, I think it might be an IDE issue.

我也注意到了这一点。我的房子挂起来了。我可以取消它，然后启动另一个，第二个构建完成。在构建（s）之后，我关闭MPLAB X IDE，Windows任务管理器显示了每个FixEddix.EXE和Windows命令处理器任务的一些杂散实例。我使用XC32版本1.43.DICK



      以下为原文

    I've noticed this too.  My build hangs.  I can cancel it and start another and that second build completes. After build(s) are done and I shut down MPLAB X IDE, Windows Task Manager shows a few stray instances of fixdeps.exe and a Windows Command Processor task for each.  
 
I'm using XC32 version 1.43.
 
Dick

“我还注意到，当退出IDE并试图重命名项目中的源文件时，Windows抱怨一个文件被另一个应用程序使用的错误。”类似的，如果我在项目窗口中重命名一个文件，所有的工作都很好，当我重新启动MPLAB X时，文件将不复存在。在项目窗口中，我必须添加文件，这可能会导致更多的问题。我发现，如果在编译之前重命名文件，它在下一次重新命名时出现。从第1天开始移动。这是个噩梦。我花了一段时间才把它拿回来，当我做的时候，我所有的书签都不见了。有时候MPLAB X决定不正确启动，我的XC16-GCC.附加选项STD= GNU99变成空白。是的，你使用得越多，你发现的微芯片就越难修复。包括所有的位，硬件寄存器）[ItNCO2BIT]。In0EP＝1；[IEC0BIT]。It00IE＝1；[IPC0BIT]。



      以下为原文

    "I've also noticed that when exiting the IDE and trying to rename a source file in the project, windows complains with an error that the file is being used by another application."
 
Similar, if I rename a file in the project window, everything works fine, when I restart MPLab X, the file will not be in the project window so I have to add files and that can cause more problems.
 
I discovered that if I rename a file before a compile it does appear on next restart.
 
rename, move have been broken from day 1.
 
The otherday I renamed main.c to slave_main.c and main.c to master_main.c
I had two files opened from separate projects.
 
What a nightmare.
Took a while to get it back and when I did, all my bookmarks had gone.
 
Sometimes MPLab X decides not to start properly and my xc16-gcc.addtional options
-std=gnu99 becomes blank.
 
Yeah, the more you use it, the more bugs you find that Microchip refuse to fix.
(Including everything with bits, hardware registers)
[INTCON2bits].INT0EP=1;
[IEC0bits].INT0IE=1;
[IPC0bits].INT0IP=7;
[printf]
 
[] = all highlighted in red with white text.

随着我对3.61版本的熟悉，我也有你们描述的相同问题。有没有最后一个稳定版本你可以推荐？我不介意向后评分。



      以下为原文

    As I'm getting more familiar with the 3.61 release, I'm having the same issues you guys are describing.  Is there a last stable version you guys can recommend?  I don't mind down grading backwards.

我认为不会有一个稳定的版本。



      以下为原文

    I don't think there will ever be a stable version.

我为此挣扎了几天。我已经尝试改变MPLAB X IDE版本（3.55，3.61）和编译器版本XC32 1.42和1.43。所有人都有不完整的构建问题，在大多数或所有文件被编译后挂起，任务管理器显示了几个FixDeP实例和几个被丢弃的Windows命令处理器实例。在同一个项目的笔记本电脑上，我没有这个问题。然后把所有的东西都移动到一个目录中，这并不能解决这个问题。但是我现在关闭了“并行制作”（工具-选项-嵌入式-项目选项）。我有一个4内核的机器，MPLAB X使用的是make -J 16，因为我显然有8个内核。但现在每个时间都在完成。



      以下为原文

    I struggled a few days with this.  I've tried changing MPLAB X IDE versions (3.55, 3.61) and compiler versions XC32 1.42 and 1.43.  All had the problem of incomplete builds, hanging after most or all files were compiled, task manager shows several instances of fixdeps and several windows command processor instances that were abandoned.
 
I don't have this problem on a laptop with the same project.
 
I had somesource files in a subdirectory and moved everything into one directory, that didn't resolve the issue.

But I have now turned off "parallel make" (Tools - Options - Embedded - Project options.  I have a 4-core machine, and MPLAB X was using make -j 16 because I evidently have 8 cores.
 
Build takes a lot longer now, a couple of minutes.  But it's completing every time now.
 
Dick
 
 

V3.15是非常稳定的，但它现在是旧的。V3.51似乎与和谐工作。1.11V3.55与一个大型PIC32 MZ项目不能很好地工作。但是PIC16就可以了



      以下为原文

    V3.15 was very stable, but it is old now.
V3.51 seems to work OK with Harmony 1.11. 
V3.55 Does not work well with a big PIC32MZ project.  But is OK for PIC16
 

似乎不太令人鼓舞，因为我使用和谐2.03B与一个大型PIC32 MZ2048 EFG064项目。如果支持我使用的设备，我会考虑回到3.15。



      以下为原文

    Doesn't seem too encouraging since I'm using harmony 2.03b with a large PIC32MZ2048EFG064 project.   I'd consider going back down to 3.15 if the device I'm using is supported. 

我一直在使用3.45没有任何问题，虽然我似乎记得其他人有问题。



      以下为原文

    I've been using 3.45 with no problems, although I seem to remember other folk had issues with it.

“但现在我关闭了“并行制造”（工具-选项-嵌入式-项目选项）。我有一个4内核的机器，MPLAB X使用的是make -J 16，因为我显然有8个内核。”- DickDI特立独行关闭“并行制作”，它对我也起作用。谢谢你的建议，DickD，似乎已经解决了这个问题。



      以下为原文

    "But I have now turned off "parallel make" (Tools - Options - Embedded - Project options.  I have a 4-core machine, and MPLAB X was using make -j 16 because I evidently have 8 cores." -DickD
 
I tried turning off "parallel make"  and it worked for me also.  Thanks for the suggestion DickD, it seems to have fixed this problem. 

FWWI发现，在将MPLAB X从WINXP移动到一个相当老的（SUSER 12.1）Linux上时，在相同的双引导框中，它从几乎无用的东西变成了相当稳定的。甚至相同的源文件。这是3.4件，但现在已经3.61了，到目前为止还行，可怕的红色涂鸦现在看起来不那么流行了。它似乎仍在逐渐地自愈并慢下来，但是MPLAB停止和重新启动似乎已经清楚了，并且改变处理器（32 Mx＆lt；-gt；32 MZ）NED大量的ICD3 USB引线和推动：都有点业余，但实际上也不是一个巨大的问题。Guror完全是另一回事。常规抽搐，同时改变每种变化的MHCP样品代码。如果它是完整的100%和100%可靠的，它可能是值得一段时间，但据我看，它的一个很长的方式也不是。一个模糊的练习，可以通过它的小自我来创建不可编译的代码，这是没有帮助的。料仓作业。



      以下为原文

    FWIW I found that after moving MPLAB X from WinXP to a fairly old (Suse 12.1) Linux on the same dual boot box it went from pretty near useless to reasonably stable. Same source files even. That was 3.4something but now on 3.61 and still ok, so far, and the dreaded red graffiti seems much less prevalent now. It does still seem to gradually clag itself up and slow down after a while, but an MPLAB stop and restart seems to clear that, and changing processors (32MX <-> 32MZ)  neesd a lot of ICD3 USB lead pulling and pushing: all a bit amateurish but in practice neither is a huge problem.
 
Harmony configurator is quite another matter. Routine seizures while screwing up the MCHP sample code with every change. If it was 100% complete and 100%  reliable in what it did it might be worth some time, but as far as I can see its a very long way from being either. An exercise in obfuscation that can create unbuildable code all by its little self is not helpful. Bin job.