Elatec TWN4 MultiTech 2 HF User manual

TWN4
System Overview
DocRev7, September 12, 2014
Elatec GmbH

Contents
Contents
1 What is TWN4? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2Products ......................................... 5
2.1 TWN4 Core Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.1 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1.2.1 Connector A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1.2.2 Connector B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.1.2.3 Connector C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1.2.4 Connector HF1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.2.5 Connector HF2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.3 Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1.4 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 TWN4 OEM PCBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.1 TWN4 Desktop OEM PCB . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.1.1 Dimensions & Pinout . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.2 TWN4 Panel OEM PCB . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3 TWN4 Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4 TWN4 Mini Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4.1 Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3Firmware ......................................... 19
3.1 Memory View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.1 Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.2 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1.3App ...................................... 20
3.1.4 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.2 Functional Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.3 Firmware Startup Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.4 Firmware Error Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.5 Backdoor for Starting the Boot Loader . . . . . . . . . . . . . . . . . . . . . . . 23
3.6 App & Firmware Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.1 App Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.2 Firmware Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.6.2.1 Naming Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4 TWN4 Developer Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
4.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Page 2of 36

Contents
5 Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 History of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1 TWN4 Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.1 Firmware V1.23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.2 Firmware V1.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.3 Firmware V1.47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
6.1.4 Firmware V1.48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1.5 Firmware V1.49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1.6 Firmware V1.57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.1.7 Firmware V1.64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2 AppBlaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.1 AppBlaster V1.03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.2.2 AppBlaster V1.40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.3 AppBlaster V1.47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.4 AppBlaster V1.49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.5 AppBlaster V1.57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2.6 AppBlaster V1.64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3Director........................................ 31
6.3.1 Director V1.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.3.2 Director V1.06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3.3 Director V1.10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3.4 Director V1.11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3.5 Director V1.12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3.6 Director V1.14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
6.3.7 Director V1.16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4General ....................................... 33
6.4.1 TWN4DevPack147 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6.4.2 TWN4DevPack148 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7 Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.1 FCC Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.2 IC (Industry Canada) Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8Trademarks........................................ 36
Page 3of 36

1 What is TWN4?
1 What is TWN4?
TWN4 is the name of a powerful and versatile series of RFID readers and writers. Here are
some of the outstanding features:
• Operation in two frequencies bands: 13.56 MHz (HF) and 125 kHz / 134.2 kHz (LF)
• Modular concept consisting of core modules, carrier boards, antennas and complete
devices in housing.
• Security features such as slots for secure access modules or cryptogrphic functions.
• Possibility to write programs which are running on TWN4 itself (Apps).
• Standalone or host-based operation.
Page 4of 36

2 Products
2 Products
2.1 TWN4 Core Module
The TWN4 family of RFID readers/writers is built around the TWN4 Core Module.
Here is a picture of the TWN4 Core Module MIFARE NFC:
There are two different core modules available:
• TWN4 Core Module MIFARE NFC
• TWN4 Core Module LEGIC NFC
Page 5of 36

2 Products
The core module contains voltage regulator, control unit, RFID front ends and communica-
tion interfaces.
2.1.1 Dimensions
The dimensions of TWN4 Core Module are as follows.:
2.1.2 Connectors
The TWN4 Core Module has several connectors on-board. There are three connectors (A, B
and C) which connect either to a carrier board or to a host. Furthermore, there is a antenna
connector and a optional position for placing a coaxial connector.
Page 6of 36

2 Products
The connectors A, B and C have identical pitch. Following type of connector is recom-
mended:
• Dual row header
• Pitch 2.0mm
• Pin shape square
• Pin width 0.5mm x 0.5mm
• Length of pins appropriate to custom requirements
2.1.2.1 Connector A
The connector A is intended for connecting a cable to the TWN4 core module, which allows
communication with a host. Typically, such a cable is either type USB or RS232. Various
appropriate USB and RS232 cables are available from stock.
There is a right-angle connector mounted on-board, which is type Hirose, DF11 series.
Pin Pin Name Function
A1 UGND USB Ground
A2 USB_D+ USB Data +
A3 UVCC USB VCC
A4 USB_D- USB Data -
A5 V24_RXD RS232 RXD (Input)
A6 GND Ground
A7 V24_TXD RS232 TXD (Output)
A8 MGND Cable Sense
Note:
If pin A6 and A8 are connected to each other this has two effects:
1. The firmware of TWN4 changes host channel to RS232
2. The integrated circuit, which is interfacing to voltage levels of RS232 is powered up.
Following order codes for connector A and mating parts:
• Pin header on TWN4 Core Module: Hirose DF11-8DP-2DS(24)
• Mating part (crimping socket): Hirose DF11-8DS-2C
• Mating part (crimping contact): Hirose DF11-22SC (22 AWG)
Page 7of 36

