Page 5
Systein Warranty Information Systein warrants that this product will be free from defects in materials and workmanship for a period of one (1) year from the date of shipment. If any such product proves defective during this warranty period, Systein, at its option, either will repair the defective product without charge for parts and labor, or will provide a replacement in exchange for the defective product.
FlashRunner Cube User’s Manual 1. FR CUBE-At a Glance Overview Congratulations for purchasing a FR CUBE In-System Programmer. The FR CUBE Series of In-System Programmers are a breakthrough in the Programming industry. The programmers support a large number of devices (microcontrollers, memories, CPLDs and other programmable devices) from various manufacturers and have a compact size for easy ATE/ fixture integration.
FR CUBE-At a Glance Features Support of microcontrollers, serial and parallel memories, CPLDs and other programmable devices High-speed, parallel programming Compact size (fixture friendly) Standalone operations or host controlled Designed for easy ATE interfacing Robust and reliable Support of several programming interfaces (JTAG, BDM, SPI, I UART, etc.) Large built-in internal memory for projects, images, etc.
FlashRunner Cube User’s Manual Model Comparison The following table summarizes the main features of the various FR CUBE family models. FR CUBE Model Comparison Feature FR CUBE GP02 FR CUBE GP04 FR CUBE GP08 General Features Programming Sites Power Supply 12-25V 12-25V 12-25V...
FR CUBE-At a Glance Package Checklist The FR CUBE package includes the following items: FR CUBE unit. 15V power supply. Serial and USB cables. FR CUBE test board. 48-way, female wire-wrap DIN41612 connector. Software CD. Connectors Overview FR CUBE has several connectors for interfacing to a host PC, to an Automatic Test Equipment (ATE), and to the target system(s) to be programmed.
FlashRunner Cube User’s Manual For details and pinout of the various connectors, see the “Connectors” chapter on page 59. LEDs The LEDs on the top cover of the instrument, from top to bottom, indicate: POWER: the instrument is turned on. STATUS: indicates system warnings.
FR CUBE-At a Glance Programming Drivers and Licenses FR CUBE comes with preinstalled programming drivers (algorithms) that support common microcontrollers and memories. When you purchase a new programming driver, you are supplied with a new driver file (.wnd) and an updated license file (.wnl). The license file enables the use of all of your purchased drivers on your specific FR CUBE unit.
FlashRunner Cube User’s Manual 2. Getting Started Guided Tutorial The following tutorial will guide you through the steps required to set up your FR CUBE programmer and create your first programming project. Install Software Insert the Setup CD into your PC and install the FR CUBE software.
Getting Started Create a New Project Select File > New Project, give a name to your programming project, and then follow the Project Creation Wizard steps. Create a New Project, Step 1 of 3 In the first Wizard step, specify the target device, by clicking the “Edit”...
FlashRunner Cube User’s Manual In the Output File section, specify the output filename by clicking the “...” button. Use the “Add” button to compose the data that will compose the Image file. Use the “...” button to specify the name of the Image file.
Page 20
Getting Started The number of tabs displayed in this window depends on the selected target device; however, three tabs (“Target I/O”, “Target Power Supply” and “Communication”) are always present and will be briefly discussed below. The first tab is “Target I/O”. The “Device I/O voltage” setting specifies the voltage of the ISP lines.
Page 21
FlashRunner Cube User’s Manual If you decide to power the target board through the FR CUBE power supply line (SxPPS), specify in the “Target Power Supply” tab the electrical and timing parameters of the target power supply line. FR CUBE is able to power the target board through a dedicated programmable power supply output line per site.
Page 22
Getting Started The content of the “Communication” tab depends on the selected target device. It allows you to select the communication protocol that will be used for programming (some target devices may provide more than one communication protocol) and its related settings, usually the communication speed and other parameters.
FlashRunner Cube User’s Manual Create a New Project, Step 3 of 3 In this step you select which programming operation to perform on the target. Click “Finish” to end the Wizard. At this point, a FR CUBE Programming Project will be created in the \Projects directory, relative to the Project Generator application location.
Getting Started Configure your FR CUBE Instrument Choose Project > Select FR CUBE Model, and specify your FR CUBE model and communication settings with the PC. Currently, FR CUBE can be connected only through a serial port. FR CUBE communicates at 115,200 bps by default. LAN and USB connections will be supported soon through a free software upgrade.
Page 25
FlashRunner Cube User’s Manual Connect to Target Device Connect FR CUBE to your target system through the ISP connector(s). To view the connections for your selected target device, select Debug > Show ISP Connections. See the table on page 60 for more details http://smh-tech.com.cn sales@smh-tech.com.cn +86-15250087885...
Page 26
Getting Started Startup FR CUBE Connect FR CUBE to your PC through the provided serial cable. Finally, power up FR CUBE using the provided power supply. Program the Target Device Select Debug > Run Project. The Project file (.wnp) and Image file (.wni) will be automatically uploaded to FR CUBE and the project will be executed.
FlashRunner Cube User’s Manual Manual Project Editing The Project file created by the Project Wizard is located, by default, in the \Projects directory, relative to the Project Generator application location (this location can be changed by specifying a different “workspace” path: to do so, in the Project Generator, select Project >...
FlashRunner Cube User’s Manual 3. Commands Overview FR CUBE is a slave unit and is always awaiting for a new command incoming from the master (PC). When the programmer receives a SOF (Start Of Frame) character ( indicating the start of a new command, it loads all incoming characters in a buffer until the reception of the return character ( , ASCII code Maximum command length is 256 characters.
Commands Command Syntax A FR CUBE command begins with the SOF character ( ), followed by the command name, followed by zero or more command switches, and ends with the return character ( This is an example of a FR CUBE valid command: #status -o ping{\n} OK Answer An OK answer is composed of zero or more characters, followed by...
FlashRunner Cube User’s Manual FR CUBE Terminal Commands can be sent (and answers received) using any terminal application. For your convenience, the Project Generator application includes a Terminal window that will simplify the communication with the instrument. Just select Tools > FR CUBE Terminal to open the Terminal window.
Commands Command Reference The following pages list all of the FR CUBE commands, grouped by function, together with their syntax and usage examples. Data In/Out Commands Syntax #data –o set –c <direction> -t file –f <filename> #data –o set –c <direction> -t volatile Parameters <direction>...
FlashRunner Cube User’s Manual Execution Command Syntax #exec -o prj -f <project> -s <sites> Parameters The Project filename to execute. <project> A 8 bit value indicating the programming sites to be enabled. <sites> Description Executes the specified Project over the specified programming sites. In case of error, a 32 bit value is returned.
Commands Status Commands Syntax #status –o ping #status –o get –p err –v <site> –l <errlevel> Parameters to get programming site errors. Use to return system errors. <site> <errlevel> Description Get instrument status or error information. When retrieving error information, one or more error lines (depending on parameter) are returned.
Page 37
FlashRunner Cube User’s Manual Examples Pings the instrument to check if communication is OK: #status –o ping pong> Retrieves the last generated errors, on programming site 1, with different error levels: #status -o get -p err -v 1 -l 1 H50000023 >...
FlashRunner Cube User’s Manual Time Commands Syntax #time –o set –p date –d <date> #time –o set –p time –d <time> #time –o get –p date #time –o get –p time Parameters A date in the format <date> yyyy/mm/dd A time in the format <time>...
Commands Volatile Memory Commands Syntax #volatile –o write –s <site> -a <start address> - l <len> -d <data> #volatile –o read –s <site> -a <start address> - l <len> Parameters Programming site. to set specific site data, to set <site> the same data for all sites.
FlashRunner Cube User’s Manual 4. Standalone Mode Overview FR CUBE can work with no connection to a PC (standalone mode). In standalone mode, the instrument is controlled through a low-level connection interface. Signals Signals needed to control the instrument in standalone mode are located in the “Low-Level Interface”...
Standalone Mode The following diagram illustrates the timing for the Low-Level Interface signals. PRJ_SELx PRJ_SELx and START_ENAx lines are sampled at the START falling edge, and must remain stable until BUSYrising edge START_ENAx START BUSY OK/ERRx lines become valid at the BUSY falling edge OK/ERRx Previous state...
FlashRunner Cube User’s Manual Project Assignment Before working in standalone mode, you must associate PRJ_SELx lines to a Project filename to execute. To do so, in the FR CUBE Project Generator application select Project > Hardware Settings. In the window that will appear, associate PRJ_SEL values to project names by clicking the “Set Project”...
FlashRunner Cube User’s Manual 5. FR CUBE API Overview You can build your own PC software that interfaces to the instrument, by using the provided FR CUBE Application Programming Interface (API). The FR CUBE API consists of a series of functions, contained in the fr_comm DLL, which allow you to set up and control the programmer.
FR CUBE API The typical program flow for interfacing with FR CUBE is the following: 1. Open communication (FR_OpenCommPort()function) 2. Execute commands(FR_ExeCommand()function) 3. Transfer files to/from the instrument’s internal memory (FR_SendFile()andFR_ReceiveFile()functions) 4. Close communication(FR_CloseCommPort()function) Function Reference API functions are listed and explained alphabetically in the following pages. http://smh-tech.com.cn sales@smh-tech.com.cn +86-15250087885...
FlashRunner Cube User’s Manual FR_CloseCommPort() Prototype FR_COMM_ERR WINAPI FR_CloseCommPortA (FR_COMM_HANDLE handle); FR_COMM_ERR WINAPI FR_CloseCommPortW (FR_COMM_HANDLE handle); Description Closes the communication channel with the instrument. Return Value The function call was successful. The function call was unsuccessful. Call the function to get error FR_GetLastErrorMessage() information.
FlashRunner Cube User’s Manual FR_GetFrame() Prototype FR_COMM_ERR WINAPI FR_GetFrameA (FR_COMM_HANDLE handle, char *answer, unsigned long maxlen, unsigned long timeout_ms); FR_COMM_ERR WINAPI FR_GetFrameW (FR_COMM_HANDLE handle, wchar_t *answer, unsigned long maxlen, unsigned long timeout_ms); Description Reads the answer to the command sent by the function.
FR CUBE API FR_GetLastErrorMessage() Prototype void WINAPI FR_GetLastErrorMessageA (char *error_msg, unsigned long tring_len); void WINAPI FR_GetLastErrorMessageW (wchar_t *error_msg, unsigned long string_ len); Description Returns a string containing the last FR CUBE error message. Parameters The string that will receive the error message. error_msg Length, in characters, of the error message buffer.
FlashRunner Cube User’s Manual FR_SendFrame() Prototype FR_COMM_ERR WINAPI FR_SendFrameA (FR_COMM_HANDLE handle, const char *command); FR_COMM_ERR WINAPI FR_SendFrameW (FR_COMM_HANDLE handle, const wchar_t *command); Description Sends a command to the instrument. Use the function to FR_GetFrame() retrieve the answer. Return Value The function call was successful. The function call was unsuccessful.
FR CUBE API FR_OpenCommPort() Prototype FR_COMM_HANDLE WINAPI FR_OpenCommPortA (const char *com_port, const char *com_settings); FR_COMM_HANDLE WINAPI FR_OpenCommPortW (const wchar_t *com_port, const wchar_t *com_settings); Description Opens a RS-232, Ethernet or USB communication channel with the instrument. Return Value alid communication handle to use in subsequent >0 functions.
FlashRunner Cube User’s Manual 6. FR CUBE File System Overview FR CUBE has a large, built-in non-volatile memory, used to store the various files required by the instrument: programming projects, image files, etc. This memory is organized by a file system. You can explore the FR CUBE files either by using a Terminal application and sending file-system related commands, or (more simply) by using the File Manager window of the Project Generator application.
FR CUBE File System File System Structure The files required by the instrument are organized in various folders, as explained below: \drivers folder: contains programming algorithms (.wnd files). These files are provided by Systein. \sys folder: contains systems files, such as programming licenses, firmware files, etc.
FlashRunner Cube User’s Manual 7. Variable Data Programming Overview FR CUBE has built-in, dedicated memory banks for each programming site. This memory can be used to temporarily store variable data that will be written to the target device during programming. This is useful for serial numbering and for any other variable data that needs to be written to the target device at programming time.
Page 58
Variable Data Programming You will then be asked for the target device address range to be programmed and the offset of the memory bank that will contain the variable data. Proceed to the end of the Project Creation wizard. Your programming project is now ready to accept variable data.
FlashRunner Cube User’s Manual 8. Power and Relay Options Power Supply Options FR CUBE can be powered in two ways: With the provided power supply (which supplies 15V DC); By providing a power supply to the PWR pin of the Low-Level Interface connector (see “Low-Level Interface Connector”...
Connectors All low-level interface lines are isolated from system GND (and are referenced to GNDI), except for the PWR line, which is referenced to GND. Ground Domains The following diagram illustrates the two ground domains of the programmer. ATE and Target Ground Domains In order to avoid undesired current paths between the programmer and the target board, we suggest to use a power supply with a floating output (ground not referenced to the...
FlashRunner Cube User’s Manual 10. Specifications Electrical Specifications Feature Value Maximum Ratings Power supply voltage ISP SxL0[1..7] voltage -0.7-6.5V ISP SxL0[1..7] current ±60mA ISP SxPPS voltage -0.7-18V ISP SxPPS current 380mA ISP SxRLY voltage -1.0-30V Low level interface PRJ_SELx, START, START_ENAx, BUSY, PASS/FAULTx -0.7-6.0V voltage...
Specification ISP Connectors ISP and Low-Level Interface connectors are DIN48 male connectors. We suggest using the following compatible female connectors. For wire wrapping: DIN41612 connector, 3 rows, 48 pins, 180° female, C style Manufacturer: Conec Manufacturer Part Number: 122A10619X Catalog Part Number: Mouser 706-122A10619X For soldering: DIN41612 connector, 3 rows, 48 pins, female, R/A C style Manufacturer: FCI...
Need help?
Do you have a question about the FlashRunner Cube Series and is the answer not in the manual?
Questions and answers