PIC24FJ256GA705和704编程速度慢

你用皮卡试试了吗？



      以下为原文

    Have you tried it with a pickit?

PK3提供了与好奇套装相同的速度，这不足为奇，因为好奇心已经减少了PICTIT3。



      以下为原文

    PK3 provides the same speed as Curiosity kit - no surprise here, as Curiosity has cut-down PicKit3 on board.
ICD3 is just marginally faster than that.

我用Linux MINT 18.2在计算机上做了同样的事情，因为Linux机器比MPLABX和其他Java怪物更好地工作得比Windows更好。这种情况似乎有不同的根本原因，所以毫不奇怪，它与Windows相同。我坚信这是一种bug MPLABX，并将尝试打开支持票。



      以下为原文

    I just tried the same thing on computer with Linux Mint 18.2, as Linux machines are known to work better with MPLABX and other java monsters better than Windows. This situation seems to have different root cause, so not surprisingly, it's the same as in Windows.
I strongly believe this is some kind of bug MPLABX, and will try to open support ticket.

当你写到你的MPU时，它编译代码，擦除然后写入。写时间似乎还好，几秒钟。



      以下为原文

    When you write to your mpu it compiles the code, erases then writes.
The write time seems ok, a few seconds.
 

4.05和4.15版本的情况相同，擦除约25秒，并将135B代码转换为PIC24FJ256GA705。



      以下为原文

    The situation is the same with 4.05 and 4.15 releases.
Roughly 25 seconds to erase and program 135B of code into PIC24FJ256GA705.

我用Microchip的支持来讨论这个问题。自从打开这个案例已经四个星期了，到目前为止，他们能够复制这个缓慢的程序，虽然速度相当慢，大约每星期一两次。不知怎的，这让我想起了与地球另一边的人的国际象棋。



      以下为原文

    I'm discussing this issue with Microchip support.
It's been four weeks since opening the case, so far, they were able to replicate this slow programming, though it goes rather slow, at rate roughly one comment per week or two. Somehow it reminds me correspondence chess with a person on other side of Earth.

从微芯片支持更新-他们知道现在的问题，并将改善在未披露的未来的情况。我没有足够的勇气去推动它，所以我关闭了这个案例。同时，我将避开这一系列的PIC设备。



      以下为原文

    Update from Microchip support - they are aware now of the problem and will improve the situation in undisclosed future. I didn't feel brave enough to push it any further, so I closed the case.
 
I'll avoid this family of PIC devices in the meantime.

许多人联系我们询问我们的程序员是否能比PICTIT3更快地编程这些芯片。也许它与这些设备上的硅Bug PGEC2/PGED2对不相关。也许PICTIT3尝试工作在周围。你使用PGEC2/PGED2吗？/WordNo.NavaRe.COM/DEV/PIC24FJ/PIC24FJ256GA702.HTMDO？



      以下为原文

    Many people have contacted us asking if our programmer can program these chips any faster than PICkit3.
 
Perhaps it is related to the silicon bug. PGEC2/PGED2 pair on these devices is not functional. Perhaps PICkit3 tries to work around.
 
http://www.northernsoftware.com/dev/pic24fj/pic24fj256ga702.htm
 
Do you use PGEC2/PGED2?

我在自己的板上使用PGED1/C1对。好奇心板使用PGED2/C2对，但在这两种情况下，我得到相同的结果。不过，在PIC24FJ256GA705勘误表中找不到任何与此相关的勘误表。我记得老式PIC24XXGA04具有非功能性PGD/PGC对的勘误表，但它不是非工作的。这个页面似乎更多地与我的问题有关：http://www. NurthnCuffa. FJ/PIC24FJ256GA705.HTMHECK，5s，5s用于完整的程序和验证。相比之下，MPLABX编程实际上是比较迟钝的，几秒钟就连接到程序员，然后是20秒的空闲，然后是2s的实际工作。另一方面，PIC24FJ128GA06在MPLABX编程得快得多，比如连接几秒钟，编程和完成几秒钟，没有20秒。在等待之间。这就是为什么我打开了支持案例，花了一个月的时间来解释他们在25s编程任意数量的代码（135B在这个特定的情况下）是错误的。



      以下为原文

    I'm using PGED1/C1 pair on my own board. Curiosity board uses PGED2/C2 pair, but in both cases I get the same results. I can't find any errata related to this in PIC24FJ256GA705 errata list, though. I remember older PIC24xxGA004 having errata with non-functional PGD/PGC pair, AFAIK it was un-workaroundable.
 
This page seems to be more related to my problem http://www.northernsoftwa...fj/pic24fj256ga705.htm
Heck, 5,5s for full program and verification. MPLABX programming is really sluggish in comparison, few seconds connecting to programmer, then 20s of nothing and then 2s of actual job.
On the other hand, PIC24FJ128GA006 are programmed much faster in MPLABX, like few seconds of connecting, then few seconds of programming and done, without the 20s of waiting in between. That is why I opened the support case and it took one month to explain them that programming any amount of code (135B in this particular case) in 25s is just wrong.

PGED2/PGEC2对与JTAG引脚复用，对SPI产生干扰，编程执行不起作用。可能是PACKIT3通过使用串行执行模式来编程，但比执行程序慢得多。



      以下为原文

   


The PGED2/PGEC2 pair is multiplexed with JTAG pins, which produces interference with SPI, thus the programming executive cannot function. May be PICkit3 works around by using serial execution mode to program, but it's much slower than the executive.
 

串行执行模式-除非以不合理的低时钟速率驱动-不能解释4/5b/s（135b/25s）编程速度。你的程序员声明大约46kb/s，是一万倍。那是非常合理的数目。除此之外，这可能是好奇板问题，但对于定制板来说，使用PKD1/PGC1对与PK3或ICD3不同，但也有与好奇心相同的症状。MPLABX在这里是共同的分母，即使是微芯片也证实了这种行为，并宣称它们将是仿效的。在未知的未来，编程速度。考虑到确认这个问题花了两个月的时间，我没有屏住呼吸。



      以下为原文

    Serial execution mode - unless driven at unreasonably low clock rate - can't explain 4,5B/s (135B per 25s) programming speed. Your programmer declares roughly 46kB/s, ten thousand times as much. That is very reasonable number. 4,5B/s isn't.
Other than that, this could be Curiosity board problem, but not much for custom board, using different PGD1/PGC1 pair with PK3 or ICD3, yet having the same symptoms as Curiosity board.
 
MPLABX is common denominator here, even Microchip confirmed this behavior and declared they will improve the programming speed in undisclosed future. Considering it took two months just to confirm this issue, I'm not holding my breath.