Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This document contains a detailed User Guide that outlines the features of the FlashPro-ARM and GangPro-ARM programmers.

Disclaimer Chapter 1 Introduction Chapter 2 Features
2.1 General Features
2.2 Custom Features
2.2.1 Encrypted Image option
2.2.2 Script file
2.2.3 DLLs
Chapter 3 Getting Started
3.1 Driver Installation
3.2 Hardware Setup
3.3 Starting up FlashPro-ARM Programmer
3.4 FlashPro-ARM Programmer Selector
Chapter 4 Main Graphical User Interface
4.1 MCU Device Type
4.2 Code File Management
4.3 Flash Protection Bits
4.4 Power Device from Adapter
4.5 Target Device Action Result
4.6 Device Action Box
4.6.1 Auto Program
4.6.2 Verify Access
4.6.3 Erase Flash
4.6.4 Blank Check
4.6.5 Write Flash
4.6.6 Write SN/Model
4.6.7 Verify Flash
4.6.8 Read/Copy
4.7 Next Button
Chapter 5 Data Viewers
Chapter 6 Memory Option Dialog Screen
6.1 Memory Erase, Write, and Verify
6.2 Read
6.3 Retain Data in Flash
6.4 Write Verification
Chapter 7 Adapter Options
7.1 Communication Speed
7.2 Reset Dialog Screen
7.2.1 Reset pulse duration
7.2.2 Final Target Device action
7.3 Preferences Dialog Screen
Chapter 8 Serialization
8.2 Serial Number Display Format
8.3 Serial Number Memory Format
8.3.1 HEX Memory Format
8.3.2 BCD Memory Format
8.3.3 ASCII Memory Format
8.4 Serial Number Output File
8.5 Model, Group, Revision
8.6 BarCode Scanner Setup
8.7 Device Serialization box
8.8 Serialization Report Dialog Screen
8.9 Serial Number Input File
Chapter 9 Check Sum Options
9.1 Check Sum types
9.1.1 Arithmetic Sum (8b/16b)
9.1.2 Arithmetic Sum (8b/32b)
9.1.3 Arithmetic Sum (16b/16b)
9.1.4 Arithmetic Sum (16b/32b)
9.1.5 CRC16 (Poly 0x11201) - (8b/16b) (Named as CRCCCITT) and CRC16 defined polynomial - (8b/16b)
9.1.6 CRC32 (Poly 0x04C11DB7) - (8b/32b) (Named as IEEE 802-3) and CRC32 defined polynomial - (8b/32b)
Chapter 10 Script File
10.1 Script button
10.2 Script file option
10.2.1 Script Limitations
10.2.2 Command Syntax
10.2.3 Instructions
Chapter 11 Setup and Image Load and Save
11.1 Load and Save Setup
11.2 Load and Save Image
11.3 Commands combined with the executable file
Chapter 12 Target Connection
Table of Figures
Figure 3.1: New Hardware Wizard, step 1. Select "Yes, this time only."
Figure 3.2: New Hardware Wizard, step 2. Select "Install the software automatically.
Figure 3.3: New Hardware Wizard, step 3. Ignore this warning.
Figure 3.4: New Hardware Wizard, step 4. USB-FPA-BOOT driver installed.
Figure 3.5: New Hardware Wizard, step5. USB-FPA (Elprotronic) driver installed.
Figure 3.6: Hardware setup, cable connections.
Figure 3.7: FPA selector. When one or more programmers are connected to the computer at once, the FPA selector allows the user to choose which programmer to operate.
Figure 4.1: Main Dialog Screen.
Figure 4.2: The MCU type can be selected here.
Figure 4.3: Select the Code file you wish to program to the MCU.
Figure 4.4: Code size exceeds Flash size.
Figure 4.5: Save code file.
Figure 4.6: The programmer will ask the user if they wish to program the debug register even if protection bits haven't been programmed successfully. This is useful in overcoming some processor bugs that prevent protection bits from being committed.
Figure 4.7: Memory Protection.
Figure 4.8: Power device.
Figure 4.9: Power-cycle required to begin verification.
Figure 4.10: Check boxes will indicate the statue of each operation during programming.
Figure 4.11: Actions that can be taken using the Programmer.
Figure 4.12: This text window shows text messages describing the actions being performed, and how long they take.
Figure 4.13: A summary of the entire programming procedure.
Figure 4.14: This message clarifies which segment of flash memory will be erased.
Figure 4.15: Flash memory contents as read from the MCU.

Page Tree
rootFlashPro-ARM & GangPro-ARM User Guide
startDepth1

Table of Contents

Figure 4.16: Contents of flash have been copied to a file and can be used as a new Code file.
Figure 4.17: The next button can take on multiple functions depending on which Device Action was used previously.
Figure 5.
1
: Code File Data. The selected option on the bottom ignores all bytes that have the value of 0xFF, which represents empty bytes.
Figure 5.2: Comparison of code and flash memory data from the target processor.
Figure 6.1: Control how memory will be accessed using this dialog window.
Figure 7.1: Use this drop-box to select the desired communication speed.
Figure 7.2: Use this dialog window to configure reset options.
Figure 7.3: Use this dialog window to configure your preferences.
Figure 8.1: If an MCU already contains serialization information at a specified location then a conflict window will appear giving the user the option to retain the old serial number, or program in a new one.
Figure 8.2: Serialization options can be selected here.
Figure 8.3: This window will appear when there is a conflict between memory allocated to code and the SN. To avoid this pop-up, select the option to "Remove code contents in the location where the serialization and model are defined" in Figure 8.2.
Figure 8.4: Seen in the main dialog window, this serialization status box will display the current device's serial number and the next serial number to be programmed.
Figure 8.5: Serialization report gives a summary of all the serial numbers programmed using the selected file.
Figure 8.6: Serial numbers read from a file.
Figure 9.1: Check Sum information compared between the file and MCU memory.
Figure 9.2: Check Sum Options.
Figure 9.3: Check Sum Report.
Figure 9.4: Check Sum Type.
Figure 9.5: Check Sum Initial Value.
Figure 9.6: Check Sum Inverted Option.
Figure 10.1: Script file not defined.
Figure 10.2: Script file active.
Figure 11.1: Image Options.
Figure 11.2: PC Hardware fingerprint.
Figure 11.3: Image Options with security settings enabled and the password lock and unlock options specified.
Figure 12.1: Adapter.