TI Santa Barbara - BIOSuite FAQ

   Technical Overview
   FAQ's
          Installation
          Board Support
          Custom Hardware
            Configuration
          DSP Compiler, Assembler,
            Linker
          Scope Tools
          Configuration Tools
          Error Messages
          DSP/BIOS Kernel API
          C54x
   Tech Support Request Form
   Press Release

Scope Tools:

1. The following error message appears when trying to load a program in BIOScope:

Cannot communicate with DSP board. Verify I/O settings and check for conflicts with other boards in your system. Reset the DSP board and try again.

If you have changed the default settings of the I/O map switches on the target board; you may need to define an environment variable. BIOScope goes though the following sequence to locate the board’s I/O address:

Checks the command line –p option
Checks D_OPTIONS environment variable (TI tools)
If no board I/O addresses have been found, it uses the default value of the board.

Example, the board I/O address is set to 0x320. You can pass a command line parameter to scope to specify the I/O address of the board. You can include this in a Windows 95 shortcut or invoke scope from the command line, e.g.,

scope.exe –p 320

Or enter the following environment variable in your autoexec.bat:

set S_OPTIONS=-p 320

You can refer to the board documentation for further information on D_OPTIONS. Also, refer to Chapter 1 'Environment Variables' in your Getting Started Guide and the PRODUCT RELEASE NOTES for additional information on environment variables.

If the steps described above do not resolve the problem, the hardware might be conflicting with some other board. Check the I/O settings for the other devices in your computer to see if there are any conflicts.

2. The following error message appears when running a program in BIOScope that is loaded in the debugger:

The target processor is busy.

If you are using BIOSuite, check to see if both BIOScope and the debugger are running. Since both BIOScope and the debugger use the JTAG connection to load, start and stop the target, you need to keep these tools synchronized in their knowledge of the state of the DSP. Refer to Appendix A `Debugger Interaction` in the User’s Guide for more details.

The following can be done in BIOScope to monitor a DSP program at the same time as the debuggers from TI or GoDSP are being used.

Choose the Optionsà LOG menu item. Set the polling rate to zero (0). Also, set the polling rate to zero for the Optionsà STS and Optionsà Trace State menu items. In BIOScope, you can right-click on a log, statistics, or trace window to manually update the display when the program is running free in the debugger.

If you are using the XDS510 emulator configuration (BIOSuite), you must exit BIOScope before running the debugger or vice-versa.