X-Git-Url: https://review.openocd.org/gitweb?p=openocd.git;a=blobdiff_plain;f=README;h=7ca5957a0e0854bf04eaa35799778798c7372cf1;hp=60338d0763b25b5a4f0b7b30b7956bfa4f15ac92;hb=cc2d4f015f72d7c30d613b50572eb9f31fac515a;hpb=6c1437a0a45513cc4524f1e0bd8e7e211f6bf809 diff --git a/README b/README index 60338d0763..7ca5957a0e 100644 --- a/README +++ b/README @@ -39,10 +39,11 @@ If you are connecting a particular adapter with some specific target, you need to source both the jtag interface and the target configs, e.g.: - openocd -f interface/ftdi/jtagkey2.cfg -f target/ti_calypso.cfg + openocd -f interface/ftdi/jtagkey2.cfg -c "transport select jtag" \ + -f target/ti_calypso.cfg -NB: when using an FTDI-based adapter you should prefer configs in the -ftdi directory; the old configs for the ft2232 are deprecated. + openocd -f interface/stlink-v2-1.cfg -c "transport select hla_swd" \ + -f target/stm32l0.cfg After OpenOCD startup, connect GDB with @@ -57,10 +58,10 @@ In addition to the in-tree documentation, the latest manuals may be viewed online at the following URLs: OpenOCD User's Guide: - http://openocd.sourceforge.net/doc/html/index.html + http://openocd.org/doc/html/index.html OpenOCD Developer's Manual: - http://openocd.sourceforge.net/doc/doxygen/html/index.html + http://openocd.org/doc/doxygen/html/index.html These reflect the latest development versions, so the following section introduces how to build the complete documentation from the package. @@ -102,12 +103,12 @@ JTAG adapters AICE, ARM-JTAG-EW, ARM-USB-OCD, ARM-USB-TINY, AT91RM9200, axm0432, BCM2835, Bus Blaster, Buspirate, Chameleon, CMSIS-DAP, Cortino, DENX, -DLC 5, DLP-USB1232H, embedded projects, eStick, FlashLINK, FlossJTAG, -Flyswatter, Flyswatter2, Gateworks, Hoegl, ICDI, ICEBear, J-Link, JTAG -VPI, JTAGkey, JTAGkey2, JTAG-lock-pick, KT-Link, Lisa/L, -LPC1768-Stick, MiniModule, NGX, NXHX, OOCDLink, Opendous, OpenJTAG, -Openmoko, OpenRD, OSBDM, Presto, Redbee, RLink, SheevaPlug devkit, -Stellaris evkits, ST-LINK (SWO tracing supported), +Digilent JTAG-SMT2, DLC 5, DLP-USB1232H, embedded projects, eStick, +FlashLINK, FlossJTAG, Flyswatter, Flyswatter2, Gateworks, Hoegl, ICDI, +ICEBear, J-Link, JTAG VPI, JTAGkey, JTAGkey2, JTAG-lock-pick, KT-Link, +Lisa/L, LPC1768-Stick, MiniModule, NGX, NXHX, OOCDLink, Opendous, +OpenJTAG, Openmoko, OpenRD, OSBDM, Presto, Redbee, RLink, SheevaPlug +devkit, Stellaris evkits, ST-LINK (SWO tracing supported), STM32-PerformanceStick, STR9-comStick, sysfsgpio, TUMPA, Turtelizer, ULINK, USB-A9260, USB-Blaster, USB-JTAG, USBprog, VPACLink, VSLLink, Wiggler, XDS100v2, Xverve. @@ -115,17 +116,18 @@ Wiggler, XDS100v2, Xverve. Debug targets ------------- -ARM11, ARM7, ARM9, AVR32, Cortex-A, Cortex-R, Cortex-M, +ARM11, ARM7, ARM9, AVR32, Cortex-A, Cortex-R, Cortex-M, LS102x-SAP, Feroceon/Dragonite, DSP563xx, DSP5680xx, FA526, MIPS EJTAG, NDS32, -XScale. +XScale, Intel Quark. Flash drivers ------------- -ADUC702x, AT91SAM, AVR, CFI, DSP5680xx, EFM32, EM357, FM3, Kinetis, -LPC2000, LPC2900, LPCSPIFI, Milandr, NuMicro, PIC32mx, Stellaris, -STM32, STMSMI, STR7x, STR9x; NAND controllers of AT91SAM9, LPC3180, -LPC32xx, i.MX31, MXC, NUC910, Orion/Kirkwood, S3C24xx, S3C6400. +ADUC702x, AT91SAM, AVR, CFI, DSP5680xx, EFM32, EM357, FM3, FM4, Kinetis, +LPC8xx/LPC1xxx/LPC2xxx/LPC541xx, LPC2900, LPCSPIFI, Marvell QSPI, +Milandr, NIIET, NuMicro, PIC32mx, PSoC4, SiM3x, Stellaris, STM32, STMSMI, +STR7x, STR9x, nRF51; NAND controllers of AT91SAM9, LPC3180, LPC32xx, +i.MX31, MXC, NUC910, Orion/Kirkwood, S3C24xx, S3C6400, XMC1xxx, XMC4xxx. ================== @@ -223,7 +225,7 @@ USB-based adapters depend on libusb-1.0 and some older drivers require libusb-0.1 or libusb-compat-0.1. A compatible implementation, such as FreeBSD's, additionally needs the corresponding .pc files. -USB-Blaster, ASIX Presto, OpenJTAG and ft2232 interface adapter +USB-Blaster, ASIX Presto and OpenJTAG interface adapter drivers need either one of: - libftdi: http://www.intra2net.com/en/developer/libftdi/index.php - ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm (proprietary, @@ -237,8 +239,8 @@ Permissions delegation Running OpenOCD with root/administrative permissions is strongly discouraged for security reasons. -For USB devices on GNU/Linux you should use the contrib/openocd.udev -rules file. It probably belongs somewhere in /etc/udev/rules.d, but +For USB devices on GNU/Linux you should use the contrib/99-openocd.rules +file. It probably belongs somewhere in /etc/udev/rules.d, but consult your operating system documentation to be sure. Do not forget to add yourself to the "plugdev" group.