CONITEC GALEP-5 User manual

Introduction
Congratulations! With GALEP-5/5D you own a professional, universal device programmer for all
programmable circuits, such as EPROMs, EEPROMs, FLASH-EPROMs, serial EEPROMs, micro-controllers,
GALs and PALCEs. For any devices with up to 48 pins and supply voltages from 1.3V up to 5V no additional
circuitry is required. Devices in the DIL package are inserted directly, for other device packages several
standard programming adapters are available. Devices with more than 48 pins can be programmed eithe
r
using special adapters, or with replaceable high-pin-count socket modules for up to 240 pin drivers with the
GALEP-5D.
The programmer runs on an internal Embedded Linux system and is connected to an USB port. GALEP-5D
can be alternatively connected to a local network. GALEP-5 is configured to run in most cases on the powe
r
provided by the USB connection. For some programmable devices needing a higher supply current or i
f
several USB devices are connected to the computer, a power adapter can be connected. To reduce the load
for a laptop battery in mobile operation, GALEP-5 can be powered additionally by 6 internal AAA batteries
(normal or rechargeable).
The GALEP-5 software provides basic functionality such as < read > , < program >, < compare > and < erase
>, it also provides an accessible range of options regarding any special features available for the user's
selected component. The powerful built-in editor permits full editing of files stored in binary, Intel-Hex,
Motorola-S or JEDEC format.
New components made available regularly as free downloads from our web site allow new and existing
owners of the GALEP-5 to be assured of an ever expanding range of functionality. The GALEP-5 has been
designed not only to resist obscolescence, but to constantly implement new device support in future, via free
software updates. This will allow the GALEP's performance to remain in the vanguard of compact, portable
universal programmers for years to come. Conitec anticipates this new generation programmer to support
over 4000 discrete device groups within the next five years.
GALEP's unique flexibility is achieved by specialized hardware. All pins of the programming socket can
individually be set to one of three configurable voltages (up to 25V), ground, clock, adjustable pull-up / pull-
down resistors, as well as logic I/O with bidirectional level-shifters for low-voltage components. Using highly
integrated FPGAs, GALEP's internal logic can be reprogrammed to be optimally adjusted to the component
j
ust selected. This way the best possible read & write speed can be achieved.
System requirements: Windows 32-Bit OS, 98(SE), ME, NT, 2000, XP oder Vista, USB port (respectively
network for GALEP-5D)
Package contains: GALEP-5/5D programmer, USB cable, (LAN cable), power adapter, software with manual
in English and German on CD
Please Note: Batteries are not included (6x normal/rechargeable AAA batteries must be purchased separately
if needed in mobile operation).
Página 1 de 1Introduction
23/04/2009mk:
@
MSITStore:C:\DOCUME~1\Laura\CONFIG~1\Temp\Directorio%20temporal...

Installing GALEP-5/5D for USB port
When the GALEP-5 is first connected to a Windows PC, the Windows hardware assistant activates
automatically to install a new hardware driver. Prior to this step, make sure the required driver files are
available on the PC, either by having pre-installed the software from the CD – the drivers are then typically
located in the subdirectory: "C:\program files\GALEP5\G5Driver" - or in the "G5Driver" subdirectory of the
GALEP5 software CD.
Important! The installation process will vary slightly depending on the Windows version running on your PC. In
all cases, do not initiate a Windows Assistant automated search for any driver - you will instead need to
enter / select one or the other, of the 2 directories mentioned above (i.e. either the installed GALEP5 software
driver subdirectory, or the driver subdirectory located on the inserted CD).
A
fter connecting the GALEP-5 to an USB cable and to the PC, initially only the white LED will blink. After a
short pause, the embedded LINUX boot process will complete. Shortly afterwards, the red LED will light up,
and a dialogue box will display on screen asking if you wish to open a connection via the automated Windows
updater utility to seek an appropriate driver. Here you will need to select the "No" option, and then click.
In the next dialogue window, you’ll need to select the option requesting that only software from a specified
source is to be installed. After this option is selected, click "Continue" again.
In the next step, select "Browse" and open a navigation window – steer the process to the subdirectory where
your "G5Driver" is located (either from CD or C:\program files\GALEP5\G5Driver). Conclude this step by
clicking "OK".
Now the option "Conitec GALEP-5 Programmer" should be selected. Proceed then by clicking all the following
"Continue" buttons (or similar) until all the installation windows have completed and are closed.
A
fter a successful installation, you should find an entry for the GALEP-5 in the Windows network environment,
this connection is set up and used by the GALEP5 software. You can also use any web browser with the IP
address 192.168.167.12 to get some device information from the GALEP-5.
Installing GALEP-5D for Ethernet port
A
lternately, GALEP-5D can be connected via Ethernet. The default IP address on the Ethernet port is
192.168.1.13. The address can be changed via a web browser.

