完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
我们使用MPLAB IDE 8.92和MPLAB X IDE 3.65与真正的ICE和ICD3程序员一起开发和生产。在使用IDES之间的程序员交换时，程序员的固件都需要更新。当使用IDE时，IDE会检测到错误的固件，并在程序员（真正的ICE或ICD3）上下载正确的版本。这很好，问题在于生产。生产不使用IDE来编程PICS。我们有脚本使用“程序实用程序”来编程PIC而不使用IDE。对于MPLAB IDE 8.92，“程序实用程序”可用ATC:程序文件（x86） Microchip MPLAB ID程序实用程序。我希望生产脚本在编程PIC之前下载程序员的正确固件。有人知道是否有相应的程序或“实用程序”T。o在没有使用IDE的情况下下载程序员的固件？谢谢。
以上来自于百度翻译 以下为原文 We use MPLAB IDE 8.92 and MPLAB X IDE 3.65 with Real ICE and ICD3 programmers for Development and Production. Both programmer's firmware needs to be updated when we use swap the programmer between IDEs. When using either IDE, the IDE detects the incorrect firmware and downloads the correct version on the programmer (Real ICE or ICD3). This is good. The problem is with Production. Production doesn't use the IDE to program the PICs. We have scripts that use the "Program Utilities" to program the PIC without using the IDE. For MPLAB IDE 8.92, "Program Utilities" are available at C:Program Files (x86)MicrochipMPLAB IDEProgram Utilities I would like the Production scripts to download the correct firmware on the programmer before programming the PIC. Does anyone know if there are corresponding programs or "Utilities" to download the firmware on the programmer without using the IDE? Thanks. B. 
0
|
|
相关推荐
12个回答
|
|
|
嗨，你需要MPLAB V8. xx和MPLAB X的原因是什么？MPLAB X包括MPLAB IPE，它可以处理任何HEX文件，甚至是最初由MPLAB V8XXX创建的文件。您应该真正停止使用MPLAB，这将消除您试图解决的问题…不管怎样，生产的一个更好的解决方案是使用像PM3这样的生产程序。需要任何PC。把你的十六进制文件放在SD卡上，然后选择一个你需要在生产过程中使用一个简单的GUI（LCD +按钮）问候。
以上来自于百度翻译 以下为原文 Hi, what is the reason that you need MPLAB v8 .xx and MPLAB X for production ?? MPLAB X includes MPLAB IPE which can handle any HEX file, even the ones originally created by MPLAB v8.xx. You should really stop using MPLAB, that would remove the issue you're trying to solve... A much better solution anyway for production is to use a production programmer like PM3 which does not need any PC. Put your hex files on an SD card and then select the one you need during production using a simple GUI (LCD + buttons) Regards |
|
|
|
|
|
使用PM3不是一种选择。我们没有PM3。我们已经集成了詹金斯在构建PIC代码，释放PIC代码，并生产推动神奇詹金斯按钮，以编程设备与PIC代码。整个过程是自动化的，比PM3更容易使用。所有这些都使用了IDE的引擎下的编译器、链接器、RealIceCMD（exe）和ICD3CMD.（EXE）。有一个控制台应用程序，可以在程序员上下载固件，或者这个特性集成在IDE里面吗？谢谢。
以上来自于百度翻译 以下为原文 Using PM3 isn't an option. We don't have a PM3. We've integrated Jenkinsin building PIC code, releasing the PIC code and having Production pushing a magic Jenkins button to program a device with PIC code. The entire process is automated and a lot easier to use than with the PM3. All of this using the compiler, linker, RealIceCMD.(exe) and ICD3CMD.(exe) that is under the hood of the IDE. Is there a console application that will download the firmware on the programmer or is this feature integrated inside the IDE? Thanks. B. |
|
|
|
|
|
你的问题是交换版本。将一个ICD3专用于生产编程，避免了问题，如果你想加载MPLAB8时代固件而不是使用MPLAB8。
以上来自于百度翻译 以下为原文 Your Problem is swapping aroung the Versions. Dedicate one ICD3 to production programming and avoid the Issue. If you want to load MPLab8 era Firmware than Use MPlab8. |
|
|
|
|
|
嗨，如果你想用MPLAB X来自动编程，那么使用MPLAB X SDK。有一个DLL可以通过API访问IDE上的动作。MPLAX SDK可以从这里自由下载：HTTP://www. opSunCE4PIC.Orgt/Copt/Copt/MPLAB-XSDK-MPLAB-X-IDReGARD
以上来自于百度翻译 以下为原文 Hi, If you want to automate the programming with MPLAB X then use MPLAB X SDK. There is a DLL which you can access through APIs to perform actions on the IDE. The MPLAB X SDK is freely downloadable from here : http://www.opensource4pic.org/content/content/mplab-x-sdk-mplab-x-ide Regards |
|
|
|
|
|
同样地，其他人都说过。在MPLABX中有一个命令行工具（IPECMD），它可以驱动Realice和ICD3。你应该能够改变所有的生产脚本来使用它，这样你就不必不断地更换驱动程序。如果需要的话，它会下载正确的固件。所有这些都假设MPLABX工具在你的设置上工作。对我来说，他们不在任何一台电脑上工作。
以上来自于百度翻译 以下为原文 Ditto to what everyone else has said. There is a command line tool (IPECMD) available in mplabx that'll drive both the realice and icd3. You should be able to change all your production scripts to use that and then you won't have to continually swap drivers. It'll download the correct firmware if it needs to. All of this assumes that the mplabx tools work on your setup. For me they don't work on any of the PC's we have. |
|
|
|
|
|
我以前有几个皮卡3装置。每个都有它自己的固件-例如从MPLAB X到PICIT3到PIC16，或者从MPLAB 8.92到PICT24到PIC24。我把它们都贴上标签，然后用正确的皮卡来做这项工作。这很好，让我避免了很多问题。
以上来自于百度翻译 以下为原文 I used to have several PICkit3 devices. Each had its own firmware - e.g. PICkit3 to program PIC16 from MPLAB X, or PICkit3 to program PIC24 from MPLAB 8.92. I labeled them all and just used the correct PICkit3 for the job. It worked great and allowed me to avoid lots of problems. |
|
|
|
|
|
我也在考虑每个部门都有一个程序员。这是一个很好的解决方案，尤其是在过程控制下。然而，无论使用什么部门的程序员，生产和研发都需要一个简单的按钮解决方案。当程序员失踪时，这一点很重要。这就是为什么我拥有詹金斯控制下的每个项目的PIC的实际编程。没有IDE，也没有学习PM3（特别是SD卡）。使用浏览器并点击这个。关于IPECMD实用程序的建议让我想到重新审视我如何编程PIC。对于MPLAB 8.9上的Realice，实用程序是RealICECD（.exe）。我又做了一个“？”关于应用程序和其中一个参数是“R<；文件>；报告”，是的，它是拼写错误的。对于在MPLAB X上的Realice，实用程序是RealICECD（.exe），但位于MPLABXMPLABBIPIP\。同样的“R<；文件>；重编程”存在。我认为这是解决方案。我将发布我的结果。感谢所有这些评论。
以上来自于百度翻译 以下为原文 I was thinking of having a programmer for each department as well. It's a good solution especially when under process control. However, Production and R&D asked for a simple button solution regardless of what department programmer is being used. This is important when programmers go missing. That's why I have all of the actual programming of the PIC for each Project under Jenkins control. No IDE and no learning of PM3 (especially SD cards too). Use browser and click this. The suggestion about the IPECMD utility got me thinking to revisit how I program the PIC. For RealICE on MPLAB 8.9, the utility program is RealICECMD(.exe) . I did another '/?' on the application and one of the arguments is "R And yes, it's misspelled as is. For RealICE on MPLAB X, the utility program is RealICECMD(.exe) but located under MPLABXmplab_ipe . The same "R I think this is the solution. I will post my results. Thanks to all that commented. B. |
|
|
|
|
|
解决方案：“/r<；文件>；”做我想要的。然而，缺点是程序在下载固件到程序员之后挂起。现在，我必须把程序推到后台（开始命令），然后睡觉，然后做一个TaskDead命令。
以上来自于百度翻译 以下为原文 Resolved. The argument "/R However, the downside is that the program hangs after downloading the firmware onto the programmer. Now, I have to push the program in the background (start command), sleep and then do a taskkill command. Thanks to everyone that responded. B. |
|
|
|
|
|
通过阅读这个线程，在我看来，你可能有一个困扰了我过去几年的问题。当使用真正的ICE，ICD3或PICTIT3在MPLABX和MPLAB V8xx上时，IDE相关固件和目标专用固件可以以某种方式失去同步。这对我来说是强制IDE特定固件的更新，然后强制为IDE和目标更新特定的固件。这第二步可能有点棘手的命令脚本。它需要告诉编程工具使用来自另一个不同家庭的PIC，然后使用我需要编程的目标设备。例如，如果我需要编程一个PIC24FJ128GA010，我将首先告诉编程工具以PIC18F45为目标，下载目标专用固件，然后告诉编程工具以PIC24FJ128GA010为目标。
以上来自于百度翻译 以下为原文 After reading through this thread it seems to me that you could have a problem that has annoyed me for the past few years. It seem that when using the Real ICE, ICD3 or PICkit3 on both MPLABX and MPLAB v8.xx the IDE related firmware and the target specific firmware can somehow get out of sync. What fixes this for me is to force an update of the IDE specific firmware, then force an update of the target specific firmware for the IDE and target. This second step can be a bit tricky to do with a command script. It requires telling the programming tool to use a PIC from another different family then use the target device I need to program. For example if I need to program a PIC24FJ128GA010 I would first tell the programming tool to target a PIC18F4550, download the target specific firmware then tell the programming tool to target the PIC24FJ128GA010. |
|
|
|
|
|
这一直是MPLAB8的一个问题。如果固件版本更新，它会认为它是可以接受的。这并不总是正确的。MPLABX版本只是这个问题的一个扩展。
以上来自于百度翻译 以下为原文 This was always an issue with MPlab8. If the Firmware version was newer it would think it was acceptable. It was not always true. The MPlabX Versions are just an extension of that issue. |
|
|
|
|
|
我发现ICD4的行为比以前的程序员好得多，尽管它还不支持几乎一样多的芯片。
以上来自于百度翻译 以下为原文 I'm finding the ICD4 is behaving much better than previous programmers althtough it does not yet support nearly as many Chips. |
|
|
|
|
|
欢迎来到我的世界。对于我来说，这一切都发生在MPLABX的所有版本中，但是MPLABX 4.xx似乎挂断了，而MPLABX 3.xx最终会超时。V4的情况更糟，我必须杀死这个过程，不管是IDE、IPE还是命令行工具。这是不可用的，这是一个问题，因为他们切换到使用WiUSB驱动程序…有些东西没有编码正确，但它们似乎满足于告诉你一个脚/重新启动（一个脚/重新启动）等。我没有这些问题与旧的MPLAB8。ICD4可能工作得更好，因为它不需要你重新编程工具固件时，你切换设备，使其绕过这个问题。打开支持票并抱怨。
以上来自于百度翻译 以下为原文 Welcome to my world. For me this happens with all versions of mplabx, but mplabx 4.xx seems to hangup while mplabx 3.xx would eventually time out. With V4 it's worse and I have to kill the process, be it the IDE, IPE, or commandline tool. It's unusable. This has been an issue ever since they switched to using WinUSB drivers... something's not coded right but they seem content to tell you to plug/unplug/stand on one foot/reboot, etc. I have none of these problems with the old MPLAB8. The ICD4 probably works better since it doesn't require you to reprogram the tool firmware when you switch devices so it bypasses this issue. Open a support ticket and complain. |
|
|
|
|
只有小组成员才能发言，加入小组>>
5234 浏览 9 评论
2026 浏览 8 评论
1950 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3201 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2253 浏览 5 评论
771浏览 1评论
659浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
588浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
670浏览 0评论
571浏览 0评论
/6 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
1514
评论
淘帖
1550
