Flyswatter2 RouterStationPro How To
- 1 Connecting the Flyswatter2 and the RouterStation Pro
- 1.1 Connect the MIPS JTAG Adapter Board to the Flyswatter2.
- 1.2 Connect the 14-pin ribbon cable to the Adapter Board.
- 1.3 Connect the Other End of the Ribbon Cable to the RouterStation Pro.
- 1.4 Connect the RS-232 Serial Cable.
- 1.5 Connect the USB Cable to the Flyswatter2.
- 1.6 Connect the CAT6 Cable to the Power Over Ethernet Injector.
- 1.7 Connect the Power Adapter to the Power Over Ethernet Injector.
- 1.8 Connect the Other End of the CAT6 Cable to the RouterStation Pro.
- 1.9 Plug the Power Adapter into a Wall Outlet.
- 1.10 Plug the USB Cable into your PC.
- 2 Installing OpenOCD
- 3 Running OpenOCD
- 4 Common OpenOCD Commands
- 5 GDB Debugger
Connecting the Flyswatter2 and the RouterStation Pro
To hook up the Flyswatter2 and the RouterStation Pro, you will need:
- 20-pin ARM to 14-pin MIPS JTAG Adapter Board
- USB Male A/Male B Cable
- 14-pin JTAG Ribbon Cable
- RS-232 Serial Cable with two female connectors
- CAT6 Cable
- Power Over Ethernet Injector (with power cable)
The items listed under RouterStationPro are included with the MIPS Linux Starter Kit.
Connect the MIPS JTAG Adapter Board to the Flyswatter2.
Connect the 14-pin ribbon cable to the Adapter Board.
Connect the Other End of the Ribbon Cable to the RouterStation Pro.
Connect the RS-232 Serial Cable.
Connect the USB Cable to the Flyswatter2.
Connect the CAT6 Cable to the Power Over Ethernet Injector.
Connect the Power Adapter to the Power Over Ethernet Injector.
Connect the Other End of the CAT6 Cable to the RouterStation Pro.
Plug the Power Adapter into a Wall Outlet.
The green LEDs on the RouterStation Pro should briefly flash, and the leftmost LED should remain on.
Plug the USB Cable into your PC.
The green power LED on the Flyswatter2 should come on and remain on.
OpenOCD (Open On-Chip Debugger) is open-source software that interfaces with the Flyswatter2. OpenOCD provides debugging and in-system programming for embedded target devices. You will need to compile OpenOCD from source, and patch the source with one of the OpenOCD Patches for Flyswatter 2 support.
Whichever guide you use, be sure to install the patch! Both guides include instructions on downloading and installing the patch.
Compiling OpenOCD Linux - This set of instructions uses libFTDI, an open-source driver library for FTDI devices.
Now you are ready to run OpenOCD. If you installed the OpenOCD Ubuntu package, open a terminal window and type the following from any directory:
openocd -f interface/flyswatter2.cfg -c "jtag_khz 15000" -f target/ar71xx.cfg
If you compiled OpenOCD yourself, navigate to the openocd-bin directory you created in the compile guide and type:
cd ~/openocd-bin sudo ./openocd -f interface/flyswatter2.cfg -c "jtag_khz 15000" -f target/ar71xx.cfg
Your terminal window should now look something like this:
You cannot enter commands directly to OpenOCD. Open a new terminal window and type:
telnet localhost 4444
You will should see this prompt:
You can give commands to OpenOCD through this prompt.
Common OpenOCD Commands
To see a full list of OpenOCD commands, enter help in the telnet window.
Resets the Flyswatter2. The output of the Reset command should look like this:
Sends a halt request to the Flyswatter2. If the Flyswatter2 halts, you will see text output in the telnet window. (If the Flyswatter2 is already halted, you will see no output.)
You can also use halt followed by a time in milliseconds. OpenOCD waits for the target to halt the specified amount of time, then gives up if the target has not halted. You can use this to avoid OpenOCD hanging because the Flyswatter2 fails to halt. For example, to send a halt command with a timeout of one second, type:
Enter resume to end a halt. You will not see any text output in the telnet window.
Displays a numbered list of all of the Flyswatter2's registers.
If the board is not halted, the list of registers will be displayed but not their values.
Run reg with a register number to display the contents of a register, in hexadecimal. The register number corresponds to the output of the reg command with no arguments, above. You must run the halt command before reading registers.
If you run reg while the Flyswatter2 is not halted, you will still see the value stored in the register. However, registers change contents very quickly while the device is running; by the time you see the value, the value actually in the register may be different. If you try to run reg while the device is not halted, you will see this:
Note that the RouterStation Pro does not show any warning if you run the reg command while the board is running.
reg [entry] [value]
Sets the value of a register. The register number corresponds to the output of the reg command with no arguments, above. Make sure the Flyswatter2 is halted (with the halt command) before you change the value of a register!
You can enter registry values in either decimal, by typing a number by itself, or in hexadecimal, by prefacing the value with 0x.
GDB, the GNU Project Debugger is a debugging tool provided with the GNU Compiler Collection (GCC). GDB allows you to stop and start a running program, examine its functioning, and make changes. GDB is installed on Ubuntu 10.04 by default, but you will need a different version of GDB build for embedded targets. Follow the instructions on the GDB Debugger page below.
The GDB debugger page will walk you through installing GDB for use with OpenOCD, and loading and testing a simple program.