The Menu Bar
File
New Opens a new buffer.
Please note: Changing address settings under Options/Buffer directly affects the following three menu
items.
Open... Opens a new buffer window, and loads the selected file in the Binary-, Intel-HEX-,
Motorola-S- or JEDEC-format. The action performed by File/Open is a shortcut,
corresponding to manually selecting File/New first and then clicking on File/Load.
Load... Loads the selected file into the active buffer starting with the buffer start address. During
load, the file extension tag defining the format of the data being loaded is proposed (Binary-
, Intel-HEX-, Motorola-S- or JEDEC format). This suggested file extension is no longer
prompted in version 1.06 (and above) and consequently can be changed by the user. The
file is automatically converted into the binary or fuse map format according to the data
format chosen.
Format errors are detected and displayed. During loading of files with absolute addresses
(HEX or Motorola-S) a warning message appears if the address area lies outside the buffer
or the memory module chosen.
Save As Saves the active buffer. You may enter a new name for the file and select the desired file
format (Binary-, Intel-HEX-, Motorola-S- or JEDEC). When giving a .gpf2 file extension the
current GALEP configuration (buffer and device type) is saved.
Close Closes the active buffer.
Exit Terminates the program.
Edit
Cut Copies a previously marked region of the active buffer onto the clipboard, before removing
that region from the buffer. All subsequent data gets shifted to the corresponding lower
addresses.
Copy Copies a previously marked region of the active buffer onto the clipboard, the buffer itself
remains unchanged.
Paste Inserts clipboard data at the current cursor position. Subsequent data gets moved to make
room for the clipboard data.
Find This command allows searching for byte-, word-, or ASCII-sequences in the current buffer.
Swap Bytes Swaps high- and low-bytes of all 16 bit words in the buffer.
Fill Buffer Fills a buffer area with a byte value
Split Buffer For programming memory chips with a data width smaller than the target system data
width. The command copies a buffer area into several new buffers that only contain all the
low and high bytes or words. The source and target buffer data width can be choosen
between 8, 16, 32, and 64 bits. The data width of the target buffers must be smaller than
the source buffer data width.
Shuffle
Buffer
For reading memory chips with a data width smaller than the target system data width. The
command copies all the low or high bytes or words from a source buffer area into the
correct positions of a target buffer. The source and target buffer data width can be choosen
between 8, 16, 32, and 64 bits. The byte or word to copy can likewise be choosen. The data
width of the target buffer must be greater than the source buffer data width.This way the
target system data content can be built from reading several memory chips with different
low or high bytes or words.
Device Action
Before selecting any of these options, please read: How to insert devices into GALEP. All operations
on the device plugged into the GALEP can be initiated by selecting a menu item in software, clicking on the
button bar, or pushing one of the assigned function keys :
Device [F8] Selects the device type. In the displayed list, pick any of the currently supported devices.
Using the [Show Manufacturer first] check box for example, devices can be sorted based on
manufacturer, or a sort can be set according to device type. To select the device you
eventually select, simply double-click on it or use the [Select Device] button.
Two check boxes, [Use Device Address] and [Use File-Load Address] allow for changing
the device-option default values. With [Use Device Address] activated the address range is
set based on the selected device's maximum address. If [Use File-Load Address] is
activated the address range is determined by the size of the currently loaded file. Some
components, such as GALs and micro controllers need to be completely reprogrammed and

