Even with an emulator / visionCLICK connection to a target board, it is sometimes desirable to not download the vxWorks image via the emulator connection but rather to allow the existing bootrom / FTP to download the image while maintaining the ability to debug it with the tool.

This has the added advantages:  

1. It works exactly the same as if the board runs on its own.  

2. No register file is required for the tool in order to configure the memory controller / RAM for file downloading.

---

 

Here is the procedure.

Project window set up:  

Symbol File: Specify the vxWorks.ab file which is converted from the vxWorks image to be debugged.  
Download File: None.
Source Paths: None or the correct paths to the source files.
Reset symbol: None.

Note that only the main debugging feature project fields were addressed above.  Any of the connection fields (microprocessor, target control, etc.) will also need to be filled in as necessary.
  
Each time a new image is built, convert the new vxWorks image to create a new symbol file and use File Read a Symbol File to load the vxWorks.ab file.

From the Terminal window, type in this command:  

inn;ihbc 100000;go

The above command is actually three commands on one line.  'inn' resets the processor. 'ihbc 100000' sets an internal hardware breakpoint at the address 0x100000, assuming this is the starting address of the image. 'go' starts the processor (from the reset vector).

Putting all 3 commands in one line is to execute them altogether quickly. This can avoid the problem that some processors with watchdog timers would timeout shortly after a reset.
  
Once this breakpoint is hit, the image has been downloaded. And you should see this:  

BKM> inn;ihbc 100000;go  
>RUN>  

!BREAK! - [msg11001] Internal hardware breakpoint; PC = 0x00100000  
BKM>  

Remove this breakpoint:

BKM> rb  

Now click on the Source window and hit the ESC key to force a refresh of the window. You should see that it displays the code and symbols at 0x00100000. You are free to debug from the GUI from this point on, such as setting other breakpoints, step, run, etc.