Technical OverviewFAQ'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 |
|
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:
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 may appear when running gmake: GMAKE.EXE: *** No targets specified and no makefile found. Stop. GMAKE.EXE: Nothing to be done for `prog.xxx’. Check to see that there is a makefile in the working directory. If not, copy or create a makefile in the appropriate directory. The product distribution provides makefiles for the gmake utility that can be used as a template. If there is a makefile, check the makefile to make sure the file name is not all capitalized. Gmake looks for makefile or Makefile, and it does not recognize MAKEFILE unless it is specified with the -f switch. Typing gmake -f MAKEFILE or renaming, MAKEFILE to makefile or Makefile will solve this problem. 3. The following error message may appear when running gmake: GMAKE.EXE: *** [executable name] Error 32767 A previous version of the same executable is currently loaded in the TI or Code Composer debugger. The debugger is locking the COFF file that is loaded, Windows 95 will not let you remove it and replace it with a new one. To solve this problem, load a different executable in the debugger, or close the debugger. 4. The following error message may appear when running gmake: Out of environment space The DOS environment space may need to be increased. Refer to the `Environment Variables` section of Chapter 1 in your Getting Started Guide. You may need to increase your DOS environment space to define these variables and to use the gmake makefiles provided with the examples. You can do this by right-clicking the shortcut you use to open MS-DOS Prompt windows. Choose Properties from the pop-up menu. Go to the Memory tab and set the Initial Environment to 4096. If you do not use a shortcut to open MS-DOS Prompt windows, use the File Explorer to find and right-click the command.com file. This file is normally located in c:\windows\. 5. 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. |