完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
电子发烧友论坛|
我正在努力计划一个PIC32 MX174F256B设备上的电路板布局，已经工作了相当多的170个设备，使用一个PICtiT3。我意识到各种各样的线程表明PICTIT3是敏感的，并且我已经尝试添加更多的去耦到芯片，并且改变晶体负载，以防174中的不同振荡器更敏感。我重新焊接了所有的连接，以防万一，因为这已经解决了过去的问题，从其他线程判断。引脚长度是合理的，并且我已经遵循复位连接的其他指导，它有1K电阻到10K/0.1UF负载。PICTIT3报告它检测和擦除设备，然后声称开始编程。它知道，这通常表示硬件问题与高速信号，但已经用尽了主意。我一事无成。有人有什么建议吗？我知道174设备是用不同的技术构建的，但即使如此，这也是从早期的线程开始的，在这里我尝试使用一个174设备的旧的软件库，我需要一个测试床——因此这个板！多谢，VJM
以上来自于百度翻译 以下为原文 I am struggling to programme a PIC32MX174F256B device on a board layout that has worked fine with many equivalent 170 devices, using a PICKit3. I am aware of the various threads that indicate that the PICKit3 is touchy, and I have tried adding more decoupling to the chip, and changing the crystal load in case the different oscillator in the 174 is more sensitive. I have re-soldered all the connections just in case, as this has solved problems in the past, judging from other threads. Lead lengths are reasonable, and I have followed other guidance on the reset connection, which has a 1k resistor to a 10k/0.1uF load. The PICKit3 reports that it detects and erases the device, then claims to start programming. It reports Connecting to MPLAB PICkit 3... Currently loaded firmware on PICkit 3 Firmware Suite Version.....01.51.08 Firmware type..............PIC32MX Target voltage detected Target device PIC32MX174F256B found. Device ID Revision = A1 Device Erased... Programming... The following memory area(s) will be programmed: program memory: start address = 0x1d001000, end address = 0x1d03ffff boot config memory configuration memory The device is code protected. Failed to program device I am aware that this normally indicates a hardware problem with the high-speed signals, but have run out of ideas. I am getting nowhere fast. Does anyone have any suggestions? I know that the 174 device is built using different technology, but even so... This follows on from earlier threads where I am trying to use older software libraries with a 174 device, and I need a test bed - hence this board! Many thanks, VJM 
0
|
|
相关推荐
19个回答
|
|
|
|
|
|
|
|
|
谢谢你的建议。我有一个最小的设置，目前，故意，试图减少变量的数量。我没有办法通过PGEC/ED引脚与其他174方进行通信。然后我注意到，我已经设置了：{ PraceMaMatg配置IICSL＝ICSU-PGX2，以在PGEC2/PGED2AI上使用PIN 21和22进行通信，这在170上设置了2（为什么，为什么我们会有这些变化……）。啊哈，我想！这是问题，虽然困惑…我把这些设置成PGX1，但没有运气。完全相同的问题和消息……老实说，我不确定如何使用IPE来擦除这个设备。我会研究这个。多谢，VJM。
以上来自于百度翻译 以下为原文 Thank you for the suggestion. I have a minimal setup at the moment, deliberately, in an attempt to reduce the number of variables. I have no means of communicating with the 174 other than through the PGEC/ED pins. I then noticed that I had set: #pragma config ICESEL = ICS_PGx2 to communicate on PGEC2/PGED2 as I am using pins 21 and 22, which are set 2 on the 170 (why, oh why do we have these changes...). Aha, I thought! This is the problem, though confused... I set these to PGx1, but no luck. Exactly the same problem and message... In all honesty, I am not sure quite how to use IPE to erase the device - I will look into this. Many thanks, VJM |
|
|
|
|
|
我同意吉姆关于IPE的看法，也不应该和振荡器有任何关系。在没有振荡器的情况下，您应该能够编程PIC。另一个远景（或不）是TDO勘误表。TDO被自动配置为输出PIN函数，当编程期间使用任何PGECX/PGEDX对时，它会切换。当发生这种情况时，TDO管脚上是否有可能导致高电流牵引？Ruben
以上来自于百度翻译 以下为原文 I agree with Jim about the IPE. Also, it shouldn't have anything to do with the oscillator. You should be able to program the PIC even without the oscillator. Another longshot (or not) is the TDO errata - TDO is automatically configured as an output pin function which toggles when any PGECx/PGEDx pair is used during programming. Do you have anything on the TDO pin that can cause high current draw when this happens? /Ruben |
|
|
|
|
|
我可能不会编译和链接正确的174设备。我正试图让UART引导加载程序进入这个设备；我曾经认为实际程序与最初的试验无关，看我是否能加载这个设备。在这个项目中，我的链接器使用的是BTLY32 MX170F256BUUAR.LD文件，这可能是不正确的。有没有人知道我在哪里可以找到与A1388 Bootloader使用的174的等价物？我不得不修改其他文件，但这一点超出了我的范围。我怀疑我应该尝试一个“干净”的174项目，作为下一步的最小行动集…我希望我不会误导读者。在PGEC/D 1和2在170和174设备之间的任意交换……VJM仍然感到恼火……
以上来自于百度翻译 以下为原文 I may not be compiling and linking correctly for the 174 device. I am trying to get the UART bootloader going for this device; I had thought that the actual programme is irrelevant for the initial trial to see if I could load the device - am I correct in this assumption? In this project, my linker is using the btl_32MX170F256B_uart.ld file, which is probably not correct. Does anyone know where I can find the equivalent for the 174 to use with the AN1388 bootloader? I have had to modify other files, but this one is a bit beyond me. I suspect that I should try a 'clean' project for the 174 with a minimal set of actions as the next step... I hope I am not misleading readers. Still annoyed at the arbitrary swap of PGEC/D 1 and 2 between the 170 and 174 devices... VJM |
|
|
|
|
|
道歉，回答交叉。该设备是相当干净的，目前，我只连接了一个Max 323到UART引脚（2和12），准备检查基本操作和串行代码加载。PIN 18（TDO）还没有被使用；它被用作I2C在最后的情况下。我仍然需要看IPE。很多。谢谢你的关心和建议，VJM
以上来自于百度翻译 以下为原文 Apologies, replies crossed. The device is quite 'clean' at the moment; I have only connected a MAX3232 to the UART pins (2 and 12) in preparation for checking basic operation and serial code loading. Pin 18 (TDO) is not yet used; it is used as I2C in the final case. I still need to look into IPE. Many thanks for your interest and advice, VJM |
|
|
|
|
|
ICESEL只用于调试。可以对任何一对进行编程。/ Ruben
以上来自于百度翻译 以下为原文 ICESEL is only for debugging. Programming can be done on any pair. /Ruben |
|
|
|
|
|
VCAP怎么样？是否安装正确的类型、电容和电压？AVDD和AVSS连接？VUSB连接到Vdd？（不要认为这对编程很重要）只要你使用正确的HEX文件，你尝试的程序就没关系了。/ Ruben
以上来自于百度翻译 以下为原文 How about VCAP? Is it mounted and of correct type, capacitance and voltage? AVDD and AVSS connected? Vu*** connected to Vdd? (Don't think this matters for programming though) And it doesn't matter what you try to program as long as you are using a correct hex file. /Ruben |
|
|
|
|
|
亲爱的Ruben和吉姆，我现在使用了IPE（第一次……），它无法擦除设备，这表明直接与PACKIT3完全相同，即设备是代码保护的，它无法擦除设备。这是否给出了提示？我看不出有什么明显的错误在硬件-这可能是显而易见的，但我不能看到它。
以上来自于百度翻译 以下为原文 Dear Ruben and Jim, I have now used IPE (first time...), and it fails to erase the device, indicating exactly the same as PICKit3 directly i.e. the device is code protected and it failed to erase the device. Does this give any hints? I cannot see anything obviously wrong in the hardware - it is probably something obvious, but I cannot see it. VJM |
|
|
|
|
|
附加信息-一些功能似乎工作（空白检查，阅读）…参见下面的回应：-连接到MPLAB拾取器3……当前加载的固件在皮卡3固件套件版本…01.1.08固件类型……PIC32 MX目标电压检测目标设备PIC32 MX174F256B找到。设备ID修订= A12018-03-17:14:0255 + 0000 -空白检查…空白检查完成，设备是空白。2018—03-17 14:03:00 + 0000设备- BLACKAN2018- 03-17 14:03:08+ 0000擦除…擦除…未能删除设备2018—03-17 14:03:12+ 0000 -擦除设备故障2018～03-17 14:03:21+4-阅读…下面的内存区域将被读取：程序内存：开始地址＝0x1d00亿，结束地址＝0x1d03fffFuff-CONFIG配置，内存读取完成，2018—03-17 14:03:41+ 0000 -读取完成，将被迷惑…谢谢您的关心和支持！VJM
以上来自于百度翻译 以下为原文 Additional information - some functions seem to work (blank check, read)... See responses below :- ***************************************************** Connecting to MPLAB PICkit 3... Currently loaded firmware on PICkit 3 Firmware Suite Version.....01.51.08 Firmware type..............PIC32MX Target voltage detected Target device PIC32MX174F256B found. Device ID Revision = A1 2018-03-17 14:02:55 +0000 - Blank checking... Blank Checking... Blank check complete, device is blank. 2018-03-17 14:03:00 +0000 - Device is blank 2018-03-17 14:03:08 +0000 - Erasing... Erasing... Failed to erase the device 2018-03-17 14:03:12 +0000 - Erase device failed 2018-03-17 14:03:21 +0000 - Reading... Reading... The following memory area(s) will be read: program memory: start address = 0x1d000000, end address = 0x1d03ffff boot config memory configuration memory Read complete 2018-03-17 14:03:41 +0000 - Read complete Still mystified... Thank you for your interest and support! VJM |
|
|
|
|
|
现在我可以擦除/编程设备，如果我坚持在PGD和PGEC引脚的范围探头（X10）。我不认为我会从范围内得到有用的信息，但我错了！我已经通过移除探针确认了，在这一点上，装置回到非合作模式……它确实不应该是敏感的。我可以有线反射，但我不认为我必须终止线路或提供串行疏忽的信号。有没有人有类似的经验？我打算用小电容加载这些线，然后继续前进。有点奇怪。非常感谢这些建议，它把我介绍给最新的IPE，这是有用的。我通常下载一个串行引导加载程序ASAP，并使用串行线路来编程设备；我用这个简单的方法维护现场设备。
以上来自于百度翻译 以下为原文 I can now erase/programme the device, if I stick scope probes (x10) on both the PGED and PGEC pins. I did not think that I would get useful information from the scope, but I was wrong! I have confirmed by removing the probes, at which point the device goes back into non-cooperative mode... It really should not be this sensitive. I could have line reflections, but I did not think that I would have to terminate lines or provide serial snubbing of the signals. Does anyone have similar experience? I intend to load the lines with a small capacitance, and move on. Bit weird. Many thanks for the suggestions; it has introduced me to the latest IPE, which is useful. I normally download a serial boot loader asap and use a serial line to programme the devices; I maintain devices in the field using this simple approach. VJM |
|
|
|
|
|
实际上只有PGEC线是敏感的，我不需要额外的电容在PGED上。后者的电容而不是前者的电容不能解决这个问题。我将再次检讨电路板布局，但似乎仍然有趣的是，174设备是敏感的，而不是170。该行确实在其他处理器引脚下面运行，但这些应该是静态的。它还执行一个选择器链接，以允许重新使用第二个串行端口的PIN，但是它不应该太坏（线长度大约超过芯片的一英寸）。我真的应该最少用170个设备填充一个板，看看是否出现同样的问题，但很可能不会有机会。这样做（我没有多余的170躺在身边，很不幸）。为了信息…再次感谢VJM
以上来自于百度翻译 以下为原文 Actually only PGEC line is sensitive; I do not need the extra capacitance on PGED. Capacitance on the latter but not the former does not fix the problem. I will review board layout again, but still seems funny that the 174 device is sensitive to this, not the 170. The line does run underneath other processor pins, but these should be quiescent initially. It also carries on to a selector link to permit re-use of the pin for the second serial port, but it should not be too bad (line length about an inch beyond the chip). I really should minimum populate a board with the 170 device and see if the same problem occurs, but will probably not get a chance to do so (I do not have a spare 170 lying around, unfortunately). For information... Many thanks again, VJM |
|
|
|
|
|
道歉的反应流。只是为了确认22PF电容在PGD线上解决了这个问题。这不是必须的，我会在电路板被加载满的时候再次检查，但是我现在的重点是添加其他的数字设备（I2C，SPI，UART），看看我是否可以使用更新后的PLIB来运行我的应用程序——这不是微不足道的，而且是后台任务，谢谢。我已经错过了。
以上来自于百度翻译 以下为原文 Apologies for the stream of responses. Just to confirm that a 22pF capacitor on the PGED line cured the problem. This should not be necessary; I will check again when the board is more fully loaded, but my priority is now to add the other digital devices (I2C, SPI, UART) and see if I can use the updated PLIB to run my applications - not trivial, and a background task, I'm afraid. Thanks for the warning on the TDO pin - I had missed that. VJM |
|
|
|
|
|
嗨，我从来没有需要把任何电容器的PGEC/PGD线。根本原因是在其他地方……你如何为设备（它自己的电源供应通过皮卡3）？（PICTIT3只能提供有限数量的MA）在项目中是否有引导加载程序？如果是这样，你能尝试只在没有引导程序的情况下编写应用程序吗？当做
以上来自于百度翻译 以下为原文 Hi, I have never ever needed to put any capacitor on the PGEC/PGED lines. The root cause is elsewhere... How do you power the device (its own power supply of through pickit3) ? ( Pickit3 can only supply limited amount of mA ) Do you have a bootloader in your project ? If so, can you please try to program only the application without the bootloader ? Regards |
|
|
|
|
|
谢谢你的评论。我倾向于同意，但我努力理解这种效果。过去我从来没有给PGEC/D线增加电容，虽然我曾经有一次需要改进去耦，让皮卡3用稍长的引线工作。小电容无疑是有效的，但很可能会掩盖解耦或电源的问题。我考虑了信号的反射，但是它们似乎没有足够快地受到板上相对较小的距离的影响。它实际上是一个最小的系统，只有PigTIT3连接，而Max 323还没有被使用（和监管者）。开放建议！回答你的问题：电源由车载调节器提供，运行在3.26V左右，可以提供500毫安。我认为它具有足够的储层电容，MX174附近的局部解耦不是理想的，但应该是足够的。我玩弄不同的脱钩，没有明显的区别。应用十规则的权力没有效果…我最初试图下载Bootloader，但放弃并测试了一个最小的项目下载（PrimaMus加上一个主要的（1））。我在为174的串行引导加载程序而苦苦挣扎，因为我目前有对未定义的库例程的引用——我不使用和声。我明天会解决这个问题，很难知道要增加什么信息，董事会的布局不理想，但很合理，我认为，任何建议或建议都值得感激！VJM
以上来自于百度翻译 以下为原文 Thank you for your comment. I tend to agree, but I am struggling to understand this effect. I have never had to add capacitance to the PGEC/D lines in the past; though I have had one occasion when I had to improve decoupling to get the PICKit 3 to work with slightly longer leads. The small capacitance undoubtedly works, but may well be masking a problem in decoupling or power. I considered reflection of the signals, but they do not appear to be fast enough to be affected by the relatively small distances on the board. It really is a minimal system with only the PICKit3 connected, and a MAX3232 that is not yet in use (and regulators). Open to suggestions! To answer your questions: Power is provided from an on-board regulator; runs at about 3.26V, and can provide up to 500mA. I think that it has enough reservoir capacitance, and local decoupling near the MX174 is not ideal, but should be adequate. I played around with different decoupling with no discernible difference. Applied the power of ten rule with no effect... I was initially trying to download a bootloader, but gave up and tested download with a minimal project (pragmas plus a main of while(1) only). I am struggling with compilation of the serial bootloader for the 174 as I currently have references to undefined library routines - I do not use harmony. I will resolve this tomorrow. It is difficult to know what information to add; the board layout is not ideal but is reasonable, in my view. Any advice or suggestions gratefully received! VJM |
|
|
|
|
|
回答Ruben的早先问题并完成背景，以防万一将来对其他人有所帮助：1。VCAP是一个10uF陶瓷，我也改变了这一点。初始电容器测量在9μF左右，但应该是FIE 2。AVSS和AVDD确实是直接连接的。我现在不使用芯片的ADC或模拟特性。3。在这个设备上没有VUSB。谢谢你澄清了程序上的要点，这证实了我先前的想法。仍然困惑…看看我是否能找到根本原因并报告。至少我可以继续我的软件测试。
以上来自于百度翻译 以下为原文 To answer Ruben's earlier questions and to complete the background, just in case this is helpful to others in the future: 1. VCAP is a 10uF ceramic; I have changed this as well. Initial capacitor measured at around 9 uF, but should have been fine 2. AVSS and AVDD are indeed connected, directly. I do not use the ADC or analogue features of the chip at the moment. 3. No Vu*** on this device. Thank you for clarifying the point on the programme, which confirms my earlier thinking. Still confused... Will see if I can find the root cause and report back if I do. At least I can continue with my testing of the software for the moment. VJM |
|
|
|
|
|
您可能会考虑报告这个问题，并将其固定到Microchip中的支持票或您当地的FAE（销售办事处）。
以上来自于百度翻译 以下为原文 You might consider reporting this problem and fix to Microchip in a support ticket or to your local FAE (sales office). |
|
|
|
|
|
戴维，谢谢你。我已经考虑过了，如果几天内没有进展，我会这么做。我仍然认为我在董事会的某个地方有问题，但是很难看到VJM在哪里。
以上来自于百度翻译 以下为原文 David, Thank you. I had considered this, and I will do so if I make no progress within a couple of days. I still think that I have a problem somewhere on the board, but it is difficult to see where... VJM |
|
|
|
|
|
还有其他职位表明，向PGC或PGD增加一个上限会有所帮助。所以这是闻所未闻的。
以上来自于百度翻译 以下为原文 There have been other posts that indicated adding a cap to pgc or pgd would help. So it is not unheard of. |
|
|
|
|
|
亲爱的库兹曼先生，谢谢你提供的信息——我不知道还有其他这样的帖子。这是令人鼓舞的。这可能意味着一些特定的轨道长度或配置导致反射在它们不需要的地方，即当数据被PICTIT3采样时。我自己的看法是，它在实际使用中过于敏感，但工具箱是一个很好的服务。
以上来自于百度翻译 以下为原文 Dear Mr Kurzman, Thank you for this information - I was not aware of any other such posts. This is encouraging. It may mean that some particular track lengths or configuration lead to reflections just where they are not wanted i.e. when the data is sampled by the PICKit3. My own view is that it is far too sensitive in practical use, but the kit has been a good servant. VJM |
|
|
|
|
只有小组成员才能发言，加入小组>>
MPLAB X IDE V6.25版本怎么对bootloader和应用程序进行烧录
475 浏览 0 评论
5795 浏览 9 评论
2334 浏览 8 评论
2224 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3530 浏览 3 评论
1126浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
1098浏览 1评论
我是Microchip 的代理商，有PIC16F1829T-I/SS 技术问题可以咨询我，微信：A-chip-Ti
873浏览 1评论
MPLAB X IDE V6.25版本怎么对bootloader和应用程序进行烧录
475浏览 0评论
/9 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
4971
评论
淘帖
2951
