[问答]

是什么原因引起的MPLABX 3.20上的模拟问题

问答对人有帮助，内容完整，我也想知道答案 0 我正在研究PIC16F688，并使用MPLAB 8.92运行仿真，当时这两个文件都是使用Project-->Quickbuild构建的。自从将两个.ASM文件移动到一个新的项目中，它们就可以很好地建立起来。当我运行模拟时，我看到模拟看门狗超时，如果我停止模拟器，我会得到“在当前PC 0x0上没有找到源代码行”。运行W0004-CORE：看门狗定时器已经导致重置。没有许可。所以我将描述我的项目设置。当处理器运行在4MHz时，我认为指令频率是1MHz。不确定RC振荡器用于什么。项目特性-->仿真-->振荡器选项-->指令频率：1项目特性-->仿真-->振荡器选项-->频率输入：MhzProject特性-->仿真-->振荡器选项-->RC振荡器频率：250Project Properties-->.-->振荡器选项-->RC振荡器频率In:Khz Project Properties-->Looad:选中“编程时加载符号...”。主要工具栏选项:Tools-->Options-->Miscell.-->Files-->File Extension:asmMy问题搜索使waTCHEFE超时成为可能的候选人，但我不确定到底是什么引起了这个问题。我也无法得到一个反汇编列表，如显示“无法生成反汇编列表文件”。我错过了什么显而易见的东西？谢谢，John C. 以上来自于百度翻译以下为原文 I'm working on a PIC16F688 and have run simulations using MPLAB 8.92 when the two files were built using the Project-->Quickbuild. Since moving the two .asm files into a new project they build fine. When I run the simulation I see the simulation watchdog timing out and if I stop the simulator I get "No source code lines were found at current PC 0x0". Running W0004-CORE: Watchdog Timer has caused a Reset. MPLABX 3.2 mpasm v5.65 I'd like to post the some screen snip's but for some reason I still don't have permission. So I'll describe the project settings I have. The Instruction Frequency I would think is 1Mhz as the processor runs at 4Mhz. Not sure what the RC Oscillator is for. Project Properties-->Simulation-->Oscillator Options-->Instruction Frequency: 1 Project Properties-->Simulation-->Oscillator Options-->Frequency In: Mhz Project Properties-->Simulation-->Oscillator Options-->RC Oscillator Frequency: 250 Project Properties-->Simulation-->Oscillator Options-->RC Oscillator Frequency In: Khz Project Properties-->Loading: Checked "Load symbols when programming....." Main toolbar options: Tools-->Options-->Miscellaneous-->Files-->File Extension: asm My problem searches make the watchdog timeout to be the likely candidate but I'm not sure what is really causing the issue. I also can't get a disassembly listing as is shows "Unable to generate the disassembly listing file. " Anything obvious I'm missing? Thanks, John C. 0
2019-7-15 07:39:23　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × qun333 该类别下有 57 个回答。邀请回答技术发广告该类别下有 56 个回答。邀请回答 caoguiqun 该类别下有 56 个回答。邀请回答 psw30 该类别下有 44 个回答。邀请回答伊丹姿子该类别下有 41 个回答。邀请回答 uwufwjrw 该类别下有 39 个回答。邀请回答 hetao1111 该类别下有 38 个回答。邀请回答 lc123617 该类别下有 35 个回答。邀请回答欧阳大大该类别下有 32 个回答。邀请回答作死不止该类别下有 31 个回答。邀请回答 asd010 该类别下有 31 个回答。邀请回答 60user92 该类别下有 29 个回答。邀请回答 wy8719 该类别下有 29 个回答。邀请回答 haikitty 该类别下有 28 个回答。邀请回答 ju978779 该类别下有 28 个回答。邀请回答嘻嘻爱哈哈该类别下有 28 个回答。邀请回答 xiuzhen122 该类别下有 27 个回答。邀请回答 pol666 该类别下有 27 个回答。邀请回答 ueywyrsdfs 该类别下有 26 个回答。邀请回答 lhly23 该类别下有 25 个回答。邀请回答举报李珏相关推荐 • MPLABX V3.20问题，调试时挂了很多 864 • MPLABX 3.20 Java SE二进制文件停止工作 1000 • MPLABX3.20寄存器变更时中断怎么回事 1593 • 是否可以关闭MPLAB X 3.20的断点识别功能？ 1240 • AD7606上电发热是什么原因引起的？ 262 • AD9446上电3.3V后电源噪声大是什么原因造成的？ 247 • PCB镀锡时电不上锡是什么原因？ 1303 • AD7195正常工作后，在模拟输入端空载的时候会有周期的尖峰出现是什么原因？ 386 • MPLABX模拟器之间存在哪些周期差？ 2468 • 行行为模拟时vivado 2013.2报告了错误是什么原因？ 1626 2个回答

答案对人有帮助，有参考价值 0 嗨，丹，开始你的项目，用我的代码交换了main.asm和user.asm（重命名为相同的文件）。看门狗正在导致模拟中断，但我仍然没有拆卸文件。在MPLAB的快速建设下，这一切都运行得很好。我还发现，如果我在MPLAB（vs. MPLABX）中创建一个新项目，并使用相同的文件，我会遇到问题。John C. 以上来自于百度翻译以下为原文 Hey Dan, Took your project and swapped your main.asm and user.asm with my code(renamed my files to be the same.) Recompiled it and got the same thing. The watchdog is causing the simulation to break but I still get no disassembly file. It all runs very well under the quickbuild in MPLAB. I also found that if I create a new project in MPLAB(vs. MPLABX) and use the same files I have problems. John C.

2019-7-15 08:09:02 评论举报罗颖

答案对人有帮助，有参考价值 0 “当前PC...”消息通常意味着模拟器或调试器已经停止，而PC指向代码未覆盖的区域（汇编器或C或其他）。通常这种情况发生在你停止在库函数或类似函数内部时。0是重置向量，通常包含“goto”到“real”代码的开头（因为中断和其他向量随后直接出现，这取决于架构）。让你知道WDT触发了。当这种情况发生时，设备执行重置，使PC机回到0。因此，关闭WDT（根据设备如何进行配置，在配置选项或代码中），问题就会消失。但是，真正的处理器只需要重新启动，并且您需要对初始测试进行编码，以查看WDT是否导致重置或上电或其他情况。我纯粹是在猜测，但是模拟器可以很好地识别这种情况并停止，因为典型的WDT超时意味着发生了可怕的错误。以上来自于百度翻译以下为原文 The 'no code at current PC...' message typically means that the simulator or debugger has stopped with the PC pointing to an area that is not covered by your code (assembler or C or whatever). Typically this occurs when you stop inside a library function or similar. The PC of 0 is the reset vector and generally contains a 'goto' to the start of the 'real' code (as the interrupt and other vectors come straight afterwards, depending on the architecture). Also in this case the message is telling you that the WDT triggered. When that happens the device performs a reset which takes the PC back to 0. Therefore turn off the WDT (either in the config options or code depending on how your device does this) and the problem will go away. I don't know in the case of the simulator (George - this is your cue to enter the discussion) but a real processor wold simply restart and you would need to code up the initial tests to see if the WDT had caused the reset or a power-up or whatever else. I'm purely guessing but the simulator may well recognise this situation and stop as typically a WDT timeout means something has gone horribly wrong. Susan

2019-7-15 08:34:53 评论举报薄坤坤