|
Has anyone had experience with the VDSP emulator when you hit a break point and then an interrupt happens? Will the VDSP continue to single step, or does the pc get "stuck"? Thanks for any info! Patience, persistence, truth, Dr. mike |
|
|
VDSP response to interrupts
Started by ●May 22, 2003
Reply by ●May 22, 20032003-05-22
|
Hi Mike If you mean the VisualDSP++ Emulation process on your PC (i.e. not an ICE), then everything stops on a breakpoint because the PC is emulating DSP Instructions (about 10,000 times slower) on your x86 CPU. When you continue from the break point (i.e. single step), any interrupts like a timer due should then fire, and you may not immediately reach the next instruction you were expecting! Btw, the PC Emulation process has a great advantage over an ICE (apart from the lack of speed) in that allows you to step into instructions after a delayed (I prefer 'deferred') branch. The ICE won't do this as jumps aren't allowed in jump delay instructions as they would break the pipeline. Cheers, Andy Coles Electronic Navigation Limited 65 Gaunt Street Westhaven Auckland New Zealand -----Original Message----- From: drmike8888 [mailto:] Sent: Friday, 23 May 2003 01:34 To: Subject: [adsp] VDSP response to interrupts Has anyone had experience with the VDSP emulator when you hit a break point and then an interrupt happens? Will the VDSP continue to single step, or does the pc get "stuck"? Thanks for any info! Patience, persistence, truth, Dr. mike _____________________________________ Note: If you do a simple "reply" with your email client, only the author of this message will receive your answer. You need to do a "reply all" if you want your answer to be distributed to the entire group. _____________________________________ About this discussion group: To Join: Send an email to To Post: Send an email to To Leave: Send an email to Archives: http://groups.yahoo.com/group/adsp Other Groups: http://www.dsprelated.com/groups.php3 ">http://docs.yahoo.com/info/terms/ |
|
|
Reply by ●May 22, 20032003-05-22
|
Thanks for the reply Andy. I'm interested in how the ICE responds in real world situations. I can see how the simulator would be an advantage here, but sometimes the real world behaves differently than is possible to simulate! Patience, persistence, truth, Dr. mike On Fri, 23 May 2003, Andy Coles wrote: > Hi Mike > > If you mean the VisualDSP++ Emulation process on > your PC (i.e. not an ICE), then everything stops > on a breakpoint because the PC is emulating DSP > Instructions (about 10,000 times slower) on your > x86 CPU. When you continue from the break point > (i.e. single step), any interrupts like a timer > due should then fire, and you may not immediately > reach the next instruction you were expecting! > > Btw, the PC Emulation process has a great > advantage over an ICE (apart from the lack of > speed) in that allows you to step into instructions > after a delayed (I prefer 'deferred') branch. The > ICE won't do this as jumps aren't allowed in jump > delay instructions as they would break the pipeline. |
Reply by ●May 22, 20032003-05-22
|
--- In , "drmike8888" <eresrch@e...> wrote: > Has anyone had experience with the VDSP emulator when you > hit a break point and then an interrupt happens? Will the > VDSP continue to single step, or does the pc get "stuck"? I'm not sure I understand the *exact* scenario you are describing. I've had the emulator receive interrupts just after it hits a breakpoint. When I single step, it goes into the ISR. If the IRQ happens at a high rate, I can never single step out of the line of code where the breakpoint is - it keeps going into the ISR. If it is a single IRQ, then I can continue single stepping through my code. Hope this helps... Cheers Bhaskar > > Thanks for any info! > > Patience, persistence, truth, > Dr. mike |
|
|
Reply by ●May 23, 20032003-05-23
|
On Thu, 22 May 2003, bhaskar_thiagarajan wrote: > I'm not sure I understand the *exact* scenario you are describing. > I've had the emulator receive interrupts just after it hits a > breakpoint. When I single step, it goes into the ISR. If the IRQ > happens at a high rate, I can never single step out of the line of > code where the breakpoint is - it keeps going into the ISR. If it is > a single IRQ, then I can continue single stepping through my code. > > Hope this helps... Thanks Bhaskar, That is *exactly* what I wanted to know! That helps me a lot. Your response is very much appreciated. Patience, persistence, truth, Dr. mike |
