JTAG Debugging

Name

JTAG Debugging -- Using System Navigator

Overview

The SEAD 3 board can be debugged using the System Navigator JTAG probe. This consists of the probe itself plus the Navigator Console software. The Navigator Console should be installed onto your host system according to the "MIPS Navigator Console Getting Started Guide". To do this you need to obtain a license from MIPS. For Linux users, the Navigator Console version 4.0.16 currently only installs on RedHat Enterprises Linux. Once the console software is installed, connect the System Navigator to the host.

Setup for standard eCosPro GNU tools

To use the System Navigator from GDB, the Navigator Console must be started independently. The Navigator Console must be supplied with a startup script which can be chosen at startup, or supplied on the command line. Choose either mips_m14k.tcl for the LX150, or mips_m14kc.tcl for the LX110/LX155. When started correctly, the console window will appear and show something similar to the following:

Main console display active (Tcl8.5.6 / Tk8.5.6)
mips_m14k initialization successful.
(scripts) 1 %
    

In addition, for Linux you should add the path to the Navigator Console binaries directory to your library load path. For example, add the following line to your .bashrc:

export LD_LIBRARY_PATH=~/MIPS/NavigatorConsole/bin:$LD_LIBRARY_PATH
    

Download and install the Sourcery CodeBench Lite tools for MIPS ELF. It is sufficient to just download the TAR archive as this download is solely required to obtain the mips-sde-elf-sprite tool. Place the "bin" directory for those tools (containing mips-sde-elf-sprite) in your shell's PATH environment variable, making sure it comes after the PATH component for the eCosPro GNU tools so that the eCosPro tools are still preferred.

Connect to the target from GDB by using the following connection command at the GDB console:

(gdb) target remote | mips-sde-elf-sprite -q -a 'mdi:/1/1?rst=5&lib=/home/USER/MIPS/NavigatorConsole/bin/libsysnav_mdi.so'
substituting in the correct location for the libsysnav_mdi.so as required.

Consult the Navigator Console documentation NavConGdbGuide.pdf for further guidance on use with GDB.

Setup for CodeSourcery tools

While eCosCentric no longer recommend using the CodeSourcery tools (other than to obtain the mips-sde-elf-sprite tool), this documentation has been preserved in case some users decide they do wish to use those tools.

To use the System Navigator from GDB, the Navigator Console must be started independently. The Navigator Console must be supplied with a startup script which can be chosen at startup, or supplied on the command line. Choose either mips_m14k.tcl or mips_m14kc.tcl for the LX50 and LX110 respectively. When started correctly, the console window will appear and show something similar to the following:

Main console display active (Tcl8.5.6 / Tk8.5.6)
mips_m14k initialization successful.
(scripts) 1 %
    

To use the System Navigator from GDB, GDB must be supplied with the name of a dynamic library to load, and the location to load it from. This is best done from a .gdbinit file. For Window this should contain:

set mdi library C:\MIPS\NavigatorConsole\bin\sysnav_mdi.dll
set mdi target 1
set mdi connectreset 7
    
And for Linux:
set mdi library libsysnav_mdi.so
set mdi connectreset 7
set mdi target 1
    

In addition, for Linux you should add the path to the Navigator Console binaries directory to your library load path. For example, add the following line to your .bashrc:

export LD_LIBRARY_PATH=~/MIPS/NavigatorConsole/bin:$LD_LIBRARY_PATH
    

With these files set up it should be possible to start GDB and connect by giving the following command:

(gdb) target mdi 1:1
Selected device jtagindex-0 on MIPS mips_m14k
Connected to MDI target
(gdb)
    

GDB should now be ready to download and debug a JTAG startup application.

2017-02-09
Documentation license for this page: eCosPro License