Flasher ST7 Supported Microcontrollers
Supported Microcontrollers
Group | MCU | Memory Size bytes | Package | |
---|---|---|---|---|
Flash Memory | RAM | |||
ST72F26x | ST72F260G1 | 4 KB | 256 Bytes | SO28/SDIP32 |
ST72F262G1 | 4 KB | 256 Bytes | SO28/SDIP32 | |
ST72F262G2 | 8 KB | 256 Bytes | SO28/SDIP32 | |
ST72F264G2 | 8 KB | 256 Bytes | SO28/SDIP32 | |
ST72F321 | ST72F321AR6 | 32 KB | 1 KB | 64-pin (TQFP64 10x10) (0.5 mm pitch) |
ST72F321AR7 | 48 KB | 1536 Bytes | 64-pin (TQFP64 10x10) (0.5 mm pitch) | |
ST72F321AR9 | 60 KB | 2 KB | 64-pin (TQFP64 10x10) (0.5 mm pitch) | |
ST72F321J7 | 48 KB | 1536 Bytes | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST72F321J9 | 60 KB | 2 KB | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST72F321R6 | 32 KB | 1 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F321R7 | 48 KB | 1536 Bytes | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F321R9 | 60 KB | 2 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F324 | ST72F324J2 | 8 KB | 384 Bytes | 42-pin (SDIP42 600mil) |
ST72F324J4 | 16 KB | 512 Bytes | 42-pin (SDIP42 600mil) | |
ST72F324J6 | 32 KB | 1 KB | 42-pin (SDIP42 600mil) | |
ST72F324K2 | 8 KB | 384 Bytes | 32-pin (SDIP32 200mil) | |
ST72F324K4 | 16 KB | 512 Bytes | 32-pin (SDIP32 200mil) | |
ST72F324K6 | 32 KB | 1 KB | 32-pin (SDIP32 200mil) | |
ST72F324B | ST72F324BJ4B | 16 KB | 512 Bytes | 42-pin SDIP |
ST72F324BJ4T | 16 KB | 512 Bytes | 44-pin (TQFP44 10x10) | |
ST72F324BJ6T | 32 KB | 1 KB | 44-pin (TQFP44 10x10) | |
ST72F324BK4B | 16 KB | 512 Bytes | 32-pin SDIP | |
ST72F324BK4T | 16 KB | 512 Bytes | 32-pin (TQFP32 7x7) | |
ST72F324BK6T | 32 KB | 1 KB | 32-pin (TQFP32 7x7) | |
ST72F324L | ST72F324LJ2T | 8 KB | 384 Bytes | 44-pin TQFP (0.8mm pitch) |
ST72F324LJ4T | 16 KB | 512 Bytes | 44-pin TQFP (0.8mm pitch) | |
ST72F324LJ6T | 32 KB | 1 KB | 44-pin TQFP (0.8mm pitch) | |
ST72F324LK2T | 8 KB | 384 Bytes | 32-pin TQFP (0.8mm pitch) | |
ST72F324LK4T | 16 KB | 512 Bytes | 32-pin TQFP (0.8mm pitch) | |
ST72F324LK6B | 32 KB | 1 KB | 32-pin (SDIP32 400mil) | |
ST72F324LK6T | 32 KB | 1 KB | 32-pin TQFP (0.8mm pitch) | |
ST72F325 | ST72F325AR6T | 32 KB | 1 KB | 64-pin (LQFP64 10x10) |
ST72F325AR7T | 48 KB | 1536 Bytes | 64-pin (LQFP64 10x10) | |
ST72F325AR9T | 60 KB | 2 KB | 64-pin (LQFP64 10x10) | |
ST72F325C6T | 32 KB | 1 KB | 48-pin (LQFP48 7x7) | |
ST72F325C7T | 48 KB | 1536 Bytes | 48-pin (LQFP48 7x7) | |
ST72F325C9T | 60 KB | 2 KB | 48-pin (LQFP48 7x7) | |
ST72F325J4T | 16 KB | 512 Bytes | 44-pin (LQFP44 10x10) | |
ST72F325J6B | 32 KB | 1 KB | 42-pin (SDIP42) | |
ST72F325J6T | 32 KB | 1 KB | 44-pin (LQFP44 10x10) | |
ST72F325J7T | 48 KB | 1536 Bytes | 44-pin (LQFP44 10x10) | |
ST72F325J9T | 60 KB | 2 KB | 44-pin (LQFP44 10x10) | |
ST72F325K4B | 16 KB | 512 Bytes | 32-pin (SDIP32) | |
ST72F325K4T | 16 KB | 512 Bytes | 32-pin (LQFP32 7x7) | |
ST72F325K6B | 32 KB | 1 KB | 32-pin (SDIP32) | |
ST72F325K6T | 32 KB | 1 KB | 32-pin (LQFP32 7x7) | |
ST72F325R9T | 60 KB | 2 KB | 64-pin (LQFP64 14x14) | |
ST72F325S4T | 16 KB | 512 Bytes | 48-pin (LQFP48 7x7) | |
ST72F325S6T | 32 KB | 1 KB | 48-pin (LQFP48 7x7) | |
ST72F32A | ST72F32AJ2T | 8 KB | 384 Bytes | 44-pin (TQFP44 10x10) |
ST72F32AK2B | 8 KB | 384 Bytes | 32-pin SDIP | |
ST72F32AK2T | 8 KB | 384 Bytes | 32-pin (TQFP32 7x7) | |
ST72F34x | ST72F340K4T6 | 16 KB | 1 KB | TQFP32 |
ST72F340S4T6 | 16 KB | 1 KB | TQFP44 | |
ST72F344K4T6 | 16 KB | 1 KB | TQFP32 | |
ST72F344S4T6 | 16 KB | 1 KB | TQFP44 | |
ST72F345C4T6 | 16 KB | 1 KB | LQFP48 | |
ST72F521 | ST72F521AR6 | 32 KB | 1 KB | 64-pin (TQFP64 10x10) (0.5 mm pitch) |
ST72F521AR9 | 60 KB | 2 KB | 64-pin (TQFP64 10x10) (0.5 mm pitch) | |
ST72F521M9 | 60 KB | 2 KB | 80-pin (TQFP80 14x14) (0.65 mm pitch) | |
ST72F521R6 | 32 KB | 1 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F521R9 | 60 KB | 2 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F561 | ST72F561J4 | 16 KB | 512 Bytes | 44-pin (TQFP44 10x10) (0.8 mm pitch) |
ST72F561J6 | 32 KB | 1 KB | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST72F561J7 | 48 KB | 1536 Bytes | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST72F561K4 | 16 KB | 512 Bytes | 32-pin (TQFP32 7x7) (0.8 mm pitch) | |
ST72F561K6 | 32 KB | 1 KB | 32-pin (TQFP32 7x7) (0.8 mm pitch) | |
ST72F561K9 | 60 KB | 2 KB | 32-pin (TQFP32 7x7) (0.8 mm pitch) | |
ST72F561R6 | 32 KB | 1 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F561R7 | 48 KB | 1536 Bytes | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST72F561R9 | 60 KB | 2 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST7DALI | STDALI | 8448 Bytes | 384 Bytes | SO20 (300mil) |
ST7FLCD1 | ST7FLCD1 | 60 KB | 2 KB | SO28 |
ST7FMC1 | ST7FMC1K2B6 | 8 KB | 384 Bytes | 32 Pin SDIP |
ST7FMC1K2T3 | 8 KB | 384 Bytes | 32-pin TQFP (0.8 mm pitch) | |
ST7FMC1K2T6 | 8 KB | 384 Bytes | 32-pin TQFP (0.8 mm pitch) | |
ST7FMC1K2TC | 8 KB | 384 Bytes | 32-pin TQFP (0.8 mm pitch) | |
ST7FMC1K4T6 | 16 KB | 768 Bytes | 32-pin TQFP (0.8 mm pitch) | |
ST7FMC2 | ST7FMC2M9T6 | 60 KB | 1536 Bytes | 80-pin TQFP (0.65 mm pitch) |
ST7FMC2N6B6 | 32 KB | 1 KB | 56-pin SDIP | |
ST7FMC2R6T6 | 32 KB | 1 KB | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST7FMC2R7T6 | 48 KB | 1536 Bytes | 64-pin (TQFP64 14x14) (0.8 mm pitch) | |
ST7FMC2S4T6 | 16 KB | 768 Bytes | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST7FMC2S4TC | 16 KB | 768 Bytes | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST7FMC2S6T6 | 32 KB | 1 KB | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST7FMC2S6TC | 32 KB | 1 KB | 44-pin (TQFP44 10x10) (0.8 mm pitch) | |
ST7FOX | ST7FOXA0B6 | 2 KB | 128 Bytes | DIP8 |
ST7FOXA0M6 | 2 KB | 128 Bytes | SO8 (150mil) | |
ST7LITE0 | ST7Lite02 | 1536 Bytes | 128 Bytes | SO16 (150mil), DIP16 |
ST7Lite05 | 1536 Bytes | 128 Bytes | SO16 (150mil), DIP16 | |
ST7Lite09 | 1664 Bytes | 128 Bytes | SO16 (150mil), DIP16 | |
ST7LITE1 | ST7Lite10 | 4 KB | 256 Bytes | SO20 (300mil), SDIP20 |
ST7Lite15 | 4 KB | 256 Bytes | SO20 (300mil), SDIP20 | |
ST7Lite19 | 4224 Bytes | 256 Bytes | SO20 (300mil), SDIP20 | |
ST7LITE1xB | ST7Lit10B | 2 KB | 256 Bytes | DIP16, SO-16W |
ST7Lit10B | 2 KB | 256 Bytes | DIP20, SO-20 | |
ST7Lit15B | 2 KB | 256 Bytes | DIP16, SO-16W | |
ST7Lit15B | 2 KB | 256 Bytes | DIP20, SO-20 | |
ST7Lit19B | 2 KB | 256 Bytes | DIP16, SO-16W | |
ST7Lit19B | 4 KB | 256 Bytes | DIP20 | |
ST7Lit19B | 2 KB | 256 Bytes | DIP20, SO-20 | |
ST7LITE2 | ST7Lite20 | 8 KB | 384 Bytes | SO20 (300mil), SDIP20 |
ST7Lite25 | 8 KB | 384 Bytes | SO20 (300mil), SDIP20 | |
ST7Lite29 | 8448 Bytes | 384 Bytes | SO20 (300mil), SDIP20 | |
ST7LITE3 | ST7FLite30 | 8 KB | 384 Bytes | SO20 (300mil), SDIP20 |
ST7FLite35 | 8 KB | 384 Bytes | SO20 (300mil), SDIP20 | |
ST7FLite39 | 8448 Bytes | 384 Bytes | SO20 (300mil), SDIP20 | |
ST7SUPERLITE | ST7LiteS2 | 1 KB | 128 Bytes | SO16 (150mil), DIP16 |
ST7LiteS5 | 1 KB | 128 Bytes | SO16 (150mil), DIP16 | |
ST7ULTRALITE | ST7LiteU05 | 2 KB | 128 Bytes | SO8 (150mil), DIP8 |
ST7LiteU09 | 2176 Bytes | 128 Bytes | SO8 (150mil), DIP8 | |
ST7LiteUS2 | 1 KB | 128 Bytes | SO8 (150mil), DIP8 | |
ST7LiteUS5 | 1 KB | 128 Bytes | SO8 (150mil), DIP8 |
Working with Flasher ARM
Working with Flasher ARM
Flasher ARM can be used for programming flash targets with the J-Flash software or stand-alone.
Setting up Flasher ARM for first use
In order to use Flasher ARM for the first time you need to install the Flasher ARM related software and documentation pack which, among others, includes the J-Flash software and connect Flasher ARM to the host PC via USB.
Connecting the target system
Power-on sequence
In general, Flasher ARM should be powered on before connecting it with the target device. That means you should first connect Flasher ARM with the host system via USB / RS232 and then connect Flasher ARM with the target device via JTAG. Power-on the device after you connected Flasher ARM to it.
If you use Flasher ARM in stand-alone mode, just power-on Flasher ARM via external power supply
Verifying target device connection with J-Link.exe
If the USB driver is working properly and your Flasher ARM is connected with the host system, you may connect Flasher ARM to your target hardware. Then start the J-Link command line tool JLink.exe, which should now display the normal Flasher ARM related information and in addition to that it should report that it found a JTAG target and the target’s core ID. The screenshot below shows the output of JLink.exe. As can be seen, it reports a Flasher ARM with 3 JTAG devices connected.
Verifying target device connection with J-Flash
Another way to verify the target connection is to connect to the target using J-Flash. To connect to the target with J-Flash you have to choose an appropriate project file for the target first. After opening the project file choose Target --> Connect from the menu to connect to the target. If everything works as expected, follow the instructions in 2.2 to download a program to Flasher ARM with J-Flash.
Using Flasher ARM with PC Software "J-Flash"
J-Flash is a software running on Windows 2000, Windows XP, Windows 2003 or Windows Vista systems and enables you to program your flash EEPROM devices via the JTAG connector on your target system.
J-Flash works with any ARM7/9/Cortex-M3 system and supports all common external flashes, as well as the programming of internal flash of ARM microcontrollers. It allows you to erase, fill, program, blank check, upload flash content, and view memory functions of the software with your flash devices.
Features
- Works with any ARM7/ARM9/Cortex-M3 chip
- ARM microcontrollers (internal flash) supported
- Most external flash chips can be programmed
- High-speed programming: up to 200 Kbytes/second (depends on flash device)
- Very high-speed blank check: Approximately 16 Mbytes/sec (depends on target)
- Smart read-back: Only non-blank portions of flash transferred and saved
- Easy to use, comes with projects for standard eval boards.
Setting up Flasher ARM for stand-alone mode
In order to setting up Flasher ARM for the "stand-alone mode" it has to be in "J-Link mode". When the correct connection of Flasher ARM to the host PC is veryfied start the J-Flash software. For more information about the general setup sequence to prepare Flasher ARM for stand-alone mode, please refer to the Flasher ARM User's Guide (UM08007)
LED status indicators
Progress and result of an operation is indicated by Flasher ARM.s LEDs:
Status of LED | Meaning |
GREEN, high frequency flashing (10 kHz) | Enumerating Flasher ARM. |
GREEN, slow blinking (1 kHz) | Programming. |
GREEN | Programming operation successful / Ready. |
RED | Programming operation failed. |
Using the serial link to program in circuit
Flasher ARM 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.
Remote control of Flasher ARM
Flasher ARM can be remote controlled by automated testers without the need of a connection to PC and Flasher ARM™s PC program. Therefore Flasher ARM is equipped with additional hardware control functions, which are connected to the SUBD9 male connector, normally used as RS232 interface to PC. The following diagrams show the internal remote control circuitry of Flasher ARM:
Pin No. | Function | Description |
1 | START | A positive pulse of any voltage between 5V and 30V with duration of min. 30 ms starts itAutole function (Clear / Program / Verify) on falling edge of pulse. Whether Clear is executed depends on Options | Filling & misc. | Automatic clear before program. |
4 | BUSY | As soon as 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 RX More
Flasher RX - Flash Programmer for Renesas RX cores
Flasher RX is a programming tool for Renesas RX600 series microcontrollers with on-chip or external flash memory and Renesas RX core. Flasher RX is designed for programming flash targets with the J-Flash software or stand-alone. In addition to that Flasher RX has all of the J-Link RX functionality. Flasher RX connects via Ethernet, USB or via RS232 interface to a PC, running Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista or Windows 7.
Flasher RX itself has a built-in 20-pin JTAG connector but is shipped with an 14-pin adapter for Renesas RX devices.
Features
- Stand-alone JTAG programmer (Once set up, Flasher can be controlled without the use of PC program)
- Support for Renesas RX600 series CPUs (RX610, RX621, RX62N, RX62T)
- Supports internal and external flash devices
- 64 MB memory for storage of target program
- Serial in target programming supported
- Data files can be updated via Ethernet/USB using J-Flash or via the mass storage functionality of Flasher RX
- Target interface: JTAG
- No power supply required, powered through USB
- Can be used as J-Link (JTAG emulator) with a download speed (into RAM) of up to 720 Kbytes/second
- Programming speed between 30-300 Kbytes/second depending on target hardware
Available software
In order to setup Flasher RX for stand-alone operation, you need the J-Flash software from the J-Link software and documentation package. The J-Link software and documentation package is available for download on our website: Software and documentation package download
Supported Devices
Currently, programming of the internal flash memory of the following devices is supported by Flasher RX:
Device | CPU core | Flash size [kByte] |
---|---|---|
R5F56104 | RX610 | 768 |
R5F56106 | RX610 | 1024 |
R5F56107 | RX610 | 1536 |
R5F56108 | RX610 | 2048 |
R5F56216 | RX621 | 256 |
R5F56217 | RX621 | 384 |
R5F56218 | RX621 | 512 |
R5F562N7 | RX62N | 384 |
R5F562N8 | RX62N | 512 |
R5F562T6 | RX62T | 64 |
R5F562T7 | RX62T | 128 |
R5F562TA | RX62T | 256 |
Support for RX630 devices is comming soon.
Specifications
General | |
---|---|
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 Microsoft Windows 7 Microsoft Windows 7 x64 |
Operating Temperature | + 5 °C ... + 60 °C |
Storage Temperature | - 20 °C ... + 65 °C |
Relative Humidity (non-condensing) | < 90% rH |
Mechanical | |
Size (without cables) | 121mm x 66mmx 30mm |
Weight (without cables) | 119g |
Available interfaces | |
USB Host Interface | USB 2.0, full speed |
Ethernet Host Interface | 10/100 MBit |
RS232 Host Interface | RS232 9-pin |
Target Interface | JTAG 20-pin (shipped with 14-pin adapter for Renesas RX) |
JTAG Interface, Electrical | |
Power Supply | USB powered, 100mA for Flasher RX. 500 mA if target is powered by Flasher RX |
Target interface voltage (VIF) | 1.2 ... 5V |
Target supply voltage | 4.5V ... 5V (on the 14-pin adapter the target supply voltage can be switched between 3.3V and 5V) |
Target supply current | max. 400mA |
Reset Type | Open drain. Can be pulled low or tristated |
Reset low level output voltage (VOL) | VOL <= 10% of VIF |
For the whole target voltage range (1.8V <= VIF <= 5V) | |
LOW level input voltage (VIL) | VIL <= 40% of VIF |
HIGH level input voltage (VIH) | VIH >= 60% of VIF |
For 1.8V <= VIF <= 3.6V | |
LOW level output voltage (VOL) with a load of 10 kOhm | VOL <= 10% of VIF |
HIGH level output voltage (VOH) with a load of 10 kOhm | VOH >= 90% of VIF |
For 3.6 <= VIF <= 5V | |
LOW level output voltage (VOL) with a load of 10 kOhm | VOL <= 20% of VIF |
HIGH level output voltage (VOH) with a load of 10 kOhm | VOH >= 80% of VIF |
JTAG Interface, Timing | |
Max. JTAG speed | up to 12MHz |
Data input rise time (Trdi) | Trdi <= 20ns |
Data input fall time (Tfdi) | Tfdi <= 20ns |
Data output rise time (Trdo) | Trdo <= 10ns |
Data output fall time (Tfdo) | Tfdo <= 10ns |
Clock rise time (Trc) | Trc <= 10ns |
Clock fall time (Tfc) | Tfc <= 10ns |
JTAG interface connection (14-pin)
Pin | Signal | Type | Description |
---|---|---|---|
1 | 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. |
3 | TRSTn | Output | JTAG Reset. Output from Flasher RX 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.
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] |
---|---|---|---|---|---|
R5F56108 | 2048 | 9.523 | 11.915 | 3.890 | 25.585 |
Flasher PPC More
Flasher PPC - Flash Programmer for PowerPC cores
Flasher PPC is a programming tool for PowerPC based microcontrollers with on-chip or external flash memory. Flasher PPC is designed for programming flash targets with the J-Flash software or stand-alone. It connects via Ethernet, USB or RS232 interface to a PC, running Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista or Windows 7.
Flasher PPC itself has a built-in 20-pin JTAG connector but is shipped with an 14-pin adapter for PowerPC devices.
Features
- Stand-alone JTAG programmer (Once set up, Flasher can be controlled without the use of PC program)
- Support for PowerPC cores
- Supports programming of internal and external flash memory
- 64 MB memory for storage of target program
- Host interfaces: Ethernet, USB, RS232
- Serial in target programming supported
- Data files can be updated via Ethernet/USB using J-Flash, via RS232 or via the mass storage functionality of Flasher PPC
- Target interface: JTAG
- No power supply required, powered through USB
- Programming speed up to 138 Kbytes/second depending on target hardware
Supported Devices
Currently, programming of the internal flash memory of the following devices is supported by Flasher PPC:
Device | CPU core | Flash size [kBytes] |
---|---|---|
ST SPC560B40 | e200z0 (PowerPC) | 320 (256 KB Code flash + 64 KB Data flash) |
ST SPC560B44 | e200z0 (PowerPC) | 448 (384 KB Code flash + 64 KB Data flash) |
ST SPC560B50 | e200z0 (PowerPC) | 576 (512 KB Code flash + 64 KB Data flash) |
ST SPC560C40 | e200z0 (PowerPC) | 320 (256 KB Code flash + 64 KB Data flash) |
ST SPC560C44 | e200z0 (PowerPC) | 448 (384 KB Code flash + 64 KB Data flash) |
ST SPC560C50 | e200z0 (PowerPC) | 576 (512 KB Code flash + 64 KB Data flash) |
ST SPC560P40 | e200z0 (PowerPC) | 320 (256 KB Code flash + 64 KB Data flash) |
ST SPC560P44 | e200z0 (PowerPC) | 448 (384 KB Code flash + 64 KB Data flash) |
ST SPC560P50 | e200z0 (PowerPC) | 576 (512 KB Code flash + 64 KB Data flash) |
If your device is not listed here, please do not hesitate to get in touch with us: このメールアドレスはスパムボットから保護されています。閲覧するにはJavaScriptを有効にする必要があります。
Specifications
General | |
---|---|
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 Microsoft Windows 7 Microsoft Windows 7 x64 |
Operating Temperature | + 5 °C ... + 60 °C |
Storage Temperature | - 20 °C ... + 65 °C |
Relative Humidity (non-condensing) | < 90% rH |
Mechanical | |
Size (without cables) | 121mm x 66mmx 30mm |
Weight (without cables) | 119g |
Available interfaces | |
USB Host Interface | USB 2.0, full speed |
Ethernet Host Interface | 10/100 MBit |
RS232 Host Interface | RS232 9-pin |
Target Interface | JTAG 20-pin (shipped with 14-pin adapter for Renesas PPC) |
JTAG Interface, Electrical | |
Power Supply | USB powered, 100mA for Flasher PPC. 500 mA if target is powered by Flasher PPC |
Target interface voltage (VIF) | 1.2 ... 5V |
Target supply voltage | 4.5V ... 5V (on the 14-pin adapter the target supply voltage can be switched between 3.3V and 5V) |
Target supply current | max. 400mA |
Reset Type | Open drain. Can be pulled low or tristated |
Reset low level output voltage (VOL) | VOL <= 10% of VIF |
For the whole target voltage range (1.8V <= VIF <= 5V) | |
LOW level input voltage (VIL) | VIL <= 40% of VIF |
HIGH level input voltage (VIH) | VIH >= 60% of VIF |
For 1.8V <= VIF <= 3.6V | |
LOW level output voltage (VOL) with a load of 10 kOhm | VOL <= 10% of VIF |
HIGH level output voltage (VOH) with a load of 10 kOhm | VOH >= 90% of VIF |
For 3.6 <= VIF <= 5V | |
LOW level output voltage (VOL) with a load of 10 kOhm | VOL <= 20% of VIF |
HIGH level output voltage (VOH) with a load of 10 kOhm | VOH >= 80% of VIF |
JTAG Interface, Timing | |
Max. JTAG speed | up to 12MHz |
Data input rise time (Trdi) | Trdi <= 20ns |
Data input fall time (Tfdi) | Tfdi <= 20ns |
Data output rise time (Trdo) | Trdo <= 10ns |
Data output fall time (Tfdo) | Tfdo <= 10ns |
Clock rise time (Trc) | Trc <= 10ns |
Clock fall time (Tfc) | Tfc <= 10ns |
JTAG interface connection (14-pin)
Pin | Signal | Type | Description |
---|---|---|---|
1 | TDI | 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. |
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". |
10 | 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. |
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. |
14 | JCOMP | 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). |
Notes:
- 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, 4, 6, 12 are GND pins connected to GND in Flasher PPC. They should also be connected to GND in the target system.
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] |
---|---|---|---|---|---|
ST SPC560B50 | 576 | 4.747 | 4.159 | 1.929 | 10.917 |
Flasher STM8 More
Flasher STM8 - Flash programmer for STM8 series of flash microcontrollers with on-chip flash
Features
- All STM8 devices can be programmed
- Integrated optical isolation between host and target system
- Standard 4-pin SWIM connector
- USB 2.0 interface
- Full duplex 100Mbit Ethernet interface
- Target voltage can be measured & monitored during program
- Fully plug and play compatible
- USB, Ethernet, RS232 and 4-pin ribbon cable included
- Windows PC software included
- Target power supply via pin 1 of the 4-pin interface (up to 300mA to target with overload protection)
Specifications
General | |
---|---|
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 Windows 7 Windows 7 x64 |
Electromagnetic compatibility (EMC) | EN 55022, EN 55024 |
Operating temperature | +5°C ... +60°C |
Storage temperature | -20°C ... +65 °C |
Relative humidity (non-condensing) | Max. 90% rH |
Size (without cables) | 121mm x 66mm x 30mm |
Weight (without cables) | 122g |
Mechanical | |
USB interface | USB 2.0, full speed |
Ethernet interface | 100Mbit, full duplex |
RS232 Host interface | RS232 9-pin |
Target interface | SWIM 4-pin connector |
SWIM interface, Electrical | |
Power supply | USB powered, 100mA for Flasher STM8. 500mA if target is powered by Flasher STM8. |
Target interface voltage (VIF) | 1.2V ... 5V |
Target supply voltage | 4.5V ... 5V (if powered with 5V on USB) |
Target supply current | Max. 300mA |
LOW level input voltage (VIL) | Max. 40% of VIF |
HIGH level input voltage (VIH) | Min. 60% of VIF |
Download speed
Flasher STM8 has been designed to allow downloading to the target as fast as the target can receive and program flash. The table below shows the measured download speed for standalone programming and for programming via PC driven software. The following testing environment has been used:
- PC with 2.53 GHz Core2Duo, running WinXP
- USB 2.0 port
- USB 2.0 hub
- STM8S208MBT6B
Operation | Standalone mode | PC mode |
---|---|---|
Program (128kB) | 8.5s (15kB/s) | 8.5s (15kB/s) |
Program and verify (128kB) | 11.3s | 11.3s |