so do not require these options. If this is the case both dialog boxes are disabled and
cannot be selected.
Selecting a new device only applies to the current Buffer, all other buffers retain their
assigned devices. This allows the user to have several buffer windows associated with
different devices. If no buffer is currently opened, a new one will be created.
Please note: All changes made under Options/Device directly affect the following menu items.
Program
[F3]
This opens the action/programming panel, showing the suggested position of the device
inside the ZIF socket. Programming is initiated by clicking on [Start]. Please note that
programming action starts immediately if [Bypass start button] is activated under the
Options/Application menu.The device is programmed in accordance with all settings
selected under Options/Device. During programming the current memory address is
tracked. If a memory location can not be written to, the programming sequence is aborted,
and the faulty address will be displayed. Click Cancel to abort programming at any time.
Use the Options/Device menu to set the desired data width. If this width is too large for the
currently selected microchip, the Galep will attempt to automatically split the data onto
several microchips. For example: for an 8-Bit EPROM with a requested data width of 16-bit,
every even byte starting at the buffer origin will be written to IC0. The odd bytes will be
written to IC1.
Verify [F4] This function will read the full content of the buffer,from it's start to it's ending address -
and compare them to the data on the memory device being used, beginning at the
EPROM's starting address. Differences are displayed in increasing address sequence. If no
difference is detected, an OK message will be returned. It is also possible to compare
selected, or non-consecutive data areas, if the buffer's start and end address do not cover
the entire area of the EPROM. If a difference between any one byte is detected, it will be
displayed along with it's address. Afterwards the comparison process may either be aborted
or further bytes may be compared. This software feature allows any discrepancies between
the device and the data in the buffer to be displayed consecutively.
Blank [F5] Checks whether the device has been successfully deleted, or erased.
Read [F6] Reads the contents of the device into the buffer.
Erase [F7] Deletes the device. This function of course is only available for electronically erasable
devices. EPROMs still have to be deleted with an ultra-violet light source.
Please note: Some devices may be completely or partially protected against over-
writing or deleting. If such devices need to be erased, the software protection switch must
be enabled first in the Options/Device menu.
Options
Application General program settings.
Buffer Each Buffer window has a unique copy of this dialog box. In the dialog box you can select
display mode (8-, 16- Bit or JEDEC) and target address for file transfer operations. Click on
[Compute] to calculate a checksum for the current buffer contents.
Device Each Buffer window having a device already selected and assigned to it has a unique copy
of this dialog box. In this dialog window, component-specific options for reading/writing the
device can be set. The available options vary greatly depending on the selected device, e.g.
for a micro controller there might be an option to read protect its memory. These additional
features are explained in the component's data sheet (note: www.aufzu.de has a list of
most semi-conductor manufacturers ). For more information cf. component-specific help.
For memory modules, such as (E)EPROMs or Flash, you can select the buffer and device
address range in this same dialog box. All bytes from [Buffer start] to [Buffer end] are
mapped into the component's [Device start] to [Device end] range. This configuration can
be used for both reading and writing, so devices can be read/written partially, and buffer
data can be split to multiple memory modules if required.
View
Toolbar Toggles display of the tool bar below the menu bar.
Status Bar Shows/hides the status bar at the lower bottom of the screen.
Info Bar Activates one of three info panes (Workspace/Devices/Action). You can also activate those
by clicking directly on one of the three labels.
Window
New Creates a copy of the current buffer window. This way two different regions of the buffer
can be viewed simultaneously.
Cascade Displays overlapping buffer windows.
Tile Displays all buffer windows in a tiled arrangement.

Arrange
Icons
Displays all window icons in an adjacent arrangement.
Close All Closes all buffer windows.
Help
Content Opens this document.
About ... Here among other things you will find the Version Number of the program.

The Data Buffer
The buffer contains the data for the device to be programmed. It may be edited per individual byte, or filled with a constant value. You may open new buffers
or save the contents of the active buffer at any time. A portion of the buffer is displayed in the buffer window. Depending on the type of device selected -
memory modules or EPLD - the buffer window will display the data either in the Hex- and ASCII format or display the Fuse-Map.
In the case of memory modules the programming-, compare-or read-actions only refer to the data area between the buffer's Start Address and End
Address.
The cursor may be positioned in the active buffer window with either the mouse or the cursor buttons. [PgUp], [PgDn], [Home] and [End] leaf through the
buffer. [TAB] changes the cursor between address, hex area and ASCII area. By entering a hexadecimal number or character respectively the byte below the
cursor will be overwritten, after which the cursor automatically moves to the next byte. The buffer window allows you to edit an EPLD-Fuse-Map just as easily
by changing the state of the fuse at the location of the cursor with [0] or [1] ([0] = ´ Fuse burned ´, [1] = ´ Fuse not burned ´).
If you wish to display a distinct address in the buffer window, simply overwrite the address in the buffer window with the desired address and confirm the
entry with a return. The buffer window will then display the data starting with the address entered.
Buffer Window
This window displays part of the buffer containing data of the device to be programmed. You may move the cursor in the buffer window and edit the data.
If you wish to display a certain address in the buffer window, simply overwrite the address in the buffer window with the desired address and confirm with a
return. The buffer window will then display the data starting with the address entered.
Split and Shuffle
The program fSplitter.exe iIn the GALEP program directory can be used for splitting a file with 16-bit data into two 8-bit files, containing the even and the
odd bytes. This method generates buffer data for two 8-bit memory devices that are combined to a 16-bit memory.
Configuration of the Data Buffer
From version 1.17.02 on there are 2 modes of use for the Data Buffer and the link to original file. They are so called Production and Developer modes.
You can switch to the mode you need in the Application Options dialog ( menu Options -> Application ) :
In the Data Buffer setting ( default ) area you have the following options to choose :
Data Buffer not linked to data file ( Production mode )
With this setting the Data Buffer isn't linked to the loaded/saved file. The Data Buffer will be entirely stored in the project file by closing and fully restored at
next start of the Galep32 application. The data file itself will be ignored ( no automatically loading ).
Data Buffer linked to data file, file monitoring off ( Developer mode )
With this setting the Data Buffer is linked to the loaded/saved file. The Data Buffer will be not stored, but the link to the loaded/saved file only. At the next
start of the Galep32 application the linked data file will be loaded ( if exist ).
Data Buffer linked to data file, file monitoring on ( Developer mode )
The same as previous, but in addition the file monitoring is activated ( to notify if the loaded/saved file was changed out of the Galep32 application ).
The setting can be changed at any time local for a project :
1. Using menu Options.
2. Usin
g
context menu of the Workspace.

