Flasher ARM More
Flasher ARM - Flash Programmer for ARM and Cortex-M3 cores
Flasher ARM is a programming tool for microcontrollers with on-chip or external Flash memory and ARM core. Flasher ARM is designed for programming flash targets with the J-Flash software or stand-alone. In addition to that Flasher ARM has all of the J-Link functionality. Flasher ARM connects via USB or via RS232 interface to a PC, running Microsoft Windows 2000, Windows XP, Windows 2003 or Windows Vista and has a built-in 20-pin JTAG connector, which is compatible with the standard 20-pin connector defined by ARM.
Features
- Stand-alone JTAG/SWD programmer (Once set up, Flasher can be controlled without the use of PC program)
- Support for ARM 7/9 and Cortex-M3
- Supports internal and external flash devices
- 64 MB memory for storage of target program
- Serial in target programming supported
- Data files can be updated as mass storage or via J-Flash
- Target interface: JTAG/SWD
- No power supply required, powered through USB
- Can be used as J-Link (JTAG emulator) with a download speed of up to 720 Kbytes/second
- Programming speed between 30-300 Kbytes/second depending on target hardware
Subscribe to Flasher ARM software notification JTAG interface connection (20 pin)
There is a standard 20 pin connector defined by ARM. Flasher ARM has a built-in 20-pin JTAG connector, which is compatible with this standard.
JTAG interface connector signals:
| 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 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 on 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 on target CPU. |
| 9 | 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. |
| 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 on 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 | DBGRQ | 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. |
| 19 | 5V-Target supply | Output | This pin can be used to supply power to the target hardware. |
Notes:
All pins marked NC are not connected inside J-Link. Any signal can be applied here; J-Link will simply ignore such a signal.
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.
Pin 2 is not connected inside J-Link. A lot of targets have pin 1 and pin 2 connected. Some targets use pin 2 instead of pin 1 to supply VCC. These targets will not work with J-Link, unless Pin 1 and Pin 2 are connected on the target's JTAG connector.
Pin 3 (TRST) should be connected to target CPUs TRST pin (sometimes called NTRST). J-Link will also work if this pin is not connected, but you may experience some limitations when debugging. TRST should be separate from the CPU Reset (pin 15)
Pin 11 (RTCK) should be connected to RTCK if available, otherwise to GND.
Pin 19 (5V-Target supply) of the connector can be used to supply power to the target hardware. Supply volatage is 5V, max. current is 300mA. The output current is monitored and protected agains 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" |
Specifications
| Power Supply | USB powered, 100mA for Flasher ARM. 500 mA if target is powered by Flasher ARM |
| USB Host Interface | USB 2.0, full speed |
| RS232 Host Interface | RS232 9-pin |
| Target Interface | JTAG 20-pin (14-pin adapter available) |
| Serial Transfer Rate between J-Link and Target | up to 12MHz |
| Supported Target Voltage | 1.8 - 5V |
| Target supply voltage | 5V |
| Target supply current | Max. 400mA |
| Operating Temperature | + 5 °C ... + 60 °C |
| Storage Temperature | - 20 °C ... + 65 °C |
| Relative Humidity (non-condensing) | < 90% rH |
| Size (without cables) | 121mm x 66mmx 30mm |
| Weight (without cables) | 120g |
| Supported OS | Microsoft Windows 2000 Microsoft Windows XP Microsoft Windows XP x64 Microsoft Windows 2003 Microsoft Windows 2003 x64 Microsoft Windows Vista Microsoft Windows Vista x64 |
Performance of MCUs with internal flash memory
The following table lists program and erase performance values 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 |
JTAG Speed
There are basically three types of speed settings:
- Fixed JTAG speed
- Automatic JTAG speed
- Adaptive clocking
Fixed JTAG speed
The target is clocked at a fixed clock speed. The maximum JTAG speed the target can handle depends on the target itself. In general ARM cores without JTAG synchronization logic (such as ARM7-TDMI) can handle JTAG speeds up to the CPU speed, ARM cores with JTAG synchronization logic (such as ARM7-TDMI-S, ARM946E-S, ARM966EJ-S) can handle JTAG speeds up to 1/6 of the CPU speed. JTAG speeds of more than 10 MHz are not recommended.
Automatic JTAG speed
Selects the maximum JTAG speed handled by the TAP controller.
NOTE:
On ARM cores without synchronization logic, this may not work reliably, since the CPU core may be clocked slower than the maximum JTAG speed.
Adaptive clocking
If the target provides the RTCK signal, select the adaptive clocking function to synchronize the clock to the processor clock outside the core. This ensures there are no synchronization problems over the JTAG interface.
NOTE:
If you use the adaptive clocking feature, transmission delays, gate delays, and synchronization requirements result in a lower maximum clock frequency than with non-adaptive clocking. Do not use adaptive clocking unless it is required by the hardware design.
Flasher 5 Release notes
Release notes for Flasher software and firmware
March 2011:
Flasher 5R3:
RENESAS R8C/36C series supported.
RENESAS R8C/3x series memory map corrected.
Flasher ST7:
RENESAS ST7FLit10B series supported.
RENESAS ST7FLit15B series supported.
RENESAS ST7FLit19B series supported.
November 2010:
Flasher 5R3:
RENESAS R8C/L35C series supported.
RENESAS R8C/L36C series supported.
RENESAS R8C/L38C series supported.
RENESAS R8C/L3AC series supported.
RENESAS R8C can now be used with ID ALeRASE.
RENESAS M16C/65 can now be used with ID ALeRASE.
April 2010:
Flasher 5R3:
RENESAS M306NKFHGP supported.
RENESAS M306NKFJTGP supported.
RENESAS M306NLFJGP supported.
RENESAS M306NLFHGP supported.
RENESAS R8C handling corrected.
January 2010:
Flasher 5R3:
RENESAS R8C/32A series supported.
RENESAS R8C/32C series supported.
RENESAS R8C/3JA series supported.
RENESAS R8C/33A series supported.
RENESAS R8C/33C series supported.
RENESAS R8C/33T series supported.
RENESAS R8C/35A series supported.
RENESAS R8C/35C series supported.
November 2009:
Flasher 5R3:
RENESAS R8C/34E series supported.
RENESAS R8C/34F series supported.
RENESAS R8C/34G series supported.
RENESAS R8C/34H series supported.
RENESAS R8C/36E series supported.
RENESAS R8C/36F series supported.
RENESAS R8C/36G series supported.
RENESAS R8C/36F series supported.
RENESAS R8C/38E series supported.
RENESAS R8C/38F series supported.
RENESAS R8C/38G series supported.
RENESAS R8C/38F series supported.
RENESAS M16C/6C series supported.
RENESAS M16C/64A series supported.
June 2009:
Flasher 5 QZ:
Custom specific Flasher hardware and software.
January 2009:
Flasher 5R3:
RENESAS R8C/1A series supported.
RENESAS R8C/1B series supported.
RENESAS R8C/24 series supported.
RENESAS R8C/25 series supported.
RENESAS R8C/2A series supported.
RENESAS R8C/2B series supported.
RENESAS R8C/2C series supported.
RENESAS R8C/2D series supported.
RENESAS M16C/56 series supported.
RENESAS M16C/5L series supported.
RENESAS M16C/63 series supported.
RENESAS M16C/65 series supported.
RENESAS M38049FFHSP and M38049FFHFP supported.
April 2008:
Flasher ST7:
ST7FOXA0 series supported.
Flasher 5R3:
RENESAS M16C/28B series supported.
RENESAS M3062LFGPFP, M3062LFGPF supported.
March 2008:
Flasher ST7:
ST7LiteU05 and ST7LiteU09 series supported.
Flasher 5R3:
RENESAS R8C/28, R8C29, M16C/64, M16C/65, M16C/6S series supported.
December 2007:
Flasher 5R3:
RENESAS R32C and R8C series supported.
January 2006:
Flasher 3, 4, 5:
RENESAS M32C/84, M32C/85, M32C/86 and M32C/87 series supported.
October 2005:
RC calibration value recovery after clearing readout protection on ST7Lite CPUs implemented.
Requires software and firmware update to version 1.92j.
September 2005:
Programming speed increased for ST7 HD-Flash devices.
Requires firmware update to version 1.92h.
May 2005:
Up to 20 COM ports supported by FLASHER PC program.
Additional options and commandline parameter added.
Multiple individual setups can be controlled with command line to support multiple Flasher on one PC.
Readout protection of ST7 devices can now be removed automatically.
Option bytes may be programmed before other FLASH sectors are programmed. This enables fast programming when internal clock of ST7 CPU has to be used.
January 2004:
Firmware since version 1.84 implements simple ASCII command interface to Flasher 3R4, Flasher 4, Flasher 4R1, Flasher 5 and Flasher ST7.
Device files from Flasher PC program replaced by a single "CSV" file. Startup time of Flasher PC program drastically reduced.
September 2003:
Software version 1.82 supports Flasher 3R4, Flasher 4, Flasher 4R1, Flasher 5 and Flasher ST7 only
Flasher 2, Flasher MV3 or Flasher 3S are not supported by this software version and will not be supported in the future.
Software version 1.78 or lower supports all Flasher versions including Flasher MV3, Flasher 3S. This version is still available from our download page.
The following table lists all major modifications of Flasher software:
| Version | New features | Improvements / Corrections | Flasher type |
| V2.00h | R8C/36C supported. | Memory maps for all R8C/3x devices with 96 KB and 128 KB Flash corrected. | Flasher 5 |
| V2.00h | ST7FLite10B series supported. ST7FLite15B series supported. ST7FLite19B series supported. |
NONE. | Flasher ST7 |
| V2.00g | NONE. | Communication to R8C corrected. With R8C/3x devices, the data Flash could not be cleared. A firmware update of Flasher is required to fix the problem. | Flasher 5 |
| V2.00f | Support for several new R8C devices added. | The special ID code "ALeRASE" can now be used for R8C and M16C devices to force erasure of the device. A firmware update of Flasher is required. | Flasher 5 |
| V2.00e | NONE | PC device dialog corrected. R32C CPUs could be selected from the list when a Flasher 4 was connected, even though Flasher 4 can not program these devices. | Flasher 4 |
| V2.00d | Support for some M306N devices added. | R8C handling corrected. The Flasher could hang forever if the connection to the target CPU was disconnected during operation. The Flasher had to be power-cycled to solve this problem. |
Flasher 5 |
| V2.00c | Support for several new R8C devices added. | None. | Flasher 5 |
| V2.00b | Support for several new devices added. | None. | Flasher 5 |
| V2.00 | Support for Flasher 5 QZ. | Custom specific Flasher, requires specific software. | Flasher 5QZ |
| V1.98 | Support for several new devices added. | Software corrected to handle R32C devices. Older software did not allow selection of R32C when using Flasher 5R3. | Flasher 5 |
| V1.96n | Support for ST7FOXA0 added. | New commandline options "-setDE"/"-clearDE" added to enable/disable "Detailed error level on return" via batch command. | Flasher ST7 |
| V1.96n | Support for M16C/28B added. Support for M3062LFGP added. |
New commandline options "-setDE"/"-clearDE" added to enable/disable "Detailed error level on return" via batch command. | Flasher 5 |
| V1.96m | Support for ST7LiteU05, ST7LiteU09 added | Previous Flasher software version did not show a recent file list and did not allow to reload the last file via menu entry. The problem is fixed with version 1.96m of the PC software. |
Flasher ST7 |
| V1.96m | Support for R8C/28, R8C/29 added | Previous Flasher software version did not show a recent file list and did not allow to reload the last file via menu entry. The problem is fixed with version 1.96m of the PC software. |
Flasher 5R3 |
| V1.96m | Support for M16C/64, M16C/65, M16C/6S added | Previous Flasher software version did not show a recent file list and did not allow to reload the last file via menu entry. The problem is fixed with version 1.96m of the PC software. |
Flasher 5, all versions |
| V1.96l | Support for R8C/14, R8C/15, R8C/24, R8C/25 added | NONE | Flasher 5R3 |
| V1.96k | Support for R32C, R8C/22, R8C/23 added | NONE | Flasher 5R3 |
| V1.96i | Support for R32C/121 added | NONE | Flasher 5R3 |
| V1.96h | Support for R8C/24, R8C/25, R8C/26, R8C/27 |
NONE | Flasher 5R3 |
| V1.96g | M30281FCHP supported | Device file for M306N5 updated. Flash block A (0xF000..0xFFFF) can be handled now. Flasher PC program now uses its own "ini" file to save all settings onto disk. Using multiple Flasher with one PC without influencing each other is therefore possible by using multiple Flasher PC programs in different subdirectories. Command line mode od Flasher PC program corrected. Parsing of all -clear**** option setting commands did not work. |
Flasher 3, 4, 5 |
| V1.96g | ST72F345C4T6 supported | Device file for M306N5 updated. Flash block A (0xF000..0xFFFF) can be handled now. Flasher PC program now uses its own "ini" file to save all settings onto disk. Using multiple Flasher with one PC without influencing each other is therefore possible by using multiple Flasher PC programs in different subdirectories. Command line mode od Flasher PC program corrected. Parsing of all -clear**** option setting commands did not work. |
Flasher ST7 |
| V1.96f | NONE | Async. mode for RENESAS CPUs modified. LEDs did not blink during target access in previous version. | Flasher 5R31 |
| V1.96e | NONE | Async. mode for RENESAS CPUs corrected. Previous version produced timeouts during clear. | Flasher 5R31 |
| V1.96d | NONE | Device file Correction. Previous version 1.96c was delivered with only one device in the device file. This problem existed in version 1.96c of the PC software only and can be fixed by installing version 1.94d. |
All |
| V1.96c | Prepared for async. serial I/O mode for RENESAS CPUs. | NONE | Flasher 5 |
| V1.96b | ST72F325R9 support added. ST72F325J9 support added. |
Timeout for programming ST7 HND CPUs enlarged to 16 seconds. Previous value of 4 seconds was too short for some devices. A firmware download is required to activate longer timeout. Reading Option bytes might have failed under some circumstances after selecting an other device. All X-Flash devices (ST7Lite) are affected. The problem existed since version 1.94l and can be fixed by a firmware download to Flasher. |
Flasher ST7 |
| V1.96a | Target CPUs with 1.5 MB Flash supported. | Flasher 5 Rev.3 now supports target CPUs with up to 1.5 MB Flash. The new firmware is useable with all Flasher 5 since series number 51584. A firmware download is required to enable large Flash support. |
Flasher 5 |
| V1.94m | NONE | Flasher 5 firmware corrected. Flasher with SN 51584 to 51688 did not work with files above 256KB. A CRC check error was reported. A firmware download is required to fix the problem. |
Flasher 5 |
| V1.94l | ST7LiteUSx supported. | ST72F34x handling corrected. Previous versions of Flasher software may have programmed wrong option byte values which could cause target CPU malfunction. | Flasher ST7 |
| V1.94j | New ASCII command "#CLEARALL" to remove readout protection of ST7 CPUs. | Blank check now returns correct error code 85 "target protected" if readout protection is activated. Clear now clears the target CPU if target CPU is readout protected and option "Automatically clear readout protection" is set. |
Flasher ST7 |
| V1.94i | ST7FLite19B1 supported. | NONE | Flasher ST7 |
| V1.94h | ST72F324B devices supported. ST72F325J6 devices supported. ST72F32A devices supported. |
NONE | Flasher ST7 |
| V1.94h | RENESAS M30280FCHP supported. | NONE | Flasher 4, Flasher 4R1, Flasher 5 |
| V1.94h | command -setFILL added which allows definition of the fill byte by command line options. | NONE | ALL |
| V1.94g | NONE | Bug in pc program fixed. If no device files were loaded, previous versions of pc program raised an exception. | ALL |
| V1.94e | NONE | Communication for "slow" and "very slow" speed setting modified for ST7 CPUs Improves communication for target boards with capacitors on data lines. |
Flasher ST7 |
| V1.94d | Four different speeds can be selected for RENESAS CPUs: Fast, Medium, Slow, Very Slow. | "Fast" and "Medium" behave like previous options "Fast" and "Slow". The new options "Slow" and "Very Slow" may be helpful for target boards with capacitors on data lines. |
All |
| V1.94c | NONE | Flasher PC program corrected. When a HEX-file with checksum error was loaded via command line, the error handler run recursive and poped up severel message boxes. | PC program only |
| V1.94b | NONE | Command line option "-com" of Flasher PC program corrected to support COM ports from COM1 to COM20 Previous versions only supported COM1 to COM9. |
All |
| V1.94a | NONE | A firmware bug in Flasher 5 Rev2 caused a CRC check error in Flasher, if selected target memory size exceeded 320KB. Only Flasher with S/N from 51002 to 51088 are affected. A firmware update is recommended. |
Flasher 5 |
| V1.92k | M30626FJPFP, M30626FJPGP, M30627FHPG, M30627FJPGP supported | NONE | Flasher 4, Flasher 4R1, Flasher 5 |
| V1.92j | RC calibration recovery after clearing readout protection of ST7Lite CPUs implemented | Clearing readout protection of ST7Lite CPUs resulted in loss of RC calibration values. New Flasher software and firmware allows recovery of these values, if "protected areas" containing these values are selected. Selection of "OPT disabled" entry mode and external clock, which may be delivered from Flasher, is required to recover RC calibration values. |
Flasher ST7 |
| V1.92i | NONE | Timeout values for erasure of M3803H CPUs and M38507 CPUs increased to 8 seconds. Previous timeout of 4 seconds was to short for some CPUs and resulted in "erase failed" error. |
Flasher 4, Flasher 4R1, Flasher 5 |
| V1.92h | NONE | ST7 programming speed increased for HD-Flash devices | Flasher ST7 |
| V1.92h | NONE | Data Flash area of M16C/62P group CPUs (Addr 0xF000) may now be programmed either serial or parallel without the need of a separate device selection or address translation in parallel mode. | Flasher 4, Flasher 4R1, Flasher 5 |
| V1.92g | NONE | H3803H CPU programming corrected. Previous versions caused target CPU timeouts. Programming or erasure of CPU was impossible. H3803H CPU reset sequence modified. Previous versions did not honor settings of Reset active / inactive time from Setup configuration. |
Flasher 4, Flasher 4R1, Flasher 5 |
| V1.92f | NONE | Online help file in PC programm updated. Previous version did not contain all command line parameter. | Flasher ST7 |
| V1.92e | NONE | Data pulse length during init sequence increased to ensure entering ICC mode on targets with capacitive load. | Flasher ST7 |
| V1.92d | ST7Lite3 series supported | NONE | Flasher ST7 |
| V1.92c | ST7FMC series supported | Blank check for ST7 CPUs optimized, runs 10 times faster. Programming of ST72F324J2/K2/LJ2T/LK2T devices corrected. These devices could not be programmed with previous versions. |
Flasher ST7 |
| V1.90b | Up to 20 COM ports supported by PC program | NONE | All |
| V1.90a | NONE | CRC calculation corrected for large target addresses and when USER & Boot mode was selected. | Flasher 4, Flasher 4R1, Flasher 5 |
| V1.90 | Additional options for command line added. Individual setups can be controlled by PC program to handle multiple individual Flasher. |
NONE | All |
| V1.89 | Option bytes may be programmed prior other FLASH sectors and final option byte programming. | NONE | Flasher ST7 |
| V1.88b | NONE | M3803 series timing corrected for "High" speed setting. Previous versions could fail with "Target chip syas busy" error Corrected with version 1.88b. |
Flasher 4, Flasher 4R1, Flasher 5 |
| V1.88a | M3803H series supported M37542F8FP series supported M16C/26,26A,28,29 supported. |
NONE | Flasher 4, Flasher 4R1, Flasher 5 |
| V1.88 | NONE | ICC_DATA pulses for entering ICC mode elongated. | Flasher ST7 |
| V1.86b | New ASCII commands implemented: #BLANK #CLEAR #START |
ASCII command "#AUTO NOINFO" corrected. This command behaved like "AUTO" before, it always returned status information. | All |
| V1.86 | ST72F324 low voltage devices supported | NONE | Flasher ST7 |
| V1.86 | TOSHIBA CPUs supported by Flasher 5T | NONE | Flasher 5T |
| V1.84h | NONE | Device files for ST72F26x series corrected. Firmware modified for improved option byte handling. Erasure of option bytes sometimes failed on ST72F32x and ST72F521 devices. |
Flasher ST7 |
| V1.84c | NONE | Device files corrected. Version 1.84 did not support programming Bootarea for Renesas CPUs in parallel mode. | Flasher 4 parallel |
| V1.84b | NONE | "-seldevice" batch command handling corrected. Screen was not updated after command execution. "-selbanks" batch command corrected. Did not work on previous versions "Edit" data function corrected. Did not work properly when data was relocated before. |
All |
| V1.84 | ASCII command interface Device files replaced by single "CSV" file. |
Startup time of Flasher PC program improved by using CSV-File instead of different device files. Device files, if present, are still read after reading the CSV-File. Device files may therefore be used to override entries of the "CSV"-Device file, or to add new devices, not supported by "CSV"-File. |
Flasher 4, Flasher 4R1, Flasher 5, Flasher ST7 |
| V1.84 | ST7Lite1 series supported. ST7LiteS2 supported. ST7LiteS5 supported. ST7Lite02 supported. ST7Lite05 supported. |
ST7Lite20 corrected. RC-oscillator calibration values were not restored. ST7DALI corrected. RC-oscillator calibration values were not restored. AUTO mode (start button or external control input) did not restore RC-oscillator calibrartion values, if target CPU was cleared prior programming. Corrected. |
Flasher ST7 |
| V1.82c | NONE | New "Clear readout protection" warning locked batch process when "-clearall" command was called from batch file. Corrected | Flasher ST7 |
| V1.82c | NONE | Error in reading "INTEL-HEX" files corrected. File open or reload could result in wrong target address calculation. This bug occured on extended Hex-Files and exists in all previous software versions. Corrected. |
All |
| V1.82b | NONE | Flasher 4 did not handle parallel programming due to a bug in Software version 1.82. Every access to parallel programming socket ended in error message "Flasher lost Setup". Corrected with version 1.82b. Please update Flasher firmware to correct this problem. |
Flasher 4, Flasher 4R1 |
| V1.82 | "Programmable areas" introduced |
ST7 Option bytes handeled as programmable area. Programming ST7 CPU including option bytes with readout protection is possible with verification now. "Clear readout protection" terminated in error "Target is read protected" if protected areas were enabled in version 1.78. Corrected. |
Flasher ST7 |
| V1.78 | ST7Lite0 supported "Protected areas" |
Protected areas allow preserving of RC oscillator calibration data | Flasher ST7 |
| V1.76c | NONE | Option byte handling improved: Option bytes are never erased and never "Blank checked". |
Flasher ST7 |
| V1.76b | NONE | Timeout problems fixed. Flasher could hang and had to be reset, if target did not respond to commands within given time. | Flasher ST7, Flasher 5 |
| V1.76a | ST7Lite2, ST7DALI supported | NONE | Flasher ST7 |
| V1.74e | NONE | SIO communication breakdown occured during "Clear Readout protection". Corrected | Flasher ST7 |
| V1.74e | M306N4FCFP supported M301N2F8TFP supported |
SIO communication sometimes was locked, when other application enabled error abort before usage of Flasher program. Corrected | All except ST7 |
| V1.74d | COM1 to COM6 selectable | -password batch command (for Renesas CPUs) now also works when Flasher is not connected. | All |
| V1.74d | Flasher 5 supported | NONE | Flasher 5 |
| V1.74b | NONE | "Overlapping areas" in target HEX file produced PC program crash. Therefore "-merge" function in batchmade could not be used. Fixed. | All |
| V1.74 | M30626FHPFP supported M306N4FGFP supported M306N5FxFP supported |
Error handling improved. Detailed errorlevel on return may be choosen | All except ST7 |
| V1.74 | ST72F26x supported ST72F561 supported ST7FLCD1 supported |
Option byte programming described in online help. Error handling improved. Detailed errorlevel on return may be choosen |
Flasher ST7 |
| V1.72m | M32C 3V types supported | None | All except ST7 |
| V1.72j | None | Option bytes are automatically cleared before programming. This is required to program brand new CPUs without the need to erase them before programming option bytes | Flasher ST7 |
| V1.72j | None | BUSY check for Renesas CPUs corrected. "Slow" speed setting could result in error 41: "Busy does not react" | Flasher 4 |
| V1.72i | M38K2 CPUs supported | Timings and reset sequence for M38 CPUs corrected to avoid error 40: "Target chip says BUSY" | Flasher 4 / 4R1 |
| V1.72g | None | Timeout for erasure of M30201 CPUs in serial mode prolonged to 60 seconds | All except ST7 |
| V1.72f | ST72F324 supported | None | ST7 |
| V1.72e | ST92F150 supported | Editing of Hexfile in Dump mode corrected. This did not work, if only a few bytes in last line. |
Flasher 4 |
| V1.72e | None | Editing of Hexfile in Dump mode corrected. This did not work, if only a few bytes in last line. |
All |
| V1.72d | Reads Mot files with lines terminated by either CR or LF | Master Copy Mode corrected (CRC Check) Validation of target program before programming via command line |
All |
| V1.72c | ST7 devices supported | None | ST7 |
| V1.72b | Command line support added, replaces FlasherPro software |
"Clear chip" function for ST9 CPUs added | All |
| V1.72 | M32C83 devices (512K) supported Device files introduced |
None | All |
| V1.70d | M306NxFC (128K) supported | BUG fixed: When ID was copied to loaded file, CRC was not recalculated | All |
| V1.70c | M38C29FF supported M38507F8 supported |
None | Flasher 4R1 |
| V1.70 | CRC check implemented | Data integrity improved | All |
| V1.66r1 | M30624FGN supported M306N0FG supported |
None | All |
| V1.66q | None | Parallel read mode modified. Newer devices of M16C caused Read or Verify errors due to different timing | Flasher 4 parallel |
| V1.66p | M30220 supported M37906 variable ID length supported |
None | Flasher 4 |
| V1.66o | M30201 user & bootsector can be programmed at once | None | All parallel |
| V1.66n | None | M30201 targets with low clock speed supported | All |
| V1.66m | None | Master copy mode | Flasher 4 |
| V1.66j | None | BUG fixed for M30201 in parallel mode. Older devices only programmed every second page | All parallel |
| V1.66i1 | M30218 supported | None | All |
| V1.66i | M37906 supported, but without ID | None | Flasher 4 |
| V1.66 | Firmware update via Flasher PC program | None | All |
| V1.64l | None | M16C/20 serial mode changed (double Reset) due to new specification from Renesas | All |
| V1.64k | None | Problems with Boot sector selection in parallel mode fixed | All parallel |
| V1.64b | None | Clearing the target before programming is optional | All |
| V1.60i | None | BUGFIX: Pages (256 byte of data) were assumed blank, when they contained data only at even addresses | All |
Copyright 2001-2011 SEGGER Microcontroller GmbH & Co KG. All rights reserved.
For more information, please visit our website www.segger.com or contact us at
このメールアドレスはスパムボットから保護されています。閲覧するにはJavaScriptを有効にする必要があります。
Flasher 5
Flasher 5 - Flash programmer for M16C, M32C, R8C, R32C, M38000 and ST9 series of flash microcontrollers
Features
- Small, compact housing
- Easy to use windows program
- Serial (in target) programming supported
- Programming / Verifying / Read back supported
- 2MByte internal Flash memory to store target program
- High speed programming: app. 17 sec for 256 kb in serial mode with 10 MHz M16C target for programming and verification
- Can be used in a production environment
- PC program allows batch mode processing for usage in automated test systems.
- Once set up, Flasher can be controlled without the use of PC program
- ASCII command interface to control Flasher without the use of PC program (Requires firmware version 1.84 or above)
New features
March 2011:
Flasher 5R3:
RENESAS R8C/36C series supported.
RENESAS R8C/3x series memory map corrected.
Flasher ST7:
RENESAS ST7FLit10B series supported.
RENESAS ST7FLit15B series supported.
RENESAS ST7FLit19B series supported.
November 2010:
Flasher 5R3:
RENESAS R8C/L35C series supported.
RENESAS R8C/L36C series supported.
RENESAS R8C/L38C series supported.
RENESAS R8C/L3AC series supported.
RENESAS R8C can now be used with ID ALeRASE.
RENESAS M16C/65 can now be used with ID ALeRASE.
April 2010:
Flasher 5R3:
RENESAS M306NKFHGP supported.
RENESAS M306NKFJTGP supported.
RENESAS M306NLFJGP supported.
RENESAS M306NLFHGP supported.
RENESAS R8C handling corrected.
January 2010:
Support for RENESAS R8C/32A added.
Support for RENESAS R8C/32C added.
Support for RENESAS R8C/3JA added.
Support for RENESAS R8C/33A added.
Support for RENESAS R8C/33C added.
Support for RENESAS R8C/33T added.
Support for RENESAS R8C/35A added.
Support for RENESAS R8C/35C added.
November 2009:
Support for RENESAS R8C/34E added.
Support for RENESAS R8C/34F added.
Support for RENESAS R8C/34G added.
Support for RENESAS R8C/34H added.
Support for RENESAS R8C/36E added.
Support for RENESAS R8C/36F added.
Support for RENESAS R8C/36G added.
Support for RENESAS R8C/36F added.
Support for RENESAS R8C/38E added.
Support for RENESAS R8C/38F added.
Support for RENESAS R8C/38G added.
Support for RENESAS R8C/38F added.
Support for RENESAS M16C/6C added.
Support for RENESAS M16C/64A added.
January 2009:
Support for RENESAS R8C/1A added.
Support for RENESAS R8C/1B added.
Support for RENESAS R8C/24 added.
Support for RENESAS R8C/25 added.
Support for RENESAS R8C/2A added.
Support for RENESAS R8C/2B added.
Support for RENESAS R8C/2C added.
Support for RENESAS R8C/2D added.
Support for RENESAS M16C/56 added.
Support for RENESAS M16C/5L added.
Support for RENESAS M16C/63 added.
Support for RENESAS M16C/65 added.
Support for RENESAS M38049FFHSP and M38049FFHFP added.
April 2008:
Support for RENESAS M16C/28B, M3062LFGPFP, M3062LFGPGP added.
March 2008:
Support for RENESAS R8C/28, R8C29, M16C/64, M16C/65, M16C/6s added.
December 2007:
Support for RENESAS R32C and R8C added.
October 2006:
Flasher 5 rev. 3 comes with 2MByte Flash to store target data.
This allows programming of all RENESAS CPUs with more than 512KB Flash when Software 1.96a or above is used.
All Flasher 5 with series number above 51584 can be upgraded by just using the new Flasher software.
May 2005:
Up to 20 COM ports supported by FLASHER PC program.
Additional options and commandline parameter added.
Multiple individual setups can be controlled with command line to support multiple Flasher on one PC.
January 2004:
ASCII command interface implemented to control Flasher from any application without the need of Flasher PC program.
A manual which describes ASCII command interface and new Flasher software can be downloaded from our downloadpage.
Flasher 5 Installing / using software
Installing / using software
Installing the FLASHER PC-software
The PC software FLASHER.EXE is distributed on the accommodating 3.5" floppy disk; In order to use the software, simply copy the setup program onto your hard drive. Starting the setup program will guide you through the installation process.
Connecting FLASHER to the PC
PC FLASHER interface cable
A standard serial interface cable (null modem) can be used to connect FLASHER to the PC.
The pin assignment of the 9 pin SUB-D male RS-232 interface connector is as follows:
| Pin no. | Signal | Function | Host-Signal |
|---|---|---|---|
| 2 | RxD | Serial asynchronous (RS232) data input | Serial data output (TxD) |
| 3 | TxD | Serial asynchronous (RS232) data output | Serial data input (RxD) |
| 5 | GND | Signal ground | Signal ground |
Getting started
- Connect FLASHER to a PC running Windows 95/98/2000 or NT using the NULL-modem cable and run the FLASHER software FLASHER.EXE
- Connect FLASHER to the power supply.
- Set up the device via Options menu of PC program
- For in-circuit programming: Connect FLASHER to target system via customized interface cable.
- Before connecting the target system to Flasher, ensure, there is no ground potential difference between target and Flasher, otherwise the Flasher may be damaged.
Using the FLASHER PC program
General
| Flasher comes with an easy to use Windows program. It allows reading of program files in Motorola or Intel hex format. The following is a screen shot of the FLASHER.EXE with loaded target program |  |
Communication between PC and FLASHER
Make sure the power supply is connected (one of FLASHERs LEDs should be illuminated) and FLASHER is connected to your PC with a NULL-modem cable as supplied. If the PC-program displays anything other than "No communication" under flasher status, the communication between Flasher and your PC is functioning.
First time setup of FLASHER
When using FLASHER for the first time, please select the menu point Options->Device. You will see the following dialog box:
 |
