Updated UrJTAG book

git-svn-id: https://urjtag.svn.sourceforge.net/svnroot/urjtag/trunk@1261 b68d4a1b-bc3d-0410-92ed-d4ac073336b7
master
Kolja Waschk 17 years ago
parent 60d85313e8
commit a3bed685b1

@ -6,7 +6,7 @@
DOXYFILE_ENCODING = UTF-8
PROJECT_NAME = urjtag
PROJECT_NUMBER = svn1258
OUTPUT_DIRECTORY = out
OUTPUT_DIRECTORY = htdocs/doxygen
CREATE_SUBDIRS = NO
OUTPUT_LANGUAGE = English
BRIEF_MEMBER_DESC = YES

@ -4,7 +4,7 @@
<book lang="en">
<bookinfo>
<title>Universal JTAG library, server and tools</title>
<date>2008-02-28</date>
<date>2008-05-27</date>
<author>
<firstname>Kolja</firstname>
<othername>Waschk</othername>
@ -12,7 +12,7 @@
</author>
<authorinitials>KW(</authorinitials>
<revhistory><revision><revnumber>1105</revnumber><date>2008-02-28</date><authorinitials>KW(</authorinitials></revision></revhistory>
<revhistory><revision><revnumber>1256</revnumber><date>2008-05-27</date><authorinitials>KW(</authorinitials></revision></revhistory>
</bookinfo>
<chapter id="_copyright">
@ -385,6 +385,11 @@ Atmel ATmega128 (partial support)
</listitem>
<listitem>
<simpara>
Atmel AT32AP7000 (partial support)
</simpara>
</listitem>
<listitem>
<simpara>
Broadcom BCM1250
</simpara>
</listitem>
@ -544,13 +549,13 @@ AMD Am29xx040B (Am29F040B, Am29LV040B)
<title>Required software for compiling UrJTAG</title>
<simpara>To run autogen.sh, you need autoconf and automake, bison, and a recent flex.</simpara>
<simpara>The distributed source tarball contains source pregenerated with a current flex
version; flex therefore is only needed if you want to compile code checked
out from our Subversion repository. Flex 2.5.4a as it comes with Cygwin will
work but some parts of UrJTAG (namely the SVF player) become more verbose if
Flex 2.5.31 or newer is used. Building the BSDL subsystem files requires Flex
2.5.33 or newer. The configure script will compare the available Flex version
against these preconditions and enables or disables the related features. ,</simpara>
<simpara>The distributed source tarball contains source pregenerated with a current
flex version; flex therefore is only needed if you want to compile code
checked out from our Subversion repository. Flex 2.5.4a as it comes with
Cygwin cannot build the scanners for BSDL and SVF. Building these files
requires Flex 2.5.33 or newer. The configure script will compare the available
Flex version against these preconditions and enables or disables the related
features.</simpara>
<simpara>Furthermore, libtool should be available, and "devel" versions of the following
packages:</simpara>
@ -656,9 +661,9 @@ without spaces in the name is better) and afterwards run configure with the
<literallayout class="monospaced">./configure --with-ftd2xx="/cygdrive/c/temp/ftdi-cdm-drivers"</literallayout>
<simpara>Configure should now report</simpara>
<literallayout class="monospaced">FTDI cable support
<literallayout class="monospaced">jtag is now configured for
...
via libftd2xx : yes</literallayout>
Detected libftd2xx : yes</literallayout>
</section>
<section id="_using_libusb_win32_in_cygwin_environment">
<title>Using LibUSB-Win32 in Cygwin environment</title>
@ -675,6 +680,31 @@ http://libusb-win32.sourceforge.net
might give problems if the path contains spaces, as "Program Files" does!):</simpara>
<literallayout class="monospaced">./configure --with-libusb="/cygdrive/c/Programme/LibUSB-Win32/"</literallayout>
</section>
<section id="_compiling_with_mingw">
<title>Compiling with MinGW</title>
<simpara>UrJTAG may be compiled into a Windows executable using the MinGW compiler
(http://www.mingw.org). This has the advantage over running in a Cygwin
environment that you don't need to install anything else but the jtag.exe.
However, because support for MinGW is quite new in UrJTAG, it may lack some
features (e.g. readline support) or run a little slower.</simpara>
<simpara>It is even possible to cross-compile and build the executable on a Linux
host:</simpara>
<literallayout class="monospaced">./configure --host=i586-mingw32msvc --with-ftd2xx=/tmp/cdm-drivers
make</literallayout>
</section>
<section id="_driver_tailoring">
<title>Driver tailoring</title>
<simpara>The configure script enables all default bus, cable and lowlevel drivers. You
can include and exclude specific drivers if required. For a list of parameters
run</simpara>
<literallayout class="monospaced">./configure --help</literallayout>
<simpara>to figure out the appropriate &#8212;enable-bus, &#8212;enable-cable and &#8212;enable-lowlevel
options.</simpara>
</section>
<section id="_building_the_bsdl_subsystem">
<title>Building the BSDL subsystem</title>
@ -1188,18 +1218,24 @@ modprobe parport_pc</literallayout>
<simpara>UrJTAG now also supports some USB cables. Unfortunately, there is no standard
for "JTAG over USB", so this support is limited to a few selected cables only.
For cables based on the FT2232 chip from FTDI, the cable command has to be
given cable name, driver name, and USB Vendor and Product ID of the cable:</simpara>
given cable name and optionally the driver name, USB Vendor, and Product ID of
the cable:</simpara>
<literallayout class="monospaced">jtag&gt; cable ARM-USB-OCD ftdi-mpsse 15ba:3</literallayout>
<simpara>For some cables, UrJTAG knows the VID:PID and you can just say ":"</simpara>
<literallayout class="monospaced">jtag&gt; cable ARM-USB-OCD vid=15ba pid=0003 driver=ftdi-mpsse</literallayout>
<simpara>For all known cables, UrJTAG knows the VID and PID so you can just say</simpara>
<literallayout class="monospaced">jtag&gt; cable JTAGkey ftdi-mpsse :</literallayout>
<simpara>On Windows, if UrJTAG was compiled to use the drivers supplied by
FTDI, the command should instead look like this:</simpara>
<literallayout class="monospaced">jtag&gt; cable ARM-USB-OCD</literallayout>
<simpara>If your cable isn't detected automatically though it's listed as a known and
supported cable, feel free to report its VID and PID. It might be a different
revision and should be added to the known &amp; tested list of cables.</simpara>
<literallayout class="monospaced">jtag&gt; cable ARM-USB-OCD ftd2xx-mpsse 15ba:3</literallayout>
<simpara>The support for USB-based cables and their configuration is work
in progress; the above syntax may change (i.e. become simpler) soon.</simpara>
<simpara>As stated above, the driver name is not mandatory for the cable
command. UrJTAG will select the driver automatically based on UrJTAG's
configuration. In case your system provides just one of libftdi or FTD2XX
the respective driver is selected. If both libraries are available, then
FTD2XX is selected. That's simply because FTD2XX showed some performance
advantages over libftdi in the past. You can still force libftdi with the
respective parameter.</simpara>
</section>
<section id="_detect">
@ -1564,6 +1600,10 @@ In case the TDO parameter of an SDR command leads to a mismatch the player
issues a warning and continues. If the player should abort in this case then
specify <emphasis>stop</emphasis> at the svf command.</simpara>
<simpara>The absence of error or warning messages indicate that the SVF file could be
executed without problems. To get a progress reporting while the player advances
through the SVF file, specify <emphasis>progress</emphasis> at the svf command.</simpara>
<sidebar>
<title>Limitations and Deficiencies</title>
<simpara>Several limitations exist for the SVF player.</simpara>
@ -1648,12 +1688,6 @@ RUNTEST SCK not supported.
</listitem>
<listitem>
<simpara>
SIR
No check is done against the TDO parameter.
</simpara>
</listitem>
<listitem>
<simpara>
TRST
Parameters Z and ABSENT are not supported.
</simpara>
@ -2338,15 +2372,10 @@ chips, and probably soon will be rewritten as "usbconn" drivers instead.</simpar
<section id="_usbconn">
<title>usbconn</title>
<simpara>The usbconn drivers provide a common API to search for and connect with USB
devices. At the moment, there's only a libusb driver, but others will follow
(e.g. to communicate with FTDI chip based cables through libftdi and/or FTD2XX,
to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and more).</simpara>
<simpara>In contrast to the parport API, the usbconn drivers provide only the functions
for connecting, disconnecting, and for releasing ressources. The actual
communication must be implemented using the underlying library's functions,
e.g. usb_write from libusb, or ftdi_write from libftdi. Therefore, each driver
using usbconn usually only works together with one particular usbconn driver.</simpara>
devices. At the moment, there are drivers for libusd, libftdi and FTD2XX
(e.g. to communicate with FTDI chip based cables through libftdi and/or
FTD2XX, to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and
more).</simpara>
</section>
</section>
@ -2414,7 +2443,7 @@ bus_write() - Write access
</simpara>
</listitem>
</itemizedlist>
<important><simpara>Address parameters to the functions listed above apecify always
<important><simpara>Address parameters to the functions listed above specify always
byte locations, independent of the actual data width. The bus driver has to
adjust the address on its own if required.</simpara></important>
<section id="_initialization_2">
@ -2438,9 +2467,10 @@ command before it lists the areas covered by this bus driver.</simpara>
</section>
<section id="_preparation">
<title>Preparation</title>
<simpara>This function is called whenever at the start of a bus operation. The driver
should perform the required preparation steps so that subsequent calls to the
bus_read_* and bus_write functions can perform their tasks properly.</simpara>
<simpara>This function is called whenever a bus operation is initiated. The
driver should perform the required preparation steps so that
subsequent calls to the bus_read_* and bus_write functions can perform
their tasks properly.</simpara>
<simpara>E.g. a BSR bus driver would put the device into EXTEST mode to activate the
boundary scan register on the device pins.</simpara>

@ -206,6 +206,16 @@ HREF="#_using_libusb_win32_in_cygwin_environment"
></DT
><DT
>2.4.7. <A
HREF="#_compiling_with_mingw"
>Compiling with MinGW</A
></DT
><DT
>2.4.8. <A
HREF="#_driver_tailoring"
>Driver tailoring</A
></DT
><DT
>2.4.9. <A
HREF="#_building_the_bsdl_subsystem"
>Building the BSDL subsystem</A
></DT
@ -963,6 +973,11 @@ least the following are supported:</P
></LI
><LI
><P
>&#13;Atmel AT32AP7000 (partial support)
</P
></LI
><LI
><P
>&#13;Broadcom BCM1250
</P
></LI
@ -1168,13 +1183,13 @@ NAME="_required_software_for_compiling_urjtag"
><P
>To run autogen.sh, you need autoconf and automake, bison, and a recent flex.</P
><P
>The distributed source tarball contains source pregenerated with a current flex
version; flex therefore is only needed if you want to compile code checked
out from our Subversion repository. Flex 2.5.4a as it comes with Cygwin will
work but some parts of UrJTAG (namely the SVF player) become more verbose if
Flex 2.5.31 or newer is used. Building the BSDL subsystem files requires Flex
2.5.33 or newer. The configure script will compare the available Flex version
against these preconditions and enables or disables the related features. ,</P
>The distributed source tarball contains source pregenerated with a current
flex version; flex therefore is only needed if you want to compile code
checked out from our Subversion repository. Flex 2.5.4a as it comes with
Cygwin cannot build the scanners for BSDL and SVF. Building these files
requires Flex 2.5.33 or newer. The configure script will compare the available
Flex version against these preconditions and enables or disables the related
features.</P
><P
>Furthermore, libtool should be available, and "devel" versions of the following
packages:</P
@ -1321,9 +1336,9 @@ CLASS="literallayout"
>Configure should now report</P
><PRE
CLASS="literallayout"
>FTDI cable support
>jtag is now configured for
...
via libftd2xx : yes</PRE
Detected libftd2xx : yes</PRE
></DIV
><DIV
CLASS="section"
@ -1356,8 +1371,49 @@ CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="_compiling_with_mingw"
>2.4.7. Compiling with MinGW</A
></H3
><P
>UrJTAG may be compiled into a Windows executable using the MinGW compiler
(http://www.mingw.org). This has the advantage over running in a Cygwin
environment that you don't need to install anything else but the jtag.exe.
However, because support for MinGW is quite new in UrJTAG, it may lack some
features (e.g. readline support) or run a little slower.</P
><P
>It is even possible to cross-compile and build the executable on a Linux
host:</P
><PRE
CLASS="literallayout"
>./configure --host=i586-mingw32msvc --with-ftd2xx=/tmp/cdm-drivers
make</PRE
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="_driver_tailoring"
>2.4.8. Driver tailoring</A
></H3
><P
>The configure script enables all default bus, cable and lowlevel drivers. You
can include and exclude specific drivers if required. For a list of parameters
run</P
><PRE
CLASS="literallayout"
>./configure --help</PRE
><P
>to figure out the appropriate &#8212;enable-bus, &#8212;enable-cable and &#8212;enable-lowlevel
options.</P
></DIV
><DIV
CLASS="section"
><HR><H3
CLASS="section"
><A
NAME="_building_the_bsdl_subsystem"
>2.4.7. Building the BSDL subsystem</A
>2.4.9. Building the BSDL subsystem</A
></H3
><P
>As mentioned above, building the BSDL lexer requires Flex 2.5.33 or newer. If
@ -1592,7 +1648,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN333"
NAME="AEN345"
></A
><TABLE
BORDER="0"
@ -2298,24 +2354,28 @@ modprobe parport_pc</PRE
>UrJTAG now also supports some USB cables. Unfortunately, there is no standard
for "JTAG over USB", so this support is limited to a few selected cables only.
For cables based on the FT2232 chip from FTDI, the cable command has to be
given cable name, driver name, and USB Vendor and Product ID of the cable:</P
><PRE
CLASS="literallayout"
>jtag&#62; cable ARM-USB-OCD ftdi-mpsse 15ba:3</PRE
><P
>For some cables, UrJTAG knows the VID:PID and you can just say ":"</P
given cable name and optionally the driver name, USB Vendor, and Product ID of
the cable:</P
><PRE
CLASS="literallayout"
>jtag&#62; cable JTAGkey ftdi-mpsse :</PRE
>jtag&#62; cable ARM-USB-OCD vid=15ba pid=0003 driver=ftdi-mpsse</PRE
><P
>On Windows, if UrJTAG was compiled to use the drivers supplied by
FTDI, the command should instead look like this:</P
>For all known cables, UrJTAG knows the VID and PID so you can just say</P
><PRE
CLASS="literallayout"
>jtag&#62; cable ARM-USB-OCD ftd2xx-mpsse 15ba:3</PRE
><P
>The support for USB-based cables and their configuration is work
in progress; the above syntax may change (i.e. become simpler) soon.</P
>jtag&#62; cable ARM-USB-OCD</PRE
><P
>If your cable isn't detected automatically though it's listed as a known and
supported cable, feel free to report its VID and PID. It might be a different
revision and should be added to the known &#38; tested list of cables.</P
><P
>As stated above, the driver name is not mandatory for the cable
command. UrJTAG will select the driver automatically based on UrJTAG's
configuration. In case your system provides just one of libftdi or FTD2XX
the respective driver is selected. If both libraries are available, then
FTD2XX is selected. That's simply because FTD2XX showed some performance
advantages over libftdi in the past. You can still force libftdi with the
respective parameter.</P
></DIV
><DIV
CLASS="section"
@ -2471,7 +2531,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN589"
NAME="AEN600"
></A
><TABLE
BORDER="0"
@ -2580,7 +2640,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN621"
NAME="AEN632"
></A
><TABLE
BORDER="0"
@ -2728,7 +2788,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN665"
NAME="AEN676"
></A
><TABLE
BORDER="0"
@ -2962,6 +3022,16 @@ CLASS="emphasis"
>stop</I
></SPAN
> at the svf command.</P
><P
>The absence of error or warning messages indicate that the SVF file could be
executed without problems. To get a progress reporting while the player advances
through the SVF file, specify <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>progress</I
></SPAN
> at the svf command.</P
><TABLE
CLASS="sidebar"
BORDER="1"
@ -2971,7 +3041,7 @@ CELLPADDING="5"
><DIV
CLASS="sidebar"
><A
NAME="AEN729"
NAME="AEN742"
></A
><P
><B
@ -3065,12 +3135,6 @@ NAME="AEN729"
></LI
><LI
><P
>&#13;SIR
No check is done against the TDO parameter.
</P
></LI
><LI
><P
>&#13;TRST
Parameters Z and ABSENT are not supported.
</P
@ -3358,7 +3422,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN820"
NAME="AEN831"
></A
><TABLE
BORDER="0"
@ -4081,15 +4145,10 @@ NAME="_usbconn"
></H4
><P
>The usbconn drivers provide a common API to search for and connect with USB
devices. At the moment, there's only a libusb driver, but others will follow
(e.g. to communicate with FTDI chip based cables through libftdi and/or FTD2XX,
to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and more).</P
><P
>In contrast to the parport API, the usbconn drivers provide only the functions
for connecting, disconnecting, and for releasing ressources. The actual
communication must be implemented using the underlying library's functions,
e.g. usb_write from libusb, or ftdi_write from libftdi. Therefore, each driver
using usbconn usually only works together with one particular usbconn driver.</P
devices. At the moment, there are drivers for libusd, libftdi and FTD2XX
(e.g. to communicate with FTDI chip based cables through libftdi and/or
FTD2XX, to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and
more).</P
></DIV
></DIV
><DIV
@ -4185,7 +4244,7 @@ ALT="Important"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Address parameters to the functions listed above apecify always
>Address parameters to the functions listed above specify always
byte locations, independent of the actual data width. The bus driver has to
adjust the address on its own if required.</P
></TD
@ -4238,9 +4297,10 @@ NAME="_preparation"
>4.2.3.4. Preparation</A
></H4
><P
>This function is called whenever at the start of a bus operation. The driver
should perform the required preparation steps so that subsequent calls to the
bus_read_* and bus_write functions can perform their tasks properly.</P
>This function is called whenever a bus operation is initiated. The
driver should perform the required preparation steps so that
subsequent calls to the bus_read_* and bus_write functions can perform
their tasks properly.</P
><P
>E.g. a BSR bus driver would put the device into EXTEST mode to activate the
boundary scan register on the device pins.</P

@ -90,13 +90,13 @@ NAME="_required_software_for_compiling_urjtag"
><P
>To run autogen.sh, you need autoconf and automake, bison, and a recent flex.</P
><P
>The distributed source tarball contains source pregenerated with a current flex
version; flex therefore is only needed if you want to compile code checked
out from our Subversion repository. Flex 2.5.4a as it comes with Cygwin will
work but some parts of UrJTAG (namely the SVF player) become more verbose if
Flex 2.5.31 or newer is used. Building the BSDL subsystem files requires Flex
2.5.33 or newer. The configure script will compare the available Flex version
against these preconditions and enables or disables the related features. ,</P
>The distributed source tarball contains source pregenerated with a current
flex version; flex therefore is only needed if you want to compile code
checked out from our Subversion repository. Flex 2.5.4a as it comes with
Cygwin cannot build the scanners for BSDL and SVF. Building these files
requires Flex 2.5.33 or newer. The configure script will compare the available
Flex version against these preconditions and enables or disables the related
features.</P
><P
>Furthermore, libtool should be available, and "devel" versions of the following
packages:</P
@ -243,9 +243,9 @@ CLASS="literallayout"
>Configure should now report</P
><PRE
CLASS="literallayout"
>FTDI cable support
>jtag is now configured for
...
via libftd2xx : yes</PRE
Detected libftd2xx : yes</PRE
></DIV
><DIV
CLASS="section"
@ -278,8 +278,49 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="_compiling_with_mingw"
>2.4.7. Compiling with MinGW</A
></H2
><P
>UrJTAG may be compiled into a Windows executable using the MinGW compiler
(http://www.mingw.org). This has the advantage over running in a Cygwin
environment that you don't need to install anything else but the jtag.exe.
However, because support for MinGW is quite new in UrJTAG, it may lack some
features (e.g. readline support) or run a little slower.</P
><P
>It is even possible to cross-compile and build the executable on a Linux
host:</P
><PRE
CLASS="literallayout"
>./configure --host=i586-mingw32msvc --with-ftd2xx=/tmp/cdm-drivers
make</PRE
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="_driver_tailoring"
>2.4.8. Driver tailoring</A
></H2
><P
>The configure script enables all default bus, cable and lowlevel drivers. You
can include and exclude specific drivers if required. For a list of parameters
run</P
><PRE
CLASS="literallayout"
>./configure --help</PRE
><P
>to figure out the appropriate &#8212;enable-bus, &#8212;enable-cable and &#8212;enable-lowlevel
options.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="_building_the_bsdl_subsystem"
>2.4.7. Building the BSDL subsystem</A
>2.4.9. Building the BSDL subsystem</A
></H2
><P
>As mentioned above, building the BSDL lexer requires Flex 2.5.33 or newer. If

@ -607,15 +607,10 @@ NAME="_usbconn"
></H3
><P
>The usbconn drivers provide a common API to search for and connect with USB
devices. At the moment, there's only a libusb driver, but others will follow
(e.g. to communicate with FTDI chip based cables through libftdi and/or FTD2XX,
to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and more).</P
><P
>In contrast to the parport API, the usbconn drivers provide only the functions
for connecting, disconnecting, and for releasing ressources. The actual
communication must be implemented using the underlying library's functions,
e.g. usb_write from libusb, or ftdi_write from libftdi. Therefore, each driver
using usbconn usually only works together with one particular usbconn driver.</P
devices. At the moment, there are drivers for libusd, libftdi and FTD2XX
(e.g. to communicate with FTDI chip based cables through libftdi and/or
FTD2XX, to communicate with Cypress FX2 using EZUSB.SYS or CyUSB.sys, and
more).</P
></DIV
></DIV
><DIV
@ -711,7 +706,7 @@ ALT="Important"></TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Address parameters to the functions listed above apecify always
>Address parameters to the functions listed above specify always
byte locations, independent of the actual data width. The bus driver has to
adjust the address on its own if required.</P
></TD
@ -764,9 +759,10 @@ NAME="_preparation"
>4.2.3.4. Preparation</A
></H3
><P
>This function is called whenever at the start of a bus operation. The driver
should perform the required preparation steps so that subsequent calls to the
bus_read_* and bus_write functions can perform their tasks properly.</P
>This function is called whenever a bus operation is initiated. The
driver should perform the required preparation steps so that
subsequent calls to the bus_read_* and bus_write functions can perform
their tasks properly.</P
><P
>E.g. a BSR bus driver would put the device into EXTEST mode to activate the
boundary scan register on the device pins.</P

@ -99,7 +99,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN820"
NAME="AEN831"
></A
><TABLE
BORDER="0"

@ -95,7 +95,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN333"
NAME="AEN345"
></A
><TABLE
BORDER="0"
@ -801,24 +801,28 @@ modprobe parport_pc</PRE
>UrJTAG now also supports some USB cables. Unfortunately, there is no standard
for "JTAG over USB", so this support is limited to a few selected cables only.
For cables based on the FT2232 chip from FTDI, the cable command has to be
given cable name, driver name, and USB Vendor and Product ID of the cable:</P
given cable name and optionally the driver name, USB Vendor, and Product ID of
the cable:</P
><PRE
CLASS="literallayout"
>jtag&#62; cable ARM-USB-OCD ftdi-mpsse 15ba:3</PRE
>jtag&#62; cable ARM-USB-OCD vid=15ba pid=0003 driver=ftdi-mpsse</PRE
><P
>For some cables, UrJTAG knows the VID:PID and you can just say ":"</P
>For all known cables, UrJTAG knows the VID and PID so you can just say</P
><PRE
CLASS="literallayout"
>jtag&#62; cable JTAGkey ftdi-mpsse :</PRE
><P
>On Windows, if UrJTAG was compiled to use the drivers supplied by
FTDI, the command should instead look like this:</P
><PRE
CLASS="literallayout"
>jtag&#62; cable ARM-USB-OCD ftd2xx-mpsse 15ba:3</PRE
><P
>The support for USB-based cables and their configuration is work
in progress; the above syntax may change (i.e. become simpler) soon.</P
>jtag&#62; cable ARM-USB-OCD</PRE
><P
>If your cable isn't detected automatically though it's listed as a known and
supported cable, feel free to report its VID and PID. It might be a different
revision and should be added to the known &#38; tested list of cables.</P
><P
>As stated above, the driver name is not mandatory for the cable
command. UrJTAG will select the driver automatically based on UrJTAG's
configuration. In case your system provides just one of libftdi or FTD2XX
the respective driver is selected. If both libraries are available, then
FTD2XX is selected. That's simply because FTD2XX showed some performance
advantages over libftdi in the past. You can still force libftdi with the
respective parameter.</P
></DIV
><DIV
CLASS="section"
@ -974,7 +978,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN589"
NAME="AEN600"
></A
><TABLE
BORDER="0"
@ -1083,7 +1087,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN621"
NAME="AEN632"
></A
><TABLE
BORDER="0"
@ -1231,7 +1235,7 @@ CLASS="informaltable"
><P
></P
><A
NAME="AEN665"
NAME="AEN676"
></A
><TABLE
BORDER="0"
@ -1465,6 +1469,16 @@ CLASS="emphasis"
>stop</I
></SPAN
> at the svf command.</P
><P
>The absence of error or warning messages indicate that the SVF file could be
executed without problems. To get a progress reporting while the player advances
through the SVF file, specify <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>progress</I
></SPAN
> at the svf command.</P
><TABLE
CLASS="sidebar"
BORDER="1"
@ -1474,7 +1488,7 @@ CELLPADDING="5"
><DIV
CLASS="sidebar"
><A
NAME="AEN729"
NAME="AEN742"
></A
><P
><B
@ -1568,12 +1582,6 @@ NAME="AEN729"
></LI
><LI
><P
>&#13;SIR
No check is done against the TDO parameter.
</P
></LI
><LI
><P
>&#13;TRST
Parameters Z and ABSENT are not supported.
</P

@ -302,6 +302,11 @@ least the following are supported:</P
></LI
><LI
><P
>&#13;Atmel AT32AP7000 (partial support)
</P
></LI
><LI
><P
>&#13;Broadcom BCM1250
</P
></LI

@ -209,6 +209,16 @@ HREF="_compilation_and_installation.html#_using_libusb_win32_in_cygwin_environme
></DT
><DT
>2.4.7. <A
HREF="_compilation_and_installation.html#_compiling_with_mingw"
>Compiling with MinGW</A
></DT
><DT
>2.4.8. <A
HREF="_compilation_and_installation.html#_driver_tailoring"
>Driver tailoring</A
></DT
><DT
>2.4.9. <A
HREF="_compilation_and_installation.html#_building_the_bsdl_subsystem"
>Building the BSDL subsystem</A
></DT

Loading…
Cancel
Save