Advanced Card Systems AET63 BioTRUSTKey User manual

Version 1.
8
09-2006
Unit 1008, 10th Floor, Hongkong International Trade and Exhibition Centre
1 Trademart Drive, Kowloon Bay, Hong Kong
Tel: [phone] Fax: [phone] Email: [e-mail] Website: www.acs.com.hk

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 2 of 29
Contents
1. Introduction ...........................................................................................................................4
2. Features .................................................................................................................................4
3. Supported Card Types ..........................................................................................................5
3.1 Microcontroller-based smart cards (asynchronous interface)............................................................. 5
4. Smart Card Interface .............................................................................................................6
4.1 Smart Card Power Supply VCC (C1).................................................................................................. 6
4.2 Programming Voltage VPP (C6)......................................................................................................... 6
4.3 Card Type Selection ........................................................................................................................... 6
4.4 Interface for Microcontroller-based Cards .......................................................................................... 6
4.5 Card Tearing Protection...................................................................................................................... 6
5. Power Supply.........................................................................................................................6
6. USB Interface .........................................................................................................................8
6.1 Communication Parameters ............................................................................................................... 8
7. Communication Protocol ......................................................................................................9
7.1 Command ........................................................................................................................................... 9
7.1.1 Normal Command (Length < 255 bytes)....................................................................................................9
7.1.2 Extended Command..................................................................................................................................10
7.2 Response.......................................................................................................................................... 10
7.2.1 No transmission error with normal response (Length < 255 bytes).........................................................10
7.2.2 No transmission error with extended response ........................................................................................12
7.2.3 Transmission error...................................................................................................................................12
7.3 Card Status Message ....................................................................................................................... 13
7.4 Transmission Protocol ...................................................................................................................... 13
8. COMMANDS .........................................................................................................................15
8.1 Control Commands........................................................................................................................... 15
8.1.1 GET_ACR_STAT......................................................................................................................................15
8.1.2 SELECT_CARD_TYPE ............................................................................................................................16
8.1.3 RESET ......................................................................................................................................................16
8.1.4 SET_NOTIFICATION ..............................................................................................................................16
8.1.5 SET_OPTION...........................................................................................................................................17
8.2 EEPROM Commands....................................................................................................................... 18
8.2.1 EEPROM_READ_DATA..........................................................................................................................18
8.2.2 EEPROM_WRITE_DATA ........................................................................................................................18
8.3 TFM (Trusted Fingerprint Module) Commands ................................................................................ 19
8.3.1 TFM_COMMAND....................................................................................................................................19
8.3.2 TFM_RESET ............................................................................................................................................19
8.3.3 TFM_SMARTCARD .................................................................................................................................19
8.3.4 TFM_OPEN_SECURE_SESSION ...........................................................................................................21
8.4 MCU-based Card .............................................................................................................................. 22
8.4.1 RESET ......................................................................................................................................................22
8.4.2 POWER_OFF...........................................................................................................................................22
8.4.3 EXCHANGE_APDU ................................................................................................................................22
8.4.4 EXCHANGE_T1_FRAME........................................................................................................................23
8.5 Security Application Module (SAM)................................................................................................... 24
8.5.1 ACTIVATE_SAM......................................................................................................................................24
8.5.2 DEACTIVATE_SAM.................................................................................................................................24
8.5.3 EXCHANGE_SAM_APDU.......................................................................................................................25
8.5.4 EXCHANGE_SAM_T1_FRAME ..............................................................................................................26

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 3 of 29
Appendix A: Supported Card Types.........................................................................................27
Appendix B: Response Status Codes ......................................................................................28
Appendix C: Technical Specifications .....................................................................................29

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 4 of 29
1. Introduction
The AET63 BioTRUSTKey is an interface for the communication between a computer (for example, a PC), a
smart card and TFM (Trusted Fingerprint Module). Different types of smart cards have different commands
and different communication protocols. This prevents, in most cases, the direct communication between a
smart card and a computer. The AET63 BioTRUSTKey establishes a uniform interface from the computer to
the smart card for a wide variety of cards. By taking care of the card specific particulars, it releases the
computer software programmer of getting involved with the technical details of the smart card operation,
which are in many cases not relevant for the implementation of a smart card system.
The AET63 BioTRUSTKey is connected to the computer through USB interface. The reader accepts
commands from the computer, carries out the specified function at the smart card and returns the requested
data or status information.
2. Features
ISO7816-1/2/3 compatible smart card interface
Enrolls fingerprint, encrypts into fingerprint template and stores inside smart card
Retrieves fingerprint template from smart card and verifies the fingerprint template inside the AET63
Supports CPU-based cards with T=0 and/or T=1 protocol
Support PPS (Protocol and Parameters Selection) with 9600 – 96000 bps in reading and writing smart
cards
USB interface to PC with simple command structure
Security application modules (SAM) inside the reader supporting CPU-based cards with T=0 and/or T=1
protocol (SAM Reader only)

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 5 of 29
3. Supported Card Types
The AET63 can operate MCU card with T=0 and T=1 protocol. The table presented in Appendix A explains
which card type selection value must be specified for the various card types supported by the reader.
3.1 Microcontroller-based smart cards (asynchronous interface)
The AET63 supports EEPROM microcontroller-based cards with internal programming voltage (VPP)
generation and the following programming parameters transmitted in the ATR:
PI1 = 0 or 5
I = 25 or 50
The AET63 performs the Protocol and Parameters Selection (PPS) procedure as specified in ISO7816-
3:1997.
When the card ATR indicates the specific operation mode (TA
2
present; bit b5 of TA
2
must be 0) and that
particular mode is not supported by the AET63, the reader will reset the card to set it to negotiable mode. If
the card cannot be set to negotiable mode, the reader will reject the card.
When the card ATR indicates the negotiable mode (TA
2
not present) and communication parameters other
than the default parameters, the AET63 will execute the PPS and try to use the communication parameters
that the card suggested in its ATR. If the card does not accept the PPS, the reader will use the default
parameters (F=372, D=1).
For the meaning of the aforementioned parameters, please refer to ISO7816, part 3.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 6 of 29
4. Smart Card Interface
The interface between the AET63 and the inserted smart card follows the specifications of ISO7816-3 with
certain restrictions or enhancements to increase the practical functionality of the AET63.
4.1 Smart Card Power Supply VCC (C1)
The current consumption of the inserted card must not be higher than 50mA.
4.2 Programming Voltage VPP (C6)
According to ISO 7816-3, the smart card contact C6 (VPP) supplies the programming voltage to the smart
card. Since all common smart cards in the market are EEPROM based and do not require the provision of an
external programming voltage, the contact C6 (VPP) has been implemented as a normal control signal in the
AET63. The electrical specifications of this contact are identical to those of the signal RST (at contact C2).
4.3 Card Type Selection
The controlling PC has to always select the card type through the proper command sent to the AET63 prior
to activating the inserted MCU card.
For MCU-based cards the reader allows to select the preferred protocol, T=0 or T=1. However, this selection
is only accepted and carried out by the reader through the PPS when the card inserted in the reader supports
both protocol types. Whenever an MCU-based card supports only one protocol type, T=0 or T=1, the reader
automatically uses that protocol type, regardless of the protocol type selected by the application.
4.4 Interface for Microcontroller-based Cards
For microcontroller-based smart cards only the contacts C1 (VCC), C2 (RST), C3 (CLK), C5 (GND) and C7
(I/O) are used. A frequency of 4 MHz is applied to the CLK signal (C3).
4.5 Card Tearing Protection
The AET63 provides a mechanism to protect the inserted card when it is suddenly withdrawn while it is
powered up. The power supply to the card and the signal lines between the AET63 and the card are
immediately deactivated when the card is being removed. As a general rule, however, to avoid any electrical
damage, a card should only be removed from the reader while it is powered down.
NOTE - The AET63 does never by itself switch on the power supply to the inserted card. This must explicitly be done by the
controlling computer through the proper command sent to the reader.
5. Power Supply
The AET63 requires a voltage of 5V DC, 100mA, regulated, power supply. The AET63 gets the power supply
from PC (through the cable supplied along with each type of reader).

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 7 of 29
Status LEDs
Two green LED on the front of the reader indicates the activation status of the smart card interface and the
status of power supply of the device:
First Green LED - Indicates power supply to the device, i.e., the device is receiving power from the
computer. As long as the device is connected to the PC, this LED light is on.
Second Green LED – Indicates that a smart card is present in the device, i.e., the smart card is activated.
As long as there is a smart card inserted in the device, this light is on.
NOTE – This is applicable if you are using the PCSC device installer for AET63

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 8 of 29
6. USB Interface
The AET63 is connected to a computer through a USB following the USB standard.
6.1 Communication Parameters
The AET63 is connected to a computer through USB as specified in the USB Specification.
The AET63 is working in low speed mode, i.e. 1.5 Mbps.
USB Interface Wiring
Pin Signal Function
1 V
BUS
+5V power supply for the reader
2 D- Differential signal transmits data between AET63 and PC.
3 D+ Differential signal transmits data between AET63 and PC.
4 GND Reference voltage level for power supply
NOTE - In order for the AET63 to function properly through USB interface, either ACS proprietary device drive or ACS PC/SC device
driver has to be installed. Please refer to the Device Driver Installation Guide for more detail.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 9 of 29
7. Communication Protocol
In the normal operation, the AET63 acts as a slave device with regard to the communication between a
computer and the reader. The communication is carried out in the form of successive command-response
exchanges. The computer transmits a command to the reader and receives a response from the reader after
the command has been executed. A new command can be transmitted to the AET63 only after the response
to the previous command has been received.
There are two cases where the reader transmits data without having received a command from the
computer, namely, the Reset Message of the reader and the Card Status Message.
7.1 Command
7.1.1 Normal Command (Length < 255 bytes)
A command consists of four protocol bytes and a variable number of data bytes and has the following
structure:
Byte 1 2 3 4 ... N+3 (0<N<255) N+4
Header Instruction Data length = N Data Checksum
Header 01
H
to indicate the start of a standard command.
02
H
to indicate the start of an encrypted command (support from firmware 0.67 onwards,
only used in PTVerifySC
(*)
and PTVerifySCAll
(*)
)
Instruction The instruction code of the command to be carried out by the AET63
Data Length Number of subsequent data bytes.(0 < N < 255)
Data Data contents of the command.
For a READ command, for example, the data bytes would specify the start address and the
number of bytes to be read. For a WRITE command, the data bytes would specify the start
address and the data to be written to the card.
The data bytes can represent values to be written to a card and/or command parameters
such as an address, a counter, etc.
Checksum The checksum is computed by XORing all command bytes including header, instruction,
data length and all data bytes.
Note (*) : Please refer to “BioTRUSTKey API Manual.doc” for the descriptions of PTVerifySC and
PTVerifySCAll.
The following example shows the structure of a command with instruction code = 91
H
and three data bytes
with the values 11
H
, 22
H
and 33
H
, respectively:

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 10 of 29
byte 1 2 3 4 5 6 7
01
H
91
H
03
H
11
H
22
H
33
H
93
H
7.1.2 Extended Command
A command consists of six protocol bytes and a variable number of data bytes and has the following
structure:
byte 1 2 3 4 5 6 ... N+5 (N>0) N+6
Header Instruction Data Length = N Data
Checksum
FF
H
Data Length N
Header 01
H
to indicate the start of a standard command.
02
H
to indicate the start of an encrypted command (support from firmware 0.67 onwards,
only used in PTVerifySC
(*)
and PTVerifySCAll
(*)
)
Instruction The instruction code of the command to be carried out by the AET63.
Data Length Number of subsequent data bytes, and is encoded in 3 bytes. The first byte is FF
H
. The
second byte and the third byte represent data length N.
Data Data contents of the command.
For a READ command, for example, the data bytes would specify the start address and the
number of bytes to be read. For a WRITE command, the data bytes would specify the start
address and the data to be written to the card.
The data bytes can represent values to be written to a card and/or command parameters
such as an address, a counter, etc.
Checksum The checksum is computed by XORing all command bytes including header, instruction,
data length and all data bytes.
Note (*) : Please refer to “BioTRUSTKey API Manual.doc” for the descriptions of PTVerifySC and
PTVerifySCAll.
7.2 Response
The response from the AET63 to any command depends on whether the command has been received by the
reader without error (e.g., checksum error).
7.2.1 No transmission error with normal response (Length < 255 bytes)
The response by the AET63 to a correctly received command consists of three protocol bytes, two status
bytes and a variable number of data bytes and has the following structure:

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 11 of 29
byte 1 2 3 4 5 ... N+4
(0<N<255)
N+5
Header SW1 SW2 Data length = N Data Checksum
Header 01
H
to indicate the start of the normal response.
02
H
to indicate the start of an encrypted response (support from firmware 0.67 onwards,
only used in PTVerifySC
(*)
and PTVerifySCAll
(*)
)
SW1 Indicates the command execution status:
90
H
= command successfully executed
60
H
= error in command data; command cannot be executed
67
H
= error detected in command execution
FF
H
= status message initiated by the reader
SW2 Further qualification of the command execution status.
A table listing the possible values of the status bytes SW1 and SW2 and the corresponding
meaning is given in Appendix B.
Data Length Number of subsequent data bytes (0 < N < 255)
Data Data contents of the command.
For a READ_DATA command, for example, the data bytes would contain the contents of the
memory addresses read from the card. The data bytes can represent values read from the
card and/or status information.
Checksum The checksum is computed by XORing all response bytes including header, status bytes,
data length and all data bytes.
Note (*) : Please refer to “BioTRUSTKey API Manual.doc” for the descriptions of PTVerifySC and
PTVerifySCAll.
The following example shows the structure of the response to a command which has successfully been
executed and which returns three data bytes with the values 11
H
, 22
H
and 33
H
, respectively:
byte 1 2 3 4 5 6 7 8
01
H
90
H
00
H
03
H
11
H
22
H
33
H
92
H

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 12 of 29
7.2.2 No transmission error with extended response
The response by the AET63 to a correctly received command consists of three protocol bytes, two status
bytes and a variable number of data bytes and has the following structure:
byte 1 2 3 4 5 6 7 ... N+6
(N>0)
N+7
Header SW1 SW2 Data length = N Data
Checksum
FF
H
Data Length N
Header 01
H
to indicate the start of the normal response.
02
H
to indicate the start of an encrypted response (support from firmware 0.67 onwards,
only used in PTVerifySC
(*)
and PTVerifySCAll
(*)
)
SW1 Indicates the command execution status:
90
H
= command successfully executed
60
H
= error in command data; command cannot be executed
67
H
= error detected in command execution
FF
H
= status message initiated by the reader
SW2 Further qualification of the command execution status.
A table listing the possible values of the status bytes SW1 and SW2 and the corresponding
meaning is given in Appendix B.
Data Length Number of subsequent data bytes, and is encoded in 3 bytes. The first byte is FF
H
. The
second byte and the third byte represent data length N.
Data Data contents of the command.
For a READ_DATA command, for example, the data bytes would contain the contents of the
memory addresses read from the card. The data bytes can represent values read from the
card and/or status information.
Checksum The checksum is computed by XORing all response bytes including header, status bytes,
data length and all data bytes.
Note (*) : Please refer to “BioTRUSTKey API Manual.doc” for the descriptions of PTVerifySC and
PTVerifySCAll.
7.2.3 Transmission error
If the receiving party of a command (i.e., the AET63) or a response (i.e., the computer) detects an error in
the data length or the checksum of a command, it disregards the received data and sends a "NOT
ACKNOWLEDGE" message to the transmitting party upon completion of the faulty transmission. The "NOT
ACKNOWLEDGE" message consists of two bytes:
byte 1 2
05
H
05
H

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 13 of 29
If the AET63 responds with a 'NOT ACKNOWLEDGE' message to a command from the computer, the
computer would normally transmit the command again. If the computer detects a transmission error in a
response from the AET63, it can send the 'NOT ACKNOWLEDGE' to the reader upon which the reader will
transmit the most recent response again.
7.3 Card Status Message
When a card is being inserted into the reader or an inserted card is being removed from the reader while the
reader is idle, i.e., not executing a command, the reader transmits a Card Status Message to notify the host
computer of the change in the card insertion status.
In a system where these unsolicited messages from the reader to the computer are not desired, they can be
disabled with the SET_NOTIFICATION command. Please note that the setting made with this command is
volatile and will be lost with the next reader reset or power up. By default, the Card Status Message will be
transmitted by the reader after a reset.
The Card Status Messages have the following structure and contents:
Card Status Message for Card Insertion
byte 1 2 3 4 5
Header SW1 SW2 Data length
Checksum
01
H
FF
H
01
H
00
H
FF
H
Card Status Message for Card Removal
byte 1 2 3 4 5
Header SW1 SW2 Data length
Checksum
01
H
FF
H
02
H
00
H
FC
H
A card status message is transmitted only once for every card insertion or removal event. The reader does
not expect an acknowledge signal from the computer. After transmitting a status message, the reader waits
for the next command from the computer.
NOTE - If the card is being removed from the reader while a card command is being executed, the reader will transmit a normal
response to the computer with the response status bytes indicating the card removal during command execution (see Appendix B:
Response Status Codes).
7.4 Transmission Protocol
The start of a command (to the reader) or a response (from the reader, including the Reset Message and
Card Status Messages) is indicated by the respective party through the transmission of the single byte Start-
of-Text (STX) character with the value 02
H
.
The end of a command or response is indicated through the single byte End-of-Text (ETX) character with the
value 03
H
.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 14 of 29
Within the command and response transmission only ASCII characters representing the hexadecimal (hex)
digits 0...F are used. Each byte of a command or response is split into its upper and lower halfbyte (nibble).
For each halfbyte is transmitted the ASCII character representing the respective hex digit value. For
example, to transmit the data byte 3A
H
, two bytes are actually sent on the interface, namely, 33
H
(ASCII code
for '3') followed by 41
H
(ASCII code for 'A'):
Data byte value 3A
H
Transmitted values 33
H
= '3' 41
H
= 'A'
The following example shows the transmission of a command with instruction code A2
H
and one data byte
with the value 3D
H
. The command has the following structure:
byte 1 2 3 4 5
Header Instruction Data length Data Checksum
01
H
A2
H
01
H
3D
H
9F
H
This command is transmitted on the serial interface in 12 bytes as follows:
byte 1 2 3 4 5 6 7 8 9 10 11 12
STX '0' '1' 'A' '2' '0' '1' '3' 'D' '9' 'F' ETX
02
H
30
H
31
H
41
H
32
H
30
H
31
H
33
H
44
H
39
H
46
H
03
H
For the representation of the hex halfbyte values as the corresponding ASCII characters in commands, the
AET63 accepts both upper case characters 'A' ... 'F' (41
H
... 46
H
) and lower case characters 'a' ... 'f' (61
H
...
66
H
):
byte 1 2 3 4 5 6 7 8 9 10 11 12
STX '0' '1' 'A' '2' '0' '1' '3' 'D' '9' 'F' ETX
02
H
30
H
31
H
41
H
32
H
30
H
31
H
33
H
44
H
39
H
46
H
03
H
... is equivalent to:
byte 1 2 3 4 5 6 7 8 9 10 11 12
STX '0' '1' 'a' '2' '0' '1' '3' 'd' '9' 'f' ETX
02
H
30
H
31
H
61
H
32
H
30
H
31
H
33
H
64
H
39
H
66
H
03
H
In its response messages, the AET63 uses upper case characters 'A' ... 'F'.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 15 of 29
8. COMMANDS
The commands executed by the AET63 can generally be divided into two categories, namely, Control
Commands and Card Commands.
Control Commands manage the internal operation of the AET63. They do not directly affect the card inserted
in the reader and are therefore independent of the selected card type.
Card Commands are directed toward the card inserted in the AET63. The structure of these commands and
the data transmitted in the commands and responses depend on the selected card type.
8.1 Control Commands
8.1.1 GET_ACR_STAT
This command returns relevant information about the particular AET63 model and the current operating
status, such as, the firmware revision number, the maximum data length of a command and response, the
supported card types, and whether a card is inserted and powered up.
Command format
Instruction Code Data length
01
H
00
H
Response data format
INTERNAL MAX_C MAX_R C_TYPE C_SEL C_STAT
INTERNAL 10 bytes data for internal use only
MAX_C The maximum number of command data bytes.
MAX_R The maximum number of data bytes that can be requested to be transmitted in a response.
C_TYPE The card types supported by the AET63. This data field is a bitmap with each bit representing a
particular card type. A bit set to '1' means the corresponding card type is supported by the
reader and can be selected with the SELECT_CARD_TYPE command. The bit assignment is
as follows:
byte 1 2
card type 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
See Appendix A for the correspondence between these bits and the respective card types.
C_SEL The currently selected card type as specified in a previous SELECT_CARD_TYPE command. A
value of 00
H
means that no card type has been selected.
C_STAT Indicates whether a card is physically inserted in the reader and whether the card is powered
up:
00
H
: no card inserted

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 16 of 29
01
H
: card inserted, not powered up
03
H
: card powered up
8.1.2 SELECT_CARD_TYPE
This command sets the required card type. The firmware in the AET63 adjusts the communication protocol
between reader and the inserted card according to the selected card type.
Command format
Instruction Code Data length Data
TYPE
02
H
01
H
TYPE See Appendix A for the value to be specified in this command for a particular card to be used.
Response data format
No response data
8.1.3 RESET
This section describes the RESET command only for the case when no card type is selected or when the
card type 00
H
is selected. For all other cases, please refer to the specific section described for each
individual card type.
Command format
Instruction Code Data length
80
H
00
H
Response data format
ATR
ATR The answer-to-reset string returned by the card.
The return status code for this command is 90 00
H
when the inserted card is a T=0 card, 90 01
H
when the
inserted card is a T=1 card, and 90 10
H
when the inserted card is a memory card; otherwise the status code
is 60 20
H
.
8.1.4 SET_NOTIFICATION
This command disables / enables the Card Status Messages transmitted by the reader to notify the host
computer of the insertion or removal of a card.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 17 of 29
Command format
Instruction Code Data length Data
NOTIFY
06
H
01
H
NOTIFY Specifies whether the Card Status Message shall be transmitted to notify the host computer of
card insertion / removal
01
H
: transmit Card Status Message
02
H
: do not transmit Card Status Message
Response data format
No response data
8.1.5 SET_OPTION
This command selects the options for the reader.
Command format
Instruction Code Data length Data
Option
07
H
01
H
Option Bit 0 (LSB bit): Select for PPS mode
Specifies reader card communication speed
0 : baud rate to/from the card is from 9600 bps to 96000 bps (default)
1 : baud rate to/from the card is at 9600 bps only
Bit 2 : Select smart card file type for storing fingerprint template
0 : transparent file type (default)
1 : record file type
Bit 4 : Select for EMV mode
Specifies whether the reader is in EMV mode
0 : reader not in EMV mode (default)
1 : reader in EMV mode
Bit 7 : Select for TFM mode
Specifies whether to access TFM in intercept or transparent mode
0 : Intercept mode (default)
1 : Transparent mode
Reserved
Response data format
No response data

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 18 of 29
8.2 EEPROM Commands
8.2.1 EEPROM_READ_DATA
This command is used to read the specified number of bytes from the specified address of the EEPROM.
Command format
Instruction Code Data length Data
ADDR LEN
9A
H
03
H
ADDR Byte address of first byte to be read from the EEPROM. The high byte of the address is
specified as the first byte of ADDR.
LEN Number N of data bytes to be read from the EEPROM
(0 < N ≤MAX_R)
Response data format
BYTE 1 BYTE 2 BYTE 3 ... ... BYTE N
BYTE x Data bytes read from the EEPROM memory
8.2.2 EEPROM_WRITE_DATA
This command is used to write the specified data bytes to the specified address of the EEPROM.
Note: The EEPROM used in AET63 is 24C512, with a page size of 64 bytes. The page write and page
alignment are not done in the firmware, and these should be done in the driver or application.
Command format
Instruction Code Data length Data
LEN ADDR BYTE 1 ... ... BYTE N
9B
H
LEN Number of data bytes to be written to the EEPROM, N, + 2
ADDR Byte address in the EEPROM of the first byte to be written. The high byte of the address is
specified as the first byte of ADDR.
BYTE x Byte values to be written to the EEPROM starting at address ADDR. BYTE 1 is written to
address ADDR; BYTE N is written to address ADDR+N-1.
Response data format
No response data

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 19 of 29
8.3 TFM (Trusted Fingerprint Module) Commands
8.3.1 TFM_COMMAND
This command is used to send the command to the TFM.
Command format
Instruction Code Data length Data
LEN TFM Command
9C
H
… … …
LEN Number N of command to be sent to the TFM
(0 < N ≤MAX_R)
DATA The TFM command (please refer to TFM API Documentation)
Response data format
BYTE 1 BYTE 2 BYTE 3 ... ... BYTE N
BYTE x Data bytes returned by the TFM (please refer to TFM API Documentation)
8.3.2 TFM_RESET
This command resets the TFM and then waits for the ATR returned from the TFM.
Command format
Instruction Code Data length
9D
H
00
H
Response data format
ATR
ATR Answer-To-Reset as transmitted by the TFM. Please refer to the TFM Communication Protocol
for the ATR format.
8.3.3 TFM_SMARTCARD
This is used to get list of APDUs from the EEPROM and then send the APDUs to the smart card. The list of
APDUs selects the correct file in the smart card for the enrollment or verification of the fingerprint template.

AET63 Reference Manual version 1.8 September 2006
Advanced Card Systems Ltd. Page 20 of 29
Command format
Instruction Code Data length Data
LEN ADDR
9E
H
02
H
ADDR Address of the EEPROM stores the list of APDUs. Please refer to the “Application Notes for
Handling Fingerprint Template in AET63” for detailed information
Response data format
No response data
Address 0x7F00
Address 0x0900
Address 0x0800
Address 0x0700
Address 0x0600
Address 0x0500
Address 0x0400
Address 0x0300
Address 0x0200
Address 0x0100
Address 0x0000
RECORD 0
RECORD 1
RECORD 2
RECORD 3
RECORD 4
Enroll (256 bytes max)
Enroll (256 bytes max)
Enroll (256 bytes max)
Enroll (256 bytes max)
Enroll (256 bytes max)
Verify (256 bytes max)
Verify (256 bytes max)
Verify (256 bytes max)
Verify (256 bytes max)
Verify (256 bytes max)
Key Encryption Key (24 bytes)