2 Products
2.1.2.2 Connector B
Pin Pin Name Function
B1 GND Ground
B2 VIN Unregulated input to on-board voltage regulator
B3 VREG 3.3V output from on-board voltage regulator
B4 VCC 3.3V power supply input
B5 RESET- Low active TTL input with internal pull-up resistor
for hard reset.
B6 PWRDWN- Low active TTL input with internal pull-up resistor
for turning off the voltage regulator.
B7 COM1_RX- Low active TTL input with internal pull-up resistor
of asynchronous RXD to COM1.
B8 COM1_TX- Low active TTL output (push/pull) of asyn-
chronous TXD from COM1.
B9 I2C_SDA Data pin of I2C interface. No internal pull up.
B10 I2C_SCL Clock pin of I2C interface. No internal pull up.
B11 CAN_RX TTL RX pin of CAN interface. A external interface
circuit is required.
B12 CAN_TX TTL TX pin of CAN interface. A external interface
circuit is required.
B13 ECI_MOSI Pin MOSI of ECI
B14 ECI_MISO Pin MISO of ECI.
B15 ECI_CLK Pin CLK of ECI.
B16 ECI_ATTN- Pin ATTN- of ECI.
B17 GND Ground
B18 Res. This pin is reserved for future purposes.
B19 SPI_MOSI Pin MOSI of SPI interface
B20 SPI_MISO Pin MISO of SPI interface
B21 SPI_SCK Pin SCK of SPI interface
B22 SPI_SS- Pin SS- of SPI interface
B23 Res. This pin is reserved for future purposes.
B24 Res. This pin is reserved for future purposes.
Page 8of 36

2 Products
2.1.2.3 Connector C
Pin Pin Name Function
C1 GND Ground
C2 ANT_HF Together with pin C1, this pin builds a 50 ohm
output for connecting external 13.56MHz anten-
nas
C3 ANT_LF1 Output 1 for connecting external 125 kHz /
134.2 kHz antennas.
C4 ANT_LF2 Output 2 for connecting external 125 kHz /
134.2 kHz antennas.
C5 Res. This pin is reserved for future purposes.
C6 SPK+ Digitally modulated output for a speaker. Sec-
ond connection for the speaker is ground. The
impedance of the speaker should be greater than
24 ohm.
C7 IO0 GPIO0, I/O pin for general purposes.
C8 IO1 GPIO1, I/O pin for general purposes.
C9 IO2 GPIO2, I/O pin for general purposes.
C10 IO3 GPIO3, I/O pin for general purposes.
C11 IO4 GPIO4, I/O pin for general purposes.
C12 IO5 GPIO5, I/O pin for general purposes.
C13 IO6 GPIO6, I/O pin for general purposes.
C14 IO7 GPIO7, I/O pin for general purposes.
C15 SAM1_CLK Clock output for SAM1
C16 GND Ground
C17 SAM1_IO I/O line for SAM1
C18 SAM1_RST Reset output for SAM1
C19 SAM2_CLK Clock output for SAM2
C20 GND Ground
C21 SAM2_IO I/O line for SAM2
C22 SAM2_RST Reset output for SAM2
continued on next page. . .
Page 9of 36

2 Products
Pin Pin Name Function
C23 COM2_RX- Low active TTL input with internal pull-up resistor
of asynchronous RXD to COM2.
C24 COM2_TX- Low active TTL output (push/pull) of asyn-
chronous TXD from COM2.
C25 Res. This pin is reserved for future purposes.
C26 Res. This pin is reserved for future purposes.
C27 Res. This pin is reserved for future purposes.
C28 VCC 3.3V power supply input or output for supplying
external components. Internally connected to B4.
Note:
• The nominal inductance for an external 125 kHz/134.2 kHz antenna is 490 µH. The
series resistance of the antenna should be lower than 10 ohms.
2.1.2.4 Connector HF1
HF connector 1 is a UMCC series 50-ohms output, which is connected internally in parallel
to pins C1 and C2.
2.1.2.5 Connector HF2
Position of HF2 offers the possibility to place another 50-ohm connector. It is connected
internally in parallel to pins C1 and C2. There are several series of RF connectors, which
can be used for position HF2, like SMA, SMB, SMC, MCX.
Page 10 of 36

2 Products
2.1.3 Jumpers
There are several jumpers on-board of the TWN4 Core Module. Depending on the require-
ments these jumpers can be soldered together.
Jumper Function
J1 The function is identical to pins A6 and A8. If J1 is closed,
the RS232 interface is turned on and the host channel is
assumed to be RS232.
J2 Same function like J1 but other side of PCB.
J3 This jumper must be closed, if TWN4 Core Module is pow-
ered via connector A, e.g. from USB. It connects VCC from
the Core Module to the on-board voltage regulator, which is
supplied from connector A. If TWN4 Core Module is mounted
on a carrier board, this connection can be avoided by con-
necting pins B3 and B4 at the carrier board, which results in
exactly the same functionality.
J4 This jumper is for internal purposes only.
2.1.4 Power Supply
The picture below is showing, how power is routed through TWN4 Core Module:
Page 11 of 36

