TEB061-S101-01.00.00.B0/en

IoT-Engine Hardware White Paper

May 2016
TRON Forum
http://www.tron.org/

Copyright © 2016 by TRON Forum. All rights reserved.

TEB061-S101-01.00.00.B0/en

IoT-Engine Hardware White Paper（Ver.1.00.00.B0）――――――――――――――――――――――――――――――――――――――――――
Copyright © 2016 by TRON ForumYou should not transcribe the content, duplicate a part of this specification, etc. without the consent of TRONForum.
For improvement, etc., information in this specification is subject to change without notice.
For information about this specification, please contact the following:

TRON Forum Secretariat Office
In YRP Ubiquitous Networking Laboratory,
Daiichi Seijitsu Building, 2-12-3
Nishi-Gotanda, Shinagawa, Tokyo 141-0031 Japan
TEL: +81-(3)-5437-0572
E-mail: office@tron.org

FAX：+81-(3)-5437-2399

Copyright © 2016 by TRON Forum. All rights reserved.

ii

TEB061-S101-01.00.00.B0/en

Copyright © 2016 by TRON Forum. All rights reserved.

iii

TEB061-S101-01.00.00.B0/en

Table of Contents

1.

Overview of IoT-Engine .................................................................52.

Hardware Specifications of IoT-Engine ..........................................82.1 Physical Form Factor of IoT-Engine Hardware ............................................................ 8
2.2 Signal Assignment ....................................................................................................... 92.3 Guideline for connector signal assignment .................................................................. 12
2.4 Variations of signal assignment ................................................................................... 14

Copyright © 2016 by TRON Forum. All rights reserved.

iv

TEB061-S101-01.00.00.B0/en

REVISION HISTORYNUMBER

DATE

PAGE

01.00.00.B0

2016/05/26-DESCRIPTIONREMARKS

Initial release

Copyright © 2016 by TRON Forum. All rights reserved.

v

TEB061-S101-01.00.00.B0/en

1.

Overview of IoT-Engine

IoT-Engine is the standard development platform that can let products (things) to collaborate in
the Internet and make appliances ready for the IoT (the Internet of Things). This is a
development platform, but is reasonably small as shown in figure 1-1, and can be embedded into
real devices. Standardization is done by the IoT Working Group of TRON Forum. The
standardized portion will be made open to the public.
IoT-Engine is MPU-agnostic and semiconductor companies can create IoT-Engine with their own
unique MPUs. IoT device makers, in turn, can use IoT-Engines that uses MPU suited forparticular applications and develop products in a short time-to-market.

Figure 1-1 An example of IoT-Engine
IoT-Engine comes with wireless module to connect to the Internet. IoT-Engine uses
energy-efficient IEEE 802.15.4 for wireless communication. IoT-Engine has adopted
IPv6-compatible protocol over UHF-band with the communication speed of 100 - 400 kbps thatcomplies with WPAN (Wireless Personal Area Network), a standard for short-distance wirelesscommunication. Devices that use IoT-Engine connect to the Internet via a so-called 6LoWPAN
border router which is reached by low-power short distance wireless communication as shown infigure 1-2. This border route plays the role of access point in the case of Wi-Fi.
Note: In figure 1-2, the 6LoWPAN boarder router connects to a Wi-Fi router via Wi-Fi, but there are
6LoWPAN border routers that connect to wirefull LAN.

IoT-Engine specifies that IEEE802.15.4 wireless function module as part of standard, and thismodule can be joined to the MPU module. Wireless function can be implemented as part of theMPU module, or MPU can implement the wireless function on its own. IEEE802.15.4 uses
Copyright © 2016 by TRON Forum. All rights reserved.

6TEB061-S101-01.00.00.B0/en

different frequencies in each country/region in the world, so replaceable wireless module canmake the adoption of modules customized for each country's wireless regulations easy, and isconvenient for development. Figure 1-3 shows an example of wireless module that is joined toMPU module.

Figure 1-2 The overview of the connection between IoT-Engine and a 6LoWPAN border router

Figure 1-3 An example of wireless module that is joined to MPU module
IoT-Engine specifications include standards for hardware, wireless communication, andoperating system, but they are not limited to them only. Rather, it includes the protocol between
the Open IoT Platform, i.e., the IoT Aggregator and IoT-Engine compliant devices cancollaborate with each other and can use various cloud services. As shown in figure 1-4,
IoT-Engine compliant devices from different manufacturers can collaborate with each other.
Between IoT-Engine and the cloud, the WPAN and the Internet are used. Since securecommunication channel is established between IoT-Engine and the cloud, we can view theconnection between the IoT-Engine and the cloud as direct. Access control to allow what users
should do what on which devices is managed on the cloud.
Copyright © 2016 by TRON Forum. All rights reserved.