To visualize the actual state, an own icon was assigned to every state. An icon exist of the frame for the state of the Data Buffer and internal drawing for the
state of the original file (only in the Production mode ). Farther below all possible states are summarized.
Production Mode
Explanation of individual icons :
Developer Mode
Explanation of individual icons :
Icons Description
No link to the loaded/saved file. The Data Buffer will be entirely stored ( in the Galep Project file ) and restored at the start of the Galep32
application.
Icon Description
- The Data Buffer isn't modified.
- The Data Buffer was modified by user.
Icons Description
The Data Buffer refers always to a file ( after File Load/Save ) and it is not stored. At the start of the Galep32 application
the original file will be reloaded ( if exist ).
Icon Description
- The Data Buffer isn't modified, no file loaded/saved yet.
- The Data Buffer was modified by user, no file loaded/saved yet.
- The Data Buffer isn't modified, the original file not changed.
- The Data Buffer was modified by user, the original file not changed.
- The Data Buffer isn't modified, the original file was changed ( and the user choose don't reload the file ).
- The Data Buffer was modified by user, the original file was changed ( and the user choose don't reload the file ).
- The Data Buffer isn't modified, the File Monitoring is deactivated.
- The Data Buffer was modified by user, the File Monitoring is deactivated.
- The Data Buffer isn't modified, the original file not found.
- The Data Buffer was modified by user, the original file not found.

Inserting devices
For the selected device an exact position of the device pins in relationship to the GALEP socket is displayed
by the software within the action window, which is shown for <program>, <verify>, <blank check>, <read> and
<erase>.
Most devices are inserted with the device's pin # 1 directed to the lever of the GALEP socket and with the
opposite end of the device aligned to the opposite end of the socket (see image above). Positioning you
r
device into the GALEP socket should be done carefully, with regard to correct pin orientation.
Exceptions: GALEP-III can not provide all the different programming voltages at each of the socket pins. This
makes it necessary to rotate or move some of the devices on the socket. Therefore it is essential to keep in
mind, that the device always must be inserted exactly as displayed in the Action window.
Such limitation obviously does not apply to the GALEP-4 and GALEP-5 ASIC pin hardware capabilities, but
both old and new GALEP share some common programming algorithms, requiring the rotation or movement
of some devices even when using GALEP-4/-5.
Please note / disclaimer: Devices incorrectly inserted into the GALEP risk permanent damage. If a device
is incorrectly inserted even once, it should under no circumstances be used any more, as it's correct function
can no longer be guaranteed. Incorrectly inserted devices can also cause damage to the GALEP, and will
void it's warranty
Device Specific Help
See the links below for device specific information
We highly recommend to study the manufacturers data sheet too. You´ll find a link to most of the
semiconductor manufacturers via www.aufzu.de .
EPROM EEPROM FLASH
PLD MCU RAM
Serial (EE)PROMs SPECIAL JTAG

Power supply / Battery operation
The standard power supply for the GALEP-5 is the USB connection. If several devices are connected to a
USB port and/or if a programmable device needs a higher supply current, a power adapter must be used. To
reduce the load of a laptop battery in mobile operation, GALEP-5 has a battery compartment located on its
base, which houses 6 AAA (rechargeable) batteries (1.2 or 1.5 Volt.). DISPOSE OF USED BATTERIES
ACCORDING TO LOCAL LAW.
For non mobile operation we suggest using the power adapter which comes with your GALEP-5 (unregulated
12 Volt DC, 500 mA). When using any other power adapter you must asure that it is UL listed within NEC
class 2 output (unregulated 12VDC min. 0.4A or regulated 14VDC min. 0.4VDC). The idle voltage of an
unregulated power adapter must not exceed 15 volts. Voltages above 15 volts may damage the GALEP-5.
GALEP-5D can not be powered through the USB connection or batteries; a power adapter must always be
used.

Modules and Adapters
For devices in packages other than DIL packages (e.g. PLCC or TSOP packages) adapters are required with
appropriate device sockets and, if necessary, with auxiliary circuits.
The following modules and adapters are currently available from CONITEC:
Article No. Module (GALEP-5D)
220008 Module 20pin SOIC 200 mil, OT
220015 Module 48pin TSOP 20 mm, OT
220002 Module 56pin TSOP 20 mm, OT
220007 Module 28pin SSOP 200 mil, OT
220016 Module 38pin TSSOP 0.65 pitch, 170 mil, OT
220009 Module 52pin PLCC 20x20 mm, OT
220010 Module 68pin PLCC 25x25 mm, OT
220011 Module 84pin PLCC 30x30 mm, OT
220017 Module 44pin QFP 0.80 pitch, 10x10 mm, OT
220014 Module 48pin QFP 0.50 pitch, 7x7 mm, OT
220013 Module 52pin QFP 0.65 pitch, 10x10 mm, OT
220005 Module 64pin QFP 0.50 pitch, 10x10 mm, OT
220004 Module 80pin QFP 0.50 pitch, 12x12 mm, OT
220001 Module 100pin QFP 0.50 pitch, 14x14 mm, OT
220003 Module 100pin QFP 0.65 pitch, 14x20 mm, OT
220006 Module 120pin QFP, 0.50 pitch, 16x16 mm, OT
220019 Module 44pin MLF 0.50 pitch, 7x7 mm, OT
Article No.
A
dapter (GALEP-4, -5, -5D)
210841 Adapter 40pin DIL to 44pin PLCC
210842 EPROM-Adapter 32pin DIL ito 32pin PLCC
210843 EPROM-Adapter 28pin DIL to 32pin PLCC
210844 GAL-Adapter 20pin DIL to 20pin PLCC
210845 GAL-Adapter 24pin DIL to 28pin PLCC
210846 Adapter 40pin DIL to 44pin SOP
210847 Adapter 40pin DIL to 44pin (T)QFP
210848 Adapter 40pin DIL to 80pin QFP
210849 Adapter 16pin DIL to 16pin SOIC (150 mil)
210850 Adapter 24pin DIL to 24pin SOIC (200 mil)
210851 Adapter 28pin DIL to 28pin SOIC (300 mil)
210854 Adapter 40pin DIL to 120pin QFP for Fujitsu-CPU MB90F394
210855 Adapter 40pin DIL to 48pin TSOP
210858 Adapter 32pin DIL to 32pin TSOP (8 x 20 mm)
210859 Adapter 32pin DIL to 32pin TSOP (8 x 14 mm)
210860 Adapter 40pin DIL to 40pin TSOP (10 x 20 mm)
210861 Adapter 40pin DIL to 40pin TSOP (10 x 14 mm)
210862 Adapter 28pin DIL to 28pin PLCC
210863 Adapter 40pin DIL to 40pin QFP (MCU)
210864 Adapter 40pin DIL to 40pin PLCC (MCU)
210865 ISP Adapter
210866 Adapter 40pin DIL to 56pin SSOP
210867 Adapter 40pin DIL to 56pin TSOP
210868 Adapter 32pin DIL to 32pin MLF/QFN
210869 Adapter 32pin DIL to 32pin QFP
210870 Adapter 40pin DIL to 208pin QFP for Fujitsu-CPU MB91Fxxx
210871 Adapter 40pin DIL to 100pin QFP for Fujitsu-CPU MB90Fxxx
210872 Adapter 40pin DIL to 120pin(144) QFP for Fujitsu-CPU MB90Fxxx
210873 Adapter 40pin DIL to 64pin QFP for Fujitsu-CPU MB90Fxxx
210874 Adapter 40pin DIL to 120pin QFP for Fujitsu-CPU MB91Fxxx
210875 Adapter 40pin DIL to 100pin QFP for Fujitsu-CPU MB91Fxxx
Página 1 de 3GALEP Adapte
r
23/04/2009mk:
@
MSITStore:C:\DOCUME~1\Laura\CONFIG~1\Temp\Directorio%20temporal...

Old adapters from CONITEC:
Some devices programmable with the GALEP require adapters which unfortunately are not offered by
CONITEC at this time.
However, reading the reference material indicated below, with regard to the adapters mentioned should
enable you to build your own adapter:
Some devices can be handled by using Adapters of Emulation Technology:
For the following devices the correct adapter can be ordered directly from the manufacturer:
210876 Adapter 40pin DIL to 120pin QFP for Fujitsu-CPU MB91Fxxx
210877 Adapter M06-QFP-100 for Fujitsu-CPU MB90Fxxx
210878 Adapter M05-QFP-100 for Fujitsu-CPU MB90Fxxx
210879 Adapter M09-QFP-64 for Fujitsu-CPU MB90Fxxx
210880 Adapter M26-QFP-48 for Fujitsu-CPU MB90Fxxx
210881 Adapter M04-QFP-208 for Fujitsu-CPU MB91F467D
210882 Adapter QFP-100 for Fujitsu-CPU MB91F464A
210883 Adapter QFP-120 for Fujitsu-CPU MB91F465K
210884 Adapter BGA-320 for Fujitsu-CPU MB91F469G
210885 Adapter M20-QFP-100 for Fujitsu-CPU MB96F348
210886 Adapter M22-QFP-100 for Fujitsu-CPU MB96F348
210887 Adapter M26-QFP-48 for Fujitsu-CPU MB90F962
210888 Adapter QFP-120 for Fujitsu-CPU MB96F387
210889 Adapter M23-QFP-64 for Fujitsu-CPU MB91F463N
210890 Adapter M08-QFP-144 for Fujitsu-CPU MB91F467B
210891 Adapter M07-QFP-176 for Fujitsu-CPU MB91F467R
210892 Adapter M08-QFP-144 for Fujitsu-CPU MB91F467C
210893 Adapter M21-QFP-80 Fujitsu MB96F326
210894 Adapter M23-QFP-64 Fujitsu MB96F536
210895 Adapter M24-QFP-64 Fujitsu MB96F536
210896 Adapter M08-QFP-144 Fujitsu MB96F338/MB96F378/MB96F379
210897 Adapter M12-QFP-144 Fujitsu MB96F338/MB96F378/MB96F379
210898 Adapter M07-QFP-176 Fujitsu MB91F465PA
210899 Adapter M07-QFP-176 Fujitsu MB91F467SA
210911 Adapter 44pin DIL to 44pin PLCC
210912 Adapter 44pin DIL to 44pin SOP
210913 Adapter 44pin DIL to 44pin (T)QFP
210914 Adapter 48pin DIL to 48pin TSOP
210915 Adapter DIL-40 => ISP-ASYNC/SYNC
Article Nr.
A
dapte
r
210823 Adapter for 32-pole PLCC-EPROMs
210824 Adapter for 20/28-pole PLCC GALs
210825 Adapter for 32-pole LCC-EPROMs
210841 Adapter for 44-pole PLCC-EPROMs and MCUs
A
dapte
r
PIC16C9XX Programming Adapter
PIC17C7xx Programming Adapter
S87C552 Programming Adapter
DIL-42 Programming Adapter (e.g. M27C160)
A
dapte
r
Emulation Adapter AS-08-08-01ML-3
A
dapte
r
HD6477034F, HD6477034VF Programming Adapter
HD64F3334Y, HD64F3337Y Programming Adapter
Página 2 de 3GALEP Adapte
r
23/04/2009mk:
@
MSITStore:C:\DOCUME~1\Laura\CONFIG~1\Temp\Directorio%20temporal...

See also Inserting an adapter into the GALEP
Página 3 de 3GALEP Adapte
r
23/04/2009mk:
@
MSITStore:C:\DOCUME~1\Laura\CONFIG~1\Temp\Directorio%20temporal...

Using Serial Numbers
The programming of serial numbers is based on a special CSV-file format. It is activated at data-buffer’s
“File/Buffer Options”-Tab.
The configuration dialog of the serial number programming offers some input elements to control the
programming run.
A Switch to turn global serial number programming on/off..
A file dialog to specify the CSV file.
A rule check for the CSV-file.
The path of the CSV file can be fully specified or the GALEP software expects the CSV file at the same
location as the project file(gpf2).
The write back of the serial number status can be activated or deactivated.
Choose the allocation rule for the serial number between use strict only once or reuse the serial number in
case of programming failure.
The CSV serial number file format.
The CSV serial number file format (Comma Separated Values ) is based in one data record per line. Each line
consists of some comma separated data written in ASCII characters. Several lines and serial number records
respectively are building a serial number block. A serial number block is valid for one device programming run.
The line format of the CSV file looks like:
Count(Dec), SerialData(Hex), SerialAddress(Hex), DataLenght(Dec), RecordType [, Status]

Status: If the status is missing, the serial number record is initially unused. The status information consists o
f
the characters p, fand u.
pstands for pending, f“ stands for fail and „u“ means used. e.g. pfpu means pending, fail, pending, used.
Normally the status information will be written by the GALEP software.
RecordType:
DataLenght describes the length of the SerialData-field. It is an ASCII coded decimal value. For the record
types „B“ and „R“ the value can be 0 up to 20.
SerialAddress is an ASCII coded hexadecimal number form 0 to FFFFFFFE and is used for the address o
f
the serial number. If the record type is „L“ the SerialAddress will be ignored.
SerialData is the serial number data limited to 20 bytes. For RecordType “R” are max 40 ASCII characters
possible. For „L“ and „B“ are max 20 ASCII characters allowed. If the serial data field is shorter than the
length specified than the unused characters will be filled with “00”.
Count is the ordinal number for the serial number record. Several record with the same count are put togethe
r
to a serial number block(look at the samples).
CSV-Samples.
Sample 1:
1, 0001, 7AA, 2, B
2, 0002, 7AA, 2, B
3, 0003, 7AA, 2, B
4, 0004, 7AA, 2, B
Sample 2:
1, 0001, 7AA, 2, R
1, 1_7AA, , , L
2, 0002, 7AA, 2, R
2, 2_7AA, , , L
3, 0003, 7AA, 2, R
3, 3_7AA, , , L
4, 0004, 7AA, 2, R
4, 4_7AA, BBBB,5 , L //SerialAddress and DataLength will be ignored.
„R“ The record describes the basic serial number data containing SerialData, SerialAddres
s
and DataLenght.
„L“ SerialData is used as label.
„B“ SerialData is used as label and serial number (togther with SerialAddress un
d
DataLenght).

Sample 3:
1, 0001, 7AA, 2, R //First device
1, 0011, 7BB, 2, R //First device
1, 1_7AA_7BB, , , L //First device
2, 0002, 7AA, 2, R //2. device
2, 0022, 7BB, 2, R //2. device
2, 2_7AA_7BB, , , L //2. device
3, 0003, 7AA, 2, R
3, 0033, 7BB, 2, R
3, 3_7AA_7BB, , , L
4, 0004, 7AA, 2, R
4, 0044, 7BB, 2, R
4, 4_7AA_7BB, BBBB,5 , L //SerialAddress and DataLength will be ignored.
5, 000A, 7AA, 2, R //Last SN
5, 000B, 7BB, 2, R //Last SN
5, Final, , , L //Last SN

Batch Mode
GALEP can be completely controlled from the command line, allowing to implement GALEP commands in
your own production software. For this, a powerful set of batch commands is available. A GALEP command
line has the following format:
galep5 [filename.gpf2] [filename.log] [/Action] [/Option]...
The command line is not case sensitive, e.g. /VerboseLevel2 is identical to /verboselevel2.
GPF2 and LOG files
A
.gpf2 (Galep-Project-File2) file contains a 'snapshot' of data, device and device configuration. The file can
be saved by selecting the GPF2 file type inside the Save As file dialog box. When giving a a GPF2 file name
as command line option, GALEP is set up to the saved stated.
A
.log file name in the command line causes the program messages to be written into this file. The /console
command line option (see below) forces the program to also open a console window for displaying program
messages.
Please note:
No relativ paths are allowed for .log and .gpf2 files. The location for files without path is the application
directory.
The .gpf2 file format must match the Galep software version. When updating to a new software version, eithe
r
create the .gpf2 files anew, or keep the installation of the old GALEP software version together with you
r
batch job and .gpf2 files in an extra folder.
A
ctions
The following Actions are available in a command line:
/prog - Program action
/read - Read action
/blank - Blank action
/verify - Verify action
/erase - Erase action
Options
The following Options are available:
/console - The program messages will appear in a console window. Use this option to test your batch file.
/showwindow - The main windows will be shown on the screen. Use this option to test your batch file.
/noexit - The program will not terminate after the batch run. This option works only togethe
r
with /showwindow.
There are up to three possible windows in a batch run: the command line window, the console window and
the data window. To terminate the batch run, close the data window, NOT the console window!
/verboselevel1 - Without this option, the program issues only the batch messages (see below).
Verboselevel1 issues all messages usually shown inside the action tab window.
/verboselevel2 - This level will issue all program messages.
Batch Messages

The format of all batch messages is:
BatchMode: „message“
The following messages could be issued by the program during batch mode without a /verboselevel option:
Standard batch mode state messages:
StartingBatchMode
InitReadAction
InitProgAction
InitVerifyAction
InitBlankAction
InitEraseAction
InitAutoAction
StartAction
ActionInProgress
ActionEnd
ActionSuccess
ActionFail
SaveFile: „filename“
TerminateBatchMode
NoExitFlagIgnored
ExitProgramm
Batch mode error messages:
GalepNotReady
ErrorInSaveFileName
ErrorWhileSaveFile: „filename“
Batch not possible with HandlerMode
AbnormalProgramTermination
NoApplicationDirFound
ErrorInLogFileName
Return values
The application returns the following values:
0-> No Batch job executed
1-> Success
2-> Error
Quick Batch Tutorial
Step 1: Start the GALEP5.exe without any command line option. Load your data file und select your device,
set your desired device options appropriatly. For time saving at startup make sure that you have only one data
window open! Choose the File/Save As command and save your Galep project file with gpf2 extension to
disk.
Step 2: Test your config file with the commandline, like this: galep5 /prog
yourproject.gpf2 /console /showwindow /noexit /verboselevel2 yourproject.log
Step 3: If you are sure that your batch command works, remove all unnecessary options and save the
command line in a .bat batch file: galep5 /prog yourproject.gpf2
Step 4: Have a look at the the batch samples below for more complex tasks.
Batch Samples
Sample 1: Erase and program a device
Página 2 de 3Batch Mode

@echo off
echo Sample 1: erase and program
if exist yourproject.gpf2 goto galep5
echo missing yourproject.gpf2
goto nobatch
:galep5
start /wait GALEP5 yourproject.gpf2 /erase /console
if errorlevel 2 goto error2
if errorlevel 1 goto success1
goto nobatch
:error2
echo Action not successfull!
goto end
:success1
start /wait GALEP5 yourproject.gpf2 /prog /console
if errorlevel 2 goto error2
if errorlevel 1 goto success2
goto nobatch
:success2
echo Action successfull!
goto end
:nobatch
echo no batch job
:end
Sample 2: Blank, erase and program
@echo off
echo Sample 2: blank,erase and program
if exist yourproject.gpf2 goto galep5
echo missing yourproject.gpf2
goto nobatch
:galep32
start /wait GALEP5 yourproject.gpf2 /blank cfg /console
if errorlevel 2 goto error_blank
if errorlevel 1 goto success_blank
goto nobatch
:error_blank
start /wait GALEP5 yourproject.gpf2 /erase /console
if errorlevel 2 goto error_erase
if errorlevel 1 goto success_erase
goto nobatch
:error_erase
:error_prog
echo Action not successfull!
goto end
:success_blank
:success_erase
start /wait GALEP5 yourproject.gpf2 /prog /console
if errorlevel 2 goto error_prog
if errorlevel 1 goto success_prog
goto nobatch
:success_prog
echo Action successfull!
goto end
:nobatch
echo no batch job
:end

On Chip Debugging with GALEP-5 and OpenOCD
The GALEP-5 device programmer series can be used as a hardware interface for OpenOCD. The OpenOCD
project is a free software project for accessing microcontrollers (MCUs) via JTAG interface. This way software
can be debugged on the original MCU and on the original board. Hardware and software breakpoints can be
triggered, the program can be interrupted and executed in single step mode... without emulator and - except
for GALEP - without any additional hardware. The JTAG interfaces can be used for -
Developing software directly on the target system
Programming flash memory
Testing circuit boards and many more...
GALEP-5 is especially well suited as an interface for OpenOCD due to its on-board ARM Linux system. The
OpenOCD software runs natively on GALEP-5 and offers a gdb debugging interface via Ethernet or emulated
USB port. This allows easy configuration and effective development.
GALEP-5 offers several other features that improve JTAG debugging. Its Ethernet interface ensures fast data
transfer. Its front side button can be used for starting OpenOCD functions. The JTAG signals can be assigned
to arbitrary pins of the programmer socket. This feature is only offered by the GALEP-5 series.
Content
Overview
Configuration
Getting Started
Debugging with gdb
Developing with OpenOCD and the GALEP-API
Overview
The following part of the documentation is for developers who want to use OpenOCD for debugging thei
r
target system.
For using GALEP-5 as interface for OpenOCD debugging, you can just install a pre-compiled
OpenOCD version. It's a snapshot of the OpenOCD project at the time of writing this documentation.
OpenOCD is permanently improved, so it could make sense to patch and compile the latest
OpenOCD version yourself. This is decribed in Part II of this document.
What you're getting from us
The OpenOCD archive on http://www.conitec.net/down/g5ocd.zip contains:
The “xyz” resp. “abc” represent the version numbers.
What the GALEP-5 / OpenOCD port can do
This software package lets you combine a fast hardware interface (the GALEP-5 device programmer) with an
Open Source software (OpenOCD) for debugging MCUs and programming many Flash device types. The
GALEP-5 / OpenOCD combination offers the same convenience as high-priced JTAG debuggers. It has
already proven itself by inhouse debugging ARM9TDMI and ARM9-EJIS cores (at the moment of writing this
document the EJIS core support was not yet fully developed).
What the GALEP-5 / OpenOCD port can not do
doc/g5ocd_e.htm This document in html format.
g5ocd-bin-svn-xyzM.tar.bz2 The GALEP-5 OCD port, pre-compiled in a Linux archive.
g5ocd-bin-svn-xyzM.tar.zip The GALEP-5 OCD port, pre-compiled in a Windows™ archive.
g5ocd-svn-xyzM.patch.bz2 GALEP patch for OpenOCD (for compiling OpenOCD yourself).
g5API-abcM.tar.bz2 The GALEP-5 API for developers.