Inside Secure M210 Contactless Coupler, M210-2G User Manual Couverture

Download:
Mirror Download [FCC.gov]
Document ID	341170
Application ID	gsihtEC1GKm0L+A15Klt7A==
Document Description	Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	35.49kB (443604 bits)
Date Submitted	2003-07-18 00:00:00
Date Available	2003-07-18 00:00:00
Creation Date	2003-07-16 14:47:52
Producing Software	Acrobat Distiller 5.0.5 (Windows)
Document Lastmod	2003-07-17 19:17:11
Document Title	Couverture
Document Creator	Adobe PageMaker 7.0
Document Author:	jjourdain

M210-2G - Datasheet - M210-2G
INSIDE CONTACTLESS
Version 1.1
DATASHEET
M210-2G
PROXIMITY READER
13.56 MHz for ISO chips
- 14 443 type A and B
- 15 693
- FeliCa
Chips > Packaging > Readers > more...
DS 1
M210-2G - Datasheet - M210-2G
Version 1.1
Content
CHAPTER 1
M210-2G DESCRIPTION
FCC and CE compliance
System Integration
M210-2G dimensions and Pin Co-ordinates
10
Mechanical Interface – Component View
M210-2G Pin coordinates – Components View
10
10
CHAPTER 2
M210-2G CONNECTION
Power supply
12
Characteristics
Noise influence
12
12
Serial Interface
13
Character Format
Baud rate
13
13
ISO 7816 T=0 Interface
14
M210-2G coupler Input and Outputs
15
Input and Outputs characteristics
Out2P power PIN
15
15
How to reset M210-2G couplers
16
Software reset
Hardware reset
16
16
DS 2
M210-2G - Datasheet - M210-2G
Version 1.1
CHAPTER 3
COMMAND INTERFACE
REFERENCE MANUAL
HOST - COUPLER protocol
description
Block protocol
Protocol configuration
LRC
Coupler commands overview
SELECT_CARD
SELECT_PAGE
10
TRANSMIT
12
GET_RESPONSE
14
READ_STATUS
15
SET_STATUS
16
Modifiable parameters
Coupler’s INPUTs AND OUTPUTS
EEPROM free area
17
18
18
DISABLE_COUPLER
19
DISABLE_COUPLER ENHANCED
20
ENABLE_COUPLER
21
ASK_RANDOM
22
LOAD_KEY_FILE
23
SELECT_CURRENT_KEY
24
DIVERSIFY_KEY
25
GET_CONFIG
26
DS 3
M210-2G - Datasheet - M210-2G
Version 1.1
CHAPTER 4
USER’S GUIDE
Managing INSIDE chips
Security configuration
Selecting a chip
Selecting a page
Reading chip memory
Writing chip memory
Halting a chip
How to work with several chips in the field
Managing INSIDE’s chips protocols
10
Managing the security
11
INSIDE chips security
Key loading
How to set a key as the active one
How to authentify a chip
How to authentify a PAGE
Protecting the keys
11
13
14
15
15
16
Managing STANDARD chips protocols
17
Time out adjustment
15 693-3 protocol
ISO 14 443 type A
ISO 14 443 type B
FeliCa ( new version)
17
17
18
18
18
Managing the RF field
19
How to reset the RF field ?
How to asleep the coupler
How to wake up the coupler
19
19
19
APPENDIX A
HOW TO LOAD A KEY IN A COUPLER
Exchange key
21
General key loading procedure
21
Terminology and notation
22
Key loading step by step
22
Algorithms
23
Key permutation
Checksum byte calculation
Load key checksum calculation
23
23
23
APPENDIX B
ERROR CODE
DS 4
Main Features :
M210-2G - DATASHEET - M210-2G
√ Serial host interfaces:
Version 1.1
!ISO 7816-3 (T=0) compatible interface
!RS-232 CMOS interface
√ Security management:
!Security module
!Secure key loading
√ Secured Key Storage
√ Contactless interfaces:
!ISO 15 693
!ISO 14 443 type A
!ISO 14 443 type B
!FELICA TM
√ Contactless transmission of data and energy supply
√ Carrier frequency: 13.56MHz
√ On board antenna
√ Transparent mode for contactless data exchange
√ Supply voltage: 5V only
√ Low power consumption < 50 mA
√ Stand-by mode < 50 µA
√ Small PCB size: 61 x 41.5 mm
√ Operating temperature range: -20°C to +50°C
√ Emission approval* : FCC, IDA singapore, Canadian, CE
Product Ordering Code
Product
Ordering code
Package
Tools
Proximity Coupler M210-2G
M210-2G
PCB
* Note : The chassis will not allow ESD air discharge at voltage over 8 kV. The distance
between the chassis and its packaging has to be superior to 0.68 mm.
DS - 5
M210-2G - DATASHEET - M210-2G
Version 1.1
CHAPTER 1
M210-2G DESCRIPTION
M210-2G couplers are developed by INSIDE contactless for
managing the RF communication interface with 13.56 MHz standard
chips.
They have the following features :
Operating frequency
Host interface
Target applications
Target chip
13.56MHz
RS-232 CMOS / ISO 7816 T=0*
Proximity and short range
applications
All INSIDE’s chips, 15693 chips,
14443 chips (type A and type B),
FELICA TM
You will find in this chapter ...
! two ways to build your application with INSIDE’s couplers
! coupler’s mechanical characteristics (PIN position, size...)
Afterwards, the term «coupler» stands for an electronic board that
converts numeric commands into contactless chip commands using
the RF interface.
* Note : The host interface is not fully compliant with the ISO 7816
T=0 protocol. But all the coupler’s commands are builded on this
format so that its integration in a device using this protocol is very
easy.
DS - 6
FCC AND CE COMPLIANCE
M210-2G - DATASHEET - M210-2G
Federal Communications COMMISSION (FCC) Part 15 STATEMENT
Version 1.1
This equipment has been tested to FCC requirements and has been found acceptable for
use. The FCC requires the following statement for your information:
This equipment generates and uses radio frequency energy and if not installed and used
properly, that is, in strict accordance with the manufacturer’s instructions, may cause
interference to radio and television reception. It has been type tested and found to comply
with the limits for a Class B computing device in accordance with the specifications in
Part 15 of FCC Rules, which are designed to provide reasonable protection against such
interference in a residential installation. However, there is no guarantee that interference
will not occur in a particular installation. If this equipment does cause interference to radio
or television reception, which can be determined by turning the equipment off and on, the
user is encouraged to try to correct the interference by one or more of the following
measures:
·
If using an indoor antenna, have a quality outdoor antenna installed.
·
Reorient the receiving antenna until interference is reduced or eliminated.
·
Move the radio or television receiver away from the receiver/control.
·
Move the antenna leads away from any wire runs to the receiver/control.
·
Plug the receiver/control into a different outlet so that it and the radio or
television receiver are on different branch circuits.
This device complies with part 15 of the FCC rules. Operation is subject to the following
two conditions : (1) this device may not cause harmful interference, and (2) : this device
must accept any interference received, including interference that may cause undesired
operation
If necessary, the user should consult the dealer or an experienced radio/television technician
for additional suggestions. The user or master may find the following booklet prepared by
the Federal Communications Commission helpful: «Interference Handbook»
This booklet is available from the U.S. Government Printing Office, Washington, DC 20402.
The user shall not make any changes or modifications to the equipment unless authorized
by the Installation Instructions or User’s Manual. Unauthorized changes or modifications
could void the user’s authority to operate the equipment.
Model: M210-2G
Made in France
Canada
210
FCC ID: Q45M210
This device may not cause
harmful interference
Complies with IDA Standards
DA102907
Electrical Rating: 5.0V
45mA
DS - 7
M210-2G - DATASHEET - M210-2G
System Integration
Version 1.1
Diagrams below show coupler’s block diagram and architecture of 2 types of applications:
1. Coupler is integrated in a stand alone reader (access control, data collection...)
2. Coupler is connected to a computer
Emitter
Processor
Ant
Receiver
Com interfaces
Power supply
M210-2G Block Diagram
Stand Alone
Application
code
Power Supply
Microcontroller
Coupler
Application data
memory
External
drivers
PicoTag
transponder
I/O
Example 1: Stand Alone Reader Structure
DS - 8
M210-2G - DATASHEET - M210-2G
Version 1.1
Driver
RS232
TTL
Power supply
Coupler
PicoTag
transponder
Example 2: Contactless Coupler Interface
DS - 9
M210-2G - DATASHEET - M210-2G
M210-2G dimensions and Pin Co-ordinates
Mechanical Interface – Component View
M210H size : 61 mm * 41.5 mm (+/- 1 mm)
M210-2G Pin coordinates – Components View
Pin pitch is 2.54 mm
Version 1.1
DS - 10
M210-2G - DATASHEET - M210-2G
Version 1.1
CHAPTER 2
M210-2G CONNECTION
This chapter describes :
! How to power the coupler
! How to communicate with the coupler through the serial line
! How to connect the INPUT and OUTPUT ports
DS - 11
M210-2G - DATASHEET - M210-2G
Power supply
Version 1.1
CHARACTERISTICS
To power up the coupler, just set Vdd PIN to 5V, and connect the ground.
PIN
description
Min.
Typical
Max.
Unit
VDD
DC voltage
4.75
5.25
50
mVss
Ripple<30MHz
Supply current
50
mA
Electrical characteristics
NOISE INFLUENCE
If coupler is integrated in a noisy environment, a PI filter on the power supply line is needed
to lower the noise level. It has to be as close as possible to the coupler.
If a RS232 driver is used, it may induce noise on the power supply line, and a PI filter
should be added. More over, noise induced by this kind of device is around 400kHz, which
is the frequency used by the 15 693 protocol. To avoid any problem on our coupler (noise
emission), or on any other device connected to the power supply line, a PI filter should be
added also on the power supply line of the RS 232 driver, as close as possible to this
component.
Vcc
10µF
10µH
10µF
Driver RS232
10µF
Serial
line
10µH
Rx Tx
Vcc
10µF
Coupler
Filter component values are choosen so that frequencies under 1MHz are eliminated. This
will avoid RF noise on the coupler receiver.
DS - 12
Serial Interface
M210-2G - DATASHEET - M210-2G
This interface allows a serial connection to the host via three wires :
Version 1.1
Configuration
RS-232 CMOS
ISO 7816 T=0
RST
RST
RST
TX
TX
I/O
RX
RX
I/O
RST resets the coupler microprocessor when tied to the ground.
Character Format
Data Rate
Parity
Number of bits
Transmission Mode
Stop bits
Flow control
9600 baud (default value)
Even
LSB first
none
Note : If user’s UART cannot manage 2 stop bits, it is possible to communicate with our
coupler using only one stop bit.
8 bits
SelectCard command frame
Baud rate
The default data rate is set at 9600 baud, but this can be changed by software to select
higher data rates :
9600
19600
38400
57600
115200
Noise
If a RS232 driver is used, it may induce noise on the power supply line, and a PI filter
should be added. More over, noise induced by this kind of device is around 400kHz, which
is the frequency used by the 15 693 protocol. To avoid any problem on our coupler (noise
emission), or on any other device connected to the power supply line, a PI filter should be
added also on the power supply line of the RS 232 driver, as close as possible to this
component.
DS - 13
M210-2G - DATASHEET - M210-2G
ISO 7816 T=0 Interface
Version 1.1
By connecting TX and RX, a single I/O inspired from ISO 7816 T=0 is obtained.
This interface is fully described in the ISO 7816 standard. It allows the coupler to be driven
directly as in an ISO contact connector or SAM module with the T=0 protocol, thereby
utilising any existing smart card software drivers.
ISO contacts
C1: VCC
C2: RST
C3: CLK
C4: C5: GND
C6: VPP
C7: I/O
C8: -
Interface
VDD
RST
(internal clock)
GND
TX – RX connected
The CLK signal used in ISO 7816 T=0 is an internal clock (default data rate = 9600 baud).
DS - 14
M210-2G coupler Input and Outputs
M210-2G - DATASHEET - M210-2G
M210-2G readers has one input and 2 outputs. A PIN can be used to power up a LED
(OUT2P)
Version 1.1
Input and Outputs characteristics
•
•
•
Input : CMOS Schmidt trigger input
- level 0 : Vin < 1
- level 1 : Vin > 4
Output 1 : TTL 5V output
Output 2 : TTL 5V output
Out2P power PIN
This PIN is connected to the 5V through a 1KΩ resistor. It can be used to power supply a
LED for exemple.
DS - 15
How to reset M210-2G couplers
M210-2G - DATASHEET - M210-2G
Resetting the coupler may be useful in two situation :
Version 1.1
a. to set the parameters (speed, disable mode, protocol settings, keys ) to the defaults
values. All these values are stored in coupler’s internal EEPROM
b. if it is impossible to communicate with the coupler (bad setting for serial communication speed mainly)
SOFTWARE RESET
It is possible to reset the coupler’s EEPROM by sending 2 commands thanks to the SET
STATUS command.
Command = $80,$F4,$80,$3E,$01 - Data = $00
Command = $80,$F4,$80,$7E,$01 - Data = $00
Then the coupler has the default setting : 9600 bds, defaults protocols....
HARDWARE RESET
If for any reason it becomes impossible to communicate with the coupler, follow this
procedure :
•
•
•
•
switch off the coupler
connect the 2 reset pins as indicated in the drawing below
power up the coupler : it will start with the default factory parameters
reset the EEPROM as indicated above
The coupler is reseted.
DS - 16
Coupler - Reference manual
Version 1.0
CHAPTER 3
COMMAND INTERFACE
REFERENCE MANUAL
In this chapter you will find the command format, and the description
of all the commands used by the coupler.
User may refer to this chapter to find the following information :
! low level description of data exchange between coupler
and host, mainly when using microcontroller or an
automat
! check the signification and/or a value of a command
parameter
RM 1
Coupler - Reference manual
HOST - COUPLER protocol
Version 1.0
DESCRIPTION
The commands are modeled on the ISO 7816 command set. This protocol is used by all
INSIDE’s couplers
A typical protocol exchange includes:
1. The host sends a command to the coupler
2. The coupler executes the command
3. The host receives a response from the coupler
Coupler command is always constituted of 5 bytes :
•
•
•
•
•
CLASS : always 80h
INSTRUCTION : command to be executed by the coupler (like SelectCard)
P1 : Command parameter
P2 : Command parameter
P3 : Command parameter
Depending on the command, coupler answers data, status words.
There are 4 cases of data exchange:
Case
Host to coupler Coupler to Host
ISO Type
None
None
ISO None
None
Yes
ISO Out
Yes
None
ISO In
Yes
Yes
ISO In / Out
Note : In case 4, data has to be sent and received from the coupler. With T=0 protocol, it
is not possible in a single command, so this command has to be split into 2 commands:
RM 2
Coupler - Reference manual
ISO In : The host sends a command + data and receives the status words.
ISO Out : The host sends a command and receives data + the status words.
Coupler with firmware former than 40-017F has only ISO NONE, ISO IN and ISO OUT
protocol available.
In all cases, status words are returned (SW1 and SW2).
Case 1: ISO None Data Exchange
Command
Host
Cla.
Ins.
P1
Status words
P2
P3
SW1
Coupler
5 bytes
nb of bytes
SW2
2 bytes
Case 2 : ISO Out Data Exchange - Coupler # Host
Command
Host
Cla.
Ins.
P1
P2
Data
Status words
= Ins.
data
SW1
= P3
P3
Coupler
nb bytes
Ack.
SW2
Class : always 80h
Instruction : command code
P1 & P2 : command parameters
P3: number of data bytes expected from the coupler
Ack. : coupler acknowledgement. It is always equal to the command code, except when
an error occurs. If the Acknoledgement value is different than the instruction byte, then
the received byte is the first byte of a status error code coded on 2 bytes.
Data : data sent to the host by the coupler. Size of the command has to be P3.
Status word : 90 00h if correct, error code.
Case 3: ISO In Data Exchange - Host # Coupler
Ack.
Command
Host
Cla.
Ins.
P1
P3
Status words
Data
= Ins.
Coupler
nb bytes
P2
Data
SW1
= P3
SW2
Class : always 80h
Instruction : command code
P1 & P2 : command parameters
Version 1.0
RM 3
Coupler - Reference manual
P3: number of data bytes sent to the coupler.
Ack. : coupler acknowledgement. It is always equal to the command code, except when
an error occurs. If Acknowledgement value is different than instruction byte, then the
received byte is the first byte of a status error code coded on 2 bytes.
Data : data sent by host to the coupler. Size of data array has to be P3.
Status word : 90 00h if correct / error code.
Error : If the Acknowledgement value is different than the instruction byte, then the received
byte is the first byte of a status error code coded on 2 bytes.
Case 4 : ISO InOut Data Exchange - Host ⇔ coupler
Command
Host
Cla.
Ins.
P1
Ack.
P2
P3
Ack.
Data out Status words
= Ins.
Data out SW1 SW2
Data in
= Ins.
Coupler
nb bytes
Data in
= P3
=P2
Class : always 80h
Instruction : command code
P1 : command parameters
P2 : number of data bytes expected from the coupler.
P3 : number of data bytes sent to the coupler.
Ack. : coupler acknowledgement. It is always equal to the command code, except when
an error occurs. If Acknowledgement value is different than instruction byte, then the
received byte is the first byte of a status error code coded on 2 bytes.
Data : data sent to the host by the coupler. Size of the command has to be P3.
Status word : 90 00h if correct / error code.
BLOCK PROTOCOL
The block mode is based on the exchange of a block sent from the host to the coupler and
after a block sent back from the coupler to the host. By this way there is no break in the
flow host-coupler. The diagram below describes this block protocol.
BLOCK
Host
Coupler if no
error in
processing
Coupler if error
in processing
Send 5 bytes
command
CLASS|INS|P1|P2|P3
Send P3
Data if any
Send an
optional LRC
Send an
acknow ledge
(INS)
Return a
status w ord
Return
Data
Return a
Send an
status w ord optional LRC
Send an
optional
LRC
LRC enables the user to check is the transmission has been performed correctly. See next
paragraph for more information.
Note: Block protocol is only available on 2G version of our readers.
Version 1.0
RM 4
Coupler - Reference manual
PROTOCOL CONFIGURATION
Version 1.0
In order that the coupler knows how much data it is supposed to receive and suppose to
send back, the CLASS byte is used to indicate how it should operate. The default value
for the CLASS byte is 0x80. To implement the block mode, the three first bits have been
used.
CLASS
BITS CLASS
(MSB..LSB)
VALUE
10000000
0x80
MEANING
Standard ISO-7816-3 T=0 protocol
10000001
0x81
Block protocol with no data from host
and back from coupler
10000011
0x83
Block protocol with no data down from
host and P3 data back from coupler
10000100
0x84
Block protocol with P3 data down from
host and no data back from coupler
10001000
0x88
Block protocol with P3 data down from
host and P1 data back from coupler
10001100
0x8C
Block protocol with P3 data down from
host and P2 data back from coupler
10001110
0x8E
Block protocol with P3 data down from
host and P3 data back from coupler
LRC
The block diagram mentions an optionnal LRC (Longitudinal Redundancy Checksum) or
CRC (Cyclic Redundancy Checksum) can be appended in the flow. This option is controlled
by a parameter into the coupler configuration which can be set via the command
SET_STATUS.
Calculation
LRC is the result of the XOR of all the bytes sent by the host including command and the
P3 data bytes. If the LRC does not correspond to the LRC calculated by the coupler, the
coupler will response with a status word equal to $6F$00.
The example below shows how the LRC is calculated:
$82$C0$00$00$03 + $01$02$03 + $41 because $41 = $82 xor $C0 xor $00 xor $00 xor
$03 xor $01 xor $02 xor $03.
The LRC calculation is equivalent to the CRC8 calculation with a poly equal to 1.
RM 5
Coupler - Reference manual
Setting the LRC
Version 1.0
The parameter P1 in the SET_STATUS command defines if the value has to be written into
the no-volatile memory EEPROM or into the volatile memory called PARAM.
If P1=0x00 then you specify the EEPROM, if P1=0x03 you specify the PARAM area.
If the user wants to use an LRC, he just has to write $01 at address $70 as follow:
•
•
$80$F2$03$70$01 + $01 : for PARAM area
$80$F2$00$70$01 + $01 : for EEPROM area.
If the user does not want to use LRC, he just has to define the poly to 0 as follow, and then
no control byte will be automatically checked or added:
•
•
$80$F2$03$70$01 + $00 : for PARAM area
$80$F2$00$70$01 + $00 : for EEPROM area.
RM 6
Coupler - Reference manual
Coupler commands overview
Version 1.0
Command
INS
Description
SELECT_CARD
‘A4h’
Selects one contactless card following list of
possible cards in the field
SELECT_PAGE
‘A6h’
Selects a page in a multi-application chip
TRANSMIT
‘C2h’
Sends and retrieve data from chip through
contactless interface : Transparent mode
GET_RESPONSE
‘C0h’
Reads the internal buffer of the coupler to retrieve
chip answer for ISO 7816 T=0 protocol.
Command
INS
Description
READ_STATUS
‘F2h’
Reads coupler status or EEPROM memory.
SET_STATUS
‘F4h’
Sets the coupler status or write in EEPROM
memory.
DISABLE_COUPLER
‘ADh’
Disables the coupler. it will only respond after a
ENABLE_COUPLER command.
ENABLE_COUPLER
‘AEh’
Enable the coupler. It wakes up the coupler after
a DISABLE_COUPLER command.
Command
INS
Description
LOAD_KEY_FILE
‘D8h’
Load new master keys for authentication
purposes.
ASK_RANDOM
‘84h’
Ask for a random number from the coupler.
SELECT_CURRENT_KEY
‘52h’
Select the key to be used for authentication
purposes.
Security module functions :
RM 7
Coupler - Reference manual
SELECT_CARD
Version 1.0
Use
Select a card in order to get the serial number. This command manages anti-collision and
authentication features.
This command is able to test several communication protocol. It answers the number of
protocol used to select the card.
Prototyping
Command sent : A4h
Command type : ISO out
Host
80h
A4h
P1
P2
P3
Coupler
A4h
Card type Serial number
90h
00h
Parameters
Bit
Function
Key
Auth Presel. Loop
Halt
Wait
P1: Parameter used for contactless configuration
IMPORTANT: ‘ – ‘ are reserved for future use, and values should be set to 0.
WAIT :
1: Wait until a card is selected or a character received from the host (e.g. PC).
0: Exit if no card is detected after 3 attempts.
Note: When SELECT_CARD uses the option «LOOP», the coupler sends
ACK=60h (See T=0 specifications) after each unsuccessful selection until
a card is selected. When a card is selected, «90h 00h» is returned. In order
to stop this scanning, host has to send a byte through the RS232 interface.
HALT:
1: Halts card after selection for fast serial numbers capture.
0: No halt after selection.
LOOP:
1: returned a frame composed of ACK | CARD TYPE | SN | 9000h or wait character
60h
0: no loop performed.
PRE:
1: Increases pre-selection with INSIDE CONTACTLESS anti-collision and a large
number of cards.
0: Standard anti-collision (best for 5 cards max.).
AUTH:
1: Performs a standard INSIDE authentication.
Authentication is performed if the key is set as the current key.
Please refer to appendix A : «How to low a key» for key loading and key management
operations details.
0: Does not perform an authentication.
RM 8
KEY:
Coupler - Reference manual
1: Authenticates with Debit Key (Kd = Key 1) if AUTH is set.
0: Authenticates with Credit Key (Kc = Key 2) if AUTH is set.
Version 1.0
P2: Parameter used for selecting the card types to be read
b7 - b4
b3
b2
b1
b0
Protocol 3
Protocol 2
Protocol 1
Protocol 0
INSIDE couplers manage the following protocols :
- Protocol 0 : ISO 14 443 type B & Inside anticollision (only for INSIDE chip)
- Protocol 1 : ISO 15 693 & Inside anticollision (only for INSIDE chip)
- Protocol 2 : ISO 14 443 type B-3
- Protocol 3 : User defined protocol - see «Other ISO chip management» chapter for more
information about Protocol 3 use.
If bit related to protocol x is set to one, coupler will run an anticollision using this protocol.
If several protocols are selected, coupler will test all of them, starting from protocol 0 to
protocol 3.
P3: Number of bytes to be return by the coupler
Set P3 = 09h for reading Pico Family Chips serial numbers.
Response: Card type (1 byte) and serial number (8 bytes)
Card type is the protocol number used by the card that has been selected for its answer.
For 15 693 INSIDE’s chips, card type value is 1 as protocol 1 is used for selection. This
value is the one to use to indicate protocol in the transmit command.
RM 9
SELECT_PAGE
Coupler - Reference manual
Use
This command is used to select and authenticate in an INSIDE multi-application chip
(8*2Ks...).
Prototyping
Command sent : A6h
Command type : ISO Out
Host
80h
A6h
P1
P2
08h
Chip 's
configuration
block
A6h
Coupler
90h
00h
Parameters
Bit
Function
Auth
Page
selection
Protocol type
P1: Parameter used for contactless configuration
b3 : Auth
0 - Does not perform authentication after PAGESEL.
1 - Performs authentication after PAGESEL
b2: Select Page
0 - Does not send the PAGESEL command before authentication
1 - Sends the PAGESEL command with page contained in P2 before authentication
Note : b2=b3=0 imply that no operation is performed
b1-b0: Protocol type:
This command can only work with PICO family chips
Contactless Communication Protocol
00
ISO14 443 B PICO family chips
01
ISO15 693 PICO family chips
10
ISO14 443 B-3
11
User’s protocol
P2 : Page number to select and authenticate and cryptographic key to use
Bit
Function
Reader key number
Page number
b7-b4 : Reader key number
Note : 0 correspond to Kd0, 1 to Kc0, …, 14 to Kd7 and 15 to Kc7.
This is the reader key number to use during authentication. The reader will use this
Version 1.0
RM 10
Coupler - Reference manual
key number (EEPROM) to diversify and authenticate the requested page with Kd or
Kc.
Version 1.0
b3 : Page’s key to use to perform the authentication
0 : authentication will be performed with page’s debit key.
1 : authentication will be performed with page’s credit key.
b2-b0 : Page number to select
P3 : Chip answer length
This parameter has to be set to 8 as the chip answers the page’s configuration block (8
bytes).
RM 11
TRANSMIT
Coupler - Reference manual
Use
Version 1.0
Transmits data from the coupler to the chip and read back chip response.
This command is the one to use to read and write data in the chip.
Prototyping
Command sent : C2h
Command type : ISO In / Out
Host
80h
C2h
P1
P2
P3
Data
C2h
Coupler
Chip answer
90h
00h
P1 : Defines the contactless communication protocol
P2 : Chip answer length
P3 : Chip command and data
Parameters
P1: Parameter used for contactless configuration
Bit
Function
Send Check
CRC CRC
Time out
Send
signature
ISO
type
RF protocol
type
b7: Send CRC:
1: The coupler automatically sends the CRC (function of the Data bytes) to the
chip. Coupler uses the CRC associated to the choosen protocol (bit 1 & 0)
0: Only P3 data bytes are sent.
b6: Compare CRC:
1: Compares the returned CRC with the expected value calculated by the coupler
(verify the data sent by the chip).
0: CRC is not checked.
b5-b4: Time Out:
The time out value depends of the protocol used (b1 and b0 values).
The time out is the time from the command’s EOF (End Of Frame) to the chip
response SOF (Start of Frame).
Bits 4& 5
Time-out
15 693
Time-out
14 443
00
800 µs
200 µs
01
4 ms
1 ms
10
24 ms
6 ms
11
40 ms
10 m
RM 12
Coupler - Reference manual
b3: Send Signature:
1: Send a cryptographic signature calculated thanks to the coupler security module.
This option may be used only for UPDATE command performed on secure PICO
family chip. Set this value to 0 for non secure chip or any other manufacturer chips
Version 1.0
0: Cryptographic signature is not sent.
b2 : HOST - COUPLER protocol type
1 : Communication is ISO IN-OUT. Coupler send back the data as soon as it
receives chip answer.
0 : Commucation between HOST and coupler follows the ISO 78-16 T=0 protocol.
Thus TRANSMIT command is only ISO IN, and user has to use the GET REPONSE
command to retrieve chip DATA from the coupler.
b1-b0: Protocol type:
Defines the contactless communication protocol number to be used. When
coupler’s EEPROM is set with the default values, the protocol types are as follows:
Contactless Communication Protocol
00
ISO14 443 B PICO family chips
01
ISO15 693 PICO family chips
10
ISO14 443 B-3
11
User protocol (default value : ISO 14 443 A-3)
P2 : Number of data bytes received from the chip after transmission of the
command.
If the Compare CRC bit of P1 is enabled, P2 should not include the CRC bytes.
Note: P2<=35 (23h).
P3 : Number of bytes in the data field of the command.
If the Send CRC or the Send Signature bit of P1 is enabled, P3 should not include the
CRC bytes or the signature.
Note: P3<=32 (20h).
Data: Commands and data to send to the chip
All PICOTAG commands are detailed in PICOTAG datasheet.
Response:
Chip answer
Status word.
RM 13
GET_RESPONSE
Coupler - Reference manual
Use
Version 1.0
This command returns the value contained in the internal buffer of the coupler.
It has to be used to get chip answer when the TRANSMIT command is used with the ISO
IN type to retreive the chip answer.
Prototyping
Command sent :C0h
Command type : ISO out
Host
80h
C0h
00h
00h
P3
Coupler
C0h
Coupler
buffer
90h
00h
Parameters
P3: Number of bytes of the coupler response. It has to be less than 35 (23h).
Response : Coupler’s buffer and status words
RM 14
READ_STATUS
Coupler - Reference manual
Use
Version 1.0
This command is used to get coupler parameters (communication speed…).
Prototyping
Command sent : F2h
Command type : ISO out
Host
80h
F2h
P1
P2
01h
Read
bytes
F2h
Coupler
90h
00h
Parameters
P1: type of parameter to read
b7 - b2
b1 - b0
Parameter
location
0 (RFU)
b1-b0 : Parameter location
$ 00 : Parameter value is read in coupler’s EEPROM (setting when power
on)
$ 01 : Coupler’s I/O
$ 10 : Reserved for Future Use
$ 11 : Parameter value is read in coupler’s RAM (current setting)
P2: set the parameter address to read
Valid values for P2 according to P1 value:
EEPROM:
00h to FFh.
I/O:
05h and 07h.
Parameter:
50h to 6Fh.
Response : byte value at the transmitted address + status word
Note: When reading the I/O, the Read byte returned indicates the IN1, OUT1, OUT2 pin
states as follows: (OUT2P is connected to VDD via a 1kÙ- resistor).
I/O Address
b7
b6
b5
b4
b3
b2
b1
b0
05h : Output
OUT2
OUT1
07h : Input
IN
RM 15
Coupler - Reference manual
SET_STATUS
Use
This command sets configuration parameters and coupler’s I/O :
Communication speed
Protocols
State at Power ON
2 outputs & 1 input
The various parameters and data used by INSIDE couplers are stored in the EEPROM.
When coupler is powered on, a part of these parameters are load in coupler’s RAM, so
that parameters may be modified in coupler’s EEPROM and in coupler’s RAM.
For a given parameter, RAM and EEPROM address are the same. For example, speed
parameter is located at address 6Dh for both RAM and EEPROM.
When updating a value in the coupler’s EEPROM, this value will be the default
value after turning the coupler on.
When updating a value in the coupler’s RAM, this value will be the current value
until the next Power Off.
When writing to EEPROM occurs, EEPROM parameters are reloaded into processor
memory (RAM).
Prototyping
Command sent : F4h
Command type : ISO In
Host
80h
F4h
P1
P2
01h
Data
F4h
Coupler
90h
00h
Parameters
P1: Sets the type of configuration parameter to update
b7
b6
b5-b2
b1 - b0
Reset coupler
Reset magnetic
field
- (RFU)
Address
b7 : Resets coupler
if this bit is set to 1, coupler will fully reload EEPROM in RAM as if the coupler is powered
on.
Note : when b7 = 1, the coupler responds 3Bh 00h.
b6 : Reset magnetic field
Magnetic field is cut for 20 ms.
When this bit is set to 1, coupler will execute no other action, including EEPROM or RAM
update.
b5-b2 : RFU (reserved for future use)
Version 1.0
RM 16
Coupler - Reference manual
Version 1.0
b1-b0 : Parameter location
" 00 : Parameter value is read in coupler’s EEPROM (setting when power
on)
" 01 : Coupler’s I/O
" 10 : Reserved for Future Use
" 11 : Parameter value is read in coupler’s RAM (current setting)
P2: Sets the parameter address to update
Valid values for P2 according to P1 value:
EEPROM : 00h to 07h and 3Eh to FFh.
I/O :
05h, 06h, 07h.
RAM :
50h to 6Fh.
Response: Status words
MODIFIABLE PARAMETERS
User can change the following parameters in coupler’s memory :
Protocols - Please refer to «Managing ISO protocol with INSIDE coupler» application
note for more information about protocol management
Serial communication speed - from 9600 to 424000 bauds depending on the
reader
Name
Serial
communication
speed
Address
State
Hex. value
9600
57h
19200
2Dh
38400
15h
57600
0Eh
115200
06h
Available on...
All readers
6Dh
All readers
except M22xH
Note 1 : When updating the COMSPEED parameter, the coupler returns the Status Words
with the previous COMSPEED before the COMSPEED update.
Example : the baudrate is set to 9600 bauds and needs to be temporarily updated to 115
200 bauds.
Send a SET_STATUS command (80h F4h 03h 6Dh 01h & 06h). The coupler responds
(Status words) using 9600 bauds.
State at power on - Is coupler emitting a field when it is powered on ? (please refer
to ENABLE and DISABLE command chapters)
Name
Address
State at
power on
42h
State
Hex. value
Enable
01h
Disable
00h
Available on...
All reader
RM 17
Coupler - Reference manual
Version 1.0
Note 2 : The ACTIVATE AT POWER ON parameter defines the state of the coupler when
you turn it on.
If you turn the coupler on and if 00h is written in the EEPROM at address 42h , it will be
«asleep» until you send an ENABLE_COUPLER command.
IMPORTANT NOTE : If change in the EEPROM is followed by a reset of the coupler
and if address 42h contains 00h then the coupler will be asleep until you send an
ENABLE command.
COUPLER’S INPUTS AND OUTPUTS
Please refer to chapter 1 for connection.
Input / Output
I/O address
Command to
use
OUT1
05h - Bit 1
Set Status
OUT 2
05h - bit 2
Set Status
IN 1
07h - bit 0
Read Status
M22xH
OUT
05h - bit 2
Set Status
M302H
OUT
06h - bit 4
Set Status
Reader
M21xH
ACCESSO
LED
05h
Set Status
Value
Bit at 0 : low level
Bit at 1 : High level
Byte value & color
04h : Red
08h : Orange
0Ch : Green
EEPROM FREE AREA
User can use EEPROM bytes from 70h to 7Dh to write some data.
RM 18
Coupler - Reference manual
DISABLE_COUPLER
Version 1.0
Use
The coupler goes in SLEEP mode that allows low power consumption and RF carrier is
desactivated.
After this command, the coupler will not respond to any command except the
ENABLE_COUPLER command.
A new feature available only on M21xH 2G is that coupler can detect if a card approach
the antenna and wake up on its own.
Prototyping
Command sent : ADh
Command Type : ISO none
Host
80h
ADh
Coupler
BCh
DAh
01h
90h
00h
Parameters
Response: Status words
Note : It is possible using the SET_STATUS command to have the coupler in a sleep
mode each time it turns on. The coupler will then be asleep until you send an
ENABLE_COMMAND. Please refer to the SET_STATUS command for activating this
feature.
RM 19
Coupler - Reference manual
DISABLE_COUPLER ENHANCED
Version 1.0
Note : This command is only available on :
- M210-2G
- ACCESSO-2G
Use
As the DISABLE_COUPLER command, this specific version enables the user to asleep
the reader.
But M210H 2G and M260H 2G have the possibility to detect that a card approaches their
antenna.
As sooon as the card is detected, the coupler will turn the RF field on, and start a card
selection.
If no card answers to the anticollision process, the coupler go back asleep. If a card is
selected, then the coupler stay awake.
Prototyping
Command sent : ADh
Command Type : ISO none
Host
80h
ADh
BCh
P2
01h
90h
Coupler
00h
Parameters
P2 : specify the anticollision to process when a card is detected. If several bit are set at 1,
all selected anticollision will be performed.
b7
b6
b5
b4
b3
b2
b1
b0
Pulse
OUT1
Ant3
Ant2
Ant1
Ant0
•
•
If Antx bit is set, then the anti-collision x will be processed else not.
If no Antx is set, then the coupler will wake-up only by detecting a field change over
the reader.
•
If b4 is set, then the OUT1 PIN is set to high for 10 ms when a card is selected.
Note : It is possible using the SET_STATUS command to have the coupler in a sleep
mode each time it turns on. The coupler will then be asleep until you send an
ENABLE_COMMAND. Please refer to the SET_STATUS command for activating this
feature.
RM 20
Coupler - Reference manual
ENABLE_COUPLER
Version 1.0
Use
This command restores a normal coupler running, with RF emission.
This command can only be used after a DISABLE_COUPLER command or if the coupler
is desactivated after power on.
Prototyping
Command sent : AEh
Command type : ISO none
Host
80h
Coupler
AEh
DAh
BCh
00h
3Bh
00h
Parameters
Response : Status words
The coupler will respond «Instruction not recognized» (6Dh 00h) if already activated.
Important note : You have to send the ENABLE_COUPLER command in a window
of 16ms. To be sure that your command will be received, send it twice. The time
between the sending of the 2 commands has to be less than 10 ms.
This is automatically done when using MX.Enable method (ActiveX component).
RM 21
ASK_RANDOM
Coupler - Reference manual
Use
Version 1.0
This command returns an 8 bytes random value from the coupler.This command has to be
used to initialize the key loading procedure.
Prototyping
Command sent : 84h
Command type : ISO out
Host
80h 84h 00h 00h 08h
Coupler
84h Random number
90h
00h
Parameters
Response : Random number; Status words
RM 22
Coupler - Reference manual
LOAD_KEY_FILE
Version 1.0
Use
This function loads into the coupler’s security module a key to be used for authentication
and security purposes.
Key loading is a security sensitive operation. In order to protect the confidentiality of the
keys transferred to the coupler, data is encrypted. A 4-byte checksum is also sent in
order to guarantee the authenticity of the data, which could be corrupted either through
transmission errors or by a deliberate attempt to fraud the system.
Refer to «Coupler’s key loading» chapter for more information about security and the way
to calculate encrypted key and checksum.
Prototype
Command sent : D8h
Command type : ISO In
Host
80h
D8h
P1
P2
Coupler
OCh
Data
D8h
90h
00h
Parameters
P1 : Parameter used for key operations
00: Load and activate the key pointed by P2.
01: Deactivate the key pointed by P2 (Forbidden option to Exchange Key Ke).
02: Delete the key pointed by P2 (Forbidden option to Exchange Key Ke).
Others value are reserved for future use.
Notes:
With the 00 option, this command will replace the old value of the key with the new value.
With the 01 and 02 options, the command has to be sent with 12-byte data at any value
(Data = XX XX XX XX XX XX XX XX XX XX XX XX).
When a key is deactivated, you need to reload it to reactivate the key.
P2 : Key number.
00h - Exchange Key Ke: used for key loading operation.
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
Data:
This field contains:
" the 8-byte encrypted master key
" the 4-byte checksum
Response: Status Words
RM 23
Coupler - Reference manual
SELECT_CURRENT_KEY
Version 1.0
Use
This function allows to choose a key for future authentications. A key that has been
deactivated or deleted cannot be selected. Only one of the 16 keys can be current at the
same time.
Prototype
Command sent : 52h
Command type : ISO In
Host
80h
52h
Coupler
00h
P2h
08h
8 * 00h
52h
90h
00h
Parameters
P2 : Key number
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
Remark: if the specified key is deactivated, the status bytes returned is 6Bh 00h.
RM 24
Coupler - Reference manual
DIVERSIFY_KEY
Version 1.0
Use
This function enables the user to calculate the result of key diversication with selected
chip serial number.
The key diversified value is used for authentication and signature calculation while writing
a secure chip.
This can have 2 uses :
- before an authentication (SELECT_PAGE or AUTHENTIFY command)
- to calculate the keys that will be written in a chip during a personalization phase (only
working with a dedicated personalization coupler)
Prototype
Command sent : 52h
Command type : ISO In
Host
80h
52h
Coupler
00h
P2h
08h
Chip serial number
52h
90h
00h
Parameters
P2 : Key number
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
Remark: if the specified key is deactivated, the status bytes returned is 6Bh 00h.
RM 25
Coupler - Reference manual
GET_CONFIG
Version 1.0
Use
This command is used to read the ID of the MCU part.
Prototype
Command sent : CAh
Command type : ISO In
Host
80h
CAh
Coupler
00h
00h
09h
CA
ID (8)
Code Info (1)
90h
00h
Parameters
Data : MCU part’s ID
Code Info (1 byte) : RFU
RM 26
Chips and readers- USER’S GUIDE
Version 1.0
CHAPTER 4
USER’S GUIDE
In this chapter ou will learn how to use the coupler
to...
! Use INSIDE chip
! Manage the security
UG 1
Chips and readers- USER’S GUIDE
Version 1.0
MANAGING INSIDE CHIPS
The various steps in INSIDE’s chips management are the following :
! Set the used key (if your application is secured)
! Select a chip
! If it is a multi-application chip, select the page in which you
want to work
! Read, Write data in the chip memory
! Halt the chip to enable another chip selection
Using INSIDE couplers, authentication and signature calculations are
managed automatically by the SELECT_PAGE or the SELECT_CARD
command. Just indicate in these commands that you want to use the
security features.
In this chapter is just indicated the way and the functions and commands
to use to reach your goal. Please refer to the Reference Manuals for more
information about the functions and its parameters.
In this chapter you will also learn :
! how to manage the various protocol at low level or with the
activeX component
! how to make a chips inventory and select a chip within several
ones.
UG 2
SECURITY CONFIGURATION
Chips and readers- USER’S GUIDE
Before using the security features, please take a look at the «Security management»
chapter. You will find there basic principles on which is based INSIDE chips security.
Version 1.0
If your application is secured, you have to ...
a. Load the key in the coupler. This operation has to be performed only once. As soon as
keys are loaded, they are stored in the coupler’s EEPROM.
b. tell to the coupler which key you want to use for your application (Kd1, Kc1, Kd2 ...)
a. Loading the key...
You have to indicate the following parameter :
- Exchange key to enable you to load the key
- New key value
- Key number (is it «Debit Key 3», «Credit key 2»)
ActiveX :
Mx.KeyLoading method
C Library :
Clib_w_KeyLoading procedure
Low level :
LOAD_KEY_FILE command
b. Activating the current key...
Two commands are available to tell to the coupler which key you want to use. One has
to be used before the selectcard command, and the other before the SelectPage or
Authentify command if you want to use a key different than the one used to authentify
the chip (or if you selected the card without authentication).
Use the following commands before the SelectCard command :
ActiveX method : Mx.CurrentKey property
C Library :
CLib_w_SelectCurrentKey procedure
Low level :
SELECT_CURRENT_KEY command
Please refer to the chapter «Managing the security» for more details about the way it
works, and to the reference manual chapter for more details about the commands.
Use the following commands before the SelectPage and Authentify
commands :
ActiveX method : Mx.DiversifyKey property
C Library :
Clib_w_DiversifyKey procedure
Low level :
DIVERSIFY_KEY command
Please refer to the chapter «Managing the security» for more details about the way it
works, and to the reference manual chapter for more details about the commands.
UG 3
SELECTING A CHIP
Chips and readers- USER’S GUIDE
During this operation, you will choose the protocol you want to use (14 443 type A, 14
443 type B or 15 693), and if you want to authentify the chip. The answer will give you the
protocol used by the chip, and its serial number
Version 1.0
Security...
P1 value
Which protocol...
P2 value
none
00h
14 443 B-2
01h
Kd authentication
30h
15 693
02h
Kc authentication
10h
14 443 B-3
04h
Then use the following command :
ActiveX method : Mx.SelectCard (P1, P2, Type_SerialNumber)
ActiveX method : Clib_w_SelectCard (P1, P2, Type_SerialNumber)
Low level :
SELECT_CARD : 80h A4h P1h P2h 09h...
Note 1 : Coupler will answer the protocol number used to communicate with the chip,
and the chip serial number. This «protocol number» is the value to use with the TRANSMIT command as «protocol value»
Note 2 : The above table show 2 protocols ISO 14 443 type B
! 14 443 type B-2 : RF protocol is the one defined in the 14 443 B standard level 2,
and anticollision is INSIDE contactless one.
! 14 443 type B-3 : RF protocol follows the 14 443 B standard level 2, and anticollision
is defined in 14 443 B standard level 3.
UG 4
Chips and readers- USER’S GUIDE
SELECTING A PAGE
Version 1.0
If you are using a Multi-application chip ( 8*2K for example ) you have to select the page
in which you want to work.
The SelectCard command selects by default page 0. The SelectPage command enables
you to work in all other pages. It will manage the authentication if the page is secured.
You have to enter...
- page number
- key to use for authentication
- protocol to use
You will get...
- page configuration block (block 1)
Then use the following command :
ActiveX method : Mx.SelectAuthPage (Key number, PageNumber, ConfigBlock)
! C Library :
Clib_w_SelectAuthPage (Key number,
PageNumber, ConfigBlock)
Low level :
Host
80h
Protocol,
SELECT_PAGE
A6h
P1
P2
08h
A6h
Coupler
Chip 's
configuration
block
90h
00h
The following table gives you parameters to select and authenticate a secured page. P2
values are just examples.
Protocol
P1 value...
Page & key number
P2 value...
14 443 B
0Ch
Key Kd1 & Page 1
21h
15 693
0Dh
Key Kc1 & Page 1
31h
14 443 A
0Eh
Key kd7 & Page 7
E7h
Note : if the page is secured, use the
diversify command to select in the coupler the
key that will be use for the authentication.
UG 5
READING CHIP MEMORY
Chips and readers- USER’S GUIDE
You will find a full memory description in the chip datasheet, but the easiest way to
discover the chip memory is to use the MX3 software (PICO MEMORY page).
Version 1.0
You have to enter...
- block number
- protocol to use
You will get...
- memory data
Then use the following command :
ActiveX method : Mx.ReadBlock (BlockStart, BlockCount, ChipResponse)
Mx.Read property : ActiveX component optimizes reading
speed by using READ or READ4 chip command depending on chip possibilities.
! C Library :
ChipResponse)
Clib_w_ReadBlock (BlockStart, BlockCount, Protocol,
Clib_w_ReadBlockBy4(BlockStart, BlockCount, Protocol,
ChipResponse)
Low level :
TRANSMIT command
+ 0Ch chip command (single read)
+ 06h chip command (read4)
All communication with a chip is done thanks to this command, including INSIDE’s chips.
You will find there how to read one block with the 15 693 standard.
Host
80h
C2h
C5h
08h
02h
0Ch Addh
C2h
Coupler
Chip's answer
90h
00h
Chip's answer
90h
00h
You can also use the Read4 chip command :
Host
Coupler
80h
C2h
C5h
20h
02h
06h Addh
C2h
Note : To use another protocol, just change the bit in P2 parameter.
14 443 B-2 : Use 80h C2h C4h...
14 443 B-3 : Use 80h C2h C6h...
UG 6
Chips and readers- USER’S GUIDE
WRITING CHIP MEMORY
Version 1.0
When writing data to a memory block you have to know if you are communicating to a
secure or non secure chip. Parameters will be different as you ask the coupler to send or
not the signature to authenticate the data you want to write (this is automatically managed
by the ActiveX component).
ActiveX method : Mx.WriteBlock (BlockStart, BlockCount, BlocksValue)
! C Library :
BlocksValue)
Clib_w_WriteBlock (BlockStart, BlockCount, Protocol, Auth,
! Low level :
TRANSMIT command + 87h chip command
This command enables you to write one block. The following example are for a 15 693
communication.
Non secure chips
Host
80h
C2h
E5h
08h
87h Addh
&Data
0Ah
C2h
Coupler
Written
data
90h
00h
Written
data
90h
00h
Secure chips
Host
80h
C2h
Coupler
6Dh
08h
87h Addh
&Data
0Ah
C2h
Note : To use another protocol, just change the appropriate bit in P2
parameter :
Non secured chip :
Secured Chip :
14 443 B-2 : Use 80h C2h E4h...
14 443 B-3 : Use 80h C2h E6h...
14 443 B-2 : Use 80h C2h 6Ch...
14 443 B-3 : Use 80h C2h 6Eh...
UG 7
HALTING A CHIP
Chips and readers- USER’S GUIDE
The following command halts the current selected chip :
TIPS : to halt the chip
as soon as you get its
serial number, use P1
parameter in the
SELECT_CARD
command
Version 1.0
ActiveX method : Mx.Halt
C Library :
Clib_w_Halt (protocol)
Low level :
TRANSMIT command + 00h chip command
Host
80h
C2h
31h
00h
Coupler
01h
00h
C2h
90h
00h
Note : To use another protocol, just change the appropriate bit in P2
parameter :
14 443 B-2 : Use 80h C2h 30h...
14 443 B-3 : Use 80h C2h 32h...
UG 8
HOW TO WORK WITH SEVERAL CHIPS IN THE FIELD
Select card
TIPS : The low level
c o m m a n d
SELECT_CARD
includes an option that
halts the chip as soon
as it is selected. This
enables to earn time
by avoiding to send the
HALT command. Just
use the following P1
parameters : P1 =
02h.
Store chip serial
number in a table
No card selected
Chips and readers- USER’S GUIDE
Here is the basic algorithm to get serial numbers of all chips in a given RF field :
Halt the selected chip
Select the chip you
want to work with
Chips inventory
Make a loop with the SELECT_CARD COMMAND with HALT option enable (P1 = 02h).
Chip selection with its serial number
Use the following command to select a given chip thanks to its serial number. The chip
will answer you its serial number.
ActiveX method : Mx.ReSelect (ChipSN)
C Library :
Clib_w_ReSelect (ChipSN)
Low level :
TRANSMIT command + 81h chip command
Host
Coupler
81h & Serial
Number
80h C2h C5h 08h 09h
C2h
Serial
number
90h 00h
Replace C5h by C4h (C6) to use 14 443 type B-2 (type B-3) protocol.
Version 1.0
UG 9
MANAGING INSIDE’S CHIPS PROTOCOLS
Chips and readers- USER’S GUIDE
Low level command and C library
Version 1.0
Protocols are always indicated in the command parameters (P2 for SELECT_CARD, P1
for TRANSMIT). You will find the appropriate value in this User’s Guide, and in the
description of each command in the «Reference manual».
ActiveX component
There are 2 command types :
- Card selection
- Select page, read, write...
Card selection
When selecting a card, you set the protocol to use in P2 parameter of the Mx.SelectCard
method. Coupler is able to test several protocols, and return the protocol use for card
detection.
Other operation (Read, Write, SelectPage etc...)
For any other operation, use the ActiveX propertie Mx.MxProtocolIndex to set the
protocol you want to use.
This property is automatically set after a SelectCard command thanks to the value returned
by the coupler indicating the protocol use for card selection.
If you want to change communication protocol when using a dual protocol chip
(PICOPASS - 15 693 & 14 443 type B), just change this protperty value to the desired
one, and all activeX command for INSIDE chip will use this protocol.
UG 10
MANAGING THE SECURITY
Chips and readers- USER’S GUIDE
INSIDE
security protects
memory from READING and/or WRITING.
Security
control e-purse
(stored value) management
Security is
based on :
- key diversification
- authentication
-signature
Key diversification implies that
each security
calculation is different
for each card
INSIDE chips security is based on secret keys that protect and authentify the chip content.
On one hand, keys are stored in the chip. On the other hand, coupler includes a security
module in which are stored the application keys.
Security is based on checking that keys are the same in the chip and in the coupler.
First paragraph explains on what is based our security and what it is for :
Authentication
Signature
Diversified keys
The following paragraphs explain how to :
load the key into the coupler / SAM
select and / or authenticate a chip with a given key
INSIDE CHIPS SECURITY
Security consists in protecting memory access and e-purse use by secret keys. User
will be able to modify card content only if the coupler contains same secret keys as
PICO chip.
Security is checked several times :
Authentication : Just after having selected the chip user has to perform an
authentication before being able to access any memory data.
Signature : for any memory modification the chip user has to send a signature
calculated as a function of sent data, secret keys and chip serial number. Thus it
is impossible to modify the chip content without knowing the application keys.
In each security calculation, a diversified key is being used, based on the chip serial
number and the application key.
All security calculations are automatically manage by INSIDE’s couplers.
Key diversification
To ensure a reliable security, every security operation (authentication, signature
calculation) is based on diversified key value.
The diversified key is an 8 bytes result of calculation including chip serial number and
key value.
Thus, 2 chips using same keys contain different diversified key values. This ensures
that it is not possible to repeat some sequence registered on one card on another card.
Key
fortification
algorythm
Secret Key
Chip serial number
Version 1.0
Diversified Key
DES
UG 11
Chips and readers- USER’S GUIDE
Authentication
protects the memory
from reading and
writing
Signature
when writing
increases memory
content security
Authentication
Authentication algorithm performs a mutual authentication.
The principle is as follows : Data are exchanged then both device perform secret
calculations on them to obtain 2 results on 4 bytes. Authentication is done if they get the
same results. The chip first checks coupler’s response then reader verifies chip’s results.
1. Coupler and chip
exchange data
Data (64bits)
Diversified
secret key
(64 bits)
Random (32 bits)
Diversified
secret key
2. Both coupler and
chip calculate 2
results on 4 bytes
R1
R2
R1
Coupler
Note :
Diversified key is written in
the chip during personalization
phase, and calculated after
each card selection by the
coupler (div. key depends on
the chip serial number)
R2
3. The chip verifies the
coupler's result 1, then
send Result 2 if OK
4. The coupler checks
chip's answer (Result 2)
Signature
Each time you want to send data to the chip, a 32 bits signature is automatically calculated
and added. Signature calculation takes into account the diversified key value (result of
operation between key value and chip serial number) and the data. Chip will check the
signature to allow data writing. This ensures very good security on the chip content.
Key Value
Chip serial number
Diversified key value
Data &
signature
Signature
Data
Chip
Coupler
Host
Signature calculation principle
Version 1.0
UG 12
Chips and readers- USER’S GUIDE
First step in
security is to load the
secret keys into the
coupler
Version 1.0
KEY LOADING
To perform this complex operation, use the function supplied with the libraries (C Libraries,
ActiveX component). You will find encryption algorithm in annex. C source code is provided
in the C libary, and ActiveX component manage automatically all security calculation.
You need to give the following parameter :
Key number
Exchange Key
New Key value
ActiveX method : Mx.KeyLoading
Use Mx.KeyLoading (KeyNum, LoadingType, ExchangeKey,NewValue) method to
load the key in the coupler at the appropriate place.
Keynum may have to following value :
- mpkPiKd (i=0 to 7)
- mpkPiKc (i=0 to 7)
Example : to load the default keys as keys 6 using the default exchange key ...
Mx.KeyLoading (mpkP6Kd, mklmXORKe,«$5C$BC$F1$DA$45$D5$FB$5F»,
«$F0$E1$D2$C3$B4$A5$96$87»)
Mx.KeyLoading (mpkP6Kc, mklmXORKe,«$5C$BC$F1$DA$45$D5$FB$5F»,
«$76$65$54$43$32$21$10$00»)
! C Library : Clib_w_KeyLoading
Clib_w_KeyLoading (KeyNum, LoadingType, ExchangeKey,NewValue)
Low level : LOAD_KEY_FILE
Calculate the Encrypted key thanks to the C library algorythm (see annexe A) and use
the LOAD_KEY_FILE command...
Host
Coupler
80h D8h 00h
P2 OCh
Encrypted key
D8h
90h 00h
P2 : Key number
00h - Exchange Key Ke: used for key loading operation.
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
UG 13
Chips and readers- USER’S GUIDE
Second step:
tell the coupler which
key has to be used
Version 1.0
HOW TO SET A KEY AS THE ACTIVE ONE
A - Before SelectCard command
ActiveX component : Mx.CurrentKey
Possible values are :
- mpkPiKd (i=0 to 7)
- mpkPiKc(i=0 to 7)
! C Library : Clib_w_SelectCurrentKey
Clib_w_SelectCurrentKey (KeyNum)
Low level :
Host
80h
SELECT_CURRENT_KEY command
52h
00h
P2h
08h
8 * 00h
52h
Coupler
90h
00h
P2 : Key number
00h - Exchange Key Ke: used for key loading operation.
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
B - Before SelectPage and Authentify command
At this stage you need to precise both the key number and the chip serial number (as
you may be working with several chips).
Actually this operation is performed automatically by the selectCard command as it
knows the key number thanks to the CurrentKey property, and the Serial Number is
given by the chip during the selection phase.
When using a standard coupler, the DiversifyKey command returns a useless data
(random number). The returned data are used only with a personalisation coupler. More
information are given in the personalisation kit.
ActiveX component : Mx.DiversifyKey
Mx.DiversifyKey (KeyNum, Chip Serial Number, Databack)
! C Library : Clib_w_DiversifyKey
Clib_w_DiversifyKey (KeyNum, Chip Serial Number, Databack)
Low level :
Host
Coupler
80h
DIVERSIFY_KEY command
52h
00h
P2h
Serial
Number
08h
52h
90h
00h
P2 : Key number
00h - Exchange Key Ke: used for key loading operation.
01h - Debit Key Kd0
02h - Credit Key Kc0
03h - Debit Key Kd1
04h - Credit Key Kc1
.....
0Fh - Debit Key Kd7
10h - Credit key Kc7
UG 14
Chips and readers- USER’S GUIDE
Last step :
Authentication is
performed during chip
selection and/or page
selection
Tips : Key
diversification is
automatically
done by the
select card
command
Tips :
Key diversification
has to be done
only once. You
don’t need to use
the Diversify
command as soon
as you work with
the same chip
and the same
key
HOW TO AUTHENTIFY A CHIP
Authentication may be done while selecting the card (or the page). It can also be done
later, for example when you want to work with both Credit key and Debit key authentication.
ActiveX component : Mx.SelectCard
SelectCard (30h ...) authenticates selected chip with Kd
SelectCard (10h ...) authenticates selected chip with Kc
! C Library : Clib_w_SelectCard
Clib_w_SelectCard (SelectMode , ChipType, TypeSN)
SelectMode = 30h : Authentify with the chip debit key
SelectMode = 10h : Authentify with the chip credit key
Low level : SELECT_CARD
80h A4h 10h P2 09h => Authenticate with Kc
80h A4h 30h P2 09h => Authenticate with Kd
HOW TO AUTHENTIFY A PAGE
Authentication follows the same principle as for the SelectCard authentication.
If you want to use a different key than the one used during the card selection, or if
selection has been done without you have to use the DiversifyKey command to set a key
as the active key if you want to change the active key.
ActiveX component :
Mx.DiversifyKey (KeyNum, Chip Serial Number, Databack)
SelectAuthPage (Key, Page, BlockConfig)
C Library :
Clib_w_Mx.DiversifyKey (KeyNum, Chip Serial Number, Databack)
Clib_w_SelectAuthPage (Key, Page, BlockConfig)
Low level : DIVERSIFY_KEY & SELECT_PAGE
DIVERSIFY_KEY
Host
52h
00h
P2h
Serial
Number
08h
52h
Coupler
90h
00h
P2 : key number
SELECT_PAGE
Host
Coupler
Version 1.0
80h
80h
A6h
P1
P2
08h
A6h
Chip 's
configuration
block
90h
00h
UG 15
P1 : contacless configuration
P2 : key and page number
Chips and readers- USER’S GUIDE
PROTECTING THE KEYS
Version 1.0
Thus all the security depends on making sure that these keys are kept secret. To ensure
a good secury, key loading has to be done in a secure environment.
The key loading procedure ensures that :
1 - nobody decrypts the key loaded in the coupler by listenning to the HOST-COUPLER
communication
2 - nobody records and uses the communication between HOST and COUPLER to load
keys in another coupler
To protect the communication, all data exchange is ciphered thanks to an exchange key
known only by the coupler. Therefore, nobody will be able decipher serial communication and find the application key value
Protect key storage (coupler, security module) so that
nobody can use your keys.
Use our coupler security protection features or store coupler or SAM keys in a secured
place.
To ensure a very good security to your application, contact us so we help you to give to
your system the security it deserves.
UG 16
MANAGING STANDARD CHIPS PROTOCOLS
Chips and readers- USER’S GUIDE
This chapter explains how to communicate with any chips that follow the 13.56MHz
standards : 15 693, 14 443 Type A and B. More over, you will find there how to
communicate with the FeliCa chip (SONY).
Note : user’s will find there the commands to use to send byte to the chip, and to get the
chip answer, but we will not mention the way to manage these chips. User has to refer to
the chip datasheet or ISO standards to find more information about these chips.
TIME OUT ADJUSTMENT
When communicating with a chip, and particularly a microprocessor, user may need to
increase the time out value.
The TimeOut configuration enables the user to change the value of the TRANSMIT
command to be sure that no ISO command will fail because a too short timeout.
Users can change 4 timeout values corresponding to the 4 Timeout "slots" that one can
use in TRANSMIT command:
•
Timeout 0 (command timeout option = b00) : Address h68
•
Timeout 1 (command timeout option = b01) : Address h69
•
Timeout 2 (command timeout option = b10) : Address h6A
•
Timeout 3 (command timeout option = b11) : Address h6B
Where "b" prefix is for binary value, "h" is for hexadecimal
To put a specific value for one of these TimeOut "slots", developper can use the following
formulas:
ISO 14443 (A-B) : TimeOut = X . 380µs + 200µs
ISO 15693
: TimeOut = (X << 2) . 380µs + 200µs
Where X is the value of the byte and << is the operation that execute a binary right shift
of the byte value.
15 693-3 PROTOCOL
This example shows how to configure the protocol, then how to send the INVENTORY
command.
Public sub Sample_15693()
‘ Configure USER protocol as 15693
Mx.MxUserProtocol = mupISO_15693_3_10pc
‘Low level command : use the SetStatus function
‘Mx.SetStatus &H3, &H5E, &H21
‘Mx.SetStatus &H3, &H5F, &H31
' Send Inventory command "1 slot" to retrieve chip serial number
Command = "$36$01$00$00"
CommandSize = &H04
AnswerSize = &H0A
UserProtocol = &HF3
Mx.Transmit UserProtocol, AnswerSize, CommandSize, Command, ChipAnswer
' Send slot marker for anticollision management
Mx.Transmit &H73, &H0A, &H00, «», ChipAnswer
End Sub
Version 1.0
UG 17
ISO 14 443 TYPE A
Chips and readers- USER’S GUIDE
Public sub Sample_14443_A()
Version 1.0
‘ Configure USER protocol as 14443-A level 3
Mx.MxUserProtocol = mupISO_14443A_3
' Low level : use the set status command
‘Mx.SetStatus &H03, &H5E, &H32
‘Mx.SetStatus &H03, &H5E, &H12
‘Mx.SetStatus &H03, &H64, &H63
‘Mx.SetStatus &H03, &H65, &H63
' Use the SelectCard command to manage anticollision
Mx.SelectCard &H00, &H08, Type_SN
'Send the RATS command :
Buffer length = 32
Name the card as card 0
Command = "$50$00"
CommandSize = &H02
AnswerSize = &H06
UserProtocol = &HF3
Mx.Transmit UserProtocol, AnswerSize, CommandSize, Command, ChipAnswer
End Sub
ISO 14 443 TYPE B
Public sub Sample_14443_B()
‘ Card selection with the select Card command : manage the anticollision
Mx.SelectCard &H00, &H04, Type_SN
‘Send REQB command
Command = "$05$00$00"
CommandSize = &H03
AnswerSize = &H0C
UserProtocol = &HF2
Mx.Transmit UserProtocol, AnswerSize, CommandSize, Command, ChipAnswer
End Sub
FELICA ( NEW VERSION)
' Low level : use the set status command to configure the protocol
Mx.SetStatus &H03, &H5E, &H79
Mx.SetStatus &H03, &H5E, &H02
Mx.SetStatus &H03, &H64, &H00
Mx.SetStatus &H03, &H65, &H00
' Send a command to the chip and retrieve the answer
Command = "$06$00$FF$FF$00$01"
CommandSize = &H06
AnswerSize = &H12
UserProtocol = &HF7
Mx.Transmit UserProtocol, AnswerSize, CommandSize, Command, ChipAnswer
UG 18
Chips and readers- USER’S GUIDE
MANAGING THE RF FIELD
Version 1.0
Possible operations you can perform on the RF field are the following :
" Cut RF emission, mainly when couplers are powered on battery
" Start RF emission
" «Reset» RF field (i.e. cut it for 20 ms in order to reset any halted chip in the field)
HOW TO RESET THE RF FIELD ?
This command will cut the RF field for 20 ms in order to reset all chips that are in the
field.
ActiveX method : Mx.ResetField
C Library : Clib_w_ResetField ()
Low level :
H o st
80h
SET_STATUS command
F 4h
40h
00h
01h
Coupler
00h
F 4h
90h
00h
HOW TO ASLEEP THE COUPLER
Just use the disable command which will cut the RF field so that no energy is wasted.
ActiveX method : Mx.Disable
C Library : Clib_w_Disable ()
Low level :
H o st
80h
DISABLE command
A D h B C h D A h 00h
Coupler
90h
00h
HOW TO WAKE UP THE COUPLER
ActiveX method : Mx.Enable
C Library : Clib_w_Enable ()
Low level :
H o st
Coupler
80h
ENABLE command
A E h D A h B C h 00h
90h
00h
Important note
Low level command : You have to send this command in a window of 16 ms so that the
coupler catches it. To be sure that this command is detected, send it twice, with no more
than 10 ms between the 2 commands sending. This is automatically managed by the
ActiveX method.
UG 19
Version 1.0
Chips and readers- USER’S GUIDE
APPENDICES
UG 20
Chips and readers- USER’S GUIDE
APPENDIX A
HOW TO LOAD A KEY IN A
COUPLER
Version 1.0
This procedure consists in several operations on the key. The final result will be sent to
the coupler using the Loag_Key_File function.
EXCHANGE KEY
To ensure the security, an exchange key will protect all key loading operations.
This key is in the coupler memory and has 2 functions :
- only host knowing this key will be able to modify the Debit and Credit keys.
- New key value are encrypted with this exchange key so it is not possible to
read the new value on the serial line.
You have to know this exchange key to modify the value of any other key. For any
modification, the Exchange key is managed exactly as the Debit key and the Credit key
: you have to use the Key Loading Procedure described in the next paragraphs.
GENERAL KEY LOADING PROCEDURE
Before the key loading starts with the LOAD_KEY_FILE command, the host must
generate a session key. This key is generated by the encryption of the current Exchange
Key (Ke) with an 8-byte random number.
Host
New key
value (Kx)
Ask random
Random
(Rnd)
Exchange
key (Ke)
Calculate the
session key
Encrypt the new
key value
Calculate
encrypted key
checksum
Reader
Exchange
key (Ke)
Calculate the
session ley
Load encrypted
key and
checksum
Decrypt new key
value
Calculate
checksum
Compare
checksum
UG 21
TERMINOLOGY AND NOTATION
Chips and readers- USER’S GUIDE
Adding p after the key name means that the key is permuted.
Adding chk means that the 8th byte replaced by the Checksum byte value.
A C before the key name means that the key has been encrypted.
Abbreviation
Kex
Kexp
Kexp_chk
Rnd
Kx
Kx p
CKxp
SK
CHK
Meaning
Exchange Key.
Permuted Exchange Key.
Kep with the 8th byte replaced by the Checksum byte value.
Random number.
Master key. (Kx equals to Kd or Kc)
Permuted master key. (Kxp equals to Kdp or Kcp)
Encrypted permuted master key. (CKxp equals to CKdp or CKcp)
Session key.
4-byte checksum.
KEY LOADING STEP BY STEP
We assume that the default keys are used.
STEP DESCRIPTION
Step 1 : Get a random number from the coupler
Send the Ask_Random command
Send 80h 84h 00h 00h 08h. The coupler answer a
random number.For this example, we assume that
Rnd = 00 00 00 00 00 00 00 00.
Step 2 : Calculate the Session Key
The session key is define by the following formula :
SK = Kexp_chk ⊕ Rnd (⊕ : bit to bit x-or
operation)
Kexp_chk means that we have to permute Kex then
to replace the 8th byte by the checksum byte
! Permute the exchange key to get Kexp
Kexp = 6E FD 46 EF CB B3 C8 OB
th
! replace the 8 byte by the checksum byte Kexp_chk = 6E FD 46 EF CB B3 C8 75
to get Kexp_chk
Calculate the session key
SK = 6E FD 46 EF CB B3 C8 75
Step 3 : Calculate the Encrypted master key
This calculation include the exchange key through
the session key (SK). This insure the protection of
the new key value.
CKxp = SK ⊕ Kxp
(⊕ : bit to bit x-or operation) CKdp = 91 F2 75 BA CB 43 04 20
Permute
the
new
key value Kx to get Kxp
Make a bit to bit X-OR operation with the
session key SK
Step 4 : Send the Load_Key_File command
! Calculate the CheckSum
! Send the command to the coupler.
Load_Key_File (CKxp + CheckSum)
Version 1.0
Example
CheckSum = 73 27 FF 01
Send 80 D8 00 01 0C & 91 F2 75 BA CB 43 04 20 &
73 27 FF 01
UG 22
ALGORITHMS
Chips and readers- USER’S GUIDE
KEY PERMUTATION
Version 1.0
Proceed as described below to permute a key.
Example: Permute the key Kex.
Kex = 0x5C 0xBC 0xF1 0xDA 0x45 0xD5 0xFB 0x5F
(0x5F) !
(0xFB) !
(0xD5) !
(0x45) !
(0xDA) !
(0xF1) !
(0xBC) !
(0x5C) !
0x6E 0xFD 0x46 0xEF 0xCB 0xB3 0xC8 (0xF4)
Replace the last byte by :
Kexp =
0x6E
0xF4 = 0B
0xFD
0x46
0xEF
0xCB
0xB3
0xC8
0x0B
CHECKSUM BYTE CALCULATION
Proceed as described below to calculate a key checksum byte.
Note: the ⊕ symbol means a bit to bit x-or operation.
Example:
K=
0x5C
Kp =
0x6E
0xBC
0xFD
0xF1
0x46
0xDA
0xEF
0x45
0xCB
0xD5
0xB3
0xFB
0xC8
0x5F
0x0B
Checksum = 0x6E ⊕ 0xFD ⊕ 0x46 ⊕ 0xEF ⊕ 0xCB ⊕ 0xB3 ⊕ 0xC8 = 0x8A
Checksum = 0x8A = 0x75
and then,
Kxp_chk =
0x6E
0xFD
0x46
0xEF
0xCB 0xB3
0xC8
0x75
LOAD KEY CHECKSUM CALCULATION
! Complete the 5 command bytes with 3 bytes 00 so to get 8 bytes
! Calculate RES = (Command bytes) ⊕ Kxp.
! Calculate the checksum CHK = Most Significant 4-Bytes(RES) ⊕ Least Significant
4-Bytes(RES).
UG 23
Chips and readers- USER’S GUIDE
Example:
The checksum when sending the default Debit Key Kd is :
Version 1.0
Command =
K dp =
RES =
CHK =
80 D8 00 01 0C 00 00 00
FF 0F 33 55 00 F0 CC 55
7F D7 33 54 0C F0 CC 55
73 27 FF 01
MSB(RES) 7F
D7
33
54
⊕ LSB(RES) 0C
F0
CC 55
________________________________
CHK =
73
27
FF
01
UG 24
Chips and readers- USER’S GUIDE
APPENDIX B
ERROR CODE
Version 1.0
When an error occurs, coupler response is only status words SW1 SW2. No data is
returned.
The following table sums up the various values.
SW1
SW2
90h
00h
Error description
Command successful
Common status errors
67h
00h
Data length, P3 incorrect
6Bh
00h
Parameters P1, P2 incorrect
6Eh
00h
Class not recognized
6Dh
00h
Instruction not recognised, parity error
Security errors
69h
82h
Card not identified (CRC or authentication
problem)
98h
35h
Command flow incorrect
Execution error
6Ah
82h
Card not found
62h
00h
EEPROM erro
UG 25

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.4
Linearized                      : No
Encryption                      : Standard V1.2 (40-bit)
User Access                     : Print, Modify, Copy, Annotate, Fill forms, Extract, Assemble, Print high-res
Create Date                     : 2003:07:16 14:47:52Z
Modify Date                     : 2003:07:17 19:17:11+02:00
Subject                         : Couverture
Page Count                      : 67
Creation Date                   : 2003:07:16 14:47:52Z
Mod Date                        : 2003:07:17 19:17:11+02:00
Producer                        : Acrobat Distiller 5.0.5 (Windows)
Author                          : jjourdain
Keywords                        : 
Metadata Date                   : 2003:07:17 19:17:11+02:00
Creator                         : jjourdain
Title                           : Couverture
Description                     : Couverture
Page Mode                       : UseOutlines

EXIF Metadata provided by EXIF.tools