7

TEB061-S101-01.00.00.B0/en

Figure 1-4 Device coordination by Open IoT Platform

Copyright © 2016 by TRON Forum. All rights reserved.

8

TEB061-S101-01.00.00.B0/en

2.

Hardware Specifications of IoT-Engine

2.1 Physical Form Factor of IoT-Engine Hardware
IoT-Engine standardizes the size and positions of board connectors and screw holes as in figure
2-1.
The board dimensions are not standardized. In figure 2-1, the sizes in () are for information
purposes only and non-normative.

Figure 2-1 IoT-Engine module mechanical specification

A Wireless module can be connected to MPU board via small board, integrated in MPU-chip, or
can be placed on MPU board. IoT-Engine uses IEEE 802.15.4 wireless communication channelsof sub-GHz UHF or 2.4 GHz band. Sub-GHz UHF band uses different frequencies in eachcountry/region in the world. IoT-Engine complies with 920 MHz ARIB T-108 in Japan.
The position of 920 MHz 6LoWPAN module in the case of separate wireless module is shown in
dotted lines for information purpose only and non-normative. It is possible to implement theantennae that goes outside the IoT-Engine MUP board so that the antennae are not easily
Copyright © 2016 by TRON Forum. All rights reserved.

9

TEB061-S101-01.00.00.B0/en

affected by the components on the board and printed wiring.
IoT-Engine uses Hirose DC40C-100DP-04V, a 0.4mm-pitch 100-pin connector that is mounted
on MPU side of the board. The distance between vertical center line and the screw hole above
the connecter in the figure is 4.5 mm. The distance between the horizontal center line and screw
hole is 14 mm. The screw hole is 2.5φ. The connector signal near the fixed screw position in thestandard is designated as signal pin No. 1. The odd-numbered pins are on the side of the edge
connector of the board.
In the case of separate wireless module, a designer is advised to place the wireless module on
the other side of the connector. If the antennae is placed on the board, it is possible to implement
the antennae that goes outside the IoT-Engine MPU board.
As an example of wireless module which can be used in Japan, IoT-Engine equipped with UC
Technology U02X0014 (RohmBP35A1that uses IoT-Engine connector firmware) uses JST 20P
3.0-JMCS-G-TF as its connector.
2.2 Signal Assignment
The signal assignment of IoT-Engine 100pin connector is shown in Table 2-1. The left side of thetable is the edge side of the board. The hatched SIGNAL ASSIGNMENT names are
Arduino-compatible I/O signals . These signals are sent to the IoT-Engine development board as
Arduino-compatible I/O connector, so many commercially available sensors, interface boards,
and extension boards that can connect to the I/O connector of Arduino, etc. can be utilized.
Note: The field of T-Car in figure 2-1 shows the usage of the signal for T-Car , a model carwhich uses IoT-Engine development board and the interface signal that can connect tosensors. These signals need to be assigned when T-Car is used.
Signal assignments are classified according to types as shown in the TYPE field of the connector
signal table: P for digital port, S for multifunction serial port, A for analog port, etc. The latest
MPU can overlay different functions on the same I/O pins by programming, and different
members of an MPU family often has different number of pins and different I/O functions. So it is
impossible to perform common signal assignment for all the MPUs. However, we can follow theguideline in table 2-2, and use the preferred pin (with smaller pin number) in the same type firstwhen we assign signals to reach a very general rough compatibility.
Type U stands for user's custom signal assignment, and you do not pay attention to thecompatibility issue for those pins. Type KEY for system use can specify the mode of the system
power supply in three mode: open, pull-up, and pull-down. Type R is used when RF module has
a controller CPU, and is used for assigning the mode signal and debug signal to it.
Copyright © 2016 by TRON Forum. All rights reserved.

10

TEB061-S101-01.00.00.B0/en

Table 2-1 IoT-Engine 100pin connector signal assignment (Part 1)

Copyright © 2016 by TRON Forum. All rights reserved.

11

TEB061-S101-01.00.00.B0/en

Table 2-1 IoT-Engine 100pin connector signal assignment (Part 2)

Copyright © 2016 by TRON Forum. All rights reserved.

12

TEB061-S101-01.00.00.B0/en

