| Line 4... |
Line 4... |
|
|
===============================================================================
|
===============================================================================
|
-- Description --
|
-- Description --
|
===============================================================================
|
===============================================================================
|
A console application implementing a GDB stub and and communication with an
|
A console application implementing a GDB stub and and communication with an
|
OpenRISC processor system via a USB debug cable.
|
OpenRISC processor system via the OpenCores USB debug cable.
|
===============================================================================
|
===============================================================================
|
-- Versions --
|
-- Versions --
|
===============================================================================
|
===============================================================================
|
0.1.0 090201 jb@orsoc.se
|
0.1.0 090201 jb@orsoc.se
|
0.1.1 090304 jb@orsoc.se
|
0.1.1 090304 jb@orsoc.se
|
0.1.2 090511 jb@orsoc.se
|
0.1.2 090511 jb@orsoc.se
|
0.1.3 090604 jb@orsoc.se
|
0.1.3 090604 jb@orsoc.se
|
0.1.4 090828 jb@orsoc.se
|
0.1.4 090828 jb@orsoc.se
|
0.1.5 090903 jb@orsoc.se
|
0.1.5 090903 jb@orsoc.se
|
0.1.6 110307 jb@orsoc.se
|
0.1.6 110307 jb@orsoc.se
|
|
0.1.7 110308 jb@orsoc.se
|
===============================================================================
|
===============================================================================
|
-- Installation --
|
-- Installation --
|
===============================================================================
|
===============================================================================
|
|
|
The OR debug proxy application runs on multiple platforms only requiring
|
The OR debug proxy application runs on multiple platforms only requiring
|
| Line 97... |
Line 98... |
to enable a high-speed JTAG interface with our hardware we require newer,
|
to enable a high-speed JTAG interface with our hardware we require newer,
|
specialised drivers from FTDI called the D2XX drivers.
|
specialised drivers from FTDI called the D2XX drivers.
|
|
|
The Linux driver can be obtained from FTDI Chip's website,
|
The Linux driver can be obtained from FTDI Chip's website,
|
http://www.ftdichip.com, and is found under the links to "Drivers" and then
|
http://www.ftdichip.com, and is found under the links to "Drivers" and then
|
"D2XX". At the time of writing, the latest version was libftd2xx 0.4.16 and
|
"D2XX".
|
could be downloaded directly off their site from
|
|
http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx0.4.16.tar.gz
|
|
|
|
Statically linked driver:
|
Statically linked driver:
|
|
|
The simplest way to enable these drivers is to link the application
|
The simplest way to enable these drivers is to link the application
|
statically - that is, have a copy of the driver along with the debugging
|
statically - that is, have a copy of the driver along with the debugging
|
| Line 119... |
Line 118... |
This will result in the executable being statically linked to the driver file
|
This will result in the executable being statically linked to the driver file
|
in the the lib/ folder.
|
in the the lib/ folder.
|
|
|
Dynamically linked driver install directions:
|
Dynamically linked driver install directions:
|
|
|
Uncompress the driver package (tar xzvf libftd2xx0.4.16.tar.gz) and read the
|
Uncompress the driver package (tar xzvf libftd2xxX.Y.Z.tar.gz) and read the
|
file "readme.dat" located inside, but don't complete their way of installing
|
file "readme.dat" located inside, but don't complete their way of installing
|
yet. Their installation method should be modified slightly to allow easier use
|
yet. Their installation method should be modified slightly to allow easier use
|
of the USB device by users. Read the following before performing the install
|
of the USB device by users. Read the following before performing the install
|
as per the instructions in "readme.dat", and amend their installation process
|
as per the instructions in "readme.dat", and amend their installation process
|
as you go.
|
as you go.
|
