I have my entire development environment hang when I press F10 to step through a call to VDK::Sleep(). Is this expected behavior for the tool?
is it possible that you have 'Mask interrupts during step' enabled under 'Settings: Target Options'? VDK Sleep uses a timer interrupt to determine how long has passed, so disabling interrupts in this way would stop this function working correctly during a step. If that is the case, you would need to place a breakpoint after the call, or use the 'Run to Cursor' option.
no, this is not expected behaviour. Can you provide an example and details of your environment: VisualDSP++ version (e.g. VisualDSP++ 5.0 Update 9.1), target and emulator (e.g. BF537 EZ-KIT Lite/Custom Board via HPUSB-ICE).
My Visual DSP++ environment is v 18.104.22.168, IDE is 22.214.171.124. The target is Blackfin BF537. It is on a custom board, and I'm connecting with ADDS-HPUSB-ICE.
I'm not sure how to send an example since our application includes a custom FPGA, etc. I suppose there is something about my application that is related to this strange behavior.
Currently, my workaround is when stepping through code, if I notice I'm about to step through a call to VDK::Sleep(), I'll set a break point after the function call and hit F5. This way, I get past the call to Sleep() and hit the breakpoint as expected.
Of course! That's it. duhhhh
Hmmm... After my IDE crashed (see http://ez.analog.com/message/23760#23760), the "Mask interrupts during step" environment setting was disabled. In this case I still fail to step through calls to VDK::Sleep. There could be something else going on besides mask interrupts.
I'm not really too worried about it though. At this point I know how to work around it.
Thanks for the follow up. Unfortunately, using a simple example (like the Dining Philosophers VDK example) I haven't been able to reproduce this with 'Mask interrupts during step' disabled; with it enabled, I can see the same behaviour.
If you are able to provide an example for us to take a closer look at, could I direct you to private support:
If you are happy to continue with the workaround of run to cursor/breakpoints; our apologies for the inconvenience.
My project is running on a custom board, so it would be hard for you to run my application. I'm certainly ok with the workaround now.
Retrieving data ...