First carefully select the correct target device. A false selection may damage your target! Then select the chip area you would like to access, the sectors of the on chip-flash and the interface you would like to use. The serial interface requires a cable to connect FLASHER to your target. For targets running at low frequencies, it may be necessary to set the speed option to Slow. |
Now you should be able to blank check, clear, program, verify or read the target chip in serial mode (if your target is properly connected to the FLASHER). The first time you program or verify, the PC downloads your your target program to the FLASHER, where it is stored in the on board RAM chip for programming or verification. The PC-Program stores all setup information in the registry; when you start the program the next time, it will start with the same settings.
Programming/clearing/verifying/blank check
| Select one of the commands in the TARGET menu to start the operation. Note that some of the menu points may be grayed if you have no connection to the target or no file loaded |  |
 |
A modal dialog box will indicate the status and progress of the operation; the operation can be canceled hitting the CANCEL button |
SETUP
 |
The operating mode of FLASHER may be changed using the setup dialog from the Options menu.Power up mode, Power down mode and Reset mode should not be changed for normal operation. Setting of Power down mode has no effect on FLASHER MV3.You may change the reset active and reset inactive time, if required by your target hardware. All setup settings are stored permanently in FLASHER after pressing 'Save setup' button. |
Additional options
 |
The operating mode of FLASHER may be changed using the setup dialog from the Options menu.Power up mode, Power down mode and Reset mode should not be changed for normal operation. Setting of Power down mode has no effect on FLASHER MV3.You may change the reset active and reset inactive time, if required by your target hardware.All setup settings are stored permanently in FLASHER after pressing 'Save setup' button. |
ID check
| When programming the chip in serial mode (in target), a 7 byte identification has to be supplied. If the target mcus user program area is blank, this id-value does not matter. However, after programming, these values need to be set correctly, because otherwise FLASHER will be unable to communicate with the target CPU. These ID-values can be set using the menu point Options|Pass code (7 byte ID). With a standard program, these values should be 0, as the high bytes of the interrupt vectors which are used to store the values are usually 0. For more detailed information, please consult the Renesas users manual. The menu point "Edit|Copy Renesas Id into loaded file" can be used to set these 7 ID bytes. |  |
Problems with ID check
You should act carefully when using the ID bytes. if you do not know the ID-value programmed into a target chip, there is no way to erase, read or reprogram the chip in-circuit. We recommend not to use this feature during the development process.
Operating FLASHER in stand-alone mode
After download the target program and all settings are stored in FLASHER 5s on board FLASH memory and remain valid until new settings or data are sent to FLASHER. Any number of microcontrollers may now be programmed by FLASHER (one at a time) without the need of a host PC, by simply pressing the start button. FLASHER will use the settings which have been made in the PC-program. This includes the selection of target address range as well as any options. Whether the target CPU will be erased before programming depends on setting of option "Automatic clear before program". Progress and result of the operation is indicated by FLASHERs LEDs:
| Status of LED | Meaning |
| GREEN, flashing | Erasing / Programming / Verifying in progress |
| GREEN | Programming operation successful |
| RED | Programming operation failed |
Remote control of FLASHER 5
FLASHER 5 can be remote controlled by automated testers without the need of a connection to PC and Flashers PC program. Therefore FLASHER 5 is equipped with additional hardware control functions, which are connected to the SUBD9 male connector, normally used as RS232 interface to PC. The following diagram shows the internal remote control circuitry of FLASHER:
ASCII command interface
FLASHER with firmware version 1.84 or above can be controlled without the need of Flashers PC program. FLASHER firmware contains an ASCII command interface function. Any application may send commands via RS232 to Flasher to start programming of target CPU.
A manual which describes ASCII command interface can be downloaded from our download page.
Using the serial link to program in circuit
FLASHER can be used for in circuit programming of supported CPUs, which incorporate built in firmware for serial update of user flash.
The target system has to be designed to support this mode of operation. Refer to target specific connection diagrams or Users manuals
of your target CPU. 
Serial programming, technical details
Serial programming uses a clock synchronous interface. 8 bits of data (1 byte) is transferred at a time.
The commands which are used are described in the Renesas manual. In general, the sequence is as follows:
FLASHER resets the target system by pulling the /Reset line low for a short period of time (1-2 ms)
FLASHER waits for app. 500 ms (tRd)) in order to allow the target system to recover from reset.
FLASHER checks the BUSY line. If it is active (high level) FLASHER stops with error message
40: Target chip says "BUSY" because it can not communicate with the target system
FLASHER outputs one clock (clock changes from high to low and back). BUSY should now be active (high).
If it is not active, FLASHER stops with error message 41: Target chip: Busy does not react
FLASHER outputs 7 more data bits ( 7 clock cycles) and wait for BUSY to go low.
More data bytes are output (or read) as explained under d)/e)
 |
