[OpenOCD-devel] [PATCH]: cdb0302 interface: Add XDS100v3 support and renamed to xds100
This is an automated email from Gerrit. Remco Bloemen (openocd-ger...@xn--2-umb.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/3632 -- gerrit commit cdb03027d3e4624620e32225c64e1c55e48038f0 Author: Remco Bloemen Date: Tue Aug 9 12:30:12 2016 +0100 interface: Add XDS100v3 support and renamed to xds100 XDS100v3 is software compatible with the XDS100v2, but has a different usb pid. This change adds the pid to the list in xds100v2.cfg. Since this file now supports both the v2 and v3, it is renamed to `xds100.cfg`. Change-Id: Ie29d325e8992d2de2f97d70862beeb63932ffa80 Signed-off-by: Remco Bloemen diff --git a/tcl/interface/ftdi/xds100.cfg b/tcl/interface/ftdi/xds100.cfg new file mode 100644 index 000..fa879c4 --- /dev/null +++ b/tcl/interface/ftdi/xds100.cfg @@ -0,0 +1,58 @@ +# +# Texas Instruments XDS100 ver 2.0 and 3.0 +# +# http://processors.wiki.ti.com/index.php/XDS100#XDS100v2_Features +# +# Detailed documentation is available only as CPLD verilog source code +# to the registered TI users. +# + +interface ftdi +ftdi_vid_pid 0x0403 0xa6d1 0x0403 0xa6d0 0x0403 0x6010 + +ftdi_layout_init 0x0038 0x597b + +# 8000 z - unused +# 4000 0 > CPLD loopback (all target side pins high-Z) +# 2000 z < !( cable connected ) (open drain on CPLD side for $reasons) +# 1000 0 > EMU1_oe +# +# 800 0 > PWR_RST = clear power-loss flag on rising edge +# 400 z < !( power-loss flag ) +# 200 z < nSRST +# 100 0 > nSRST_oe +# +#80 z < RTCK +#40 0 > EMU0_oe +#20 1 > EMU_EN +#10 1 > nTRST +# +# 8 1 > TMS +# 4 z < TDO +# 2 0 > TDI +# 1 0 > TCK +# +# As long as the power-loss flag is set, all target-side pins are +# high-Z except the EMU-pins for which the opposite holds unless +# EMU_EN is high. +# +# To use wait-in-reset, drive EMU0 low at power-on reset. If the +# target normally reuses EMU0 for other purposes, clear EMU_EN to +# keep the EMU pins high-Z until the target is power-cycled. +# +# The LED only turns off at USB suspend, which is also the only way to +# set the power-loss flag manually. (Can be done in software e.g. by +# changing the USB configuration to zero.) +# + +ftdi_layout_signal nTRST -data 0x0010 +ftdi_layout_signal nSRST -oe 0x0100 +ftdi_layout_signal EMU_EN -data 0x0020 +ftdi_layout_signal EMU0 -oe 0x0040 +ftdi_layout_signal EMU1 -oe 0x1000 +ftdi_layout_signal PWR_RST -data 0x0800 +ftdi_layout_signal LOOPBACK -data 0x4000 + +echo "\nInfo : to use this adapter you MUST add ``init; ftdi_set_signal PWR_RST 1; jtag arp_init'' to the end of your config file!\n" +# note: rising edge on PWR_RST is also needed after power-cycling the +# target diff --git a/tcl/interface/ftdi/xds100v2.cfg b/tcl/interface/ftdi/xds100v2.cfg deleted file mode 100644 index 2628aa0..000 --- a/tcl/interface/ftdi/xds100v2.cfg +++ /dev/null @@ -1,58 +0,0 @@ -# -# Texas Instruments XDS100v2 -# -# http://processors.wiki.ti.com/index.php/XDS100#XDS100v2_Features -# -# Detailed documentation is available only as CPLD verilog source code -# to the registered TI users. -# - -interface ftdi -ftdi_vid_pid 0x0403 0xa6d0 0x0403 0x6010 - -ftdi_layout_init 0x0038 0x597b - -# 8000 z - unused -# 4000 0 > CPLD loopback (all target side pins high-Z) -# 2000 z < !( cable connected ) (open drain on CPLD side for $reasons) -# 1000 0 > EMU1_oe -# -# 800 0 > PWR_RST = clear power-loss flag on rising edge -# 400 z < !( power-loss flag ) -# 200 z < nSRST -# 100 0 > nSRST_oe -# -#80 z < RTCK -#40 0 > EMU0_oe -#20 1 > EMU_EN -#10 1 > nTRST -# -# 8 1 > TMS -# 4 z < TDO -# 2 0 > TDI -# 1 0 > TCK -# -# As long as the power-loss flag is set, all target-side pins are -# high-Z except the EMU-pins for which the opposite holds unless -# EMU_EN is high. -# -# To use wait-in-reset, drive EMU0 low at power-on reset. If the -# target normally reuses EMU0 for other purposes, clear EMU_EN to -# keep the EMU pins high-Z until the target is power-cycled. -# -# The LED only turns off at USB suspend, which is also the only way to -# set the power-loss flag manually. (Can be done in software e.g. by -# changing the USB configuration to zero.) -# - -ftdi_layout_signal nTRST -data 0x0010 -ftdi_layout_signal nSRST -oe 0x0100 -ftdi_layout_signal EMU_EN -data 0x0020 -ftdi_layout_signal EMU0 -oe 0x0040 -ftdi_layout_signal EMU1 -oe 0x1000 -ftdi_layout_signal PWR_RST -data 0x0800 -ftdi_layout_signal LOOPBACK -data 0x4000 - -echo "\nInfo : to use this adapter you MUST add ``init; ftdi_set_signal PWR_RST 1; jtag arp_init'' to the end of your config file!\n" -# note: rising edge on PWR_RST is also needed after power-cycling the -# target -- -- What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most band
[OpenOCD-devel] [PATCH]: 71b5294 interface: Add udev rule for XDS100v3
This is an automated email from Gerrit.
Remco Bloemen (openocd-ger...@xn--2-umb.com) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/3631
-- gerrit
commit 71b52947462bc5b140b397a4fefd2eeb25b10242
Author: Remco Bloemen
Date: Tue Aug 9 12:26:41 2016 +0100
interface: Add udev rule for XDS100v3
Add the usb vid and pid for XDS100V3 to the rules.
Change-Id: I1660881c4e763a74ee7088bae20f711293c96bf7
Signed-off-by: Remco Bloemen
diff --git a/contrib/99-openocd.rules b/contrib/99-openocd.rules
index 057c4b7..94eab91 100644
--- a/contrib/99-openocd.rules
+++ b/contrib/99-openocd.rules
@@ -30,6 +30,9 @@ ATTRS{idVendor}=="0403", ATTRS{idProduct}=="8a99",
MODE="664", GROUP="plugdev"
# XDS100v2
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d0", MODE="664", GROUP="plugdev"
+# Texas Instruments XDS100 Ver 3.0
+ATTRS{idVendor}=="0403", ATTRS{idProduct}=="a6d1", MODE="664", GROUP="plugdev"
+
# Xverve Signalyzer Tool (DT-USB-ST), Signalyzer LITE (DT-USB-SLITE)
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bca0", MODE="664", GROUP="plugdev"
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="bca1", MODE="664", GROUP="plugdev"
--
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
[OpenOCD-devel] [PATCH]: 003910c xilinx-xc7: correct Artix7 15T IDCODE
This is an automated email from Gerrit.
Felix Held (felix-open...@felixheld.de) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/3633
-- gerrit
commit 003910c1475a945a037fb1b826d370c0fe37ecd9
Author: Felix Held
Date: Wed Aug 10 03:09:02 2016 +0200
xilinx-xc7: correct Artix7 15T IDCODE
The IDCODE of Artix7 15T in the UG470 is wrong; Artix7 35T and 15T don't
have the same IDCODE.
I've tested this on real hardware.
Change-Id: Iac267dc449c23454dd119126749dbeb8267c18ac
Signed-off-by: Felix Held
diff --git a/tcl/cpld/xilinx-xc7.cfg b/tcl/cpld/xilinx-xc7.cfg
index 5c5b023..d5824f8 100644
--- a/tcl/cpld/xilinx-xc7.cfg
+++ b/tcl/cpld/xilinx-xc7.cfg
@@ -9,7 +9,7 @@ if { [info exists CHIPNAME] } {
# the 4 top bits (28:31) are the die stepping/revisions. ignore it.
jtag newtap $_CHIPNAME tap -irlen 6 -ignore-version \
- -expected-id 0x0362D093 \
+ -expected-id 0x0362E093 \
-expected-id 0x0362D093 \
-expected-id 0x0362C093 \
-expected-id 0x03632093 \
--
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
___
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
[OpenOCD-devel] [PATCH]: 9075f8d Replace "daemon" with "server" in user-visible strings
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/3634
-- gerrit
commit 9075f8d8719bf6e0b9cc1eb47d249ffe42c5
Author: Paul Fertser
Date: Wed Aug 10 09:40:34 2016 +0300
Replace "daemon" with "server" in user-visible strings
Since OpenOCD doesn't fit most common definitions of the word "daemon",
using it in the documentation is confusing.
Reported by IRC user ohsix.
Change-Id: I688d722771b084b17c2a7af8e83fd64bab6141b8
Signed-off-by: Paul Fertser
diff --git a/doc/openocd.texi b/doc/openocd.texi
index 983ce3c..06d259e 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -66,7 +66,7 @@ Free Documentation License''.
* Running:: Running OpenOCD
* OpenOCD Project Setup::OpenOCD Project Setup
* Config File Guidelines:: Config File Guidelines
-* Daemon Configuration:: Daemon Configuration
+* Server Configuration:: Server Configuration
* Debug Adapter Configuration:: Debug Adapter Configuration
* Reset Configuration:: Reset Configuration
* TAP Declaration:: TAP Declaration
@@ -752,13 +752,13 @@ on the command line or, if there were no @option{-c
command} or
At the end of the configuration stage it verifies the JTAG scan
chain defined using those commands; your configuration should
ensure that this always succeeds.
-Normally, OpenOCD then starts running as a daemon.
+Normally, OpenOCD then starts running as a server.
Alternatively, commands may be used to terminate the configuration
stage early, perform work (such as updating some flash memory),
-and then shut down without acting as a daemon.
+and then shut down without acting as a server.
-Once OpenOCD starts running as a daemon, it waits for connections from
-clients (Telnet, GDB, Other) and processes the commands issued through
+Once OpenOCD starts running as a server, it waits for connections from
+clients (Telnet, GDB, RPC) and processes the commands issued through
those channels.
If you are having problems, you can enable internal debug messages via
@@ -775,7 +775,7 @@ informational messages, warnings and errors. You can also
change this
setting from within a telnet or gdb session using @command{debug_level}
(@pxref{debuglevel,,debug_level}).
-You can redirect all output from the daemon to a file using the
+You can redirect all output from the server to a file using the
@option{-l } switch.
Note! OpenOCD will launch the GDB & telnet server even if it can not
@@ -1994,8 +1994,8 @@ proc setc15 @{regs value@} @{
-@node Daemon Configuration
-@chapter Daemon Configuration
+@node Server Configuration
+@chapter Server Configuration
@cindex initialization
The commands here are commonly found in the openocd.cfg file and are
used to specify what TCP/IP ports are used, and how GDB should be
@@ -,7 +,7 @@ port is .
@end itemize
-@section Daemon Commands
+@section Server Commands
@deffn {Command} exit
Exits the current telnet session.
@@ -6692,7 +6692,7 @@ Useful in connection with script files
@end deffn
@deffn Command shutdown [@option{error}]
-Close the OpenOCD daemon, disconnecting all clients (GDB, telnet,
+Close the OpenOCD server, disconnecting all clients (GDB, telnet,
other). If option @option{error} is used, OpenOCD will return a
non-zero exit code to the parent process.
@end deffn
diff --git a/src/target/image.c b/src/target/image.c
index 0612ea7..f97d904 100644
--- a/src/target/image.c
+++ b/src/target/image.c
@@ -729,7 +729,7 @@ int image_open(struct image *image, const char *url, const
char *type_string)
retval = image_ihex_buffer_complete(image);
if (retval != ERROR_OK) {
LOG_ERROR(
- "failed buffering IHEX image, check daemon
output for additional information");
+ "failed buffering IHEX image, check server
output for additional information");
fileio_close(image_ihex->fileio);
return retval;
}
@@ -780,7 +780,7 @@ int image_open(struct image *image, const char *url, const
char *type_string)
retval = image_mot_buffer_complete(image);
if (retval != ERROR_OK) {
LOG_ERROR(
- "failed buffering S19 image, check daemon
output for additional information");
+ "failed buffering S19 image, check server
output for additional information");
fileio_close(image_mot->fileio);
return retval;
}
--
--
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Rev
