|
Hi All, I'm using EZ-ICE emulator with 2183 processor. after downloading my prog into the emulator and ginen run command to the emulator, emulator executes only one instruction at 0x0 and halts, if many times run command is given then it starts executing prog but stops at some location beyong my prog (This prog is automatically added after my prog). my prog is very simple there is no bug or any chance to jump at some location beyond my prog. this prog may breakpoint code of the emulator ( i'm not sure). to find where things goes wrong when using single stepping, prog control transfer after RTI instruction. If any body can tell why this is so happning & exactly from where prog code is added to my prog? Why prog execution halts after 1 instruction? along with this prog is also not responding to interrupt generated by INTE, why? Thanks in advance Amit __________________________________ |
Help for EZ-ICE 218X
Started by ●December 23, 2004
Reply by ●December 23, 20042004-12-23
|
On Thu, 23 Dec 2004, Jain Amit wrote: > Hi All, > I'm using EZ-ICE emulator with 2183 processor. after > downloading my prog into the emulator and ginen run > command to the emulator, emulator executes only one > instruction at 0x0 and halts, if many times run > command is given then it starts executing prog but > stops at some location beyong my prog (This prog is > automatically added after my prog). my prog is very > simple there is no bug or any chance to jump at some > location beyond my prog. this prog may breakpoint code > of the emulator ( i'm not sure). to find where things > goes wrong when using single stepping, prog control > transfer after RTI instruction. > If any body can tell why this is so happning & exactly > from where prog code is added to my prog? > Why prog execution halts after 1 instruction? > along with this prog is also not responding to > interrupt generated by INTE, why? Howdy Amit, I'm not familiar with the 2183, but you might try setting the program counter (PC) to the first instruction of your program and single stepping from there. If you use libraries or software break points, then the linker will add more code to yours. There should be a command to step over library calls, something like "next" instead of "step". That way you don't have to go thru stuff that's not yours. Debugging interrupts is difficult. Set break points inside the interrupt, and use the trick of masking all interrupts except for one to debug each one. When you have several at once, and the bug is an interaction between them, it's pretty hard to find. Easy to fix usually :-) Patience, persistence, truth, Dr. mike |
