Debugging LabVIEW/Blackfin application is VERY SLOW...

[LRoy]

Hey guys,

I am working through the evaluation example programs for LabVIEW Embedded for Blackfin, and I'm using various debug channels (instrumented, non-instrumented), but I do not have an emulator....

I have found that the debugging (breakpoints, single-stepping, etc.) is extremely slow and painful....is this a non-issue with an emulator ($4000!)?

I can't see where debugging with the non-emulator channels is practical....I'm hoping that an emulator (ADI-HPUSB-ICE or equivalent) solves the problem and behaves more like a local debugger when single-stepping and such...

Does anyone have any experience with development and debug using an emulator vs. the slower speed intrusive debug methods?

Thanks,

Larry

[Michael.Phillips]

Hi Larry,

It is true that instrumented debugging can have a significant performance impact, especially if you have many controls/indicators on your front panel. To improve performance, you can use TCP debugging, which is higher speed than serial debugging, or you can use a JTAG emulator. The HPUSB-ICE emulator is much faster than the built-in USB JTAG emulator, so you will see faster debugging performance with that.

[LRoy]

Ok...that's what I thought.  I am only early in the eval phase, so I don't think I can justify the $4k for the emulator, but I'm going to be at a training class Thur and again next Tues where LabVIEW and Blackfin is going to be the subject....so maybe the presenter will be using an emulator and I'll be able to get a feel for the debugging improvements when using JTAG emulation.

Thanks for the reply!

[LRoy]

Guys,

I am using a laptop with a wireless connection as well as a wired ethernet connection.  The secret to debugging using ethernet on the EZkit with this configuration is:

1. Set the wired ethernet port addr to a fixed IP.  I am using 192.168.0.1 on my laptop.

2. Run a DHCP server to serve up a fixed IP for the EZ-Kit.  I use 192.168.0.2 for the EZ-Kit.

3. Disable the wireless adaptor, so that the debugger code definitely connects using the correct adaptor (IP).

4. Disable the Windows Firewall in Control Panel (not really needed, since wireless is disabled now).

Now, change the LabVIEW project options to use Instrumented debugging using TCP/IP.

Having done these things, debugging using TCP/IP is very close to debugging a normal windows-based LabVIEW program...very fast indeed!

[eric.atherton]

Do you have more details of how you set up your project?  I tried using the Debug Method of TCP/IP, and is stops working after a small period of time.

-  Do you have a dedicated Hub for your laptop and the Blackfin, or are you using a X-Over cable?
-  What options do you have selected in your LVE Project?

[LRoy]

Hey,

I use the yellow crossover cable that came with my EZ-Kit.

As I stated earlier, I make sure that the only ethernet connection that is "live" is the one connected to the EZ-Kit.

I use the Processor Status window to view the current state of the connection with the board.   Sometimes, I find that I have to press the Debug button on the project window, then Cancel the connection to get the board to HALT.  I have reached a point where I don't need to hard-reset or unplug the board very often.

I have attached screen shots of the Build Options panels that I am using now.

Hope this helps,

Larry