2.3 Guidelines for connector signal assignment
Utilizing the features of the on-board MPU, the priority of signal assignment is specified to ensure
the minimum-level of compatibility. Table2-2 shows the categorized signals to be assigned toeach group. Regarding the compatibility, the items with ★ are basically compatible with thesignals in the table. JS and MS depend on MPU.

Table 2-2 Guidelines for connector signal assignment
Digital PortTYPE[P0] ★

Arduino I/O-compatible UART

[P1] ★

Arduino I/O-compatible -INT/IO/PWM[P2]

Arduino I/O-compatible -INT/IO[P3] ★

Arduino I/O-compatible I2C[P4]General-purpose I/O, PWM

Analog Port
TYPE
[A0] ★

Arduino I/O-compatible AI (analog input)[A1]

Arduino I/O-compatible AI (analog input)[A2]

AI (analog input)[A3]

AI (analog input) or I2C[A4]

AI (analog input) or AO (analog output)[A5]

AI (analog input)[S2] shared area

Multifunction/Serial Port (USART: Can be used as SPI/UART/I2C.)
TYPE[S0] ★

Arduino I/O-compatible SPI[S1]SPI for SD card

[S2] ★

UART (for debug)

[S3]

UART

[S4]

General-purpose I/O[A5] shared area

User I/O (user custom signal)
TYPE
[U0]

User I/O (UART is added)[U1]

User I/O

Copyright © 2016 by TRON Forum. All rights reserved.

13

TEB061-S101-01.00.00.B0/en

For System Use
TYPE
[JS]
[Q0]

For debugger connection★

- NMI and interrupt for standard systems[Q1]

Interrupt for USB/SD or GPIO

[MS]- RESET and mode signal[RS]

RTC and signal for power management

[KEY]

★

Mode specification of power-supply voltage,etc. (See the appendix for the details)

RF Module Custom Signal
TYPE
[R0]

Mode signal, etc. for RF[R1]

Debug signal for RF

Mode specification of power-supply voltage, etc.
KEY1

KEY2

Vcc voltage

OPENOPEN

3.3 V

Pull Down

OPEN

2.5 V

OPEN

Pull Down

1.8 V

Pull Down

Pull Down

5V

OPEN

Pull Up

3.3 V

Other

The maximum voltage of I/O device is 5V.

Pull UpOPEN

3.3 V

w/o AI (analog input) signal

Pull Down

Pull Up

2.5 V

w/o AI (analog input) signal

Pull Up

Pull Down

1.5 V

w/o AI (analog input) signal

Pull Up

Pull Up

reserve

Reserve“The maximum voltage of I/O device is 5 V.” in Mode specification of power-supply voltage, etc.
can identify by using this KEY when the power-supply system of MPU is 3.3 V, but the I/O canconnect 5 V system. “w/o AI signal” has A0 in the field with★ to ensure the compatibility.
Identification can be performed by using the KEY when some MPU does not have analog input.

Copyright © 2016 by TRON Forum. All rights reserved.

14

TEB061-S101-01.00.00.B0/en

2.4 Variations of signal assignment
The followings are examples of various assignments to meet requirements such as “I2S, CAN,etc. need to be assigned” and “If the debug signal is different from Table 2-1, where can it beassigned?” according to the type of on-board MPU.
The even-numbered IoT-Engine connector signals are application signals of the devices mainly
controlled by IoT-Engine. The odd-numbered signals are the ones of the MPU system ofIoT-Engine which are used for debugging and or connecting the programs and data storage. It
is recommended to assign signals by considering these grouping approach.

SPI signal

I2C signal

I2S signal

TYPE

PIN

SIGNAL

S3-INT

S3-INT

I2SWS

S33-WKUP

S3-SCLK

S3-SCLI2SCK

S35SCK

S3-MOSI

S3-SDAI2SDO

S37TXD

I2SDI

S39RXD

S3-SS

S311GPIO

DA signal

TYPE

PIN

SIGNAL

DA0P435

PWM /DAC

S3-MISO

USART signal

I2C signal

SIM card signal

TYPE

PIN

SIGNAL

S1-RXDS1-INT

IC_CLKS139

MISO, IO12S1-TXD

S1-SDA

IC_VCCS141

MOSI, IO11

S1-SCK

S1-SCLIC_VPEN

S143

CLK, IO13

IC_RST

S145

SS, IO10GND

47

GND

IC_DATA

P249

PWM, IO9 (PWM)

IC_CINP251

GPIO, IO8 (IO)

USART signal

I2C signal

TYPE

PIN

SIGNAL

A1-RXD

A1-INT

A171

AIN, A3

A1-TXD

A1-SDA

A173

AIN, A4

A1-SCK

A1-SCL

A175

