TWN4 System Overview DocRev7, September 12, 2014 Elatec GmbH
Contents Contents 1 What is TWN4? . . . . . . . . . . . . . . 2 Products . . . . . . . . . . . . . . . . . . 2.1 TWN4 Core Module . . . . . . . . . . 2.1.1 Dimensions . . . . . . . . . . . 2.1.2 Connectors . . . . . . . . . . . 2.1.2.1 Connector A . . . . . . 2.1.2.2 Connector B . . . . . . 2.1.2.3 Connector C . . . . . . 2.1.2.4 Connector HF1 . . . . . 2.1.2.5 Connector HF2 . . . . . 2.1.3 Jumpers . . . . . . . . . . . . . 2.1.4 Power Supply . . . . . . . . . . 2.2 TWN4 OEM PCBs . . . . . . . . . . . 2.2.
Contents 5 Compatibility . . . . . . . . . . . . . 6 History of Changes . . . . . . . . . . 6.1 TWN4 Firmware . . . . . . . . . 6.1.1 Firmware V1.23 . . . . . . 6.1.2 Firmware V1.40 . . . . . . 6.1.3 Firmware V1.47 . . . . . . 6.1.4 Firmware V1.48 . . . . . . 6.1.5 Firmware V1.49 . . . . . . 6.1.6 Firmware V1.57 . . . . . . 6.1.7 Firmware V1.64 . . . . . . 6.2 AppBlaster . . . . . . . . . . . . 6.2.1 AppBlaster V1.03 . . . . . 6.2.2 AppBlaster V1.40 . . . . . 6.2.3 AppBlaster V1.47 . . . . . 6.2.
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).
2 Products 2 Products 2.1 TWN4 Core Module The TWN4 family of RFID readers/writers is built around the TWN4 Core Module.
2 Products The core module contains voltage regulator, control unit, RFID front ends and communication 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.
2 Products The connectors A, B and C have identical pitch. Following type of connector is recommended: • 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.
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.
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 antennas 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. Second connection for the speaker is ground.
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 asynchronous 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.
2 Products 2.1.3 Jumpers There are several jumpers on-board of the TWN4 Core Module. Depending on the requirements 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 powered via connector A, e.g. from USB.
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.
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.
2 Products Page 14 of 36
2 Products 2.2.
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 antenna and subset of IOs compared to TWN4 Core Module. TWN4 Mini Reader is currently available as version TWN4 Mini Reader MIFARE NFC.
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.
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.
3 Firmware 3 Firmware 3.1 Memory View The TWN4 Core Module has internal 256 kBytes of flash and 96 kBytes of RAM. The memory 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 reset. 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 entered. 3.1.
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.
3 Firmware 3.
3 Firmware 3.3 Firmware Startup Sequence The diagram below is showing the sequence of how boot loader, firmware and App are started: 3.4 Firmware Error Conditions There are several reasons, because the firmware may run into a unwanted condition. If this happens, the condition is shown by a on-board diagnostic red LED of the TWN4 Core Module. The LED is signalling the error code by a number of flashes separated by a pause.
3 Firmware This signalling is called blink code. Following blink codes are defined: • Flash 1 time: There is no valid firmware installed on TWN4. This might be caused, if programming a new firmware onto TWN4 is interrupted by a power failure. In this case, the programming must be started from the beginning. • Flash 2 times: There is no valid App installed on TWN4. This might be caused, if programming a new App onto TWN4 is interrupted by a power failure.
3 Firmware 3.6.2.1 Naming Scheme There is a standard naming scheme for firmware images, which are given to the customer.
4 TWN4 Developer Pack 4 TWN4 Developer Pack The TWN4 developer pack contains all software and documents necessary to operate, program and configure TWN4. Please see separate document for a detailed description of the program AppBlaster, which is used to prepare TWN4 for operation according to your requirements. 4.1 Installation You received the TWN4 developer pack as zip file.
5 Compatibility 5 Compatibility The table below is giving an overview about compatibility of TWN4 to various platforms and their requirements. System Mode Supported Windows XP RS232 Yes Windows 7 32/64 Bit Driver Remark Supported Port: by OS e.g.
6 History of Changes 6 History of Changes 6.1 TWN4 Firmware 6.1.1 Firmware V1.23 • Initially released version. 6.1.2 Firmware V1.40 Firmware: • LEGIC: System functions SM4200_xxx were renamed to SM4X00 due to support of LEGIC chip SM4500 with identical API. Old style of functions is still available via macros. • LEGIC: New system functions for reprogramming OS of LEGIC SM4200 or SM4500. • USB CDC: No modprobe required anymore under Linux. • USB CDC: TWN4 is mounted as /dev/ttyACMx instead of /dev/ttyUSBx.
6 History of Changes • Cotag: Improved reading with the additional option to turn off verify, which further speeds up recognition speed at still reliable reading performance • Cotag: Decoded reading of ID data instead of a hash value. • Inditag: Second read mode made available as known from TWN3 system function IndiTagSearch2 • Honeytag: Decoded reading of ID data instead of a hash value. • iCLASS: Support for SIO in a SAM slot. • iCLASS: Support for reading of PAC from appropriate transponders.
6 History of Changes • Functions memcmp, memcpy, memset are made available to Apps. • Definition for NULL • API for using the Simple Protocol from own Apps. • Function SetHostChannel for redirecting output to other than default host port. 6.1.4 Firmware V1.
6 History of Changes • ISO7816: Fix T=0 speed/timeout issue • AT55xx: Fix support of bit rates below f/64 6.1.7 Firmware V1.
6 History of Changes 6.2.2 AppBlaster V1.40 • New work flow based on projects and templates. • Save and load of projects. • Support for all new transponder types of TWN4. • Support for iCLASS PAC. • Possibility to generate production images. 6.2.3 AppBlaster V1.47 • Support of new types of transponders including NFC 6.2.4 AppBlaster V1.49 • Support for Cotag 48 bits 6.2.5 AppBlaster V1.57 • Include correct App name and version into firmware image • Support TWN4 Mini Reader Mifare NFC 6.2.
6 History of Changes 6.3.2 Director V1.06 • Support system functions of TWN4 firmware V1.
6 History of Changes • Support of USB HID reports • Support of TWN4 SmartCard (slot ID-1, ID-0/SAM, slot 3 and 4) • Support extended version string (Core Module or Mini Reader) 6.3.7 Director V1.16 • Support firmware V1.
7 Regulatory Information 7 Regulatory Information 7.1 FCC Statement 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. Section 15.
7 Regulatory Information this device must accept any interference, including interference that may cause undesired operation of the device. Le présent appareil est conforme aux CNR d’Industrie Canada applicables aux appareils radio exempts de licence.
8 Trademarks 8 Trademarks All referenced brands, product names, service names and trademarks mentioned in this document are the property of their respective owners.
