完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
大家好,经过多年的微控制器,我第一次遇到这个错误,我花了半个下午试图摆脱它,但没有成功。我的情况如下:我在一个新的板上有AdSPIC3FJ64 GS606,它被ICD3正确识别,我使用PGC/PG。D3端口(正确设置在MPLAB 8.88 -是的,我仍然使用旧版本,我不理解任何在新的……)如果我使用ICD3作为程序员,一切工作良好的所有振荡器配置(内部,XT,有或没有PLL……)。当我使用它作为调试器时,程序被写入,验证,但是我得到0040错误。我已经检查了微控制器的安装,它看起来很好,程序员引脚似乎是正确的引脚上的连接器,复位只有一个100K上拉,它是直接连接到TH。电路板几乎完全无人居住(只有SPI总线上的ADC和M3322收发器,我不认为它们能在这一点上干扰),我已经尝试过任何可能的保险丝设置组合,但结果总是一样的。当编程和执行速度根据振荡器设置改变时,我倾向于排除振荡器或板本身的硬件问题。IC PIS与ICD连接器之间的电阻是0.4OHM,所以我也排除了焊接的一些问题,ICD电缆是标准的短路,作为USB电缆。连接器只放置在离微控制器几毫米的地方,所以轨道很短。程序还没有做任何事情,只是将一个端口设置为输出并闪亮LED,因为我把所有的东西都移除了,以确保那里没有干扰。我明天唯一能做的就是组装一个第二个PCB,测试一个只排除一个微控制器故障,所以任何建议都是非常欢迎的。谢谢!吉安保罗
以上来自于百度翻译 以下为原文 Hi all, after many years of microcontrollers I have encountered for the first time this error and I have spent half afternoon trying to get rid of it, but without success. My situation is as follows: I have a dsPIC33FJ64GS606 on a new board, it is correctly identified by the ICD3, I am using the PGC/PGD3 port (correctly set in MPLAB 8.88 -yes, I am still using the old version, I do not understand anything in the new one...). If I use the ICD3 as a programmer, everything works fine with all oscillator configuration (internal, XT, with or without PLL...). When I use it as a debugger, the program gets written, verified, but I get the 0040 error. I have checked the mounting of the microcontroller and it seems fine, the programmer pins seems to be going to the correct pins on the connector, the reset has only a 100k pullup and it is wired directly to the ICD connector. The PCB is almost completely unpopulated (only an ADC on the SPI bus and a MAX3232 transceiver, I don't think they can interfere at this point), I have tried any possible combination of fuse settings I could think of, but the result is always the same. Since the microcontroller works when programmed and the execution speed changes according to the oscillator setup, I tend to exclude an hardware issue with the oscillator or with the board itself. The resistance between the IC pis and the ICD connector is 0.4Ohm, so I would also exclude some problem with soldering, the ICD cable is the standard short one, as the USB cable. The connector is placed only a few millimeters away from the microcontroller, so tracks are very short. The program is not doing anything yet, just setting one port as output and flashing a led, since I removed everything to be sure that there were no interference from there. I am quite out of ideas, the only thing I can try tomorrow is to assembly a second PCB and test that one just to exclude a microcontroller failure, so any suggestion is very welcome. Thanks! Gian Paolo |
|
相关推荐
12个回答
|
|
我不这么认为……所有的代码保护都关闭了,我也试过完全擦除设备。从一开始我就不能在调试模式下连接,而且在设备配置窗口中也没有看到任何“可疑”……你知道我需要检查的具体设置吗?
以上来自于百度翻译 以下为原文 I don't think so... All code protections were off, I have tried also the complete erase of the device. I was not able to connect in debug mode since the beginning and I have not seen anything "suspicious" in the device configuration window... Do you know any specific setting that I may have to check? |
|
|
|
该死的!mad:http://www1.micro..com/downloads/en/DeviceDoc/80000489L.pdfDevice调试在使用PGEC3/PGED3时钟/数据引脚时不起作用。我讨厌这些东西!现在将是一个混乱,修补PCB和交换连接的两个引脚!嗯…
以上来自于百度翻译 以下为原文 Damn it! mad: http://ww1.microchip.com/downloads/en/DeviceDoc/80000489L.pdf Device debugging is not functional when using the PGEC3/PGED3 clock/data pins. I hate these things! Now it will be a mess to patch the PCB and swap the connections of two pins! ARGHHH.... |
|
|
|
真正的程序员使用调试器来评估外围设置,而不用编写一行代码:(我承认:只有在特殊情况下)。但这不会是第一次……
以上来自于百度翻译 以下为原文 real programmers USE debuggers - to evaluate the peripheral setup without writing a single line of code :) (I admit: only in special cases. But it wouldn't be for the first time...) |
|
|
|
真正的程序员不焊接——他们修补软件。最好是在HexFobe上完成。一个同事被称为Pt'''Huffisher。(他的姓听起来有点像那个。)他修改了8051机器代码的十六进制,把十六进制文件带回来了,并且有一个年轻的团队将补丁反向工程成源代码。虽然一些补丁只是const值的变化。很有趣,但不是“绿色”的同事…
以上来自于百度翻译 以下为原文 real programmers don't solder - they patch the software. Best to be done on the hexfile. A colleague was called Patch'n'hacker. (His surname sounded a bit like that.) He modified 8051 machine code in hex, brought the hexfile back and had a younger colleage to reverse engineer the patches into source code. Though some of the patches were just changes of const values. Quite funny, but not for the 'green' colleague... |
|
|
|
我希望我能用CordGrin修补一个硅臭虫:
以上来自于百度翻译 以下为原文 I wish I were able to patch a silicon bug with code grin: |
|
|
|
不幸的是,他们倾向于孵化硅臭虫而不是移除它们。“这不是一个bug——它是一个‘特征’。”=8。
以上来自于百度翻译 以下为原文 Unfortunately, they tend to hatch silicon bugs instead of removing them. "It's not a bug - it's a 'feature'." =8- |
|
|
|
当然,关键是使用串行端口代替调试器……PS:至于设置硬件而不用编写代码……嗯,我得承认我从来没想到过!:)
以上来自于百度翻译 以下为原文 Of course, the point is that you use a serial port in place of the debugger... PS: as for setting hardware without writing code... well, I have to admit I never ever thought of that! :) |
|
|
|
最后,我修补了PCB,微控制器现在工作得很好。一个漂亮的PCB被PIC bug损坏了…
以上来自于百度翻译 以下为原文 Just to conclude, I patched the PCB and the microcontroller is working fine now. A nice PCB spoiled by a PIC bug... |
|
|
|
在选择CPU之前总是要阅读勘误表,而不仅仅是微芯片。
以上来自于百度翻译 以下为原文 Always read the Errata Before selecting a CPU, and not just Microchip. |
|
|
|
我知道,那是我的缺点。我不得不说,我必须用一些错误来处理过去,但是没有这个幅度。它不只是一个小bug,是非工作外围设备。考虑到是的,我应该已经阅读了勘误表,我认为,如果您在制造一个具有三个调试端口的产品,并且一个没有工作,那么您应该“宣传”它,而不仅仅是在勘误表中……
以上来自于百度翻译 以下为原文 I know, my fault under that aspect. I have to say that I had to deal in the past with some bug, but nothing of this amplitude. It is not just a little bug, is a non working peripheral. Considering that yes, I should have been reading the errata, I think that if you are manufacturing a product with three debug port and one is not working your should "advertise" it a bit more clearly than just in the errata... |
|
|
|
我认为数据表/市场营销人员假设它最终会被修复,但它没有。有些图片有严重的问题,因为任何商业原因永远不会得到修复。即使是固定的,现在也不会对你有帮助。仍然在供应链中。
以上来自于百度翻译 以下为原文 I think the Data sheet / Marketing people assumed it would be fixed eventually, but it did not. Some PICs have serious issues which for what ever business reasons never get fixed. Even if was is slated to get fixed, that would not help you now. It is also important in case you get old rev chips that are still in the supply chain. |
|
|
|
您可能是对的,但是由于他们已经发布了三个特定的uC,所以他们有足够的时间更新描述/数据表。在这一点上,它不是bug,它是一个特性绿色:无论如何,经验教训-在开始示意图之前检查勘误表,不要对墨菲的露齿大笑造成任何限制:
以上来自于百度翻译 以下为原文 You are probably right, but since they have made three releases of this specific uC, they had plenty of time to update the description/datasheet. At this point, it is not a bug, it is a feature mr green: Anyway, lesson learned -check the errata before starting the schematics and don't pose any limit to Murphy's law grin: |
|
|
|
只有小组成员才能发言,加入小组>>
5184 浏览 9 评论
2005 浏览 8 评论
1932 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比?
3179 浏览 3 评论
请问电源和晶体值之间有什么关系吗?PIC在正常条件下运行4MHz需要多少电压?
2230 浏览 5 评论
742浏览 1评论
628浏览 1评论
有偿咨询,关于MPLAB X IPE烧录PIC32MX所遇到的问题
512浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
640浏览 0评论
538浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-28 22:09 , Processed in 1.512737 second(s), Total 99, Slave 82 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号