AIN, A5

Copyright © 2016 by TRON Forum. All rights reserved.

15

TEB061-S101-01.00.00.B0/en

RF SPI signal

RF JTAG signal

TYPE

PIN

SIGNAL

RF_SCLK

RF_TCK

R185

RF_SWCLK

RF_SS

RF_TMS

R187

RF_SWDIO

RF_MOSI

RF_TDO

R189

RF_SWO

RF_MISO

RF_TDI

R291

RF_NMI

RF_RESET

RF_TRST

R293

RF_RESET

RF_MODE

RF_MODE

R295

RF_MODE

TYPE

PIN

SIGNAL

KEY

97

EEPROM signal
KEY-SDA

Pull-Uprequirement

KEY-SCLKEY2Pull-Up

KEY

99

requirement

KEY1USART signal

I2C signal

TYPE

PIN

SIGNAL

U0-RXD

U0-INT

U06

USER-OPT1U0-TXD

U0-SDA

U08

USER-OPT2

U0-SCK

U0-SCLU010USER-OPT3USART signal

I2C signal

DA signal

TYPE

PIN

SIGNAL

U1-SCL

DA1U112USER-OPT4U114USER-OPT5U116USER-OPT6JTAG signal

TYPE

PIN

SIGNAL(RTCK)

U112USER-OPT4TRST

U114USER-OPT5

TDI/P_MISO

U116

USER-OPT6GND

18GND

U1-TXD

U1-SDA

U1-RXDcJTAG signal

TCK

TCK/P_SCLK

JS

20

SWCLK

TMS

TMS/P_SS

JS

22

SWDIO

TDO/P_MOSI

JS

24

SWO

Vref

JS

26

Vref (Pull-Up)

Copyright © 2016 by TRON Forum. All rights reserved.

16TEB061-S101-01.00.00.B0/enCMSIS signal

CMSIS signal

TYPE

PIN

SIGNAL<GND>

U112USER-OPT4CMSIS_DAP+U114USER-OPT5

CMSIS_DAP-U116USER-OPT6GND

18GND(CMSIS_DAP+)

JS

20

SWCLK

(CMSIS_DAP-)

JS

22SWDIO(<GND>)

JS

24

SWO

JS

26

Switching

Drive to [L]signal

Vref (Pull-Up)

USART signal

I2C signal

TYPE

PIN

SIGNAL

S0-RXDS0-INT

S042

MISO

S0-TXD

S0-SDA

S044

MOSI

S0-SCK

S0-SCL

S046

CLK

UART Signal

CAN Signal

RS485 Signal

TYPEPIN

SIGNAL

TXD

CAN_H

D+USB50D+RXD

CAN_L

D-USB

52

D-USART signal

I2C signal

SPI signal

TYPE

PIN

SIGNALS4-RXD

S4-INT

S4-MISO

S456

GPIO

S4-TXD

S4-SDA

S4-MOSI

S458

GPIO

S4-SCK

S4-SCL

S4-SCLK

S460

GPIO

S4-SS

S462

GPIO

LED I2S signal

TYPE

PIN

SIGNAL

I2SDI

S456

GPIO

LED-A

I2SDO

S458

GPIO

LED-B

I2SCK

S460

GPIO

onboardsignal

Copyright © 2016 by TRON Forum. All rights reserved.

17

TEB061-S101-01.00.00.B0/en

I2SWS

S462

GPIO

BOOT signal

TYPE

PIN

SIGNAL(BOOT)MS

68

MODE0

SPI signal

USART signal

SIM card signal

TYPE

PIN

SIGNAL

S2-SS

S2-RTS

IC_CLK

S272

CTS

S2-MOSIS2-TXD

IC_VCC

S274

RXD

S2-MISO

S2-RXD

IC_VPEN

S276

TXD

S2-SCLK

S2-SCK

IC_RST

S278

SCK

S2-INT

S2-CTS

IC_DATA

S280

RTS

GND

82

AGND

(IC_CIN)

A284

AI

UART Signal

TYPE

PIN

SIGNAL

S2-SDA

S276

TXD

S2-SCLS278

SCK

S2-INT

S280

RTS

GND

82

AGND

A2-SDA

A284

AI

A2-SCL

A286

AI

S5-RXD

A3-INT

A388AIS5-TXD

A3-SDAA390

AI

S5-SCK

A3-SCL

A392

AI

A494

AI

S6-RXD

A4 (S6)96

AI

S6-TXD

A4 (S6)98

AI

USART signal

I2C signal

Copyright © 2016 by TRON Forum. All rights reserved.

18