[问答]

pic18f调试-重置WDT问题

问答对人有帮助，内容完整，我也想知道答案 0 我有一个PIC18F项目，有一个错误导致MCU挂机。这是一种罕见的错误，每天可能发生一次。看门狗定时器启动并重新启动PIC。我想调试这个问题。我现在意识到，我的方法不是最好的，因为我所做的是在WDT事件上设置一个调试器断点并等待。几小时后，断点被击中了。不幸的是，我不能仅仅从内存内容中找到原因，所以如果程序继续的话，我想分析一下程序流。我能修改一些寄存器的内容，让PIC继续下去，就像WDT没有开机一样吗？以上来自于百度翻译以下为原文 I have a PIC18F project with a bug that causes the mcu to hang. It's a rare bug happening maybe once a day. The watchdog timer kicks in and restarts the PIC. I want to debug the issue. I realize now that my approach isn't the best, as what I did is set a debugger breakpoint on the WDT event and wait. After several hours the breakpoint was hit. Unfortunately I haven't been able to find the cause from just the memory contents, so instead I'd like to analyse the program flow if it were to continue. Can I modify some register's contents to allow the PIC to continue as if WDT isn't kicking in? 0
2019-7-4 09:33:32　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × qun333 该类别下有 57 个回答。邀请回答技术发广告该类别下有 56 个回答。邀请回答 caoguiqun 该类别下有 56 个回答。邀请回答 psw30 该类别下有 44 个回答。邀请回答伊丹姿子该类别下有 41 个回答。邀请回答 uwufwjrw 该类别下有 39 个回答。邀请回答 hetao1111 该类别下有 38 个回答。邀请回答 lc123617 该类别下有 35 个回答。邀请回答欧阳大大该类别下有 32 个回答。邀请回答作死不止该类别下有 31 个回答。邀请回答 asd010 该类别下有 31 个回答。邀请回答 wy8719 该类别下有 29 个回答。邀请回答 60user92 该类别下有 29 个回答。邀请回答 ju978779 该类别下有 28 个回答。邀请回答嘻嘻爱哈哈该类别下有 28 个回答。邀请回答 haikitty 该类别下有 28 个回答。邀请回答 pol666 该类别下有 27 个回答。邀请回答 xiuzhen122 该类别下有 27 个回答。邀请回答 ueywyrsdfs 该类别下有 26 个回答。邀请回答 lhly23 该类别下有 25 个回答。邀请回答举报倪辰曦相关推荐 • 如何找PIC18F集成电路 1148 • PIC18F怎么做2线SPI总线？ 1256 • 为什么8位开发板不支持PIC18F系列？ 1171 • PIC18F有几种不同的闪烁方法 2170 • 为PIC18F创建程序下载什么编译器 3060 • PIC18F定时器的预加载周期寄存器？ 1063 • 请问有谁能指导方针来为PIC18f设备生成引导加载程序代码吗？ 1123 • 使用XC8在PIC18F中编程与使用HTC的PIC16F877A相同吗？ 1781 • RN4871在两个PIC18F之间怎么进行P2P数据传输 1086 • 各种PIC18F版本的（E）CCP之间有何区别？ 3445 3个回答

答案对人有帮助，有参考价值 0 你的问题是WDT导致了一个不象陷阱或ISR的重置。虽然您可以检测到重置是由WDT引起的，但是您没有调用堆栈或类似程序来帮助您确定发生WDT重置时MCU的状态。您可能能够创建用于保持代码当前状态的持久全局变量（或两个）。比如-在函数“X”中，在ISR“y”中，“在主循环中空闲”等。通过使变量持久化，它不会被运行时代码重置（假设您正在用C编程），并且在WDT重置的“main”的开始有一个测试权限，并使用它来设置断点，可以看到这些持久变量的状态，并开始了解发生了什么。不是100%有效，但是它可以给你一些想法。苏珊以上来自于百度翻译以下为原文 The issue you have is that the WDT causes a reset which is not like a trap or ISR. While you can detect the fact that the reset was caused by the WDT, you don't have a call stack or similar to help you determine the state of the MCU when the WDT reset occurred. You might be able to create a persistent global variable (or two) that you use to keep the current state of your code. Something like - In function 'X', In ISR 'y', 'Idling in the main loop' etc. By making the variable persistent, it will not be reset by the runtime code (assuming you are programming in C) and by having a test right at the start of the 'main' for the WDT reset and using that to set a breakpoint, you can see the state of those persistent variables and start to get an idea of what happened. Not 100% effective but it can give you ideas. Susan

2019-7-4 09:50:47 评论举报薄坤坤

答案对人有帮助，有参考价值 0 谢谢，真的很有帮助！同样发现问题：当等待设置TMRxIF标志时，它挂起，但是由于另一个问题，计时器可能被意外地禁用。这发生在中断发生时，直接在主循环设置某个内存地址之后。主循环要做的下一件事是禁用中断，但是在此之前，isr有机会弄乱刚刚设置的地址，最终导致对T2CON寄存器（可能还有其他寄存器）的不希望的写入！… 以上来自于百度翻译以下为原文 Thanks, that's helpful indeed! Found the issue too: it hangs when waiting on a TMRxIF flag to be set, but due to another issue said timer can be unintendedly disabled. That happened when my interrupt occurs, directly after the main loop sets up a certain memory address. The very next thing the main loop does is disable interrupts, but before that the isr has a chance to mess up the address that was just set up, ultimately causing an unwanted write to the T2CON register (and probably others!)...

2019-7-4 10:08:34 评论举报李木木