完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
问候语。我们最近使用PIC12F1571(MSOP-8包)生产了20个定制板。我在星期五用IDE(V3.35)使用了我的PICtiT3程序,其中12个都是正确的。今天,我用IPE(V3.35)使用了相同的PACTIT3编程其他8个,并且它们都出现了,按照IPE正确地编程。然而,2的电路板表现得好像MCU没有被编程。我试图用IPE来验证它们,验证失败了。我读取一个MCU的内容,并将其验证到原始的HEX文件-它匹配。我关闭IPE并打开IDE,它将无法连接到PICTIT3。我拔掉了皮卡3,重新连接起来。我用IDE对两个板进行编程,这两个工作都很好。硬件细节:编程板从板对面的MCU大约5mm。CLK和DAT线被用作模拟输入-我有2K电阻隔离运算放大器和MCU引脚的输出。MCLR引脚仅用于VPP和I AMLN使用内部上拉电阻。VDD绕过引脚与100NF和10uF陶瓷帽。VDD是5V。在这两种情况下,我使用PICTIT3为目标板。在VDD上从其他设备汲取的总电流大约为1Ma。有没有其他人看到这种行为?最困扰我的部分是IPE没有产生任何错误,即使它好像没有正确地编程MCU。谢谢,比尔。
以上来自于百度翻译 以下为原文 Greetings. We recently produced 20 custom boards using the PIC12F1571 (MSOP-8 package). I programmed 12 of them on Friday using my PICKIT3 with the IDE (v3.35) and all of them worked correctly. Today, I programmed the other 8 using with the same PICKIT3 using the IPE (v3.35) and all of them "appeared" to program correctly according to the IPE. However, 2 of the boards behaved as if the MCU had not been programmed. I tried to verify them using the IPE and the verification failed. I read back the contents of one of the MCUs and verified it to the original hex file - it matched. I closed the IPE and opened the IDE - it wouldn't connect to the PICKIT3. I unplugged the PICKIT3 and reconnected it. I programmed both boards using the IDE and both work fine. Hardware details: the programming pads are about 5mm from the MCU on the opposite side of the board. The CLK and DAT lines are used as analog inputs - I have 2K resistor isolating the outputs of an op-amp and the MCU pins. The MCLR pin is used only for VPP and I am only using the internal pull-up resistor. VDD is bypassed at the pin with 100nF and 10uF ceramic caps. VDD is 5V. I used the PICKIT3 to target the board when programming in both cases. Total current draw from other devices on VDD is about 1mA. Has any one else seen this behavior? The part that troubles me the most is that the IPE didn't generate any errors even though it doesn't seem like it correctly programmed the MCU. Thanks in advance, Bill |
|
相关推荐
4个回答
|
|
如果读回的HEX文件与您所编程的程序相匹配,则PICSHAVE被正确编程。但这也是验证的结果。如果验证失败,你如何读回正确的数据?
以上来自于百度翻译 以下为原文 If the read-back HEX file matches what you programed in, then the PICs have been programmed correctly. But that's also what the verification would do. If verification fails, how could you read back the correct data? |
|
|
|
|
|
|
|
HI,如果差异导致验证失败位于配置区域中,程序存储器的内容,EEPROM存储器(如果存在),用户ID可以被读取并给出正确的内容。如果配置寄存器中的数据在一个(或多个)掩蔽位中是不同的,那么配置数据看起来是正确的,但是验证失败。
以上来自于百度翻译 以下为原文 Hi, if the difference witch causes verify to fail is located in configuration area, the content of the program memory, eeprom memory (if exists), user ids can be read back and gives the correct content. If data in a configuration register is different in one (or more) masked bit(s) the configuration data seems to be correct, but can fail the verification. |
|
|
|
原始编译的HEX文件和从MCU读出的HEX文件之间的唯一区别是程序存储器中的几行空白字和用户ID存储器中的一个空白字。配置词匹配,这个MCU没有任何EEPROM。
以上来自于百度翻译 以下为原文 The only differences between the original compiled HEX file and the HEX file read out of the MCU were several lines of blank words in the program memory and one blank word in the User ID memory. The configuration words match and this MCU does not have any EEPROM. -Bill |
|
|
|
只有小组成员才能发言,加入小组>>
5242 浏览 9 评论
2031 浏览 8 评论
1955 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3207 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2256 浏览 5 评论
778浏览 1评论
666浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
595浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
677浏览 0评论
576浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-23 13:00 , Processed in 1.810411 second(s), Total 84, Slave 67 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号