完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
德赢Vwin官网
论坛
2239
|
有没有人注意到，在MPLLABX（v3.35）下，在PICkit3的命令行上完成擦除和程序等基本命令所需的时间比在MPLLAB8.92下要长得多？PIC24FJ64 GA102的擦除命令花了大约14秒完成。它的速度比8.92版本快得多。任何人都能确认命令行工具变得慢得多吗？戴夫
以上来自于百度翻译 以下为原文 Has anyone noticed that basic commands like erase and program all take a lot longer to complete on the command line for PICkit3 under MPLABX (v3.35) than they did under MPLAB 8.92? The erase command for PIC24FJ64GA102 took about 14 seconds to finish. It was a lot faster with the version that came with 8.92. Can anyone confirm that the command line tools have become much slower? Dave 
0
|
|
相关推荐
9个回答
|
|
|
我做了一些速度测试，我发现从命令行开始的每个PICkit3（和ICD3）操作需要7-9秒的开销。在测试过程中，我在后台打开了IPE，但我没有使用它。测试结束后，我关闭了IPE，并且注意到开销延迟增加了5秒左右，这与您观察到的情况类似。也许，如果在后台打开IPE，命令行操作可能会变得更快一点。
以上来自于百度翻译 以下为原文 I did some speed tests, and I found out it's about 7 to 9 seconds overhead on every PICkit3 (and ICD3) operation from the command line. During the tests I had IPE open in the background, but I didn't use it. After the tests I closed IPE and I noticed that the overhead delays increased by 5 seconds or so, which would be similar to what you observe. Perhaps, if you open IPE in the background, the command line operations may become a little bit faster. |
|
|
|
|
|
我用我正在编写的VisualStudio程序来控制PK3。用8.92命令行.exe，我能够发送命令擦除、程序全部或从10秒超时重置释放，并且永远不会有超时故障。今天，我一直使用来自MPLABX 3.35的命令行.exe，这是我必须使用的，因为8.92版本不知道我需要编程的新PIC32 MX，并且我必须不断增加超时值来防止失败。我现在有50秒的超时时间。我想我可以使用8.92版本来编程PIC24，并且只使用MPLABX版本来更新新的PIC32 MX。戴夫。
以上来自于百度翻译 以下为原文 I'm controlling the PK3 with a Visual Studio program I'm writing. With the 8.92 command line .exe, I was able to send commands for erase, program all, or release from reset with a 10 second timeout and never have a timeout failure. Today, I have been using the command line .exe from MPLABX 3.35, which I have to use because the 8.92 version doesn't know about a newer PIC32MX that I also need to program, and I had to keep increasing my timeout value to prevent failures. I'm currently up to a 50 second timeout. I suppose I could use the 8.92 version for programming the PIC24 and only use the MPLABX version for the newer PIC32MX. Dave |
|
|
|
|
|
PIC24FJ64GA102使用IPECMD和PICkit3需要15秒，使用IPECMD和ICD3需要12秒，但是使用命令行实用程序和我的程序员只需1.7秒就可以对整个内存进行编程。
以上来自于百度翻译 以下为原文 PIC24FJ64GA102 takes 15 seconds with IPECMD and PICkit3, 12 seconds with IPECMD and ICD3, but only 1.7 seconds with command line utility and my programmer to program the entire memory. Which PIC32MX do you use? |
|
|
|
|
|
|
|
|
|
|
|
有了这个，PIPIT3编程速度对IPECMD开销更为重要。使用PICkit3的IPECMD可以在53秒内完成编程，其中只有9秒是IPECMD开销，44秒是纯编程。相比之下，IPECMD和ICD3可以在18秒内完成编程。我的程序员可以在11秒内完成编程。我敢肯定，如果您有一个高端的程序员，比如Segger，您将负责编程。它甚至更快，虽然我没有测量它。
以上来自于百度翻译 以下为原文 With that one, the PICkit3 programming speed is more important that IPECMD overhead. IPECMD with PICkit3 can fully program it in 53 sec, of which only 9 sec is IPECMD overhead and 44 sec is pure programming. For comparison, IPECMD with ICD3 can program it in 18 sec. My programmer can program it in 11 sec. I'm pretty sure that if you get a high end programmer, such as Segger, you'll get it even faster, although I didn't measured it. |
|
|
|
|
|
此时测试器硬件已经锁定，所以PK3仍然存在。我调整错误的超时设置欺骗了自己。编程命令超时设置为20秒，8.92命令行的一切都很好。我不得不将时间增加到30秒，它似乎可以用MPLABX命令行对PIC24进行编程。
以上来自于百度翻译 以下为原文 The tester hardware has already been locked in at this point, so the PK3 stays. I fooled myself by adjusting the wrong timeout setting. The programming command timeout was set at 20 seconds, and everything was fine with the 8.92 command line. I have had to bump it up to 30 seconds and it seems to be working for programming the PIC24 with the MPLABX command line. I may be looking at the commands that only program the pages needed for the PIC32. Dave |
|
|
|
|
|
您好，注意PACTIT3不是生产编程的辅助设备。（用户手册）问候
以上来自于百度翻译 以下为原文 Hi, Pay attention that Pickit3 is not garanteed for production programming... (user manual) Regards |
|
|
|
|
|
我也看到了，并把它展示给了硬件设计师。他指出，我们已经使用PK3在测试器上为以前的产品编写PIC32s程序好几年了，没有出现问题。
以上来自于百度翻译 以下为原文 I saw that, too, and showed it to the hardware designer. He pointed out that we have been programming PIC32s on the tester for our previous product using PK3 for several years now without problems. Dave |
|
|
|
|
|
这是过去讨论过的。据说，这个问题比正确性更持久。这是因为PIC实际运行程序周期而不是外部工具。
以上来自于百度翻译 以下为原文 This was discussed in the past. The issue was said to be a durability issue rater than a correctness one. This is due to the fact that that PIC actually runs the program cycle not the external tool. |
|
|
|
|
只有小组成员才能发言，加入小组>>
5238 浏览 9 评论
2028 浏览 8 评论
1950 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3204 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2253 浏览 5 评论
778浏览 1评论
666浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
595浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
677浏览 0评论
576浏览 0评论
/6 
关注我们的微信
下载发烧友APP
德赢Vwin官网 观察
版权所有 © 湖南华秋数字科技有限公司
德赢Vwin官网 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
评论
淘帖
1352
