Flasher User Guide Software Version V4.72 Manual Rev. 0 Date: June 12, 2013 Document: UM08022 A product of SEGGER Microconroller GmbH & Co. KG www.segger.com 2 Disclaimer Specifications written in this document are believed to be accurate, but are not guaranteed to be entirely free of error. The information in this manual is subject to change for functional or performance improvements without notice. Please make sure your manual is the latest edition. While the information herein is assumed to be accurate, SEGGER Microcontroller GmbH & Co. KG (the manufacturer) assumes no responsibility for any errors or omissions. The manufacturer makes and you receive no warranties or conditions, express, implied, statutory or in any communication with you. The manufacturer specifically disclaims any implied warranty of merchantability or fitness for a particular purpose. Copyright notice You may not extract portions of this manual or modify the PDF file in any way without the prior written permission of the manufacturer. The software described in this document is furnished under a license and may only be used or copied in accordance with the terms of such a license. (c) 2013 SEGGER Microcontroller GmbH & Co. KG, Hilden / Germany Trademarks Names mentioned in this manual may be trademarks of their respective companies. Brand and product names are trademarks or registered trademarks of their respective holders. Contact address SEGGER Microcontroller GmbH & Co. KG In den Weiden 11 D-40721 Hilden Germany Tel.+49 2103-2878-0 Fax.+49 2103-2878-28 Email: support@segger.com Internet: http://www.segger.com Revisions This manual describes the Flasher device. For further information on topics or routines not yet specified, please contact us . Revision Date By V4.72 Rev. 0 130612 EL V4.64a Rev. 0 130226 EL V4.63a Rev. 0 130131 EL V4.62 Rev. 0 130125 EL Flasher User Guide (UM08022) Explanation Chapter "Working with Flasher" * Section "Patch file support" Chapter "Working with Flasher" * Section "LED status indicators" updated. Chapter "Remote Control" * Section "ASCII command interface" Chapter "ASCII interface via Telnet" added. Flasher ARM, Flasher RX and Flasher PPC manual have been combined. (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 3 About this document This document describes the Flasher family (Flasher ARM, Flasher RX and Flasher PPC). It provides an overview about the major features of the Flasher, gives some background information about JTAG and describes Flasher related software packages available from Segger. Finally, the chapter Support and FAQs on page 63 helps to troubleshoot common problems. For simplicity, we will refer to Flasher ARM/RX/PPC as Flasher in this manual. Typographic conventions This manual uses the following typographic conventions: Style Used for Body Body text. Keyword Text that you enter at the command-prompt or that appears on the display (that is system functions, file- or pathnames). Reference Reference to chapters, tables and figures or other documents. GUIElement Buttons, dialog boxes, menu names, menu commands. Table 1.1: Typographic conventions Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 4 SEGGER Microcontroller GmbH & Co. KG develops and distributes software development tools and ANSI C software components (middleware) for embedded systems in several industries such as telecom, medical technology, consumer electronics, automotive industry and industrial automation. SEGGER's intention is to cut software developmenttime for embedded applications by offering compact flexible and easy to use middleware, allowing developers to concentrate on their application. Our most popular products are emWin, a universal graphic software package for embedded applications, and embOS, a small yet efficient real-time kernel. emWin, written entirely in ANSI C, can easily be used on any CPU and most any display. It is complemented by the available PC tools: Bitmap Converter, Font Converter, Simulator and Viewer. embOS supports most 8/16/32-bit CPUs. Its small memory footprint makes it suitable for single-chip applications. Apart from its main focus on software tools, SEGGER develops and produces programming tools for flash microcontrollers, as well as J-Link, a JTAG emulator to assist in development, debugging and production, which has rapidly become the industry standard for debug access to ARM cores. Corporate Office: http://www.segger.com EMBEDDED SOFTWARE (Middleware) United States Office: http://www.segger-us.com SEGGER TOOLS emWin Flasher Graphics software and GUI emWin is designed to provide an efficient, processor- and display controller-independent graphical user interface (GUI) for any application that operates with a graphical display. Starterkits, eval- and trial-versions are available. Flash programmer Flash Programming tool primarily for microcontrollers. J-Link embOS JTAG emulator with trace USB driven JTAG interface for ARM cores with Trace memory. supporting the ARM ETM (Embedded Trace Macrocell). Real Time Operating System embOS is an RTOS designed to offer the benefits of a complete multitasking system for hard real time applications with minimal resources. The profiling PC tool embOSView is included. emFile JTAG emulator for ARM cores USB driven JTAG interface for ARM cores. J-Trace J-Link / J-Trace Related Software Add-on software to be used with SEGGER's industry standard JTAG emulator, this includes flash programming software and flash breakpoints. File system emFile is an embedded file system with FAT12, FAT16 and FAT32 support. emFile has been optimized for minimum memory consumption in RAM and ROM while maintaining high speed. Various Device drivers, e.g. for NAND and NOR flashes, SD/MMC and CompactFlash cards, are available. emUSB USB device stack A USB stack designed to work on any embedded system with a USB client controller. Bulk communication and most standard device classes are supported. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 5 Table of Contents 1 Introduction ......................................................................................................................7 1.1 1.1.1 1.1.2 1.2 1.2.1 1.2.2 1.2.3 Flasher overview .......................................................................................8 Features of Flasher ....................................................................................8 Working environment .................................................................................8 Specifications.......................................................................................... 10 Specifications for Flasher ARM ................................................................... 10 Specifications for Flasher RX ..................................................................... 12 Specifications for Flasher PPC .................................................................... 14 2 Working with Flasher .....................................................................................................17 2.1 2.1.1 2.2 2.2.1 2.2.2 2.2.3 2.3 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.5 2.6 2.7 2.7.1 2.8 2.8.1 2.8.2 2.8.3 2.9 2.9.1 2.9.2 2.9.3 Setting up the IP interface ........................................................................ 18 Connecting the first time .......................................................................... 18 Operating modes ..................................................................................... 19 J-Link mode ............................................................................................ 19 Stand-alone mode ................................................................................... 23 MSD mode.............................................................................................. 24 Multiple File Support ................................................................................ 25 Serial number programming...................................................................... 26 Serial number settings ............................................................................. 26 Serial number file .................................................................................... 27 Serial number list file ............................................................................... 27 Programming process............................................................................... 28 Downloading serial number files to Flasher.................................................. 29 Sample setup.......................................................................................... 29 Patch file support..................................................................................... 31 Target interfaces ..................................................................................... 32 Supported microcontrollers ....................................................................... 33 Flasher................................................................................................... 33 Support of external flashes ....................................................................... 34 Flasher ARM............................................................................................ 34 Flasher RX .............................................................................................. 34 Flasher PPC ............................................................................................ 34 Supported cores ...................................................................................... 35 Flasher ARM............................................................................................ 35 Flasher RX .............................................................................................. 35 Flasher PPC ............................................................................................ 35 3 Remote control...............................................................................................................37 3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.3.5 3.3.6 Overview ................................................................................................ 38 Handshake control ................................................................................... 39 ASCII command interface ......................................................................... 40 Introduction............................................................................................ 40 General command and reply message format .............................................. 40 Settings for ASCII interface via RS232........................................................ 40 Settings for ASCII interface via Telnet ........................................................ 40 Commands to Flasher............................................................................... 41 Reply from Flasher................................................................................... 46 4 Performance ..................................................................................................................49 4.1 Performance of MCUs with internal flash memory ......................................... 50 Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 6 4.1.1 4.1.2 4.1.3 Flasher ARM ........................................................................................... 50 Flasher RX.............................................................................................. 50 Flasher PPC ............................................................................................ 50 5 Hardware .......................................................................................................................51 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.3 5.4 5.4.1 5.4.2 5.5 5.5.1 5.5.2 5.6 Flasher ARM 20-pin JTAG/SWD Connector .................................................. 52 Pinout JTAG............................................................................................ 52 Pinout SWD ............................................................................................ 53 Target power supply ................................................................................ 53 Flasher RX 14-pin connector ..................................................................... 55 Target power supply ................................................................................ 55 Flasher PPC 14-pin connector.................................................................... 57 Target board design ................................................................................ 58 Pull-up/pull-down resistors ....................................................................... 58 RESET, nTRST ........................................................................................ 58 Adapters ................................................................................................ 59 JTAG Isolator.......................................................................................... 59 J-Link Needle Adapter .............................................................................. 60 How to determine the hardware version ..................................................... 61 6 Support and FAQs .........................................................................................................63 6.1 6.2 Contacting support .................................................................................. 64 Frequently Asked Questions...................................................................... 65 7 Background information .................................................................................................67 7.1 7.1.1 7.1.2 7.1.3 Flash programming ................................................................................. 68 How does flash programming via Flasher work ?.......................................... 68 Data download to RAM ............................................................................. 68 Available options for flash programming ..................................................... 68 8 Glossary.........................................................................................................................69 9 Literature and references...............................................................................................73 Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 7 Chapter 1 Introduction This chapter gives a short overview about the different models of the Flasher family and their features. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 8 CHAPTER 1 1.1 Introduction Flasher overview Flasher is a programming tool for microcontrollers with on-chip or external flash memory. Flasher is designed for programming flash targets with the J-Flash software or stand-alone. In addition to that Flasher can also be used as a regular J-Link. For more information about J-Link in general, please refer to the J-Link / J-Trace User Guide which can be downloaded at http://www.segger.com. Flasher connects to a PC using the USB/Ethernet/RS232 interface, running Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 7 or Windows 8. In stand-alone mode, Flasher can be driven by the start/stop button, or via the RS232 interface (handshake control or ASCII interface). Flasher always has a 20-pin connector, which target interfaces are supported depends on the Flasher model: * * * 1.1.1 * * * * * * * * For Flasher ARM: JTAG and SWD are supported. For Flasher RX: JTAG is supported. Flasher comes with additional 14-pin RX adapter For Flasher PPC: JTAG is supported. Flasher comes with additional 14-pin PPC adapter. Features of Flasher Three boot modes: J-Link mode, stand-alone mode, MSD mode Stand-alone JTAG/SWD programmer (Once set up, Flasher can be controlled without the use of PC program) No power supply required, powered through USB Supports internal and external flash devices 64 MB memory for storage of target program Can be used as J-Link (emulator) with a download speed of up to 720 Kbytes/ second Serial in target programming supported Data files can updated via USB/Ethernet (using the J-Flash software), via RS232 or via the MSD functionality of Flasher Flasher model Flasher ARM Flasher RX Flasher PPC 1.1.2 Supported cores ARM7/ARM9/Cortex-M Renesas RX610, RX621, RX62N, RX62T Power PC e200z0 Supported target interfaces JTAG, SWD JTAG JTAG Flash programming speed (depending on target hardware) between 30-300 Kbytes/ second between 170 and 300 Kbytes/second up to 138 Kbytes/second Working environment General Flasher can operate from a PC with an appropriate software like J-Flash or in standalone mode. Host System IBM PC/AT or compatible CPU: 486 (or better) with at least 128MB of RAM, running Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 7 or Windows 8. It needs to have a USB, Ethernet or RS232 interface available for communication with Flasher. Power supply Flasher requires 5V DC, min. 100mA via USB connector. If USB is not connected, the USB connector is used to power the device. Supply voltage is the same in this case. Please avoid excess voltage. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 9 Installing Flasher PC-software J-Flash The latest version of the J-Flash software, which is part of the J-Link software and documentation package, can always be downloaded from our website: http:// www.segger.com/download_jlink.html. For more information about using J-Flash please refer to UM08007_FlasherARM.pdf (J-Flash user guide) which is also available for download on our website. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 10 CHAPTER 1 1.2 Introduction Specifications 1.2.1 Specifications for Flasher ARM General Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows +5 C ... +60 C -20 C ... +60 C <90% rH Supported OS Operating Temperature Storage Temperature Relative Humidity (non-condensing) 2000 XP XP x64 2003 2003 x64 Vista Vista x64 7 7 x64 8 8 x64 Mechanical Size (without cables) Weight (without cables) 121mm x 66mm x 30mm 119g Available interfaces USB Host interface Ethernet Host interface RS232 Host interface Target interface USB 2.0, full speed 10/100 MBit RS232 9-pin JTAG 20-pin (14-pin adapter available) JTAG Interface, Electrical Power Supply Target interface voltage (VIF) Target supply voltage Target supply current Reset Type Reset low level output voltage (VOL) USB powered, 100mA for Flasher ARM. 500 mA if target is powered by Flasher ARM 1.2 ... 5V 4.5V...5V (on the 14-pin adapter the target supply voltage can be switched between 3.3V and 5V) max. 400mA Open drain. Can be pulled low or tristated V OL <= 10% of VIF For the whole target voltage range (1.8V <= V IF <= 5V) LOW level input voltage (VIL) V IL <= 40% of V IF HIGH level input voltage (VIH) V IH >= 60% of VIF For 1.8V <= V IF <= 3.6V LOW level output voltage (V OL) with a load of 10 kOhm HIGH level output voltage (VOH ) with a load of 10 kOhm V OL <= 10% of VIF V OH >= 90% of V IF For 3.6 <= V IF <= 5V LOW level output voltage (V OL) with a load of 10 kOhm V OL <= 20% of VIF Table 1.1: Flasher ARM specifications Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 11 HIGH level output voltage (VOH ) with a load of 10 kOhm V OH >= 80% of V IF JTAG Interface, Timing Max. JTAG speed Data input rise time (Trdi) up to 12MHz Trdi <= 20ns Data input fall time (Tfdi) Data output rise time (Trdo) T fdi <= 20ns Data output fall time (T fdo) Clock rise time (Trc) T fdo <= 10ns Trdo <= 10ns Trc <= 10ns Clock fall time (Tfc) Table 1.1: Flasher ARM specifications T fc <= 10ns 1.2.1.1 Flasher ARM download speed The following table lists Flasher ARM performance values (Kbytes/second) for writing to memory (RAM) via the JTAG interface: Hardware Flasher ARM ARM7 memory download 720 Kbytes/s (12MHz JTAG) Table 1.2: Download speed of Flasher ARM Note: The actual speed depends on various factors, such as JTAG, clock speed, host CPU core etc. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 12 CHAPTER 1 1.2.2 Introduction Specifications for Flasher RX General Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows +5 C ... +60 C -20 C ... +60 C <90% rH Supported OS Operating Temperature Storage Temperature Relative Humidity (non-condensing) 2000 XP XP x64 2003 2003 x64 Vista Vista x64 7 7 x64 8 8 x64 Mechanical Size (without cables) Weight (without cables) 121mm x 66mm x 30mm 119g Available interfaces USB Host interface Ethernet Host interface RS232 Host interface USB 2.0, full speed 10/100 MBit RS232 9-pin JTAG 20-pin (shipped with 14-pin adapter for Renesas RX) Target interface JTAG Interface, Electrical Power Supply Target interface voltage (VIF) Target supply voltage Target supply current Reset Type Reset low level output voltage (VOL) USB powered, 100mA for Flasher ARM. 500 mA if target is powered by Flasher ARM 1.2 ... 5V 4.5V...5V (on the 14-pin adapter the target supply voltage can be switched between 3.3V and 5V) max. 400mA Open drain. Can be pulled low or tristated V OL <= 10% of VIF For the whole target voltage range (1.8V <= V IF <= 5V) LOW level input voltage (VIL) V IL <= 40% of V IF HIGH level input voltage (VIH) V IH >= 60% of VIF For 1.8V <= V IF <= 3.6V LOW level output voltage (V OL) with a load of 10 kOhm HIGH level output voltage (VOH ) with a load of 10 kOhm V OL <= 10% of VIF V OH >= 90% of V IF For 3.6 <= V IF <= 5V LOW level output voltage (V OL) with a load of 10 kOhm HIGH level output voltage (VOH ) with a load of 10 kOhm V OL <= 20% of VIF V OH >= 80% of V IF Table 1.3: Flasher RX specifications Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 13 JTAG Interface, Timing Max. JTAG speed Data input rise time (Trdi) up to 12MHz Trdi <= 20ns Data input fall time (Tfdi) Data output rise time (Trdo) T fdi <= 20ns Data output fall time (T fdo) Clock rise time (Trc) T fdo <= 10ns Clock fall time (Tfc) T fc <= 10ns Trdo <= 10ns Trc <= 10ns Table 1.3: Flasher RX specifications 1.2.2.1 Flasher RX download speed The following table lists Flasher RX performance values (Kbytes/second) for writing to memory (RAM) via the JTAG interface: Hardware Flasher RX Flasher RX600 series memory download 720 Kbytes/s (12MHz JTAG) Table 1.4: Download speed of Flasher RX Note: The actual speed depends on various factors, such as JTAG, clock speed, host CPU core etc. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 14 CHAPTER 1 1.2.3 Introduction Specifications for Flasher PPC General Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows Microsoft Windows +5 C ... +60 C -20 C ... +60 C <90% rH Supported OS Operating Temperature Storage Temperature Relative Humidity (non-condensing) 2000 XP XP x64 2003 2003 x64 Vista Vista x64 7 7 x64 8 8 x64 Mechanical Size (without cables) Weight (without cables) 121mm x 66mm x 30mm 119g Available interfaces USB Host interface Ethernet Host interface RS232 Host interface USB 2.0, full speed 10/100 MBit RS232 9-pin JTAG 20-pin (shipped with 14-pin adapter for Renesas PPC) Target interface JTAG Interface, Electrical Power Supply Target interface voltage (VIF) Target supply voltage Target supply current Reset Type Reset low level output voltage (VOL) USB powered, 100mA for Flasher ARM. 500 mA if target is powered by Flasher ARM 1.2 ... 5V 4.5V...5V (on the 14-pin adapter the target supply voltage can be switched between 3.3V and 5V) max. 400mA Open drain. Can be pulled low or tristated V OL <= 10% of VIF For the whole target voltage range (1.8V <= V IF <= 5V) LOW level input voltage (VIL) V IL <= 40% of V IF HIGH level input voltage (VIH) V IH >= 60% of VIF For 1.8V <= V IF <= 3.6V LOW level output voltage (V OL) with a load of 10 kOhm HIGH level output voltage (VOH ) with a load of 10 kOhm V OL <= 10% of VIF V OH >= 90% of V IF For 3.6 <= V IF <= 5V LOW level output voltage (V OL) with a load of 10 kOhm HIGH level output voltage (VOH ) with a load of 10 kOhm V OL <= 20% of VIF V OH >= 80% of V IF Table 1.5: Flasher PPC specifications Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 15 JTAG Interface, Timing Max. JTAG speed Data input rise time (Trdi) up to 12MHz Trdi <= 20ns Data input fall time (Tfdi) Data output rise time (Trdo) T fdi <= 20ns Data output fall time (T fdo) Clock rise time (Trc) T fdo <= 10ns Clock fall time (Tfc) T fc <= 10ns Trdo <= 10ns Trc <= 10ns Table 1.5: Flasher PPC specifications 1.2.3.1 Flasher PPC download speed The following table lists Flasher PPC performance values (Kbytes/second) for writing to memory (RAM) via the JTAG interface: Hardware Flasher PPC Memory download 530 Kbytes/s (8 MHz JTAG) Table 1.6: Download speed of Flasher PPC Note: The actual speed depends on various factors, such as JTAG, clock speed, host CPU core etc. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 16 Flasher User Guide (UM08022) CHAPTER 1 Introduction (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 17 Chapter 2 Working with Flasher This chapter describes functionality and how to use Flasher. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 18 CHAPTER 2 2.1 Working with Flasher Setting up the IP interface Since hardware version 3 Flasher family comes with an additional Ethernet interface to communicate with the host system. These Flashers also come with a built-in webserver which allows some basic setup of the emulator, e.g. configuring a default gateway which allows using it even in large intranets. 2.1.1 Connecting the first time When connecting Flasher the first time, it attempts to acquire an IP address via DHCP. The recommended way for finding out which IP address has been assigned to Flasher is, to use the J-Link Configurator. The J-Link Configurator is a small GUIbased utility which shows a list of all emulator that are connected to the host PC via USB and Ethernet. For more information about the J-Link Configurator, please refer to UM08001_JLinkARM.pdf (J-Link / J-Trace user guide), chapter Setup, section JLink Configurator. The setup of the IP interface of Flasher is the same as for other emulators of the J-Link family. For more information about how to setup the IP interface of Flasher, please refer to UM08001, J-Link / J-Trace User Guide, chapter Setup, section Setting up the IP interface. For more information about how to use Flasher via Ethernet or prepare Flasher via Ethernet for stand-alone mode, please refer to Operating modes on page 19. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 19 2.2 Operating modes Flasher is able to boot in 3 different modes: * * * J-Link mode Stand-alone mode MSD (Mass storage device) mode If Flasher can establish an Ethernet uplink or can enumerate on the USB port, it boots in "J-Link mode". In this mode, Flasher can be used as a J-Link. When supply power is enabled and Flasher can not establish a connection with the host, the "stand-alone mode" is started. In this mode Flasher can be used as a stand-alone flash programmer. When the Start/Stop button is pressed when power supply is enabled, Flasher boots in "MSD mode". In this mode, Flasher boots as a mass storage device. 2.2.1 J-Link mode If you want to use Flasher for the first time you need to install the J-Link software and documentation package. After installation, connect Flasher to the host PC via USB or Ethernet. For more information about how to install the J-Link software and documentation package please refer to the J-Link / J-Trace User Guide, chapter Setup which can be downloaded from http://www.segger.com/download_jlink.html. 2.2.1.1 Connecting the target system Power-on sequence In general, Flasher should be powered on before connecting it with the target device. That means you should first connect Flasher with the host system via USB / Ethernet and then connect Flasher with the target device via JTAG or SWD. Power-on the device after you connected Flasher to it. Flasher will boot in "J-Link mode". Verifying target device connection with J-Link.exe If the USB driver is working properly and your Flasher is connected with the host system, you may connect Flasher to your target hardware. Then start the J-Link command line tool JLink.exe, which should now display the normal Flasher related information and in addition to that it should report that it found a JTAG target and the targets core ID. The screenshot below shows the output of JLink.exe. 2.2.1.2 Setting up Flasher for stand-alone mode In order to set up Flasher for the stand-alone mode it needs to be configured once using the J-Flash software. For more information about J-Flash, please refer to the JFlash User Guide. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 20 CHAPTER 2 Working with Flasher After starting J-Flash, open the appropriate J-Flash project for the target Flasher shall be configured for, by selecting File -> Open Project. If J-Flash does not come with an appropriate sample project for the desired hardware, a new project needs to be created by selecting File -> New Project. After the appropriate project has been opened / created, the data file which shall be programmed needs to be loaded, by selecting File -> Open. After this J-Flash should look like in the screenshot below. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 21 Before downloading the configuration (project) and program data (data file) to Flasher, the connection type (USB/IP) needs to be selected in the project. These settings are also saved on a per-project basis, so this also only needs to be setup once per J-Flash project. The connection dialog is opened by clicking Options -> Project settings -> General. The connection dialog allows the user to select how to connect to Flasher. When connecting to a Flasher via TCP/IP it is not mandatory to enter an IP address. If the field is left blank and File->Download to programmer is selected, an emulator selection dialog pops up which shows all Flasher which have been found on the network. The user then can simply select the Flash he wants to download the configuration to. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 22 CHAPTER 2 Working with Flasher In order to download the configuration and program data to the Flasher, simply select File -> Download config & data file to Flasher. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 23 The J-Flash log window indicates that the download to the emulator was successful. From now on, Flasher can be used in stand-alone mode (without host PC interaction) for stand-alone programming. 2.2.2 Stand-alone mode In order to use Flasher in "stand-alone mode", it has to be configured first, as described in Setting up Flasher for stand-alone mode on page 19. To boot Flasher in the "stand-alone mode", only the power supply to Flasher has to be enabled (Flasher should not be connected to a PC). In the "stand-alone mode" Flasher can be used as a stand-alone flash programmer. Note: Flasher can only program the target device it was configured for. In order to program another target device, you have to repeat the steps described in Setting up Flasher for stand-alone mode on page 19. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 24 CHAPTER 2 Working with Flasher 2.2.2.1 LED status indicators Progress and result of an operation is indicated by Flasher's LEDs: # 0 1 2 3 4 Status of LED Meaning Flasher ARM is waiting for USB enumeration or ethernet link. As soon as USB has been enumerated or ethernet link has been established, the green LED stops flashing and is switched to conGREEN stant green. In stand-alone-mode, Flasher high frequency blinking remains in the high frequency blinking state until (On/Off time: 50ms => 10Hz) state #1 is reached. Flasher goes to state #1 as soon as a #START command has been received via the ASCII interface or the Start button has been pushed. GREEN Connect to target and perform init sequence. constant Flashing operation in progress: 1. Erasing (slow blinking on/off time: 80 ms => 6.25 HZ) GREEN 2. Programming (slow blinking on/off slow blinking time: 300ms => ~1.67 Hz) 3. Verifying (slow blinking, on/off time: 100ms => 5 Hz) GREEN Operation successful. Goes back to state #0 constant automatically. Operation failed. Goes back to state #0 automatRED ically but red LED remains on until state #1 (next constant programming cycle) is entered again. Table 2.1: Flasher LEDs 2.2.3 MSD mode When pressing the Start/Stop button of Flasher while connecting it to the PC, Flasher will boot in the "MSD mode". This mode can be used to downdate a Flasher firmware version if a firmware update did not work properly and it can be used to configure Flasher for the "stand-alone mode", without using J-Flash. If Flasher has been configured for "stand-alone mode" as described in the section above, there will be four files on the MSD, FLASHER.CFG, FLASHER.DAT, FLASHER.LOG, SERIAL.TXT. FLASHER.CFG contains the configuration settings for programming the target device and FLASHER.DAT contains the data to be programmed. FLASHER.LOG contains all logging information about the commands, performed in stand-alone mode. The SERIAL.TXT contains the serial number, which will be programmed next. J-Flash supports to configure Flasher for automated serial number programming. For furhter information about how to configure Currently, J-Flash does not support to configure Flasher for automated serial number programming. If you want to configure multiple Flasher for the same target you do not have to use J-Flash all the time. It is also possible to copy the FLASHER.CFG and the FLASHER.DAT files from a configured Flasher to another one. To copy these files boot Flasher in "MSD mode". Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 25 2.3 Multiple File Support It is also possible to have multiple data files and config files on Flasher, to make Flasher more easy to use in production environment. To choose the correct configuration file and data file pair, a FLASHER.INI file is used. This init file contains a [FILES] section which describes which configuration file and which data file should be used for programming. A sample content of a FLASHER.INI file is shown below: [FILES] DataFile = "Flasher1.dat" ConfigFile = "Flasher1.cfg" Using this method all configuration files and data files which are used in the production only have to be downloaded once. From there on a configuration file / data file pair can be switched by simply replacing the FLASHER.INI by a new one, which contains the new descriptions for the configuration file and data file. The FLASHER.INI can be replaced in two ways: 1. 2. Boot Flasher in MSD mode in order to replace the FLASHER.INI If Flasher is already integrated into the production line, runs in stand-alone mode and can not be booted in other mode: Use the file I/O commands provided by the ASCII interface of Flasher, to replace the FLASHER.INI. For more information about the file I/O commands, please refer to File I/O commands on page 44. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 26 CHAPTER 2 2.4 Working with Flasher Serial number programming Flasher supports programming of serial numbers. In order to use the serial number programming feature, the J-Flash project to be used as well as some files on the Flasher (depending on the configuration) need to be configured first. In general, Flasher supports two ways of programming a serial number into the target: 1. 2. Programming continuous serial numbers. Serial number is 1-4 bytes in size. Start serial number, increment, serial number size and address is configured in the J-Flash project. Programming custom serial numbers from a serial number list file. Start line into serial number list file to get next serial number bytes, line increment, serial number size and address is configured in J-Flash project. Serial number list file needs to be specified and created by user. In the following some generic information how to setup Flasher & the J-Flash project for serial number programming are given. Note: Full serial number programming support has been introduced with V4.51d of the J-Flash software and the Flasher firmware that comes with it. Note: Currently, programming of serial numbers is only supported for standalone mode. Future versions of J-Flash may also support serial number programming in J-Link mode. 2.4.1 Serial number settings In order to enable the programming of serial numbers in stand-alone mode, the JFlash project has to be configured to enable programming a serial number at a specific address. This is done by enabling the Program serial number option as shown in the screenshot and table below: Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 27 Setting Address Meaning The address the serial number should be programmed at. The length of the serial number (in bytes) which should be programmed. If no serial number list file is given, JFlash allows to use a 1-4 byte serial number. In case of 8 is selected as length, the serial number and its complementary is programmed at the given address. Len In case a serial number list file is given, Flasher will take the serial number bytes from the list file. If a serial number in the list file does not define all bytes of Len, the remaining bytes are filled with 0s. No complements etc. are added to the serial number. In case no serial number list file is given, Next SN is next serial number which should be programmed. The serial number is always stored in little endian format in the flash memory. Next SN Increment In case a serial number list file is given, Next SN describes the line of the serial number list file where to read the next serial number bytes from. Flasher starts counting with line 0, so in order to start serial number programming with the first line of the SNList.txt, Next SN needs to be set to 0. Specifies how much Next SN is incremented. Table 2.2: Flasher serial number settings 2.4.2 Serial number file When selecting File -> Download serial number file to Flasher, J-Flash will create a Serial number file named as <JFlashProjectName>_Serial.txt. This file is downloaded as SERIAL.TXT on Flasher. The file is generated based on the serial number settings in the J-Flash project and will contain the value defined by the Next SN option. The serial number file can also be manually edited by the user, since the serial number is written ASCII encoded in the SERIAL.TXT file. 2.4.3 Serial number list file In order to program custom serial numbers which can not be covered by the standard serial number scheme provided by J-Flash (e.g. when programming non-continuous serial numbers or having gaps between the serial numbers), a so called serial number list file needs to be created by the user. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 28 CHAPTER 2 Working with Flasher When selecting File-> Download serial number file to Flasher, J-Flash will look for a serial number list file named as <JFlashProjectName>_SNList.txt in the directory where the J-Flash project is located. This file is downloaded as SNList.txt on Flasher. The serial number list file needs to be created manually by the user and has the following syntax: * * One serial number per line Each byte of the serial number is described by two hexadecimal digits. Example A 8-byte serial number should be programmed at address 0x08000000. It should be programmed as follows in the memory: 0x08000000: 0x01 0x02 0x03 0x04 0x55 0x66 0x77 0x88 The serial number list file should look as follows: 0102030455667788 The number of bytes to read per line is configured via the Len option in J-Flash. For more information, please refer to Serial number settings on page 26. Which line Flasher will read at the next programming cycle, is configured via the Next SN option in J-Flash. For more information, please refer to Serial number settings on page 26. In this case Next SN needs to be set to 0, since programming should be started with the serial number bytes defined in the first line of the file. Note: If the number of bytes specified in a line of the serial number list file is less than the serial number length defined in the project, the remaining bytes filled with 0s by Flasher. Note: If the number of bytes specified in a line of the serial number list file is greater than the serial number length defined in the J-Flash project, the remaining bytes will be ignored by Flasher. 2.4.4 Programming process Flasher will increment the serial number in SERIAL.TXT by the value defined in Increment, after each successful programming cycle. For each programming cycle, the FLASHER.LOG on the Flasher is updated and contains the value from SERIAL.TXT that has been used for the programming cycle. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 29 Note: The serial number in SERIAL.TXT will also be incremented in case if serial number programming is disabled, to make sure that for the Flasher logfile there is a reference which programming cycle passed and which not. As long as serial number programming has not been enabled in the J-Flash project, Flasher does not merge any serial number data into the image data to be programmed. 2.4.5 Downloading serial number files to Flasher Downloading the serial number files needs to be done explicitly by selecting File-> Download serial number file to Flasher. Please note that the File -> Download config & data file to Flasher option does only download the configuration and data file to Flasher since usually the current serial number used for programming shall not be reset/overwritten when just updating the image Flasher shall program. 2.4.6 Sample setup In the following a small sample is given how to setup Flasher for serial number programming. In the following sample, 4-byte serial numbers starting at 1234567 (0x12D687) shall be programmed at address 0x08001000. Defining serial number address, length and start value In the J-Flash project the following needs to be defined: * * * * Address is 0x08001000 Next SN is 1234567 Increment is 1 Len is 4 (bytes) Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 30 CHAPTER 2 Working with Flasher Downloading configuration, data and serial number to Flasher. After setting up the rest of the configuration (Target interface etc.) and selecting an appropriate data file, the configuration, data and serial number file is downloaded into Flasher via the File -> Download config & data file to Flasher and File-> Download serial number file to Flasher option. After downloading the serial number to Flasher, J-Flash also created the <JFlashProjectName>_Serial.txt. Now Flasher is prepared to program the 8-byte serial number. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 31 2.5 Patch file support In stand-alone mode Flasher supports patch files which allows to patch the content of the data to be programmed. Before starting programming process in stand-alone mode, Flasher will look for a file named Patches.txt being present on the Flasher. This file includes the patches. If this file is present, the number in Serial.txt describes the line number of the Patches.txt that will be used for the current cycle (line counting starts at 0). Each line in the Patches.txt can hold up to 4 patches, where each patch can be up to 32 bytes in length. Syntax The syntax for <NumPatches>==4 is as follows: <NumPatches>,<Addr>,<NumBytes>,<Data>,<Addr>,<NumBytes>,<Data>,<Addr>, <NumBytes>,<Data>,<Addr>,<NumBytes>:<Data>\r\n Each patch-line containts describes each parameter. Parameter <NumPatches> <Addr> <NumBytes> <Data> Note: <Addr>,<NumBytes>:<Data>. Find below a table which Description Describes the number of patches in this patch line. Max. value is 4. Describes the address to be patched. Value is expected in hex. Number of bytes for the current patch. Max. value is 20h (32 in decimal). Describes the data to be patched. <Data> is always expected as 2 characters per byte. All values are expected in hexadecimal format (hex). <Data> section is always preceeded by ":", not ",". Example Please find below a sample sequence which clarifies the usage of patch files. Patches.txt, which is located on the Flasher, contains the following line: 3,100025,3,AABBCC,100063,2,DDEE,100078,1,FF Serial.txt contains a "0" which force the Flasher to use line 0 from Patches.txt. After starting the programming cycle, the following data will be patched: Addr 0x100025: 3 byte 0xAA 0xBB 0xCC Addr 0x100063: 2 byte 0xDD 0xEE Addr 0x100078: 1 byte 0xFF Single patch via RS232 Alternatively, you can start a programming cycle with patch data that is only valid for this one cycle (no need for a Patches.txt file): Send the #AUTO PATCH <NumPatches>,<Addr>,<NumBytes>:<Data> command via Flasher ASCII interface. The parameters have the same function as described in the table above. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 32 CHAPTER 2 2.6 Working with Flasher Target interfaces The table below shows the supported target interfaces of the different Flasher models. Hardware Flasher ARM Flasher RX Flasher PPC Supported interfaces JTAG, SWD JTAG JTAG Table 2.3: Supported target interfaces by Flasher For more information about the target interfaces itself, please refer to: * * UM08001, chapter "Working with J-Link and J-Trace", section "JTAG interface" UM08001, chapter "Working with J-Link and J-Trace", section "SWD interface" Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 33 2.7 Supported microcontrollers 2.7.1 Flasher Flasher supports download into the internal flash of a large number of microcontrollers. The number of supported devices is steadily growing, so you can always find the latest list of supported devices on our website: http://www.segger.com/supported-devices.html Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 34 CHAPTER 2 2.8 Working with Flasher Support of external flashes 2.8.1 Flasher ARM In general Flasher ARM supports programming of external flashes listed below: * * * * parallel NOR flash serial NOR flash NAND flash DataFlash If the parallel NOR flash device which is used is not CFI-compliant you have to select the flash device in J-Flash explicitly, for a list of all parallel NOR flash devices which can be explicitly selected in J-Flash, please refer to UM08003, J-Flash User Guide, chapter Supported Flash Devices. For serial NOR flash, NAND flash and DataFlash devices a custom RAMCode is needed since the connection of the flash to the CPU differs from device to device. The J-Flash software comes with sample projects for custom RAMCodes. For a complete list of all custom RAMCode projects which come with the J-Flash software, please refer to: http://www.segger.com/supporteddevices.html 2.8.2 Flasher RX Programming of external parallel NOR flash is currently not supported by Flasher RX. This limitation will be lifted in the near future. 2.8.3 Flasher PPC Programming of external parallel NOR flash is currently not supported by Flasher PPC. This limitation will be lifted in the near future. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 35 2.9 Supported cores 2.9.1 Flasher ARM Flasher ARM supports and has been tested with the following cores, but should work with any ARM7/9, Cortex-M0/M1/M3/M4 core. If you experience problems with a particular core, do not hesitate to contact Segger. * * * * * * * * * * * * 2.9.2 ARM7TDMI (Rev 1) ARM7TDMI (Rev 3) ARM7TDMI-S (Rev 4) ARM920T ARM922T ARM926EJ-S ARM946E-S ARM966E-S Cortex-M0 Cortex-M1 Cortex-M3 Cortex-M4 Flasher RX Flasher RX supports and has been tested with the following cores. If you experience problems with a particular core, do not hesitate to contact Segger. * * * * 2.9.3 RX610 RX621 RX62N RX62T Flasher PPC Flasher PPC supports and has been tested with the following cores. If you experience problems with a particular core, do not hesitate to contact Segger. * e200z0 Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 36 Flasher User Guide (UM08022) CHAPTER 2 Working with Flasher (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 37 Chapter 3 Remote control This chapter describes how to control Flasher via the 9-pin serial interface connector. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 38 CHAPTER 3 3.1 Remote control Overview There are 3 ways to control Flasher operation: * * * Manual: Programming operation starts when pressing the button. The LEDs serve as visible indication. Via Handshake lines: 3 lines on the serial interface are used. 1 line is an input and can be used to start operation, 2 lines are outputs and serve as Busy and status output Terminal communication via RS232. Note: All three ways to control Flasher operation are working only if Flasher is in standalone mode. In J-Link / MSD mode they have no effect. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 39 3.2 Handshake control Flasher can be remote controlled by automated testers without the need of a connection to PC and Flasher's PC program. Therefore Flasher is equipped with additional hardware control functions, which are connected to the SUBD9 male connector, normally used as RS232 interface to PC. The following diagrams show the internal remote control circuitry of Flasher: 5 4 BUSY 7 OK 1 START 470 Flasher internal Logic 470 22k 4k7 START BUSY BUSY OK Pin No. Ready previous state Function 1 START 4 BUSY 5 GND 7 OK Undefined valid Not OK OK Description A positive pulse of any voltage between 5 and 30V with duration of min. 30 ms starts "Auto" function (Clear / Program / Verify) on falling edge of pulse. The behavior of the "Auto" function depends on the project settings, chosen in J-Flash at the Production tab. As soon as the "Auto" function is started, BUSY becomes active, which means that transistor is switched OFF. Common Signal ground. This output reflects result of last action. It is valid after BUSY turned back to passive state. The output transistor is switched ON to reflect OK state. Table 3.1: Flasher LED status Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 40 CHAPTER 3 3.3 Remote control ASCII command interface 3.3.1 Introduction Once set up using J-Flash, Flasher can be driven by any application or just a simple terminal using ASCII commands. Every known command is acknowledged by Flasher and then executed. After command execution, Flasher sends an ASCII reply message. Note: Note: There are situations where the execution of a known command is rejected with #NACK:ERRxxx if Flasher is currently busy and the received command is not allowed to be sent while Flasher is busy 3.3.2 * * * 3.3.3 General command and reply message format Any ASCII command has to start with the start delimiter #. Any ASCII command has to end with simple carriage return ('\r', ASCII code 13). Commands can be sent upper or lower case. Settings for ASCII interface via RS232 Flasher is driven via a RS232 serial port with the following interface settings: * * * 8 data bits, no parity 1 stop bit at 9600 baud. 3.3.4 Settings for ASCII interface via Telnet A client application can connect to Flasher via Telnet on port 23. Find below a screenshot of Flasher which is remot controlled via Telnet: Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 41 3.3.5 Commands to Flasher The table below gives a overview about the commands which are supported by the current version of Flasher firmware. Click on the names for a detailed descripion: Commands #AUTO #AUTO PATCH #AUTO NOINFO #CANCEL #ERASE #PROGRAM #RESULT #SELECT <Filename> #START #STATUS #VERIFY File I/O commands #FCLOSE #FDELETE <Filename> #FOPEN <Filename> #FREAD <Offset>,<NumBytes> #FSIZE #FWRITE <Offset>,<NumBytes>:<Data> Reply from Flasher #ACK #NACK #OK #OK:<NumBytes>:<Data> #OK:<Size> #STATUS: #ERRxxx #AUTO The #AUTO command behaves exactly as the start button or external remote control input. Usually, the following command sequence will be performed when receiving the #AUTO command: * * * Flasher starts erasing Flasher programs target CPU Flasher verifies target CPU Depending on the settings chosen in the Production tab in J-Flash, this sequence can differ from the one shown above. Finally, Flasher responds with * * #OK if no error occurred #ERRxxx if any error occurred during operation. xxx represents the error code, normally replied to Flasher PC program. The #ERRxxx message may be followed by an additional error text. During execution of the #AUTO command, Flasher automatically sends "status" messages via RS232 to reflect the state of execution. Typically during execution of #AUTO command, Flasher will reply the following sequence of messages: #ACK Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 42 CHAPTER 3 Remote control #STATUS:INITIALIZING #STATUS:CONNECTING #STATUS:UNLOCKING #STATUS:ERASING #STATUS:PROGRAMMING #STATUS:VERIFYING #OK (Total 13.993s, Erase 0.483s, Prog 9.183s, Verify 2.514s) #AUTO PATCH The #AUTO PATCH command allows to patch the content of the data to be programmed. Flasher responds with * * #OK if no error occurred #ERRxxx if any error occurred during operation. xxx represents the error code, normally replied to Flasher PC program. The #ERRxxx message may be followed by an additional error text. For further information about the usage of the #AUTO PATCH command please refer to Patch file support on page 31. #AUTO NOINFO This command may be used instead of #AUTO, if no status messages from Flasher should be sent during execution. The NOINFO extension is also available for all other commands. The command ends with #OK or #ERRxxx #BAUDRATE<Baudrate> This command can be sent in order to change the baudrate of the UART used for the ASCII command interface communication. <Baudrate> is expected in decimal format. If this command succeeds, Flasher responds with: #ACK #OK Otherwise it will respond with one of the following error messages: #ERR255: Invalid parameters or #ERR255: Baudrate is not supported Note: After sending the #BAUDRATE command you will first have to wait until the Flasher responds with the #OK message. It is recommended wait 5ms before sending the next command with the new baudrate in order to give the Flasher the time to change the baudrate. #CANCEL This command can be sent to abort a running program. It may take a while until the current program is actually canceled. Flasher will respond with: #ERR007:CANCELED. #ERASE This command can be sent to erase all selected target flash sectors. Flasher will reply the following sequence of messages: Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 43 #ACK #STATUS:INITIALIZING #STATUS:CONNECTING #STATUS:UNLOCKING #STATUS:ERASING #OK (Total 0.893s, Erase 0.483s) #PROGRAM This command can be used instead of #AUTO to program a target without erasing the target before programming and without performing a final verification. #RESULT This command can be sent any time, even during other command execution. Flasher responds with the last result of the previously executed command. #SELECT <Filename> The #SELECT command is used to select a specific config and data file pair which should be used by Flasher to program the target. <Filename> specifies the name of file pair without extensions (.CFG and .DAT) on the Flasher which should be selected. Flasher saves the selected config and data file in the FLASHER.INI file. So this selection is remembered even between power-cycling Flasher. This may be verfy helpful in cases where several config and data files are stored on Flasher. The user can easily switch between these config and data files without connecting Flasher to a host. If this command succeeds, Flasher responds with: #ACK #OK Find below a sample sequence which shows how to use the #SELECT command: #SELECT ATSAM7_1 // ATSAM7_1.CFG and ATSAM7_1.DAT is selected #ACK #OK #AUTO // Start auto programming #ACK #STATUS:INITIALIZING #STATUS:CONNECTING #STATUS:UNLOCKING #STATUS:ERASING #STATUS:PROGRAMMING #STATUS:VERIFYING #OK (Total 8.416s, Erase 0.005s, Prog 6.845s, Verify 0.959s) #SELECT ATSAM7_2 // ATSAM7_2.CFG and ATSAM7_2.DAT is selected #ACK #OK #AUTO // Start auto programming #ACK #STATUS:INITIALIZING #STATUS:CONNECTING #STATUS:UNLOCKING #STATUS:ERASING #STATUS:PROGRAMMING #STATUS:VERIFYING #OK (Total 8.632s, Erase 0.005s, Prog 7.051s, Verify 0.969s) #START This command can be sent to release Flasher's target interface. All signals from Flasher to target will be set into high-Z mode, reset of target will be released. It may be used to start target application program. Flasher will reply with the following sequence of messages: Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 44 CHAPTER 3 Remote control #ACK #STATUS:INITIALIZING #STATUS:CONNECTING #OK (Total 1.148s) #STATUS This command can be sent any time, even during other command execution. Flasher responds with its current state. All defined state messages are described under Reply from Flasher on page 46. #VERIFY This command can used to verify the target Flash content against the data stored in Flasher. 3.3.5.1 File I/O commands The ASCII interface of Flasher also supports file I/O operations via RS232. The following file I/O commands are supported: #FCLOSE The #FCLOSE command closes the file on Flasher which was opened via #FOPEN. After this command has been issued further file I/O operations except #FDELETE are not allowed until the #FOPEN command is send again. A typical sequence when using the #FCLOSE command does look like as follows: #FCLOSE #ACK #OK Note: When using the #FCLOSE command a file has to be open (previously opened by #FOPEN). Otherwise Flasher will respond with the following if no file has been opened: #ACK #ERR255:No file opened #FDELETE <Filename> The #FDELETE command is used to delete a file on Flasher where <Filename> specifies the name of the file. A typical sequence when using the #FDELETE command does look like as follows: #FDELETE flasher.dat #ACK #OK Note: If deletion of the file fails for example if the file does not exist, Flasher will respond with the following sequence: #ACK #ERR255:Failed to delete file #FOPEN <Filename> The #FOPEN command is used to open a file on Flasher for further file I/O operations. <Filename> specifies the file on the Flasher which should be opened. If <Filename> can not be found on Flasher a new one will be created. A typical sequence using the #FOPEN command does look like as follows: #FOPEN flasher.dat #ACK #OK Note: Currently only one file can be open at the same time. If #FOPEN is send and another file is already open, Flasher will respond with: Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 45 #ACK #ERR255:A file has already been opened #FREAD <Offset>,<NumBytes> The #FREAD command is used to read data from a file on Flasher. <Offset> specifies the offset in the file, at which data reading is started. <NumBytes> specifies the number of bytes which should be read. A typical sequence when using the #FREAD command does look like as follows: #FREAD 0,4 #ACK #OK:04:466c6173 If the #FREAD command succeeds, Flasher will finally respond with a #OK:<NumBytes>:<Data> reply message. For more information about the Flasher reply messages, please refer to Reply from Flasher on page 46. Note: In order to use the #FREAD command. A file has to be opened before, via the #FOPEN command. Otherwise Flasher will respond with the following sequence: #ACK #ERR255:No file opened #FSIZE The #FSIZE command is used to get the size of the currently opened file on Flasher. A typical sequence when using the #FSIZE command does look like as follows: #FSIZE #ACK #OK:10 // file on flasher which is currently open, has a size of 16 bytes If the #FSIZE command succeeds, Flasher will respond with a #OK:<Size> reply message. For more information about the Flasher reply messages, please refer to Reply from Flasher on page 46. Note: In order to use the #FREAD command. A file has to be opened before, via the #FOPEN command. Otherwise Flasher will respond with the following sequence: #ACK #ERR255:No file opened #FWRITE <Offset>,<NumBytes>:<Data> The #FWRITE command is used to write to a file on Flasher. <Offset> specifies the offset in the file, at which data writing is started. <NumBytes> specifies the number of bytes which are send with this command and which are written into the file on Flasher. <NumBytes> is limited to 512 bytes at once. This means, if you want to write e.g. 1024 bytes, you have to send the #FWRITE command twice, using an appropriate offset when sending it the second time. <Offset> and <NumBytes> are expected in hexadecimal format. #FWRITE 0,200:<Data> #FWRITE 200,200:<Data> The data is expected in hexadecimal format (two hexadecimal characters per byte). The following example illustrates the use of #FWRITE: Data to be send: Hello ! ASCII values: 0x48, 0x65, 0x6C, 0x6C, 0x6F, 0x20, 0x21 #FWRITE 0,7:48656C6C6F2021 Note: In order to use the #FWRITE command a file has to be opened via the #FOPEN command, first. Otherwise Flasher will respond with the following sequence: #ACK #ERR255:No file opened Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 46 CHAPTER 3 3.3.6 Remote control Reply from Flasher The reply messages from Flasher follow the same data format as commands. Any reply message starts with ASCII start delimiter #, ends with simple carriage return (ASCII code 13) and is sent in uppercase. In contrast to commands, replies can be followed by a description message, which gives more detailed information about the reply. This description is sent in mixed case. The #OK reply, for example, is such a reply. It is followed by a string containing information about the performance time needed for the operations: #OK (Total 13.993s, Erase 0.483s, Prog 9.183s, Verify 2.514s) The following reply messages from Flasher are defined: #ACK Flasher replies with #ACK message on reception of any defined command before the command itself is executed. #NACK Flasher replies with #NACK, if an undefined command was received. #OK Flasher replies with #OK, if a command other than #STATUS or #RESULT was executed and ended with no error. #OK:<NumBytes>:<Data> Flasher replies with #OK:<Len>:<Data> if a #FREAD command was executed. <NumBytes> is the number of bytes which could be read. This value may differ from the number of requested bytes, for example if more bytes than available, were requested. <NumBytes> and <Data> are send in hexadecimal format (for <Data>: two hexadecimal characters per byte). #OK:<Size> Flasher replies if #OK:<Size> if a #FSIZE command has been executed. <Size> is the size (in bytes) of the currently opened file. <Size> is send in hexadecimal format. #STATUS: Flasher replies with its current state. The following status messages are currently defined: Message #STATUS:READY #STATUS:CONNECTING #STATUS:INITIALIZING #STATUS:UNLOCKING #STATUS:ERASING #STATUS:PROGRAMMING #STATUS:VERIFYING Description Flasher is ready to receive a new command. Flasher initializes connection to target CPU. Flasher performs self check and internal init. Unlocking flash sectors. Flasher is erasing the flash of the target device. Flasher is programming the flash of the target device. Flasher verifies the programmed flash contents. Table 3.2: List of status messages that are currently defined Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 47 #ERRxxx If any command other than #STATUS or #RESULT was terminated with an error, Flasher cancels the command and replies with an error message instead of #OK message. Some error codes may be followed by colon and an additional error text. For example: #ERR007:CANCELED. The error code numbers are described in the following table: Message #ERR007 #ERR008 #ERR255 Description Flasher received #CANCEL command and has canceled the current operation. Flasher is already busy with execution of previous command. Undefined error occurred. This reply is followed by an error string. Table 3.3: List of error code numbers which are currently defined Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 48 Flasher User Guide (UM08022) CHAPTER 3 Remote control (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 49 Chapter 4 Performance The following chapter lists programming performance of common flash devices and microcontrollers. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 50 CHAPTER 4 4.1 Performance Performance of MCUs with internal flash memory 4.1.1 Flasher ARM The following table lists program and erase performance values of Flasher ARM for different controllers. Microcontroller Analog Devices Atmel AT91SAM7S64 Atmel AT91SAM7S256 NXP LPC1768 NXP LPC2106 NXP LPC2129 NXP LPC2138 NXP LPC2148 NXP LPC2294 NXP LPC2478 ST STM32F103ZE ST STR711 ST STR912 TI TMS470R1B1M Size [kByte] 62 64 256 512 120 248 500 500 2048 504 512 272 544 1024 Erase time [sec] 2.943 ----3.740 0.448 0.449 0.448 0.448 0.808 0.448 0.028 0.429 1.167 2.289 Program time [sec] 2.286 3.488 7.709 8.559 1.204 2.916 5.488 5.632 15.976 5.419 18.763 5.476 12.907 8.147 Verify time [sec] 0.563 0.438 1.053 5.092 0.634 1.347 2.649 2.721 9.669 2.559 3.939 4.742 5.236 5.362 Total time [sec] 5.792 3.926 8.762 17.391 2.286 4.712 8.585 8.801 26.453 8.426 22.730 10.647 19.310 15.798 Table 4.1: List of performance values of MCUs with internal flash 4.1.2 Flasher RX The following table lists program and erase performance values of Flasher RX. Microcontroller R5F56108 Size [kByte] 2.048 Erase time [sec] 9.523 Program time [sec] 11.915 Verify time [sec] 3.890 Total time [sec] 25.585 Table 4.2: List of performance values of MCUs with internal flash 4.1.3 Flasher PPC The following table lists program and erase performance values of Flasher PPC. Microcontroller ST SPC560B50 Size [kByte] 576 Erase time [sec] 4.747 Program time [sec] 4.159 Verify time [sec] 1.929 Total time [sec] 10.917 Table 4.3: List of performance values of MCUs with internal flash Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 51 Chapter 5 Hardware This chapter gives an overview about Flasher specific hardware details, such as the pinouts and available adapters. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 52 CHAPTER 5 5.1 Hardware Flasher ARM 20-pin JTAG/SWD Connector Flasher has a JTAG connector compatible with ARM's Multi-ICE. The JTAG connector is a 20 way Insulation Displacement Connector (IDC) keyed box header (2.54mm male) that mates with IDC sockets mounted on a ribbon cable. 5.1.1 Pinout JTAG The following table lists the Flasher JTAG pinout. PIN SIGNAL TYPE 1 VTref Input 2 Vsupply NC 3 nTRST Output 5 TDI Output 7 TMS Output 9 TCK Output 11 RTCK Input 13 TDO Input 15 RESET I/O 17 DBGRQ NC 19 5V-Target supply Output VTref 1 2 Vsupply nTRST TDI 3 5 4 6 GND GND TMS TCK 7 9 8 GND 10 GND 12 GND RTCK 11 TDO RESET 13 15 DBGRQ 17 V5-Supply 19 14 GND 16 GND 18 GND 20 GND Description This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. This pin is not connected to Flasher ARM. It is reserved for compatibility with other equipment. Connect to Vdd or leave open in target system. JTAG Reset. Output from Flasher ARM to the Reset signal of the target JTAG port. Typically connected to nTRST of the target CPU. This pin is normally pulled HIGH on the target to avoid unintentional resets when there is no connection. JTAG data input of target CPU. It is recommended that this pin is pulled to a defined state on the target board. Typically connected to TDI of target CPU. JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS of target CPU. JTAG clock signal to target CPU. It is recommended that this pin is pulled to a defined state of the target board. Typically connected to TCK of target CPU. Return test clock signal from the target. Some targets must synchronize the JTAG inputs to internal clocks. To assist in meeting this requirement, you can use a returned, and retimed, TCK to dynamically control the TCK rate. Flasher ARM supports adaptive clocking, which waits for TCK changes to be echoed correctly before making further changes. Connect to RTCK if available, otherwise to GND. JTAG data output from target CPU. Typically connected to TDO of target CPU. Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". This pin is not connected in Flasher ARM. It is reserved for compatibility with other equipment to be used as a debug request signal to the target system. Typically connected to DBGRQ if available, otherwise left open. This pin is used to supply power to some eval boards. Typically left open on target hardware. Table 5.1: Flasher pinout JTAG Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are GND pins connected to GND in Flasher ARM. They should also be connected to GND in the target system. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 53 5.1.2 Pinout SWD The 20-pin connector of Flasher is also compatible to ARM's Serial Wire Debug (SWD) interface. The following table lists the J-Link / J-Trace SWD pinout. PIN 1 2 3 5 7 9 11 13 15 17 19 SIGNAL TYPE VTref 1 2 Vsupply Not used Not used 3 5 4 6 GND GND SWDIO SWCLK 7 9 8 GND 10 GND Not used 11 12 GND SWO RESET 13 15 14 GND 16 GND Not used V5-Supply 17 19 18 GND 20 GND Description This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for VTref Input the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. This pin is not connected in J-Link. It is reserved for comVsupply NC patibility with other equipment. Connect to Vdd or leave open in target system. This pin is not used by J-Link. If the device may also be Not Used NC accessed via JTAG, this pin may be connected to nTRST, otherwise leave open. This pin is not used by J-Link. If the device may also be Not used NC accessed via JTAG, this pin may be connected to TDI, otherwise leave open. SWDIO I/O Single bi-directional data pin. Clock signal to target CPU. It is recommended that this pin is pulled to a defined state SWCLK Output of the target board. Typically connected to TCK of target CPU. This pin is not used by J-Link. This pin is not used by J-Link when operating in SWD mode. If the device may also be Not used NC accessed via JTAG, this pin may be connected to RTCK, otherwise leave open. Serial Wire Output trace port. (Optional, not required for SWO Output SWD communication.) Target CPU reset signal. Typically connected to the RESET RESET I/O pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". Not used NC This pin is not connected in J-Link. 5V-TarThis pin is used to supply power to some eval boards. Not get sup- Output all J-Links supply power on this pin, only the KS (Kickstart) ply versions. Typically left open on target hardware. Table 5.2: Flasher pinout SWD Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are GND pins connected to GND in J-Link. They should also be connected to GND in the target system. 5.1.3 Target power supply Pin 19 of the connector can be used to supply power to the target hardware. Supply voltage is 5V, max. current is 300mA. The output current is monitored and protected against overload and short-circuit. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 54 CHAPTER 5 Hardware Power can be controlled via the J-Link commander. The following commands are available to control power: Command power power power power on off on perm off perm Explanation Switch target power on Switch target power off Set target power supply default to "on" Set target power supply default to "off" Table 5.3: Command List Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 55 5.2 Flasher RX 14-pin connector Flasher RX itself has a 20-pin JTAG connector mounted but comes with a 14-pin adapter for Renesas RX devices. This adapter also enables Flasher RX to optionally power the connected target hardware. On the adapter there is a jumper which allows selection between 3.3V and 5V supply target voltage supply. The target is supplied via the VTref connection when the supply option is jumpered. The following table lists the Flasher RX 14-pin JTAG pinout. Pin Signal 1 TCK 3 TRSTn 4 EMLE 5 TDO 6 7 ----- 8 VTref 9 TMS 10 --- 11 TDI 13 nRES Type TCK 1 2 GND TRSTn TDO 3 5 4 6 EMLE --- --TMS 7 9 8 VTref 10 --- TDI 11 12 GND nRES 13 14 GND Description JTAG clock signal to target CPU. It is recommended that this Output pin is pulled to a defined state on the target board. Typically connected to TCK on target CPU. JTAG Reset. Output from Flasher ARM to the Reset signal of the target JTAG port. Typically connected to nTRST of the Output target CPU. This pin is normally pulled HIGH on the target to avoid unintentional resets when there is no connection. Pin for the on-chip emulator enable signal. When the onchip emulator is used, this pin should be driven high. When Output not used, it should be driven low. Pulled HIGH to VTref via 1k pull-up resistor on 14-pin adapter. JTAG data output from target CPU. Typically connected to Input TDO on target CPU. NC This pin is not connected to Flasher RX. NC This pin is not connected to Flasher RX. This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for Input the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. JTAG mode set input of target CPU. This pin should be Output pulled up on the target. Typically connected to TMS on target CPU. NC This pin is not connected to Flasher RX. JTAG data input of target CPU. It is recommended that this Output pin is pulled to a defined state on the target board. Typically connected to TDI on target CPU. Target CPU reset signal. Typically connected to the RESET I/O pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". Table 5.4: Flasher RX pinout 14-pin connector * * 5.2.1 All pins marked NC are not connected to Flasher RX. Any signal can be applied here; Flasher RX will simply ignore such a signal. Pins 2, 12, 14 are GND pins connected to GND in Flasher RX. They should also be connected to GND in the target system. Target power supply Pin 8 of the 14-pin connector can be used to supply power to the target hardware. Supply voltage is 3.3V / 5V, max. current is 300mA. The output current is monitored and protected against overload and short-circuit. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 56 CHAPTER 5 Hardware Power can be controlled via the J-Link commander. The following commands are available to control power: Command power power power power on off on perm off perm Explanation Switch target power on Switch target power off Set target power supply default to "on" Set target power supply default to "off" Table 5.5: Command List Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 57 5.3 Flasher PPC 14-pin connector Flasher PPC itself has a 20-pin JTAG connector mounted but comes with a 14-pin adapter for PowerPC devices. The following table lists the Flasher PPC 14-pin JTAG pinout. Pin Signal 1 TDI 3 TDO 5 TCK 7 8 ----- 9 nRES 10 TMS 11 VDDE7 13 nRDY 14 JCOMP Type TDI 1 2 GND TDO TCK 3 5 4 6 GND GND --nRES 7 9 VDDE7 11 8 --10 TMS 12 GND nRDY 13 14 JCOMP Description JTAG data input of target CPU. It is recommended that this Output pin is pulled to a defined state on the target board. Typically connected to TDI on target CPU. JTAG data output from target CPU. Typically connected to Input TDO on target CPU. JTAG clock signal to target CPU. It is recommended that this Output pin is pulled to a defined state on the target board. Typically connected to TCK on target CPU. NC This pin is not connected to Flasher PPC. NC This pin is not connected to Flasher PPC. Target CPU reset signal. Typically connected to the RESET I/O pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". JTAG mode set input of target CPU. This pin should be Output pulled up on the target. Typically connected to TMS on target CPU. This is the target reference voltage. It is used to check if the target has power, to create the logic-level reference for Input the input comparators and to control the output logic levels to the target. It is normally fed from Vdd of the target board and must not have a series resistor. Nexus ready output. Indicates to the development tools that Input the data is ready to be read from or written to the Nexus read/write access registers. JTAG TAP Controller Enable / JTAG Compliancy (JCOMP). JCOMP is used to enable the TAP controller for communication to the JTAG state machine for boundary scan and for Output debug access. This pin is set to HIGH by Flasher PPC (in order to enable the JTAG TAP controller on the target device). Table 5.6: Flasher PPC pinout 14-pin connector * * All pins marked NC are not connected to Flasher PPC. Any signal can be applied here; Flasher PPC will simply ignore such a signal. Pins 2, 12, 6, 12 are GND pins connected to GND in Flasher PPC. They should also be connected to GND in the target system. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 58 CHAPTER 5 5.4 Hardware Target board design We strongly advise following the recommendations given by the chip manufacturer. These recommendations are normally in line with the recommendations. Please refer to the the appropriate tables depending on the core: * * * * Pinout JTAG on page 52 Pinout SWD on page 53 Flasher RX 14-pin connector on page 55 Flasher PPC 14-pin connector on page 57 In case of doubt you should follow the recommendations given by the semiconductor manufacturer. 5.4.1 Pull-up/pull-down resistors Unless otherwise specified by developer's manual, pull-ups/pull-downs are recommended to be between 2.2 kOhms and 47 kOhms. 5.4.2 RESET, nTRST The debug logic is reset independently from the CPU core with nTRST. For the core to operate correctly it is essential that both signals are asserted after power-up. The advantage of having separate connection to the two reset signals is that it allows the developer performing software debug to setup breakpoints, which are retained by the debug logic even when the core is reset. (For example, at the reset vector address, to allow the code to be single-stepped as soon as it comes out of reset). This can be particularly useful when first trying to bring up a board with a new ASIC. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 59 5.5 Adapters 5.5.1 JTAG Isolator The JTAG Isolator can be connected between Flasher and JTAG adapter, to provide electrical isolation. This is essential when the development tools are not connected to the same ground as the application. For more information about the JTAG Isolator, please refer to J-Link JTAG Isolator User Manual (UM08010) which can be downloaded from our website. VCC 1 2 VCC nTRST TDI 3 4 5 6 GND GND TMS TCK 8 9 10 GND GND GND RTCK 11 12 TDO RESET 13 14 N/C N/C 5.5.1.1 Pinout 7 15 GND 16 GND 17 18 19 20 GND GND The following table shows the target-side pinout of the J-Link JTAG Isolator. Pin Signal Type 1 2 VCC VCC Output Output 3 nTRST Output 5 TDI Output 7 TMS Output 9 TCK Output 11 RTCK Input 13 TDO Input 15 RESET I/O 17 N/C N/C 19 N/C N/C Description The target side of the isolator draws power over this pin. The target side of the isolator draws power over this pin. JTAG Reset. Output from Flasher to the Reset signal of the target JTAG port. Typically connected to nTRST of the target CPU. This pin is normally pulled HIGH on the target to avoid unintentional resets when there is no connection. JTAG data input of target CPU. It is recommended that this pin is pulled to a defined state on the target board. Typically connected to TDI of target CPU. JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS of target CPU. JTAG clock signal to target CPU. It is recommended that this pin is pulled to a defined state of the target board. Typically connected to TCK of target CPU. Return test clock signal from the target. Some targets must synchronize the JTAG inputs to internal clocks. To assist in meeting this requirement, you can use a returned, and retimed, TCK to dynamically control the TCK rate. JTAG data output from target CPU. Typically connected to TDO of target CPU. Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called "nRST", "nRESET" or "RESET". This pin is not connected on the target side of the isolator. This pin is not connected on the target side of the isolator. Table 5.7: Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are connected to GND. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 60 CHAPTER 5 5.5.2 Hardware J-Link Needle Adapter To connect to the J-Link OB via programming interface the J-Link Needle Adapter is recommended. Why to choose the J-Link Needle Adapter: 1. 2. 3. 4. 5. No additional connector required on your PCB Very small footprint High reliability spring pins for secure connections Designed with 3 locating pins, so the adapter can not be connected the wrong way No external power supply required! The J-Link Needle Adapter comes with the option to power the target hardware via J-Link. These features make the J-Link Needle Adapter the perfect solution for production purposes. The pinout of the J-Link Needle Adapter is based on the pinout of the needle adapter by Tag-Connect. Please note, that both pinouts are not identical since the J-Link Needle Adapter comes with a 5V-supply pin. As you can see on the image below, the three locating pins ensure, that the adapter cannot be connected to the PCB the wrong way. Moreover, the two "legs" on each side of the connector guarantee a stable and secure contact between pins and the PCB. The J-Link Needle Adapter can be connected to J-Link via the 20-pin 0.1'' JTAG to a 10-pin needle connector. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 61 5.6 How to determine the hardware version To determine the hardware version of your Flasher, the first step should be to look at the label at the bottom side of the unit. Flasher has the hardware version printed on the back label. If this is not the case with your Flasher, you can use JLink.exe to determine your hardware version (if Flasher is in J-Link mode). As part of the initial message, the hardware version is displayed. For more information about how to ensure that Flasher is in J-Link mode, please refer to J-Link mode on page 19. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 62 Flasher User Guide (UM08022) CHAPTER 5 Hardware (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 63 Chapter 6 Support and FAQs This chapter contains troubleshooting tips together with solutions for common problems which might occur when using Flasher. There are several steps you can take before contacting support. Performing these steps can solve many problems and often eliminates the need for assistance. This chapter also contains a collection of frequently asked questions (FAQs) with answers. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 64 CHAPTER 6 6.1 Support and FAQs Contacting support Before contacting support, make sure you tried to solve your problem by trying your Flasher with another PC and if possible with another target system to see if it works there. If the device functions correctly, the USB setup on the original machine or your target hardware is the source of the problem, not Flasher. If you need to contact support, send the following information to support@segger.com: * * * * A detailed description of the problem Flasher serial number Information about your target hardware (processor, board, etc.). FLASHER.CFG , FLASHER.DAT, FLASHER.LOG , SERIAL.TXT file from Flasher. To get these files, Flasher has to be in MSD mode. For more information about how to boot Flasher in MSD mode, please refer to MSD mode on page 24. Flasher is sold directly by SEGGER. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 65 6.2 Frequently Asked Questions Maximum JTAG speed Q: A: What is the maximum JTAG speed supported by Flasher? Flasher's maximum supported JTAG speed is 12MHz. Maximum download speed Q: A: What is the maximum download speed? The maximum download speed is currently about 720 Kbytes/second when downloading into RAM. The actual speed depends on various factors, such as JTAG, clock speed, host CPU core etc. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 66 Flasher User Guide (UM08022) CHAPTER 6 Support and FAQs (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 67 Chapter 7 Background information This chapter provides background information about flash programming in general. It also provides information about how to replace the firmware of Flasher manually. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 68 CHAPTER 7 7.1 Background information Flash programming Flasher comes with a DLL, which allows - amongst other functionalities - reading and writing RAM, CPU registers, starting and stopping the CPU, and setting breakpoints. 7.1.1 How does flash programming via Flasher work ? This requires extra code. This extra code typically downloads a program into the RAM of the target system, which is able to erase and program the flash. This program is called RAM code and "knows" how to program the flash; it contains an implementation of the flash programming algorithm for the particular flash. Different flash chips have different programming algorithms; the programming algorithm also depends on other things, such as endianess of the target system and organization of the flash memory (for example 1 * 8 bits, 1 * 16 bits, 2 * 16 bits or 32 bits). The RAM code requires data to be programmed into the flash memory. The data is supplied by downloading it to RAM. 7.1.2 Data download to RAM The data (or part of it) is downloaded to another part of the RAM of the target system. The Instruction pointer (PC) of the CPU is then set to the start address of the Ram code, the CPU is started, executing the RAM code. The RAM code, which contains the programming algorithm for the flash chip, copies the data into the flash chip. The CPU is stopped after this. This process may have to be repeated until the entire data is programmed into the flash. 7.1.3 Available options for flash programming In general, there are two possibilities in order to use Flasher for flash programming: * * Using Flasher stand-alone to program the target flash memory (stand-alone mode) Using Flasher in combination with J-Flash to program the target flash memory (Flasher in "J-Link mode") 7.1.3.1 Using Flasher in stand-alone mode In order to use the Flasher in stand-alone mode, it has to be configured first. For more information about how to setup Flasher for using in "stand-alone mode", please refer to Setting up Flasher for stand-alone mode on page 19. 7.1.3.2 J-Flash - Complete flash programming solution J-Flash is a stand-alone Windows application, which can read / write data files and program the flash in almost any ARM system. For more information about J-Flash please refer to the J-Flash User Guide , which can be downloaded from our website http://www.segger.com . Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 69 Chapter 8 Glossary This chapter describes important terms used throughout this manual. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 70 CHAPTER 8 Glossary Big-endian Memory organization where the least significant byte of a word is at a higher address than the most significant byte. See Little-endian. Cache cleaning The process of writing dirty data in a cache to main memory. Coprocessor An additional processor that is used for certain operations, for example, for floatingpoint math calculations, signal processing, or memory management. Dirty data When referring to a processor data cache, data that has been written to the cache but has not been written to main memory is referred to as dirty data. Only write-back caches can have dirty data because a write-through cache writes data to the cache and to main memory simultaneously. See also cache cleaning. Halfword A 16-bit unit of information. Host A computer which provides data and other services to another computer. Especially, a computer providing debugging services to a target being debugged. ICache Instruction cache. ID Identifier. IEEE 1149.1 The IEEE Standard which defines TAP. Commonly (but incorrectly) referred to as JTAG. Image An executable file that has been loaded onto a processor for execution. Instruction Register When referring to a TAP controller, a register that controls the operation of the TAP. IR See Instruction Register. Joint Test Action Group (JTAG) The name of the standards group which created the IEEE 1149.1 specification. Little-endian Memory organization where the least significant byte of a word is at a lower address than the most significant byte. See also Big-endian. Memory coherency A memory is coherent if the value read by a data read or instruction fetch is the value that was most recently written to that location. Obtaining memory coherency is difficult when there are multiple possible physical locations that are involved, such as a system that has main memory, a write buffer, and a cache. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 71 Memory management unit (MMU) Hardware that controls caches and access permissions to blocks of memory, and translates virtual to physical addresses. Memory Protection Unit (MPU) Hardware that controls access permissions to blocks of memory. Unlike an MMU, a MPU does not translate virtual addresses to physical addresses. RESET Abbreviation of System Reset. The electronic signal which causes the target system other than the TAP controller to be reset. This signal is also known as "nSRST" "nSYSRST", "nRST", or "nRESET" in some other manuals. See also nTRST. nTRST Abbreviation of TAP Reset. The electronic signal that causes the target system TAP controller to be reset. This signal is known as nICERST in some other manuals. See also nSRST. Open collector A signal that may be actively driven LOW by one or more drivers, and is otherwise passively pulled HIGH. Also known as a "wired AND" signal. Processor Core The part of a microprocessor that reads instructions from memory and executes them, including the instruction fetch unit, arithmetic and logic unit, and the register bank. It excludes optional coprocessors, caches, and the memory management unit. Remapping Changing the address of physical memory or devices after the application has started executing. This is typically done to make RAM replace ROM once the initialization has been done. RTOS Real Time Operating System. TAP Controller Logic on a device which allows access to some or all of that device for test purposes. The circuit functionality is defined in IEEE1149.1. Target The actual processor (real silicon or simulated) on which the application program is running. TCK The electronic clock signal which times data on the TAP data lines TMS, TDI, and TDO. TDI The electronic signal input to a TAP controller from the data source (upstream). Usually, this is seen connecting the J-Link Interface Unit to the first TAP controller. TDO The electronic signal output from a TAP controller to the data sink (downstream). Usually, this is seen connecting the last TAP controller to the J-Link Interface Unit. Test Access Port (TAP) The port used to access a device's TAP Controller. Comprises TCK, TMS, TDI, TDO, and nTRST (optional). Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 72 CHAPTER 8 Glossary Transistor-transistor logic (TTL) A type of logic design in which two bipolar transistors drive the logic output to one or zero. LSI and VLSI logic often used TTL with HIGH logic level approaching +5V and LOW approaching 0V. Word A 32-bit unit of information. Contents are taken as being an unsigned integer unless otherwise stated. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 73 Chapter 9 Literature and references This chapter lists documents, which we think may be useful to gain a deeper understanding of technical details. Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 74 CHAPTER 9 Reference Title Literature and references Comments [J-Link] J-Link / J-Trace User Guide [J-Flash] J-Flash User Guide This document describes J-Link and J-Trace. It is publicly available from SEGGER (www.segger.com ). This document describes J-Flash. It is publicly available from SEGGER ( www.segger.com ). Table 9.1: Literature and References Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 75 Index A N Adaptive clocking .................................70 nTRST .......................................... 52, 71 C O Cache cleaning ....................................70 Coprocessor ........................................70 Open collector .................................... 71 D Dirty data ...........................................70 H P Processor Core ................................... 71 R Halfword .............................................70 Host ...................................................70 Remapping ......................................... 71 RESET ............................................... 71 RTOS ................................................. 71 I S ICache ...............................................70 ID .....................................................70 IEEE 1149.1 ........................................70 Image ................................................70 Instruction Register ..............................70 IR ......................................................70 Support ........................................ 63, 69 J J-Link Adapters ..........................................59 Features ............................................ 8 Specifications ....................................10 Supported chips .......................... 35, 58 Joint Test Action Group (JTAG) ...............70 T TAP Controller .................................... Target ............................................... TCK .............................................. 52, TDI .............................................. 52, TDO ............................................. 52, Test Access Port (TAP) ......................... Transistor-transistor logic (TTL) ............. 71 71 71 71 71 71 72 W Word ................................................. 72 L Little-endian .......................................70 M Memory coherency ...............................70 Memory management unit (MMU) ..........71 Memory Protection Unit (MPU) ...............71 Flasher User Guide (UM08022) (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG 76 Flasher User Guide (UM08022) Index (c) 2004-2013 SEGGER Microcontroller GmbH & Co. KG