5.16.01FLASHERPORTABLE

Flasher User Guide Document: UM08022 Software Version: 7.82 Date: October 20, 2022 A product of SEGGER Microcontroller GmbH www.segger.com 2 Disclaimer The information written in this document is assumed to be accurate without guarantee. The information in this manual is subject to change for functional or performance improvements without notice. SEGGER Microcontroller GmbH (SEGGER) assumes no responsibility for any errors or omissions in this document. SEGGER disclaims any warranties or conditions, express, implied or statutory for the fitness of the product for a particular purpose. It is your sole responsibility to evaluate the fitness of the product for any specific use. Copyright notice You may not extract portions of this manual or modify the PDF file in any way without the prior written permission of SEGGER. 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. © 2004-2022 SEGGER Microcontroller GmbH, Monheim am Rhein / 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 Ecolab-Allee 5 D-40789 Monheim am Rhein Germany Tel. Fax. E-mail: Internet: +49-2173-99312-0 +49-2173-99312-28 support@segger.com www.segger.com Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 3 Manual versions This manual describes the Flasher device. For further information on topics or routines not yet specified, please contact us. Print date: October 20, 2022 Manual Revision version Date By Description 7.82 0 221020 JB Updated how to enter the file access mode 7.68c 0 220725 AB Updated Universal Flashloader specifics 7.62b 0 220317 JB Typo in “DisplayName” corrected 7.59a 0 211118 LG * Replaced occurrences of “MSD mode” with “file access mode” * Replaced occurrences of “J-Link mode” with “PC-based mode” 7.56c 0 211029 JC Chapter “Working with Flasher” * Added Logfile section * Improved some sections according to the feedback from the “Flasher Reader Test” 6.98 0 210401 AG Added Flasher Compact 6.51 0 200114 AB moved Universal Flashloader device specifics to UM08037 6.50c 0 190918 MF added secure are ASCII commands 6.46 0 190704 MF corrected multi image sample 6.36 0 190509 MF added Portable PLUS specific section in multiple-file chapter for clarification 6.34 3 190221 MF updated chapter Batch Programming in stand-alone mode 6.34 2 180205 AB Removed all Flasher ATE related topics. * Content has been moved to UM08035_FlasherATE.pdf Chapter “Hardware” * Added safety disclaimer for JTAG isolator 6.32 2 180205 AB Chapter “Working with Flasher” * Added STM8 support to universal flash loader. 6.30 1 180222 AG Chapter “Working with Flasher” * Section “Custom labels” added. 6.20 1 171130 AB Chapter “Working with Flasher” * Section “Flasher ATE” added. Added chapter “TCP Services” 6.20 0 171121 AB Chapter “Working with Flasher” * Section “Flasher Portable PLUS” added. 6.10a 0 160922 EL Chapter “Introduction” * Section “Flasher Portable” updated. 6.00 0 160715 NG Chapter “Working with Flasher” * Section “Batch Programming” added. 5.12e 0 160511 NG Chapter “Working with Flasher” * Section “Setting up Flasher for stand-alone mode” moved. * Section “Preparing for stand-alone operation manually” added. 5.02f 0 151023 RH Chapter “Remote control” * Section “General usage” addded. 5.02e 0 151021 EL Chapter “Introduction” * Section “Specifications” updated for all models. 5.02f 0 151014 RH Chapter “Working with Flasher” * Section “Programming multiple targets” addded. 4.50c 0 150611 EL Chapter “Working with Flasher” * Section “Programming multiple targets in parallel” addded. 4.98 0 150205 AG Chapter “Working with Flasher” * Section “Authorized flashing” added. * Section “Limiting the number of programming cycles” added. * Section “Operating Modes” updated. 4.86 0 140610 AG Chapter “Working with Flasher” * Section “Newline encoding” added. 4.80 1 131220 AG Chapter “Working with Flasher” Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 4 Manual Revision version Date By Description * Section “Multiple File Support” updated. 4.80 0 131031 EL Chapter “Remote control” * Section “Commands to Flasher” updated. “#FCRC” command added. 4.78 0 130917 AG Chapter “Introduction” * Section “Features of Flasher Portable” added. Chapter “Working with Flasher” * Section “Flasher Portable” added. * Section “Multiple File Support” updated. 4.72 0 130612 EL Chapter “Working with Flasher” * Section “Patch file support” added. 4.64a 0 130226 EL Chapter “Working with Flasher” * Section “LED status indicators” updated. 4.63a 0 130131 EL Chapter “Remote Control” * Section “ASCII command interface” Chapter “ASCII interface via Telnet” added. 4.62 0 130125 EL Flasher ARM, Flasher RX and Flasher PPC manual have been combined. 5.02 0 150807 RE New commands #FLIST and #MKDIR in ASCII command interface Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 5 About this document Assumptions This document assumes that you already have a solid knowledge of the following: • • • • The software tools used for building your application (assembler, linker, C compiler). The C programming language. The target processor. DOS command line. If you feel that your knowledge of C is not sufficient, we recommend The C Programming Language by Kernighan and Richie (ISBN 0--13--1103628), which describes the standard in C programming and, in newer editions, also covers the ANSI C standard. How to use this manual This manual explains all the functions and macros that the product offers. It assumes you have a working knowledge of the C language. Knowledge of assembly programming is not required. Typographic conventions for syntax 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). Parameter Parameters in API functions. Sample Sample code in program examples. Sample comment Comments in program examples. Reference Reference to chapters, sections, tables and figures or other documents. GUIElement Buttons, dialog boxes, menu names, menu commands. Emphasis Very important sections. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 6 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 7 Table of contents 1 Introduction ..................................................................................................................10 1.1 1.2 2 Flasher overview .......................................................................................... 11 1.1.1 Features of Flasher ARM/PPC/RX/PRO .................................................. 11 1.1.2 Features of Flasher Compact .............................................................. 11 1.1.3 Features of Flasher Portable/Flasher Portable PLUS ................................ 12 1.1.4 Working environment .........................................................................12 Specifications ...............................................................................................14 1.2.1 Specifications for Flasher ARM ............................................................ 14 1.2.2 Specifications for Flasher RX .............................................................. 16 1.2.3 Specifications for Flasher PPC ............................................................. 18 1.2.4 Specifications for Flasher PRO .............................................................20 1.2.5 Specifications for Flasher Compact ...................................................... 23 1.2.6 Specifications for Flasher Portable PLUS ............................................... 26 1.2.7 Specifications for Flasher Portable ....................................................... 29 Working with Flasher .................................................................................................. 32 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Flasher Portable PLUS ...................................................................................33 2.1.1 Housing & Buttons ............................................................................ 33 2.1.2 Configuration .................................................................................... 34 Flasher Portable ........................................................................................... 35 2.2.1 Housing & Buttons ............................................................................ 35 File system ..................................................................................................37 Setting up the IP interface ............................................................................ 38 2.4.1 Connecting the first time ................................................................... 38 Operating modes ......................................................................................... 39 2.5.1 PC-based mode .................................................................................39 2.5.2 Stand-alone mode ............................................................................. 40 2.5.3 File access mode ...............................................................................42 Setting up Flasher for stand-alone mode .........................................................43 2.6.1 Preparing for stand-alone operation manually ....................................... 46 Universal Flash Loader mode ......................................................................... 48 2.7.1 Preparing manually ........................................................................... 48 2.7.2 Preparing using the PC utility ............................................................. 51 Multiple File Support .....................................................................................52 2.8.1 Flasher Portable specifics ................................................................... 52 2.8.2 Flasher Portable PLUS specifics ........................................................... 53 Custom labels ..............................................................................................55 2.9.1 Hardware and software requirements .................................................. 55 2.9.2 Assigning labels ................................................................................ 55 2.9.3 Considerations .................................................................................. 56 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 8 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 3 TCP Services .............................................................................................................. 76 3.1 3.2 4 Overview .....................................................................................................80 Handshake control ....................................................................................... 81 ASCII command interface ............................................................................. 82 4.3.1 Introduction ......................................................................................82 4.3.2 General command and reply message format ....................................... 82 4.3.3 General usage .................................................................................. 82 4.3.4 Settings for ASCII interface via RS232 .................................................82 4.3.5 Settings for ASCII interface via Telnet ................................................. 82 4.3.6 Commands and replies ...................................................................... 83 Performance ................................................................................................................93 5.1 6 FTP Server .................................................................................................. 77 3.1.1 Access data ...................................................................................... 77 Web server ..................................................................................................78 Remote control ............................................................................................................79 4.1 4.2 4.3 5 Programming multiple targets ...................................................................... 57 2.10.1 Programming multiple targets with J-Flash ......................................... 57 Batch Programming in stand-alone mode ...................................................... 58 2.11.1 Flasher Portable specifics ..................................................................59 2.11.2 Examples ........................................................................................60 Serial number programming ........................................................................ 61 2.12.1 Serial number settings ..................................................................... 61 2.12.2 Serial number file ............................................................................62 2.12.3 Serial number list file ...................................................................... 62 2.12.4 Programming process .......................................................................63 2.12.5 Downloading serial number files to Flasher ......................................... 64 2.12.6 Sample setup ..................................................................................64 Patch file support ....................................................................................... 66 2.13.1 Newline encoding ............................................................................ 67 Limiting the number of programming cycles .................................................. 68 2.14.1 Changed fail/error LED indicator behavior ...........................................68 2.14.2 Required Flasher hardware version for Cntdown.txt support .................. 68 Authorized flashing ..................................................................................... 69 2.15.1 Creating / Adding the secure area ..................................................... 69 2.15.2 Moving files to the secure area ......................................................... 69 2.15.3 Considerations to be taken when using the secure area ........................ 70 2.15.4 Required Flasher hardware version .................................................... 70 Target interfaces ........................................................................................ 71 Supported architectures .............................................................................. 72 2.17.1 External flashes .............................................................................. 72 2.17.2 Cores ............................................................................................. 72 Programming multiple targets in parallel ....................................................... 74 Logfiles and Quality Management ................................................................. 75 Performance of 5.1.1 Flasher 5.1.2 Flasher 5.1.3 Flasher 5.1.4 Flasher 5.1.5 Flasher MCUs with internal flash memory ............................................. 94 ARM ..................................................................................... 94 PRO ..................................................................................... 94 Compact ............................................................................... 94 RX ....................................................................................... 94 PPC ...................................................................................... 94 Hardware .....................................................................................................................95 6.1 Flasher 6.1.1 6.1.2 6.1.3 ARM 20-pin JTAG/SWD Connector ....................................................... 96 Pinout JTAG ......................................................................................96 Pinout SWD ...................................................................................... 97 Target power supply .......................................................................... 98 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 9 6.2 6.3 6.4 6.5 6.6 7 Support and FAQs .................................................................................................... 107 7.1 7.2 8 Flasher RX 14-pin connector ..........................................................................99 6.2.1 Target power supply ........................................................................ 100 Flasher PPC 14-pin connector ...................................................................... 101 Target board design ....................................................................................102 6.4.1 Pull-up/pull-down resistors ............................................................... 102 6.4.2 RESET, nTRST ................................................................................. 102 Adapters ................................................................................................... 103 6.5.1 JTAG Isolator .................................................................................. 103 6.5.2 J-Link Needle Adapter ...................................................................... 104 How to determine the hardware version ........................................................ 106 Contacting support ..................................................................................... 108 Frequently Asked Questions .........................................................................109 Background information ............................................................................................ 110 8.1 Flash programming .....................................................................................111 8.1.1 How does flash programming via Flasher work? ...................................111 8.1.2 Data download to RAM .....................................................................111 8.1.3 Available options for flash programming ............................................. 111 8.1.4 How does the universal flash programming work? ................................111 9 Glossary .................................................................................................................... 112 10 Literature and references ........................................................................................116 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 1 Introduction This chapter gives a short overview about the different models of the Flasher family and their features. Additional information can be found in our Wiki. You can find it under the following URL: https://wiki.segger.com/Main_Page Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 11 CHAPTER 1 1.1 Flasher overview 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 (what host interfaces are available depends on the Flasher model), running Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista, Windows 7, Windows 8 or Windows 10. 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 • • • • • • • Flasher Flasher Flasher Flasher Flasher ARM: JTAG and SWD are supported. RX: JTAG is supported. Flasher comes with additional 14-pin RX adapter PPC: JTAG is supported. Flasher comes with additional 14-pin PPC adapter. PRO: JTAG and SWD are supported. Compact: JTAG and SWD are supported. Features of Flasher ARM/PPC/RX/PRO Three boot modes: PC-based mode, stand-alone mode, file access 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 128 MB memory for storage of target program Can be used as J-Link (emulator) with a download speed of up to 720 Kbytes/second Data files can updated via USB/Ethernet (using the J-Flash software), via FTP, via RS232 or via the file access mode of Flasher Supported cores Supported target interfaces Flasher ARM ARM7/ARM9/Cortex-M JTAG, SWD between 170 and 300 Kbytes/second Flasher RX Renesas RX610, RX621, RX62N, RX62T JTAG between 30-300 Kbytes/second JTAG up to 138 Kbytes/second JTAG, SWD between 30-300 Kbytes/ second Flasher model Flasher PPC Power PC e200z0 Flasher PRO 1.1.2 • • • • • • • ARM7/ARM9/Cortex-M Renesas RX610, RX621, RX62N, RX62T Power PC e200z0 Flash programming speed (depending on target hardware) Features of Flasher Compact Three boot modes: PC-based mode, stand-alone mode, file access 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 128 MB memory for storage of target program Can be used as J-Link (emulator) with a download speed of up to 720 Kbytes/second Data files can updated via USB/Ethernet (using the J-Flash software) or via the file access mode of Flasher Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 12 CHAPTER 1 Flasher overview Supported cores Supported target interfaces Flasher ARM ARM7/ARM9/Cortex-M JTAG, SWD between 170 and 300 Kbytes/second Flasher RX Renesas RX610, RX621, RX62N, RX62T JTAG between 30-300 Kbytes/second JTAG up to 138 Kbytes/second JTAG, SWD between 30-300 Kbytes/ second Flasher model Flasher PPC Power PC e200z0 Flasher Compact 1.1.3 • • • • • • • • • • ARM7/ARM9/Cortex-M Renesas RX610, RX621, RX62N, RX62T Power PC e200z0 Flash programming speed (depending on target hardware) Features of Flasher Portable/Flasher Portable PLUS Stand-alone in-circuit-programmer (Once set up, Flasher can be controlled without the use of a PC program) Powered by an internal rechargeable battery (standard batteries for Flasher Portable), no Laptop or external power supply required. Multiple firmware images can be stored on Flasher 128 MB memory for storage of target program Easy selection of image to be programmed, via button Supported CPUs: ARM Cortex, Legacy ARM7/9, Renesas RX, Freescale PowerPC Supports internal and external flash Free software updates*, 1 year of support Data files can be updated via the file access mode functionality or via J-Flash Programming speed between 30-300 Kbytes/second (actual speed depends on target hardware) Note Ethernet and RS232 as host interface are not available for Flasher Portable Note *As a legitimate owner of a SEGGER Flasher, you can always download the latest software free of charge. Though not planned and not likely, we reserve the right to change this policy. Note that older models may not be supported by newer versions of the software. Typically, we support older models with new software at least 3 years after end of life Supported cores Supported target interfaces Flash programming speed (depending on target hardware) ARM7/ARM9/Cortex-M JTAG, SWD between 30-300 Kbytes/second Renesas RX610, RX621, RX62N, RX62T JTAG between 170 and 300 Kbytes/second Power PC e200z0 JTAG up to 138 Kbytes/second 1.1.4 Working environment General The Flasher can operate from a PC with an appropriate software like J-Flash or in standalone mode. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 13 CHAPTER 1 Flasher overview 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, Windows 8 or Windows 10. It needs to have a USB, Ethernet or RS232 interface available for communication with Flasher. Power supply Flasher Portable: 3x standard AAA batteries or 5V DC, min. 100 mA via USB connector. Flasher Portable PLUS: internal rechargeable 680mAh Li-Ion battery, min. 100 mA via USB connector. Other Flashers: 5V DC, min. 100 mA via USB connector. 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: segger.com/jlink-software.html For more information about using J-Flash please refer to UM08003_JFlashARM.pdf (J-Flash user guide) which is also available for download on our website. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 14 CHAPTER 1 1.2 Specifications Specifications 1.2.1 Specifications for Flasher ARM General Supported OS Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Windows Windows Windows Windows Windows Windows Windows Windows Windows Windows Windows Windows Windows Operating Temperature +5 °C … +60 °C Storage Temperature -20 °C … +60 °C Relative Humidity (non-condensing) 6.25 Hz) • Programming (slow blinking on/off time: 300ms => ~1.67 Hz) • Verifying (slow blinking, on/off time: 100ms => 5 Hz) GREEN: constant RED: off or constant GREEN constant, RED off: Operation successful. GREEN constant, RED constant: Operation failed Goes back to state #0 automatically, but in case of operation failed, RED remains on until state #1 is entered the next time. 2 3 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 42 CHAPTER 2 2.5.3 Operating modes File access mode When pressing the Start/Stop button (for Flasher Portable PLUS PRG button) of the Flasher while connecting it to the PC, Flasher will boot in the “file access mode”. If you are using a self-powered Flasher such as the Flasher Portable Plus, the Flasher must be turned off before connecting it. 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 drive, 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. 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 “file access mode”. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 43 2.6 CHAPTER 2 Setting up Flasher for stand-alone mode 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 J-Flash User Guide. 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 -> 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) © 2004-2022 SEGGER Microcontroller GmbH 44 CHAPTER 2 Setting up Flasher for stand-alone mode 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) © 2004-2022 SEGGER Microcontroller GmbH 45 CHAPTER 2 Setting up Flasher for stand-alone mode 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) © 2004-2022 SEGGER Microcontroller GmbH 46 CHAPTER 2 Setting up Flasher for stand-alone mode 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.6.1 Preparing for stand-alone operation manually As an alternative, J-Flash can also be used to save config and data file to a hard drive. This files can later be copied to a Flasher without using J-Flash, which is useful to prepare additional Flasher for stand-alone programming, if for example a company plans to widen its production, new Flasher units can be bought and used in production by simply copying the files to the new units. Creating config and data files J-Flash config (*.CFG) and data (*.DAT) files can be created by using the “Save Flasher config file…” and “Save Flasher data file…” options in the “File” menu. For some devices, additional files (*.PEX) are needed. J-Flash will create a subdirectory (in the same directory as the config file) with the same name as the config file and place the files needed in this directory. About *.PEX files When using the “Save Flasher config file…” menu point or when using the “multiple configurations stored on Flasher” feature (See Multiple File Support on page 52.) feature, the following needs to be taken care of: For some devices, special connect, reset etc. sequences are necessary which are stored in so-called *.PEX files on the Flasher. When using the “Download config & data file to Flasher”, J-Flash takes care of correct use and download of these files to Flasher. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 47 CHAPTER 2 Setting up Flasher for stand-alone mode When creating the config files manually and later download them to the Flasher manually, it is user’s responsibility to put them at the right place. The *.PEX files need to be placed in a subdirectory with the same name as the corresponding *.cfg file. J-Flash creates a directory with the correct name automatically when a config file is created. Example: MyConf0 is a project for a device that requires a *.PEX file for connect. MyConf1 is a project for a device that requires no *.PEX file at all. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 48 CHAPTER 2 2.7 Universal Flash Loader mode Universal Flash Loader mode As an alternative to the stand-alone mode, configured via J-Flash, there is the Universal Flash Loader mode. While the normal stand-alone mode relies on using the debug interface of the device, the Universal Flash Loader mode uses device or vendor specific programming interfaces and protocols and therefore it is independent of the CPU core. The Universal Flash Loader is available for the following Flasher models: • • • Flasher PRO Flasher Compact Flasher Portable PLUS For some of the supported devices, SEGGER offers specific adapters. 2.7.1 Preparing manually The Universal Flash Loader uses an initialization file (*.UNI), a device specific flash programming algorithm (*.PEX) and a data file (*.DAT). 2.7.1.1 Configuration The initialization file basically is split into three parts. The first part, the section [DEVICE], controls the generic behavior of the Universal Flash Loader. It specifies which protocol driver and data file to use. It allows enabling and configuring target power and it defines which actions to perform. The second part consists of one or more [BANKx] sections, which contain information about the memories. The third part, the section [CONFIG], includes configuration settings for the protocol driver. An .ini file might look as follows: [OPTIONS] TargetPower = "0" ChipErase = "0" [TASKS] CheckBlank Erase Program Verify Secure = = = = = [DEVICE] Algo Data Offset = "RL78.PEX" = "ALL_6k.mot" = "0x00000000" "1" "1" "1" "1" "1" [BANK0] ; Code Flash Base = "0x00000000" Size = "0x00004000" Sect = "0x00000400" [BANK1] ; Data Flash Base = "0x000F1000" Size = "0x00000800" Sect = "0x00000400" [CONFIG] BaudRate = "1000000" ClearConfigOnConnect = "0x00" Security = "0xFF" ShieldStart = "0x0000" ShieldEnd = "0x000F" Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 49 CHAPTER 2 Universal Flash Loader mode [OPTIONS] TargetPower If set to a value >0, power is applied to the target. The value defines the delay (in ms) after enabling the target power supply and before starting to communicate with the target. ChipErase If set to 1, the chip erase function is called for erasing the chip. Note Do not enable this setting if the flash programming algorithm does not support chip erase. [TASKS] CheckBlank Defines if a blank check should be performed before erasing a sector. Erase Defines if the sector should be erased before programming. Program Defines if the sector should be programmed. Verify Defines if the sector should be verified after programming. Secure Defines if the device should be secured or protected against read-out after verifying. [DEVICE] Algo File name of the flash programming algorithm. This file is provided by SEGGER and will typically support a series of devices. Data File name of the data file to program. The flasher supports the Flasher DTA, the Intel HEX, the Motorola S-Record and the binary file format. Flasher DAT files are generated by J-Flash and offer high performance together with high flexibility. The other file formats produce a small overhead, because they have to be parsed before the data can be programmed. Offset Offset to apply when programming a binary data file. Unless specified differently, binary files start at offset 0x00000000. [BANKx] x blocks with configuration data for the flash banks. All three parameters (Base, Size and Sect) are mandatory. Base Base address of the flash bank. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 50 CHAPTER 2 Universal Flash Loader mode Size Total size of the flash bank. Sect Sector size of the flash bank. [CONFIG] This section includes specific configuration data for the flash programming algorithm. There are no general parameters. Note The data file must be organized in ascending address order. Gaps can be included. But descending addresses will result in programming errors. You can sort the data files by loading them into the J-Flash tool and saving it as a new file. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 51 CHAPTER 2 2.7.2 Universal Flash Loader mode Preparing using the PC utility In order to set up Flasher for the Universal Flash Loader mode, a PC utility called SEGGER Universal Flash Loader Configurator is available for download. The Universal Flash Loader Configurator comes with a large list of devices and flash programming algorithms. If you are going to use a device from one of the supported families which currently is not available in the utility, feel free to contact the support. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 52 CHAPTER 2 2.8 Multiple File Support 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. Boot Flasher in file access mode in order to replace the FLASHER.INI 2. 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 87. Note Flasher supports 8.3 filenames only (8 characters filename, 3 characters file extension). Using longer filenames may result in incorrect operation. 2.8.1 Flasher Portable specifics Flasher Portable allows to choose between four configuration and data file pairs during runtime by using the select/arrow button on the front of Flasher Portable. Which config / data file pair is used for which image selection position is determined by the contents of the FLASHER.INI. For this, the FLASHER.INI contents in the [FILES] section have been extended. The sample below shows how to enable the user to select between four different images on the Flasher portable via the select / arrow button: [FILES] DataFile = "First.dat" ConfigFile = "First.cfg" DataFile1 = "Second.dat" ConfigFile1 = "Second.cfg" DataFile2 = "Third.dat" ConfigFile2 = "Third.cfg" DataFile3 = "Fourth.dat" ConfigFile3 = "Fourth.cfg" Using this method, all configuration files and data files which are used in the production only have to be stored on Flasher Portable via file access mode. From there on, switching between the files can be done by simply using the selection button of Flasher Portable. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 53 CHAPTER 2 2.8.1.1 Multiple File Support Example 1 Target, 2 Datafiles (e.g. boot loader und application) --> same configuration file (*.CFG) but different data files (*.DAT) should be used. • • • • • • • • • Open pre-configured J-Flash project File -> Save Flasher config file … (DEFAULT.CFG) Open data file 1 (boot loader) File -> Save Flasher data file … (BOOT.DAT) Open data file 2 (application) File -> Save Flasher data file … (APP.DAT) Create the a FLASHER.INI file (content see below) Connect the Flasher in file access mode to the PC Copy DEFAULT.CFG, BOOT.DAT, APP.DAT and FLASHER.INI on the Flasher FLASHER.INI content: [FILES] DataFile ConfigFile DataFile1 ConfigFile1 2.8.2 = = = = "BOOT.DAT" "DEFAULT.CFG" "APP.DAT" "DEFAULT.CFG" Flasher Portable PLUS specifics Flasher Portable PLUS allows to choose between 16 configuration and data file pairs during runtime by using the select button on the front of Flasher Portable PLUS. Which config / data file pair is used for which image selection position is determined by the contents of the FLASHER.INI. For this, the FLASHER.INI may contain several [BATCH] sections. The sample below shows how to enable the user to select between five different images on the Flasher Portable PLUS via the select / arrow button: [BATCH] DataFile = ConfigFile [BATCH1] DataFile = ConfigFile [BATCH2] DataFile = ConfigFile [BATCH7] DataFile = ConfigFile [BATCH15] DataFile = ConfigFile "First.dat" = "First.cfg" "Second.dat" = "Second.cfg" "Third.dat" = "Third.cfg" "Proj_8.dat" = "Proj_8.cfg" "Proj_16.dat" = "Proj_16.cfg" Using this method, all configuration files and data files which are used in the production only have to be stored on Flasher Portable PLUS via file access mode. From there on, switching between the files can be done by simply using the selection button of Flasher Portable PLUS. Please also consider the chapter Batch Programming in stand-alone mode on page 58. Note There the Flasher Portable PLUS checks if the files exist on its flash storage. If the a file is missing the entry will be skip and the selection jumps directly to the next entry in the list. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 54 CHAPTER 2 Multiple File Support Note You may have gaps in the list. The missing entries will be skipped when selecting the next configuration. Note The [Files] section is supported by the Flasher Portable PLUS, too. But the number of configuration is limited to four. 2.8.2.1 Example 1 Target, 2 Datafiles (e.g. boot loader und application) --> same configuration file (*.CFG) but different data files (*.DAT) should be used. • • • • • • • • • Open pre-configured J-Flash project File -> Save Flasher config file … (DEFAULT.CFG) Open data file 1 (boot loader) File -> Save Flasher data file … (BOOT.DAT) Open data file 2 (application) File -> Save Flasher data file … (APP.DAT) Create the a FLASHER.INI file (content see below) Connect the Flasher in file access mode to the PC Copy DEFAULT.CFG, BOOT.DAT, APP.DAT and FLASHER.INI on the Flasher FLASHER.INI content: [BATCH] DataFile = "BOOT.DAT" ConfigFile = "DEFAULT.CFG" DisplayName = "Bootloader" [BATCH1] DataFile = "APP.DAT" ConfigFile = "DEFAULT.CFG" DisplayName = "Application" [BATCH2] DataFile = "BOOT.DAT" ConfigFile = "DEFAULT.CFG" DataFile1 = "APP.DAT" ConfigFile1 = "DEFAULT.CFG" DisplayName = "BL and App" Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 55 CHAPTER 2 2.9 Custom labels Custom labels Flasher supports to assign custom labels to configurations. This allows to specify easy to remember names for configurations that are stored on the Flasher. 2.9.1 Hardware and software requirements This feature is supported by the following models: • Flasher Portable PLUS This feature is supported since V6.30e of the software package and firmware 2.9.2 Assigning labels The configuration and data file pairs are specified in the FLASHER.INI file: [FILES] DataFile ConfigFile DataFile1 ConfigFile1 = = = = "IMAGE0.dat" "IMAGE0.cfg" "IMAGE1.dat" "IMAGE1.cfg" By default, Flasher will show the names of the configuration and data file: By adding DisplayName, DisplayName1, … keys to the FLASHER.INI, a custom label can be shown instead: [FILES] DisplayName DataFile ConfigFile DisplayName1 DataFile1 ConfigFile1 = = = = = = "FW smartwatch" "IMAGE0.dat" "IMAGE0.cfg" "FW smart meter" "IMAGE1.dat" "IMAGE1.cfg" The images will now be shown as follows: Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 56 CHAPTER 2 2.9.3 • Custom labels Considerations The maximum length of a custom label is 32 characters. If this length is exceeded, the label is ignored and Flasher switches back to default mode for the affected configuration. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 57 CHAPTER 2 2.10 Programming multiple targets Programming multiple targets It is possible to program multiple targets which are located in a JTAG chain. The targets will be programmed each with a configuration and a data file. The configuration for the desired target must be selected before it can be programmed, this can be done with the #SELECT command. For more information how to use the #SELECT command please refer to Chapter “3.3.5 Commands to Flasher”. Example Three devices should be programmed. JTAG Chain: TDI --> Device2 --> Device1 --> Device0 --> TDO Three configurations would be stored on the flasher: Config 0: Configured to program Device0 (DEVICE0.CFG, DEVICE0.DAT) Config 1: Configured to program Device1 (DEVICE1.CFG, DEVICE1.DAT) Config 2: Configured to program Device2 (DEVICE2.CFG, DEVICE2.DAT) Selection and programming of the target will be done via the ASCII interface: #SELECT DEVICE0 #AUTO #SELECT DEVICE1 #AUTO #SELECT DEVICE2 #AUTO 2.10.1 Programming multiple targets with J-Flash Programming multiple targets can also be done via J-Flash using the command line interface. For this each target must be handled with its own project file. Example JFlash.exe -openproj"Device0.jflash" -open"Device0.hex" -auto -exit JFlash.exe -openproj"Device1.jflash" -open"Device1.hex" -auto -exit JFlash.exe -openproj"Device2.jflash" -open"Device2.hex" -auto -exit Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 58 CHAPTER 2 2.11 Batch Programming in stand-alone mode Batch Programming in stand-alone mode Batch programming allows to execute different stand-alone mode jobs in batch to be executed in immediate succession, without any user interaction in between. This can be used for example to program multiple targets in a JTAG-Chain or multiple data files to a target. A batch may contains an unlimited number of configurations which consist of a data file (*.DAT) and config file (*.CFG). For further information regarding config and data files, please refer to Preparing for stand-alone operation manually on page 46. In order to specify the batch jobs, a FLASHER.INI file is used. This init file contains a [BATCH] section which describes which configuration pairs (*.DAT and *.CFG file) should be used for each batch job. A sample content of a FLASHER.INI file is shown below: [BATCH] DataFile = "Flasher0.dat" ConfigFile = "Flasher0.cfg" DataFile1 = "Flasher1.dat" ConfigFile1 = "Flasher1.cfg" The Flasher Portable PLUS screen will show that the number of jobs contained in the batch and the configuration file name of the first job. The progress will be shown during the flashing action. The Flasher lists the current job of the batch, the current sector address and the percentage of the currently executed action. The result of the programming will be shown on the screen after finishing all jobs. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 59 CHAPTER 2 Batch Programming in stand-alone mode Creating / Replacing of the FLASHER.INI file can done in two ways: 1. Boot Flasher in file access mode in order to replace the FLASHER.INI 2. 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 87. In case of an error occurred during execution, the Flasher terminates the entire batch processing. Note Please note that the batch programming feature can not be used with the multiple file support feature. Therefore, neither the #SELECT ASCII command nor the [FILES] tag in the FLASHER.INI file can be used. Note Flasher supports 8.3 filenames only (8 characters filename, 3 characters file extension). Using longer filenames may result in incorrect operation. 2.11.1 Flasher Portable specifics Flasher Portable allows to choose between four different batches during runtime by using the select/arrow button on the front of Flasher Portable. Which batch configuration is used for which image selection position is specified in the FLASHER.INI. For this, the FLASHER.INI contents in the [BATCH] section have been extended. The sample below shows how to enable the user to select between four different batches on the Flasher Portable via the select / arrow button: [BATCH] DataFile = "Flasher0.dat" ConfigFile = "Flasher0.cfg" DataFile1 = "Flasher1.dat" ConfigFile1 = "Flasher1.cfg" DataFile2 = "Flasher2.dat" ConfigFile2 = "Flasher2.cfg" [BATCH1] DataFile = "TEST.dat" ConfigFile = "Test.cfg" [BATCH2] DataFile = "VALIDATE.dat" ConfigFile = "Flasher0.cfg" Using this method allows to have different batches for different setups used in the production to be stored once on the Flasher Portable via file access mode. From there on, switching between the batches can be done by simply using the selection button of Flasher Portable. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 60 CHAPTER 2 2.11.2 Batch Programming in stand-alone mode Examples Example 1: Programming two Data files to the same target • • • • • • • Open your J-Flash project. Use File -> Save Flasher config file… to save the .CFG file (in this example: STM32F4.CFG). Select the first binary and use File -> Save Flasher Data file… to save the first .DAT file (in this example: DATA0.DAT). Select the second binary and use File -> Save Flasher Data file… to save the second data file .DAT file (in this example: DATA1.DAT). Copy the Files to the Flasher e.g. by using file access mode. Create a FLASHER.INI file in the root directory of the Flasher. Exemplary content of FLASHER.INI: [BATCH] DataFile = "DATA0.dat" ConfigFile = "emPower.cfg" DataFile1 = "DATA1.dat" ConfigFile1 = "emPower.cfg" Example 2: Programming one Data file to the first target in a JTAG-Chain and then programming two data files to another device in the JTAG chain. Example scenario: 2 Devices in a JTAG chain, a STM32F1 and a STM32F4. • • • • Follow the same as described before and additionally: Create one project file per target (and create a .CFG file of each one). Make sure each project file is configured correctly, especially the JTAG-Chain position (See UM8003 “J-Flash” for more detailed info). Exemplary content of FLASHER.INI: [BATCH] DataFile = "F1DATA.dat" ConfigFile = "STM32F1.cfg" DataFile1 = "F4DATA0.dat" ConfigFile1 = "STM32F4.cfg" DataFile2 = "F4DATA1.dat" ConfigFile2 = "STM32F4.cfg" Example 3: Using multiple Batch sections with Flasher Portable. Example scenario: 2 Devices in a JTAG chain, a STM32F1 and a STM32F4. Selection 1 will program the STM32F1 target. Selection 2 will program the STM32F4 target using “F4DATA0.dat”. Selection 3 will program the STM32F4 target using “F4DATA1.dat”. Selection 4 will execute 1, 2 and 3 in sequence. • Exemplary content of FLASHER.INI: [BATCH] DataFile = "F1DATA.dat" ConfigFile = "STM32F1.cfg" [BATCH1] DataFile = "F4DATA0.dat" ConfigFile = "STM32F4.cfg" [BATCH2] DataFile = "F4DATA1.dat" ConfigFile = "STM32F4.cfg" [BATCH3] DataFile = "F1DATA.dat" ConfigFile = "STM32F1.cfg" DataFile1 = "F4DATA0.dat" ConfigFile1 = "STM32F4.cfg" DataFile2 = "F4DATA1.dat" ConfigFile2 = "STM32F4.cfg" Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 61 CHAPTER 2 2.12 Serial number programming 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. 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. 2. 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 JFlash software and the Flasher firmware that comes with it. Note Currently, programming of serial numbers is only supported for stand-alone mode. Future versions of J-Flash may also support serial number programming in PC-based mode. 2.12.1 Serial number settings In order to enable the programming of serial numbers in stand-alone mode, the J-Flash 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) © 2004-2022 SEGGER Microcontroller GmbH 62 CHAPTER 2 Setting Serial number programming Meaning Address The address the serial number should be programmed at. Len The length of the serial number (in bytes) which should be programmed. If no serial number list file is given, J-Flash 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. 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. Next SN 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. 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. Increment Specifies how much Next SN is incremented. 2.12.2 Serial number file When selecting File -> Download serial number file to Flasher, J-Flash will create a Serial number file named as _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.12.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. When selecting File-> Download serial number file to Flasher, J-Flash will look for a serial number list file named as _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. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 63 CHAPTER 2 Serial number programming 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 61. 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 61. 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.12.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. 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 programFlasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 64 CHAPTER 2 Serial number programming ming 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.12.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.12.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) © 2004-2022 SEGGER Microcontroller GmbH 65 CHAPTER 2 Serial number programming 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 _Serial.txt. Now Flasher is prepared to program the 8-byte serial number. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 66 CHAPTER 2 2.13 Patch file support Patch file support In stand-alone mode Flasher supports patch files which allows to patch the content of the data to be programmed. Patches for undefined memory locations will be ignored, so there need to be placeholders in the data file. 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 Each line begins with followed by each patch ,: in sequence and separated by commas. So the syntax for = = 4 would be as follows: ,,:,,:,, :,,:\r\n Find below a table which describes each parameter. Parameter 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). Value is expected in hex. Describes the data to be patched. is always expected as 2 hexadecimal characters per byte. Note All values are expected in hexadecimal format (hex). section is always preceded by “:”, not “,”. Example Below is an example patch. 1,18,4:01020304\r\n Patching the following data: with the example patch will result in the following data: Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 67 CHAPTER 2 Patch file support Please note that as mentioned earlier patching undefined memory locations will be ignored. Applying the example patch to the following data: Causes no data to be patched, as can be seen in the following image: Therefore it is necessary to first write placeholder data to the memory locations which are supposed to be patched. An example for such a placeholder can be seen here: Please note that the actual data inside the placeholder does not matter to the Flasher, because it is overwritten during patching. Applying the example patch will now work as expected: 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 ,,: command via Flasher ASCII interface. The parameters have the same function as described in the table above. 2.13.1 Newline encoding In general, for all patch files, init files etc. Flasher supports both newline encodings: • • Windows: \r\n Unix/Mac: \n All parser functionality etc. are written to be independent from the host operating system. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 68 CHAPTER 2 2.14 Limiting the number of programming cycles Limiting the number of programming cycles Flasher provides a mechanism to limit the number of programming cycles that can be performed in stand-alone mode with the configuration that is stored on the Flasher. To make use of this feature, a file called Cntdown.txt needs to be placed on the Flasher. This file simply contains a decimal number (32-bit unsigned integer) that describes how many programming cycles can be performed with the current setup. This feature especially makes sense when used in combination with authorized flashing. For more information about authorized flashing, please refer to Authorized flashing on page 69. Note The number in the Cntdown.txt is only updated on a successful programming cycle. Programming cycles that failed, do not affect the Cntdown.txt. 2.14.1 Changed fail/error LED indicator behavior In case a Cntdown.txt is found at boot time, the fail/error LED of Flasher behaves different from normal. If the number of programming cycles left is 10 or below, the following will happen: • • The red error/fail LED will lit for 1 second After this, it will blink/toggle x times @ 5 Hz, indicating the number of programming cycles left. (blinking 5 times for 5 cycles left, …) 2.14.2 Required Flasher hardware version for Cntdown.txt support Older Flasher models do not support the limiting of programming cycles. The Flashers with the following serial number ranges do not support limiting of programming cycles: • • • • 1621xxxxx 1630xxxxx 4210xxxxx 4110xxxxx (Flasher (Flasher (Flasher (Flasher ARM V2) ARM V3) PPC V1) RX V1) All other models / hardware versions support limiting of programming cycles. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 69 CHAPTER 2 2.15 Authorized flashing Authorized flashing Current hardware versions of Flasher support creation of a so called secure area which allows to pre-configure the Flasher with a given setup and then give it to external production facilities etc. without the possibility to read out the Flasher contents via file access mode, FILE I/O functionality (J-Link Commander) or RS232 commands. This section describes how to setup a secure area on a Flasher and how to move the configuration/data file(s) into it. 2.15.1 Creating / Adding the secure area By default, Flashers are shipped with a public area only (full Flasher flash size accessible via file access mode etc.). The secure area has to be activated / created once, to make use of it. This will reserve half of the Flasher storage size (on current models this will be ~64 MB) for the secure area. The secure area can be removed at any time, providing the full flasher storage to the public area again. The secure area can be created / removed via J-Link Commander, which is part of the software package that comes with Flasher. The following secure area related commands are available in J-Link Commander: • • securearea create securearea remove Note When creating or removing the secure area, all configuration and data files being stored on the Flasher, are lost. Please make sure that they are not needed anymore, before adding / removing the security area. 2.15.2 Moving files to the secure area Before moving configuration + data to the secure area, proper functionality of the setup should be tested in stand-alone mode. Once the setup is working as expected, do the following, to move the configuration + data into the secure area: • Start Flasher in file access mode (For more info, please refer to: file access mode on page 42) • • Create a folder “_SECURE” Move all files that shall be moved to the secure area, into this folder Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 70 CHAPTER 2 • • 2.15.3 area Authorized flashing Reboot Flasher (Do not enter file access mode again, yet! Otherwise, contents will not be moved). Now, depending on the configuration and data file size, it may take a bit, before the Flasher Power LED lit. Once it lit, all contents have been moved to the secure area and the _SECURE folder in the public area has been deleted. Now Flasher can be used in stand-alone mode, as normal, but the files cannot be read back by the user / operator. Considerations to be taken when using the secure When using the secure area, some things need to be considered: • • • • 2.15.4 All features like multiple file support, patch file support etc. can also be used when operating from the secure area. The secure area cannot be read back by any utility. Solely the FLASHER.LOG is always placed and updated in the public area, even when Flasher operates from the secure area. If there is any file/folder in the public area, except the FLASHER.LOG and there is also any configuration / data present in the secure area, stand-alone flashing will fail because it is not unambiguous which configuration / data shall be used. In such cases, Flashers with Ethernet / RS232 interface will output an appropriate error message on programming. All Flasher models will output an appropriate error message in the FLASHER.LOG. Moving files from the public into the secure area can be done multiple times, as explained in Moving files to the secure area on page 69. Each time files are moved from the public area to the secure area, all contents of the secure area are erased first, to make sure that no previous configuration is present there. Required Flasher hardware version Older Flasher models do not support authorized flashing. The Flashers with the following serial number ranges do not support authorized flashing: • • • • 1621xxxxx 1630xxxxx 4210xxxxx 4110xxxxx (Flasher (Flasher (Flasher (Flasher ARM V2) ARM V3) PPC V1) RX V1) All other models / hardware versions support authorized flashing. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 71 CHAPTER 2 2.16 Target interfaces Target interfaces The table below shows the supported target interfaces of the different Flasher models. Hardware Supported interfaces Flasher PRO JTAG, SWD Flasher Compact JTAG, SWD Flasher ARM JTAG, SWD Flasher RX JTAG Flasher PPC JTAG 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) © 2004-2022 SEGGER Microcontroller GmbH 72 CHAPTER 2 2.17 Supported architectures Supported architectures Flasher supports programming of the internal flash of a large number of different microcontrollers. The number of supported devices is steadily growing. You can always find the latest list of supported devices on our website: http://www.segger.com/supported-devices.html Sometimes, especially early in MCU development, only a few samples/boards are available and may not be made available to third parties (e.g. SEGGER) to add support for a new device. Also the existence of the device may have confidential status, so it might not be mentioned as being supported in public releases yet. Therefore it might be desirable to be able to add support for new devices on your own, without depending on SEGGER and a new release of the J-Link Software an Documentation Pack being available. The J-Link DLL allows customers to add support for new devices on their own. It is also possible to edit / extend existing device support by for example adding new flash banks (e.g. to add support for internal EEPROM programming or SPIFI programming). The following article in our Wiki https://wiki.segger.com/Open_Flashloader explains how new devices can be added to the DLL and how existing ones can be edited / extended. If a device is not supported, you can always contact us. We will be happy to provide you with an offer. 2.17.1 External flashes In general our Flashers support programming of external flashes listed below: • • • • • parallel NOR flash serial NOR flash NAND flash I2C/(Q)SPI EEPROM/Flash FRAM 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. Since the connection of the flash to the CPU can be different for each of the other flash types mentioned above, a suitable Open Flashloader can be used in such a case. The J-Flash software comes with sample projects for Open Flashloader. For a complete list of all Open Flashloader projects for use with J-Flash software, see also: http://www.segger.com/supported-devices.html Note Complete Information about Open Flashloaders can be found in our Wiki: https://wiki.segger.com/Open_Flashloader 2.17.2 Cores 2.17.2.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. • • • • • ARM7TDMI (Rev 1) ARM7TDMI (Rev 3) ARM7TDMI-S (Rev 4) ARM920T ARM922T Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 73 CHAPTER 2 • • • • • • • Supported architectures ARM926EJ-S ARM946E-S ARM966E-S Cortex-M0 Cortex-M1 Cortex-M3 Cortex-M4 2.17.2.2 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. • • • • RX610 RX621 RX62N RX62T 2.17.2.3 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 2.17.2.4 Flasher PRO/Compact/Portable PLUS All of the above cores using J-Flash. Many more and constantly growing by means of Universal Flash Loader https://www.segger.com/supported-devices/flasher/. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 74 CHAPTER 2 2.18 Programming multiple targets in parallel Programming multiple targets in parallel To program multiple targets in parallel there are the following possibilities: • • Using a Flasher gang, or Using multiple Flashers, each connecting to one CPU. Devices for gang progamming are: • • Flasher ATE; suitable for programming up to 10 targets in parallel. Refer Flasher ATE user manual (UM08035_FlasherATE.pdf). Flasher Hub in conjunction with up to 24 Flasher (Compact). Refer Flasher Hub user manual (UM08039_FlasherHUB.pdf). When using multiple flashers, this can be done with the J-Flash production programming software. For further information, please refer to Chapter “Command Line Interface” Sub-chapter “Programming multiple targets in parallel” of the J-Flash User Guide (UM08003_JFlash.pdf) which is part of the Flasher Software and Documentation package. https://www.segger.com/downloads/flasher/#FlasherSoftwareAndDocumentationPack Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 75 CHAPTER 2 2.19 Logfiles and Quality Management Logfiles and Quality Management All Flasher models keep a log file named Flasher.log which logs each programming attempt. This file contains the serial number of the device, the result of the programming attempt, and the programming duration for quality tracking purposes. An example of a Flasher.log file might look like the following: SN: SN: SN: SN: SN: SN: 1 1 2 3 4 5 - Failed Failed O.K. (931 O.K. (931 O.K. (933 O.K. (932 ms) ms) ms) ms) If applicable, the logfile contains more detailed error messages. For example: ERROR: Programming failed @ address 0x00000000 (1) ERROR: Cannot connect to CPU. Target interface speed too high? The Flasher Portable PLUS creates an additional log file named UNIERROR.LOG for Universal Flash Loader projects. This file contains error messages that would otherwise have been displayed by the other flashers on the terminal. For example: Verify error config word area @ config word config word read back Verify error flash area @ data from file data read back Note These log files can be accessed by booting the flasher into file access mode or directly via FTP if the flasher has an appropriate network interface. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 3 TCP Services This chapter describes the integrated TCP services. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 77 CHAPTER 3 3.1 FTP Server FTP Server The FTP server provides easy access to the files on the internal file system. The server supports a maximum of 2 simultaneous connections and works with all common FTP clients. 3.1.1 Access data Anonymous access to the FTP server is limited to read-only access to the file system. For write access, special login credentials have to be used: Login: admin Password: 1234 Note The access data for read/write access can not be modified and it is intended to be used only as a convenience feature to avoid unintended modification of the Flasher’s file system. It is not meant as a security feature. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 78 3.2 CHAPTER 3 Web server Web server All Flashers which come with an Ethernet interface also come with a built-in web server, which provides a web interface for information and network configuration. For the network, the IP address settings can be changed and a nick name can be assigned to the device. Additionally, the web interface provides information about the status of the integrated operating system, the IP stack and the target hardware. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 4 Remote control This chapter describes how to control Flasher via the 9-pin serial interface connector or via the integrated Telnet interface. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 80 CHAPTER 4 4.1 Overview Overview There are 3 ways to control Flasher operation: • • • • Manual: Programming operation starts when pressing the button. The LEDs serve as visible indicators. 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 signals. Terminal communication via RS232. Terminal communication via Telnet. Note All ways to control Flasher operation are working only if Flasher is in standalone mode. In PC-based mode or file access mode they have no effect. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 81 CHAPTER 4 4.2 Handshake control Handshake control Some Flasher models can be remote controlled by automated testers without the need of a connection to a PC. 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 handshake control is available for the following Flashers: • • • Flasher ARM Flasher PRO Flasher Compact (via Flasher Hub only) The following diagrams show the internal remote control circuitry of Flasher: Pin No. Function Description 1 START 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. 4 BUSY As soon as the “Auto” function is started, BUSY becomes active, which means that transistor is switched OFF. 5 GND Common Signal ground. 7 OK 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. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 82 CHAPTER 4 4.3 ASCII command interface ASCII command interface 4.3.1 Introduction Once set up using J-Flash, the Flasher can be driven by any application or just a simple terminal using ASCII commands. Every known command is acknowledged by the Flasher and then executed. After command execution, Flasher sends an ASCII reply message. 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 4.3.2 • • • 4.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 General usage Reply messages must be considered in each case. In general, a new command must not be sent before a reply for the last one has been received. When a flash programming function (#AUTO, #CANCEL, #ERASE, #PROGRAM, #VERIFY) has finished, the debug logic of the MCU is disabled (power down) and the target interface of the module is switched off (tristated). 4.3.4 Settings for ASCII interface via RS232 Flasher is driven via a RS232 serial port with the following interface settings: • • • • 9600 baud 8 data bits no parity 1 stop bit The baud rate can be changed by using the #BAUDRATE command. 4.3.5 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 remote controlled via Telnet: Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 83 CHAPTER 4 4.3.6 ASCII command interface Commands and replies The table below gives an overview about the commands which are supported by the current version of Flasher firmware. Click on the names for a detailed description: Commands to the Flasher #BAUDRATE #AUTO #AUTO PATCH #AUTO NOINFO #CANCEL #ERASE #PROGRAM #RESULT #SELECT #START #STATUS #VERIFY File I/O commands #FCLOSE #FCRC #FDELETE #FOPEN #FREAD , #FSIZE #FWRITE ,: #FLIST #MKDIR SecureArea commands #HASSECUREAREA #SECUREAREA Replies from the Flasher #ACK Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 84 CHAPTER 4 ASCII command interface Commands to the Flasher #NACK #OK #OK:: #OK: #STATUS: #DONE #ERRxxx Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 85 CHAPTER 4 4.3.6.1 ASCII command interface Commands to the Flasher #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: • • • The Flasher erases the target CPU (if not blank) The Flasher programs the target CPU The Flasher verifies the 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 #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 patching of 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 66. #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 This command can be sent in order to change the baud rate of the Flasher’s RS232 interface used for communication. 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 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 86 CHAPTER 4 ASCII command interface 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: #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 The #SELECT command is used to select a specific config and data file pair which should be used by Flasher to program the target. specifies the name of file pair without extensions (.CFG and .DAT) on the Flasher which should be selected. If you are using the universal flash programming mode, specifies the full name of the .UNI file including the extension. 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 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 87 CHAPTER 4 ASCII command interface #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 start the application using the method configured in the JFlash project. Flasher will reply with the following sequence of messages: #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 Replies from Flasher on page 91. #VERIFY This command can used to verify the target flash content against the data stored in Flasher. 4.3.6.2 File I/O commands The ASCII interface of the Flasher also supports file I/O operations. 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: Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 88 CHAPTER 4 ASCII command interface #ACK #ERR255:No file opened #FCRC The #FCRC command calculates a 32-bit CRC of the given file. This CRC can be used to verify file integrity. This command should not be used while a file has been opened via #FOPEN. The CRC will be also reported by J-Flash when downloading or saving files via J-Flash. A typical sequence when using the #FCRC command does look like as follows: #FCRC flasher.dat #ACK #OK:0x75BC855A #FDELETE The #FDELETE command is used to delete a file on Flasher where 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 The #FOPEN command is used to open a file on Flasher for further file I/O operations. specifies the file on the Flasher which should be opened. If 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: #ACK #ERR255:A file has already been opened #FREAD , The #FREAD command is used to read data from a file on Flasher. specifies the offset in the file, at which data reading is started. 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 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 89 CHAPTER 4 ASCII command interface If the #FREAD command succeeds, Flasher will finally respond with a #OK:: reply message. For more information about the Flasher reply messages, please refer to Replies from Flasher on page 91. 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: reply message. For more information about the Flasher reply messages, please refer to Replies from Flasher on page 91. 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 ,: The #FWRITE command is used to write to a file on Flasher. specifies the offset in the file, at which data writing is started. specifies the number of bytes which are send with this command and which are written into the file on Flasher. 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. and are expected in hexadecimal format. #FWRITE 0,200: #FWRITE 200,200: 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) © 2004-2022 SEGGER Microcontroller GmbH 90 CHAPTER 4 ASCII command interface #FLIST The #LIST command is used to list all files stored on the Flasher. A typical sequence using the #FLIST command does look like as follows: #FLIST #ACK FLASHER.INI Size: 60 SERIAL.TXT Size: 3 FLASHER.LOG Size: 207 FOLDER (DIR) FOLDER\TEST1.CFG Size: 2048 FOLDER\TEST1.DAT Size: 12288 #OK #MKDIR The #MKDIR command is used to create a directory on Flasher. specifies the name of the new directory. may also specify a path to create a subdirectory. A typical sequence using the #MKDIR command does look like as follows: #MKDIR folder #ACK #OK Note If the directory can not be created because of a bad argument, Flasher will respond with: #ACK #ERR255:Failed to create directory 4.3.6.3 Secure Area Commands #HASSECUREAREA The #HASSECUREAREA command checks if the Flasher is configured with a secure area. #RESULT:YES indicates the secure area is present, #RESULT:NO indicates no secure area is present. #SECUREAREA The #SECUREAREA command allows to create or remove the secure area on the Flasher. • • the action CREATE creates the secure area. the action REMOVE will remove the secure area. A typical sequence using the #SECUREAREA command does look like as follows: #SECUREAREA CREATE #ACK #DONE Note When creating or removing the secure area, all configuration and data files being stored on the Flasher, are lost. Please make sure that they are not needed anymore, before adding / removing the security area. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 91 CHAPTER 4 4.3.6.4 ASCII command interface Replies 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 descriptive 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:: Flasher replies with #OK:: if a #FREAD command was executed. 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. and are send in hexadecimal format (for : two hexadecimal characters per byte). #OK: Flasher replies if #OK: if a #FSIZE command has been executed. is the size (in bytes) of the currently opened file. is send in hexadecimal format. #STATUS: The Flasher replies with its current state. The following status messages are currently defined: Message Description #STATUS:READY Flasher is ready to receive a new command. #STATUS:CONNECTING Flasher initializes connection to target CPU. #STATUS:INITIALIZING Flasher performs self check and internal init. #STATUS:UNLOCKING Unlocking flash sectors. #STATUS:ERASING Flasher is erasing the flash of the target device. #STATUS:PROGRAMMING Flasher is programming the flash of the target device. #STATUS:VERIFYING Flasher verifies the programmed flash contents. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 92 CHAPTER 4 ASCII command interface #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 Description #ERR007 Flasher received #CANCEL command and has canceled the current operation. #ERR008 Flasher is already busy with execution of previous command. #ERR009 Failed to allocate memory. #ERR010 Failed to open file. #ERR011 Failed to read file. #ERR012 Failed to write file. #ERR013 Failed to delete file. #ERR255 Undefined error occurred. This reply is followed by an error string. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 5 Performance The following chapter lists programming performance of common flash devices andmicrocontrollers. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 94 CHAPTER 5 5.1 Performance of MCUs with internal flash memory Performance of MCUs with internal flash memory 5.1.1 Flasher ARM The following table lists program and erase performance values of Flasher ARM for different controllers. Microcontroller Size [kByte] Erase time [sec] Program time [sec] Verify time [sec] Total time [sec] Analog Devices 62 2.943 2.286 0.563 5.792 Atmel AT91SAM7S64 64 — 3.488 0.438 3.926 Atmel AT91SAM7S256 256 — 7.709 1.053 8.762 NXP LPC1768 512 3.740 8.559 5.092 17.391 NXP LPC2106 120 0.448 1.204 0.634 2.286 NXP LPC2129 248 0.449 2.916 1.347 4.712 NXP LPC2138 500 0.448 5.488 2.649 8.585 NXP LPC2148 500 0.448 5.632 2.721 8.801 NXP LPC2294 2048 0.808 15.976 9.669 26.453 NXP LPC2478 504 0.448 5.419 2.559 8.426 ST STM32F103ZE 512 0.028 18.763 3.939 22.730 ST STR711 272 0.429 5.476 4.742 10.647 ST STR912 544 1.167 12.907 5.236 19.310 TI TMS470R1B1M 1024 2.289 8.147 5.362 15.798 5.1.2 Flasher PRO See Flasher ARM. 5.1.3 Flasher Compact See Flasher ARM. 5.1.4 Flasher RX The following table lists program and erase performance values of Flasher RX. Microcontroller R5F56108 5.1.5 Size [kByte] 2.048 Erase time [sec] 9.523 Program time [sec] 11.915 Verify time [sec] 3.890 Total time [sec] 25.585 Flasher PPC The following table lists program and erase performance values of Flasher PPC. Microcontroller ST SPC560B50 Flasher User Guide (UM08022) Size [kByte] 576 Erase time [sec] 4.747 Program time [sec] 4.159 Verify time [sec] 1.929 Total time [sec] 10.917 © 2004-2022 SEGGER Microcontroller GmbH Chapter 6 Hardware This chapter gives an overview about Flasher specific hardware details, such as the pinouts and available adapters. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 96 CHAPTER 6 6.1 Flasher ARM 20-pin JTAG/SWD Connector 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. 6.1.1 Pinout JTAG The following table lists the Flasher JTAG pinout. PIN SIGNAL TYPE Description 1 VTref Input 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. 2 Vsupply NC 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. 3 nTRST Output 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. 5 TDI Output 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. 7 TMS Output JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS of target CPU. 9 TCK Output 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. 11 RTCK Input 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. 13 TDO Input JTAG data output from target CPU. Typically connected to TDO of target CPU. 15 RESET I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called “nRST”, “nRESET” or “RESET”. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 97 CHAPTER 6 PIN SIGNAL 17 DBGRQ 19 5V-Target supply TYPE Flasher ARM 20-pin JTAG/SWD Connector Description NC 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. Output This pin is used to supply power to some eval boards. Typically left open on target hardware. 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. 6.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 SIGNAL TYPE Description 1 VTref Input 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. 2 Vsupply NC This pin is not connected in J-Link. It is reserved for compatibility with other equipment. Connect to Vdd or leave open in target system. 3 Not Used NC This pin is not used by J-Link. If the device may also be accessed via JTAG, this pin may be connected to nTRST, otherwise leave open. 5 Not used NC This pin is not used by J-Link. If the device may also be accessed via JTAG, this pin may be connected to TDI, otherwise leave open. 7 SWDIO I/O Single bi-directional data pin. Output 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. 11 Not used NC 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 accessed via JTAG, this pin may be connected to RTCK, otherwise leave open. 13 SWO Output Serial Wire Output trace port. (Optional, not required for SWD communication.) 9 SWCLK Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 98 CHAPTER 6 PIN SIGNAL TYPE Flasher ARM 20-pin JTAG/SWD Connector Description 15 RESET I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called “nRST”, “nRESET” or “RESET”. 17 Not used NC This pin is not connected in J-Link. Output This pin is used to supply power to some eval boards. Not all J-Links supply power on this pin, only the KS (Kickstart) versions. Typically left open on target hardware. 19 5V-Target supply 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. 6.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 400mA. The output current is monitored and protected against overload and short-circuit. Power can be controlled via the J-Link commander. The following commands are available to control power: Command Explanation power on Switch target power on power off Switch target power off power on perm Set target power supply default to “on” power off perm Set target power supply default to “off” Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 99 CHAPTER 6 6.2 Flasher RX 14-pin connector 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 1 3 Signal TCK TRSTn Type Description Output JTAG clock signal to target CPU. It is recommended that this pin is pulled to a defined state on the target board. Typically connected to TCK on target CPU. Output 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. 4 EMLE Output Pin for the on-chip emulator enable signal. When the on-chip emulator is used, this pin should be driven high. When not used, it should be driven low. Pulled HIGH to VTref via 1k pull-up resistor on 14-pin adapter. 5 TDO Input JTAG data output from target CPU. Typically connected to TDO on target CPU. 6 — NC This pin is not connected to Flasher RX. 7 — NC This pin is not connected to Flasher RX. 8 VTref Input 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. 9 TMS Output JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS on target CPU. 10 — NC This pin is not connected to Flasher RX. 11 TDI Output 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 on target CPU. 13 nRES I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called “nRST”, “nRESET” or “RESET”. • • 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. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 100 CHAPTER 6 6.2.1 Flasher RX 14-pin connector 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 400mA. The output current is monitored and protected against overload and short-circuit. Power can be controlled via the J-Link commander. The following commands are available to control power: Command Explanation power on Switch target power on power off Switch target power off power on perm Set target power supply default to “on” power off perm Set target power supply default to “off” Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 101 CHAPTER 6 6.3 Flasher PPC 14-pin connector 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 Type Description 1 TDI Output 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 on target CPU. 3 TDO Input JTAG data output from target CPU. Typically connected to TDO on target CPU. 5 TCK Output JTAG clock signal to target CPU. It is recommended that this pin is pulled to a defined state on the target board. Typically connected to TCK on target CPU. 7 — NC This pin is not connected to Flasher PPC. 8 — NC This pin is not connected to Flasher PPC. 9 nRES I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called “nRST”, “nRESET” or “RESET”. Output JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS on target CPU. 11 VDDE7 Input 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. 13 nRDY Input Nexus ready output. Indicates to the development tools that the data is ready to be read from or written to the Nexus read/write access registers. Output 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 debug access. This pin is set to HIGH by Flasher PPC (in order to enable the JTAG TAP controller on the target device). 10 TMS 14 JCOMP • • 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) © 2004-2022 SEGGER Microcontroller GmbH 102 CHAPTER 6 6.4 Target board design 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 96 Pinout SWD on page 97 Flasher RX 14-pin connector on page 99 Flasher PPC 14-pin connector on page 101 In case of doubt you should follow the recommendations given by the semiconductor manufacturer. 6.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. 6.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) © 2004-2022 SEGGER Microcontroller GmbH 103 CHAPTER 6 6.5 Adapters Adapters 6.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 JLink JTAG Isolator User Manual (UM08010) which can be downloaded from our website. 6.5.1.1 Pinout The following table shows the target-side pinout of the J-Link JTAG Isolator. Pin Signal Type Description 1 VCC Output The target side of the isolator draws power over this pin. 2 VCC Output The target side of the isolator draws power over this pin. 3 nTRST Output 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. 5 TDI Output 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. 7 TMS Output JTAG mode set input of target CPU. This pin should be pulled up on the target. Typically connected to TMS of target CPU. 9 TCK Output 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. 11 RTCK Input 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. 13 TDO Input JTAG data output from target CPU. Typically connected to TDO of target CPU. 15 RESET I/O Target CPU reset signal. Typically connected to the RESET pin of the target CPU, which is typically called “nRST”, “nRESET” or “RESET”. 17 N/C N/C This pin is not connected on the target side of the isolator. 19 N/C N/C This pin is not connected on the target side of the isolator. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 104 CHAPTER 6 Adapters Pins 4, 6, 8, 10, 12, 14, 16, 18, 20 are connected to GND. 6.5.1.2 Safety This isolator provides basic isolation only. Do not use with hazardous voltages without further protection measures to avoid risk of electrical shock and fire. SEGGER isolators provide a basic isolation to withstand high voltages as mentioned in the resp. technical data section. To preserve integrity of human beings when dealing with potential hazardous voltages it is mandatory to have a second protection measure in place in case the first insulation barrier fails. This is called double or reinforced isolation. How this double isolation can be achieved depends on the use case or application setup. Also check your the local safety related directives valid for your country to make sure all requirements are met. 6.5.2 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 TagConnect. 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. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 105 CHAPTER 6 Adapters The J-Link Needle Adapter can be connected to J-Link via the 20-pin 0.1’’ JTAG to a 10pin needle connector. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 106 6.6 CHAPTER 6 How to determine the hardware version 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 PC-based mode). As part of the initial message, the hardware version is displayed. For more information about how to ensure that Flasher is in PC-based mode, please refer to PC-based mode on page 39. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 7 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) © 2004-2022 SEGGER Microcontroller GmbH 108 CHAPTER 7 7.1 Contacting support 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 file access mode. For more information about how to boot Flasher in file access mode, please refer to file access mode on page 42. Flasher is sold directly by SEGGER. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 109 7.2 CHAPTER 7 Frequently Asked Questions Frequently Asked Questions Maximum JTAG speed Q: What is the maximum JTAG speed supported by Flasher? A: Flasher’s maximum supported JTAG speed is 12MHz. Maximum download speed Q: What is the maximum download speed? A: 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) © 2004-2022 SEGGER Microcontroller GmbH Chapter 8 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) © 2004-2022 SEGGER Microcontroller GmbH 111 CHAPTER 8 8.1 Flash programming 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. 8.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. 8.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. 8.1.3 Available options for flash programming In general, there are two possibilities in order to use Flasher for flash programming: • • 8.1.3.1 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 “PC-based mode”) 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 43. 8.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. 8.1.4 How does the universal flash programming work? In universal flash programming mode, the flasher typically communicates with a boot loader running on the device using a vendor specific protocol, rather than using the debug interface. Universal flash programming is available only for stand-alone mode. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH Chapter 9 Glossary This chapter describes important terms used throughout this manual. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 113 CHAPTER 9 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 floating-point 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 Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 114 CHAPTER 9 there are multiple possible physical locations that are involved, such as a system that has main memory, a write buffer, and a cache. 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. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 115 CHAPTER 9 Test Access Port (TAP) The port used to access a device’s TAP Controller. Comprises TCK, TMS, TDI, TDO, and nTRST (optional). 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) © 2004-2022 SEGGER Microcontroller GmbH Chapter 10 Literature and references This chapter lists documents, which we think may be useful to gain a deeper under- standing of technical details. Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH 117 CHAPTER 10 Reference Title Comments [J-Link] J-Link / J-Trace User Guide This document describes J-Link and J-Trace. It is publicly available from SEGGER (www.segger.com). [J-Flash] J-Flash User Guide This document describes J-Flash. It is publicly available from SEGGER (www.segger.com). Flasher User Guide (UM08022) © 2004-2022 SEGGER Microcontroller GmbH