trd: typ 500ms |
Serial target interface circuitry
Error messages
error messages are documented in the Flasher online help (since version 1.74a).
Trouble shooting
Proper operation of FLASHER in serial mode depends on your target system. If you have any
trouble operating FLASHER in serial mode, please:
- Check your target hardware
- Check the connecting cable
- Use an oscilloscope to check the state of the signals on the target connector,
especially to check if the target CPU is RESET properly and the target CPUs BUSY signal works properly.
Known limitations and problems
Serial mode
- Older versions of the Renesas M16C/62 boot loader sometimes do not start after RESET. If you experience problems in communicating with the target system, power down the target system, power it up and try again.
Support
For support questions please send an email to このメールアドレスはスパムボットから保護されています。閲覧するにはJavaScriptを有効にする必要があります。 .
Flasher 5 Target system interface
Target system interface for Flasher 5
The clocked synchronous interface from FLASHER to target system has to be connected to the 10 pin dual in line pin connector, (pin 1 is on the top left, marked at the connector) as shown in the diagram.
| Target interface to M16C62/M16C80/M32C (M30624/M30625/M30800) | |||
|---|---|---|---|
| Pin nr. | Signal | Function | Specification/remarks. |
| 1 | VCCS | Positive supply voltage of target | Input 3.0 .. 5.5V to supply the interface |
| 2 | BUSY | Target CPU Busy signal output. | FLASHER Input with Pull-Up to internal 3.3V |
| 3 | SCLK | Target CPU Serial clock (input) | FLASHER Output, CMOS driver via 220 Ohms |
| 4 | RxD | Target CPU Serial data input | FLASHER Output, CMOS driver via 220 Ohms |
| 5 | CE | Chip enable signal of target CPU | FLASHER Input/Output |
| 6 | EPM | EPM signal of target CPU | FLASHER Input/Output |
| 7 | GND | Common signal ground | --- |
| 8 | RESET | RESET signal of target system | FLASHER Output, CMOS driver via 220 Ohms |
| 9 | CNVss | Target CPU CNVss signal | FLASHER analog Output |
| 10 | TxD | Target CPU Serial data output | FLASHER Input/Output |
The pull-up resistors of outputs are connected to VCCS.
If RESET of the target system is driven by a reset circuitry with active high driver, RESET output of FLASHER must not be connected directly to CPU reset of target. For M16C/62 or M16C/80 targets you do not have to connect RESET to FLASHER; you can always manually reset your target system after connecting FLASHER.
| Target system interface for M16C/62, M16C/80, M32C | Target system interface for M30201 |
|---|---|
 |
 |
| Target system interface for M16C26, M16C28 | Target system interface for M16C26A, M16C29 |
 |
 |
| Target system interface for M30220 | Target system interface for M37906F8 |
 |
 |
| Target system interface for M38xx groups | Target system interface for M3803H group |
 |
 |
| Target system interface for M38507 groups | Target system interface for M38C2 groups |
 |
 |
| Target system interface for 7542 groups | Target system interface for R8C groups |
 |
 |