完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
|
这是一个严重的问题，阻碍了我们的发展。这已经到了我需要在代码改变之后重新启动我的电脑的地步。常规的固件编程似乎发生得很好，但是当我试图开始一个调试会话时，程序员挂起了。这就是我所看到的：我体验到这两个真正的冰和ICD3。我尝试从3.40升级到MPLAB X V3.45，但没有效果。我发现唯一可靠工作的解决方案是重新启动整个PC。在我修改代码的任何时候都会出现这种情况。这对我们来说是个大问题。
以上来自于百度翻译 以下为原文 This is a serious problem that is holding up our development. It has gotten to the point where I need to reboot my PC after any code change. Regular firmware programming seems to happen fine, but when I try to begin a debugging session, the programmer hangs. This is what I see: ***************************************************** Connecting to MPLAB REAL ICE... Currently loaded firmware on REAL ICE Firmware Suite Version.....01.45.41 Firmware type..............dsPIC33F/24F/24H Target voltage detected Target device PIC24FJ256GB210 found. Device ID Revision = 0x4 I am experiencing this with both the Real ICE and the ICD3. I tried upgrading to MPLAB X v3.45 from 3.40 to no avail. The only solution I've found that works reliably is rebooting the whole PC. It seems to happen any time I modify the code. This is a big, big problem for us. 
0
|
|
相关推荐
9个回答
|
|
|
位9-8ICS<1:0>：模拟器管脚位置选择位11=模拟器功能与PGEC1/PGED110共享=模拟器功能与PGEC2/PGED201共享=模拟器功能与PGEC3/PGED3Did共享，在配置设置中选择要连接的那个？
以上来自于百度翻译 以下为原文 bit 9-8 ICS<1:0>: Emulator Pin Placement Select bits 11 = Emulator functions are shared with PGEC1/PGED1 10 = Emulator functions are shared with PGEC2/PGED2 01 = Emulator functions are shared with PGEC3/PGED3 Did you select the One that you are connected to in your config settings? |
|
|
|
|
|
它被设置为PGX2，它根据Explorer 16数据表（相关附图）看起来是正确的。
以上来自于百度翻译 以下为原文 It is set to PGx2, which looks correct according to the Explorer 16 data sheet (relevant diagram attached). Attached Image(s) |
|
|
|
|
|
哪位探险家16.ICD2看起来老了。你把PIN追踪到PIM去确保他们去哪里了吗？肯定是2？你禁用了登机调试器吗？
以上来自于百度翻译 以下为原文 Which Explorer 16. ICD2 looks old. Did you trace the pins to your PIM to insure where they go? It is definitely 2? Did you disable the on board debugger? |
|
|
|
|
|
我只知道两个Explorer板：探险家16和探险家16/32。我正在使用Explorer 16.ICD 2，就是他们如何在电路图中标示RJ-11连接器。不管你用的是ICD 2，ICD 3，还是真正的ICE。我主要使用真正的ICE，并在ICD 3上复制了这个问题。如果不知何故，Explorer 16文档或我对它的解释是错误的，我将无法对该设备进行编程。我不确定您所说的车载调试器是什么意思。
以上来自于百度翻译 以下为原文 I'm only aware of two Explorer boards: the Explorer 16 and the Explorer 16/32. I'm using the Explorer 16. ICD 2 is just how they labelled the RJ-11 connector in the circuit diagram. It doesn't matter whether you're using ICD 2, ICD 3, or Real ICE. I am using Real ICE primarily, and replicated the issue on the ICD 3. If somehow the Explorer 16 documentation or my interpretation of it was wrong, I would not be able to program the device. I'm not sure what you mean by on-board debugger. |
|
|
|
|
|
HTTP://WW1.MICCHIP.COM/DeLoSt/En/DeVICECDOC/5000 01589B.PDFID没有显示ICD2，我知道连接器没有改变。有时，微芯片会重新制作电路板，并且与旧版本不完全相同。U2是板上调试器，如果你能编程，它就像旁路一样。你是否跟随或欧姆出引脚，以确保你连接到正确的。这是你问题的最常见原因。你的boARD可以承担所有的上限。我认为你是从供电电源板。
以上来自于百度翻译 以下为原文 http://ww1.microchip.com/downloads/en/DeviceDoc/50001589b.pdf did not show ICD2, I know the connector has not changed. Sometimes microchip remakes the board and it is not exactly the same as the older version. U2 is the Onboard debugger, If you can program it is most like bypassed. Did you follow or ohm out the pins to be sure you are connected to the correct ones. That is the most common reason for your issue. Your board can assume to have all its caps. And I assume you are powering the board from its supplied power supply. |
|
|
|
|
|
不，我没有。如果插销错了，我就不能编程PIC了，对吗？PC的重新启动不会暂时允许调试工作，对吗？对我来说，这意味着微芯片产品和Windows之间存在某种问题。顺便说一句，上周一切正常。似乎没有漏帽，我正在使用板子上的电源。另外，我用一个全新的PIM在不同的探险者16板上复制了这个问题。
以上来自于百度翻译 以下为原文 No, I haven't. If the pins were wrong, I would be unable to program the PIC, correct? And a reboot of the PC would not temporarily allow debugging to work, correct? To me, this implies some sort of problem between the Microchip products and Windows. By the way, everything was working fine last week. There appear to be no missing caps, and I am using the power supply that came with the board. Also, I have replicated the issue on a different Explorer 16 board, with a brand-new PIM. |
|
|
|
|
|
对不起，你可以调试。如果你能调试，那不是问题。我认为你可以编程，但不能调试。在MplabX中的怪异行为有时可以通过清除缓存来治愈。转到Help->aboutNote用户目录和缓存目录。关闭程序Delete或重命名这两个文件夹。我建议对导入设置说“否”。看看是否有帮助。
以上来自于百度翻译 以下为原文 I am sorry You can debug. If you can debug that is not the issue. I thought you could program, but not debug. weird behavior in MplabX sometimes can be cured by clearing the cache. Go to Help->about Note the User directory and the cache directory. Close the program Delete or rename those two folders. start the program in your case I would recommend saying no to import settings. See if that helps. |
|
|
|
|
|
所以偶然的，我看到一些关于断点的奇怪的简短的弹出。我删除了所有的断点，现在看来我可以调试了。我不会把这个问题解决。似乎有一个与断点有关的bug。
以上来自于百度翻译 以下为原文 So by chance, I saw some weird, brief popup about breakpoints. I deleted all the breakpoints, and now it seems I am able to debug. I wouldn't call the issue resolved. There seems to be a bug somewhere related to breakpoints. |
|
|
|
|
|
MplabX非常古怪，如果你能找出如何打破它，他们会解决它。
以上来自于百度翻译 以下为原文 MplabX is very quirky. If you can figure out how to break it they will fix it. |
|
|
|
|
只有小组成员才能发言，加入小组>>
5160 浏览 9 评论
1998 浏览 8 评论
1927 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3170 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2225 浏览 5 评论
731浏览 1评论
613浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
503浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
629浏览 0评论
527浏览 0评论
/6 
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
1290
评论
淘帖
1261