2 Products
2.2 TWN4 OEM PCBs
An OEM PCB combines all components including antennas and core module, which are
required to build a full functional device. A OEM PCB consists of a carrier board, where
all other parts ar placed. Only cable and power supply is required to bring device into
operation.
Following OEM PCBs are available:
• TWN4 MIFARE NFC OEM PCB (Desktop)
• TWN4 LEGIC NFC OEM PCB (Desktop)
• TWN4 MIFARE NFC OEM PCB (Panel)
• TWN4 LEGIC NFC OEM PCB (Panel)
Page 12 of 36

2 Products
2.2.1 TWN4 Desktop OEM PCB
Here is a picture of a TWN4 Desktop OEM PCB (it is a MIFARE NFC):
The block diagram looks as follows:
2.2.1.1 Dimensions & Pinout
The dimensions and pinout of TWN4 OEM PCB as follows.:
Page 13 of 36

2 Products
Page 14 of 36

2 Products
2.2.2 TWN4 Panel OEM PCB
Here is a picture of TWN4 Panel OEM PCB:
The block diagram looks as follows:
Page 15 of 36

2 Products
2.3 TWN4 Desktop
A TWN4 Desktop is a device, which contains TWN4 Desktop OEM PCB, housing and USB
or RS232 cable for host connection. It is available either in black or white.
2.4 TWN4 Mini Reader
TWN4 Mini Reader is a module to be integrated on custom PCB. It has a built-in HF an-
tenna and subset of IOs compared to TWN4 Core Module. TWN4 Mini Reader is currently
available as version TWN4 Mini Reader MIFARE NFC.
Page 16 of 36

2 Products
2.4.1 Connectors
The TWN4 Mini Reader has two on-board single row headers with 8 positions each. The
pins of these two connectors are together enumerated from 1 to 16.
• Single row header
• Pitch 2.54mm
• Pin shape square 0.635mm
Page 17 of 36

2 Products
Pin Pin Name Function
1 RESET- Low active TTL input with internal pull-up resistor
for hard reset.
2 PWRDWN- Low active TTL input with internal pull-up resistor
for turning off the voltage regulator.
3 GND Ground
4 VIN Unregulated input to on-board voltage regulator
5 RXD- Low active TTL input with internal pull-up resistor
of asynchronous RXD to COM1.
6 TXD- Low active TTL output (push/pull) of asynchronous
TXD from COM1.
7 Res. Reserved for future use (intended for SCK from
SPI host interface).
8 Res. Reserved for future use (intended for SS- from SPI
host interface).
9 VCC Internaly regulated 3.0V power supply. To be used
for SAM1.
10 SAM_IO I/O line for SAM1.
11 GPIO3 GPIO3, I/O pin for general purposes.
12 GPIO2 GPIO2, I/O pin for general purposes.
13 GPIO1 GPIO1, I/O pin for general purposes.
14 GPIO0 GPIO0, I/O pin for general purposes.
15 SAM_CLK Clock output for SAM1
16 SAM_RST Reset output for SAM1
Page 18 of 36

3 Firmware
3 Firmware
3.1 Memory View
The TWN4 Core Module has internal 256 kBytes of flash and 96 kBytes of RAM. The mem-
ory is devided into several sections as shown in the following diagram:
3.1.1 Boot Loader
The boot loader is the entry point for the firmware after powering up TWN4 or after a re-
set.
Only the boot loader provides functions for programming new firmware or Apps. This means
in order to program either a new firmware or another App, the boot loader must be en-
tered.
3.1.2 Firmware
The firmware occupies most space in flash memory. It provides functions for accessing
IO or doing RFID operations. Furthermore, the execution of an App is controlled by the
firmware.
The firmware cannot be read back from a TWN4.
Page 19 of 36

3 Firmware
3.1.3 App
The App is the part of flash memory, which specifies the behaviour of a TWN4. Due to this,
the programmer of the App has full control over the behaviour of the final application. An
App can be programmed by the customer. In order to do so, an appropriate developer pack
is provided.
An App cannot be read back from a TWN4. This allows to store secret keys and other
cryptographic functionality as part of an App. Furthermore, the possibility to clone a device
is avoided and the intellectual property is protected.
3.1.4 Storage
Storage is the section, where data is stored, which can be accessed via the storage func-
tions. In other words, in this aera, the file system is located.
Page 20 of 36