Welcome to OpenOCD! =================== OpenOCD provides on-chip programming and debugging support with a layered architecture of JTAG interface and TAP support, debug target support (e.g. ARM, MIPS), and flash chip drivers (e.g. CFI, NAND, etc.). Several network interfaces are available for interactiving with OpenOCD: HTTP, telnet, TCL, and GDB. The GDB server enables OpenOCD to function as a "remote target" for source-level debugging of embedded systems using the GNU GDB program. This README file contains an overview of the following topics: - how to find and build more OpenOCD documentation, - the build process - packaging tips. - configuration options ===================== OpenOCD Documentation ===================== In addition to in-tree documentation, the latest documentation may be viewed on-line at the following URLs: OpenOCD User's Guide: http://openocd.berlios.de/doc/html/index.html OpenOCD Developer's Manual: http://openocd.berlios.de/doc/doxygen/index.html These reflect the latest development versions, so the following section introduces how to build the complete documentation from the package. For more information, refer to these documents or contact the developers by subscribing to the OpenOCD developer mailing list: openocd-development@lists.berlios.de Building the OpenOCD Documentation ---------------------------------- The OpenOCD User's Guide can be produced in two different format: # If PDFVIEWER is set, this creates and views the PDF User Guide. make pdf && ${PDFVIEWER} doc/openocd.pdf # If HTMLVIEWER is set, this creates and views the HTML User Guide. make html && ${HTMLVIEWER} doc/openocd.html/index.html The OpenOCD Developer Manual contains information about the internal architecture and other details about the code: # NB! make sure doxygen is installed, type doxygen --version make doxygen # If HTMLVIEWER is set, this views the HTML Doxygen output. ${HTMLVIEWER} doxygen/index.html The remaining sections describe how to configure the system such that you can build the in-tree documentation. ================== Installing OpenOCD ================== On Linux, you may have permissions problems to address. The best way to do this is to use the contrib/udev.rules file. It probably belongs somewhere in /etc/udev/rules.d, but consult your operating system documentation to be sure. In particular, make sure that it matches the syntax used by your operating system's version of udev. A Note to OpenOCD Users ----------------------- If you would rather be working "with" OpenOCD rather than "on" it, your operating system or JTAG interface supplier may provide binaries for you in a convenient-enough package. Such packages may be more stable than git mainline, where bleeding-edge development takes place. These "Packagers" produce binary releases of OpenOCD after the developers produces new "release" versions of the source code. Previous versions of OpenOCD cannot be used to diagnose problems with the current release, so users are encouraged to keep in contact with their distribution package maintainers or interface vendors to ensure suitable upgrades appear regularly. Users of these binary versions of OpenOCD must contact their Packager to ask for support or newer versions of the binaries; the OpenOCD developers do not support packages directly. A Note to OpenOCD Packagers --------------------------- You are a PACKAGER of OpenOCD if you: - Sell dongles: and include pre-built binaries - Supply tools: A complete development solution - Supply IDEs: like Eclipse, or RHIDE, etc. - Build packages: RPM files, or DEB files for a Linux Distro As a PACKAGER, you will experience first reports of most issues. When you fix those problems for your users, your solution may help prevent hundreds (if not thousands) of other questions from other users. If something does not work for you, please work to inform the OpenOCD developers know how to improve the system or documentation to avoid future problems, and follow-up to help us ensure the issue will be fully resolved in our future releases. That said, the OpenOCD developers would also like you to follow a few suggestions: - Send patches, including config files, upstream. - Always build with printer ports enabled. - Use libftdi + libusb for FT2232 support. Remember, the FTD2XX library cannot be used in binary distributions, due to restrictions of the GPL v2. ================ Building OpenOCD ================ The INSTALL file contains generic instructions for running 'configure' and compiling the OpenOCD source code. That file is provided by default for all GNU automake packages. If you are not familiar with the GNU autotools, then you should read those instructions first. The remainder of this document tries to provide some instructions for those looking for a quick-install. OpenOCD Dependencies -------------------- Presently, GCC is required to build OpenOCD. The developers have begun to enforce strict code warnings (-Wall, -Werror, -Wextra, and more) and use C99-specific features: inline functions, named initializers, mixing declarations with code, and other tricks. While it may be possible to use other compilers, they must be somewhat modern and could require extending support to conditionally remove GCC-specific extensions. Also, you need to install the appropriate driver files, if you want to build support for a USB or FTDI-based interface: - ft2232, jlink, rlink, vsllink, usbprog, arm-jtag-ew: - libusb: required for portable communication with USB dongles - ft2232 also requires: - libftdi: http://www.intra2net.com/opensource/ftdi/ *OR* - ftd2xx: http://www.ftdichip.com/Drivers/D2XX.htm, or the Amontec version (from http://www.amontec.com), for easier support of JTAGkey's vendor and product IDs. Many Linux distributions provide these packages through their automated installation and update mechanisms; however, some Linux versions include older versions of libftdi. In particular, using Ubuntu 8.04 has been problematic, but newer versions of Ubuntu do not have this problem. Compiling OpenOCD ----------------- To build OpenOCD (on both Linux and Cygwin), use the following sequence of commands: ./configure [with some options listed in the next section] make make install The 'configure' step generates the Makefiles required to build OpenOCD, usually with one or more options provided to it. The first 'make' step will build OpenOCD and place the final executable in ./src/. The final (optional) step, ``make install'', places all of the files in the required location. Cross-Compiling Options ----------------------- To cross-compile, you must specify both --build and --host options to the 'configure' script. For example, you can configure OpenOCD to cross-compile on a x86 Linux host to run on Windows (MinGW32), you could use the following configuration options: ./configure --build=i686-pc-linux-gnu --host=i586-mingw32msvc ... Likewise, the following options allow OpenOCD to be cross-compiled for an ARM target on the same x86 host: ./configure --build=i686-pc-linux-gnu --host=arm-elf ... Both must be specified to work around bugs in autoconf. Scripts for producing ARM cross-compilers can be found on the web with a little searching. A script to produce an x86 Linux-hosted MinGW32 cross-compiler can be downloaded from the following URL: http://www.mingw.org/wiki/LinuxCrossMinGW Configuration Options --------------------- The configure script takes numerous options, specifying which JTAG interfaces should be included (among other things). The following list of options was extracted from the output of './configure --help'. Other options may be available there: --enable-maintainer-mode enable make rules and dependencies not useful (and sometimes confusing) to the casual installer NOTE: This option is *required* for GIT builds! It should *not* be used to build a release. --enable-dummy Enable building the dummy JTAG port driver --enable-ft2232_libftdi Enable building support for FT2232 based devices using the libftdi driver, opensource alternate of FTD2XX --enable-ft2232_ftd2xx Enable building support for FT2232 based devices using the FTD2XX driver from ftdichip.com --enable-gw16012 Enable building support for the Gateworks GW16012 JTAG Programmer --enable-parport Enable building the pc parallel port driver --disable-parport-ppdev Disable use of ppdev (/dev/parportN) for parport (for x86 only) --enable-parport-giveio Enable use of giveio for parport (for CygWin only) --enable-presto_libftdi Enable building support for ASIX Presto Programmer using the libftdi driver --enable-presto_ftd2xx Enable building support for ASIX Presto Programmer using the FTD2XX driver --enable-amtjtagaccel Enable building the Amontec JTAG-Accelerator driver --enable-arm-jtag-ew Enable building support for the Olimex ARM-JTAG-EW Programmer --enable-jlink Enable building support for the Segger J-Link JTAG Programmer --enable-rlink Enable building support for the Raisonance RLink JTAG Programmer --enable-usbprog Enable building support for the usbprog JTAG Programmer --enable-vsllink Enable building support for the Versaloon-Link JTAG Programmer --enable-oocd_trace Enable building support for the OpenOCD+trace ETM capture device --enable-ep93xx Enable building support for EP93xx based SBCs --enable-at91rm9200 Enable building support for AT91RM9200 based SBCs --enable-ecosboard Enable building support for eCos based JTAG debugger --enable-zy1000 Enable ZY1000 interface --enable-minidriver-dummy Enable the dummy minidriver. --enable-ioutil Enable ioutil functions - useful for standalone OpenOCD implementations --enable-httpd Enable builtin httpd server - useful for standalone OpenOCD implementations --disable-doxygen-html Disable building Doxygen manual as HTML. --enable-doxygen-pdf Enable building Doxygen manual as PDF. Miscellaneous Configure Options ------------------------------- The following additional options may also be useful: --disable-assert turn off assertions --enable-verbose Enable verbose JTAG I/O messages (for debugging). --enable-verbose-jtag-io Enable verbose JTAG I/O messages (for debugging). --enable-verbose-usb-io Enable verbose USB I/O messages (for debugging) --enable-verbose-usb-comms Enable verbose USB communication messages (for debugging) --enable-malloc-logging Include free space in logging messages (requires malloc.h). --disable-gccwarnings Disable extra gcc warnings during build. --disable-wextra Disable extra compiler warnings --disable-werror Do not treat warnings as errors --disable-option-checking Ignore unrecognized --enable and --with options. --disable-dependency-tracking speeds up one-time build --enable-shared[=PKGS] build shared libraries [default=no] --enable-static[=PKGS] build static libraries [default=yes] Parallel Port Dongles --------------------- If you want to access the parallel port using the PPDEV interface you have to specify both --enable-parport AND --enable-parport-ppdev, since the the later option is an option to the parport driver (see http://forum.sparkfun.com/viewtopic.php?t=3795 for more info). The same is true for the --enable-parport-giveio option, you have to use both the --enable-parport AND the --enable-parport-giveio option if you want to use giveio instead of ioperm parallel port access method. FT2232C Based USB Dongles ------------------------- There are 2 methods of using the FTD2232, either (1) using the FTDICHIP.COM closed source driver, or (2) the open (and free) driver libftdi. Using LIBFTDI ------------- The libftdi source code can be download from the following website: http://www.intra2net.com/en/developer/libftdi/download.php For both Linux and Windows, both libusb and libftdi must be built and installed. To use the newer FT2232H chips, supporting RTCK and USB high speed (480 Mbps), you need libftdi version 0.16 or newer. Many Linux distributions provide suitable packages for these libraries. For Windows, libftdi is supported with versions 0.14 and later. With these prerequisites met, configure the libftdi solution like this: ./configure --prefix=/path/for/your/install --enable-ft2232_libftdi Then type ``make'', and perhaps ``make install''. Using FTDI's FTD2XX ------------------- The (closed source) FTDICHIP.COM solution is faster on MS-Windows. That is the motivation for supporting it even though its licensing restricts it to non-redistributable OpenOCD binaries, and it is not available for all operating systems used with OpenOCD. You may, however, build such copies for personal use. The FTDICHIP drivers come as either a (win32) ZIP file, or a (Linux) TAR.GZ file. You must unpack them ``some where'' convenient. As of this writing FTDICHIP does not supply means to install these files "in an appropriate place." If your distribution does not package these, there are several './configure' options to solve this problem: --with-ftd2xx-win32-zipdir Where (CYGWIN/MINGW) the zip file from ftdichip.com was unpacked --with-ftd2xx-linux-tardir Where (Linux/Unix) the tar file from ftdichip.com was unpacked --with-ftd2xx-lib Use static or shared ftd2xx libs on default static If you are using the FTDICHIP.COM driver, download and unpack the Windows or Linux FTD2xx drivers from the following location: http://www.ftdichip.com/Drivers/D2XX.htm Remember, this library is binary-only, while OpenOCD is licenced according to GNU GPLv2 without any exceptions. That means that _distributing_ copies of OpenOCD built with the FTDI code would violate the OpenOCD licensing terms. Linux Notes *********** The Linux tar.gz archive contains a directory named libftd2xx0.4.16 (or similar). Assuming that you have extracted this archive in the same directory as the OpenOCD package, you could configure with options like the following: ./configure \ --enable-ft2232_ftd2xx \ --with-ft2xx-linux-tardir=../libftd2xx0.4.16 \ ... other options ... Note that on Linux there is no good reason to use these FTDI binaries; they are no faster (on Linux) than libftdi, and cause licensing issues. ========================== Obtaining OpenOCD From GIT ========================== You can download the current GIT version with a GIT client of your choice from the main repository: git://openocd.git.sourceforge.net/gitroot/openocd/openocd You may prefer to use a mirror: http://repo.or.cz/r/openocd.git git://repo.or.cz/openocd.git Using the GIT command line client, you might use the following command to set up a local copy of the current repository (make sure there is no directory called "openocd" in the current directory): git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd Then you can update that at your convenience using git pull There is also a gitweb interface, which you can use either to browse the repository or to download arbitrary snapshots using HTTP: http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd http://repo.or.cz/w/openocd.git Snapshots are compressed tarballs of the source tree, about 1.3 MBytes each at this writing. Tips For Building From a GIT Repository --------------------------------------- Building OpenOCD from a repository requires a recent version of the GNU autotools (autoconf >= 2.59 and automake >= 1.9). 1) Run './bootstrap' to create the 'configure' script and prepare the build process for your host system. 2) Run './configure --enable-maintainer-mode' with other options. 80 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137