Skip to content

MOX Hardware details⚓︎

MOX is an unique network device. It contains usual set of pins (I2C, GPIO, …) but also unique MOXTET bus. MOXTET bus allows us to extend MOX with various modules. The MOXTET bus provides access to faster buses like PCIe or SGMII.

It is based on Marvell Armada 3720 dual core armv8 CPU clocked at 1GHz. It can contain either 512M or 1G of RAM. Storage-wise it features one micro SD slot and 8MB SPI NOR flash that contains U-Boot and rescue system.

Network interfaces⚓︎

CPU in Turris MOX has two network interfaces. First one – eth0 – is connected directly to the gigabit Ethernet port on CPU module. Second one – eth1 – is 2,5 GBit and passed thought the MOXTET. If you have MOX D, then your SFP is eth1 directly and is able to do up to 2,5 Gbit.

Multiple switches⚓︎

MOX C and MOX D are simple examples of which network configurations can be created and it is probably quite obvious how do they work. Things get a little bit more complicated with MOX E. In that case, 2,5 Gbit link goes from CPU to the first switch which exposes 8 Gigabit ports for generic use, but internally has 10 ports. One of the two non-exposed ports is connected to your CPU and the other one is connected to MOXTET for future use by other modules. Both of them are 2,5 Gbit.

That other module on MOXTET can easily be another MOX E that would do the same thing. On both MOX Es you have 8x 1GBit ports, but the switches are connected to each other via 2,5 GBit links and only one of them is connected directly to CPU via 2,5 GBit link. That is something to consider when designing your network. Devices that exchange a lot of data quite often between each other should be connected to the same MOX E, while devices that hardly ever talk to each other can easily be on different switches. You want to minimize the amount of data that has to pass trough the switch as that could be a bottleneck.

For example, if you connect MOX D and use it as a WAN, then your traffic has to go through the switch(es) to the CPU, get natted/filtered/routed there and go through the switch(es) back to the final destination.

GPIO Pin Header⚓︎


Turris MOX uses 1.8V logic! Connecting to it to common devices with higher voltage logic will most likelly destroy your MOX.

You can find 34-pin GPIO connector On MOX A. Signals are as follows:

Description Signal Pin Pin Signal Description
System Ground GND 1 2 +1V8 GPIO Power Supply
Boot Configuration Option SetBoot.B0 3 4 SetBoot.B1 Boot Configuration Option
System Ground GND 5 6 +1V8 GPIO Power Supply
System and System Bus Reset nRES 11 12 JTAG.RSTn JTAG (GPIO1_24)
System Ground GND 15 16 ONE_WIRE One Wire (GPIO1_4)
GPIO 2 (PWM_3, LED_3) GPIO1_14 17 18 GPIO1_13 GPIO 2 (PWM_2, LED_2)
GPIO 2 (PWM_1, LED_1) GPIO1_12 19 20 GPIO1_11 GPIO 2 (PWM_0, LED_0)
System Ground GND 21 22 +1V8 GPIO Power Supply
I2C 2 Bus (GPIO1_3) I2C2.SDA 23 24 I2C2.SCL I2C 2 Bus (GPIO1_2)
System Ground GND 25 26 +1V8 GPIO Power Supply
U-Boot SPI NOR Flash Access SPI.nSS0 27 28 SPI.MISO U-Boot SPI NOR Flash Access
System and System Bus Reset nRES 31 32 GND System Ground
System Ground GND 33 34 +12V0 System Power Supply

PoE Pin header⚓︎

If you have PoE add-on attached, you have full GPIO connector inaccessible, but you can use small one on PoE add-on.

Description Signal Pin Pin Signal Description
System Ground GND 1 2 +1V8 GPIO Power Supply
Boot Configuration Option SetBoot.B0 3 4 SetBoot.B1 Boot Configuration Option
System and System Bus Reset nRES 5 6 GND System Ground


The Moxtet system bus is used to connect single boards of the MOX modular router. Bus connections can be used freely, but when using non-original MOX modules, make sure they maintain signal compatibility and do not damage other connected boards.

The Moxtet system uses a standard PCIe connector, but with different signals.

Description Signal Pin Pin Signal Description
System Ground GND A1 B1 GND System Ground
System Power Supply +12V0 A2 B2 +12V0 System Power Supply
+12V0 A3 B3 +12V0
System Bus Configuration (SPI) MISO A4 B4 +5V0_PG Power Supplies Start-Up Control
MOSI A5 B5 +3V3_PG
SCK A6 B6 +1V8_PG
SSn A7 B7 +1V5_PG
System and System Bus Reset SYSRSTn A8 B8 +1V35_PG
System Bus Device Reset DEVRSTn A9 B9 +1V2_PG
System Bus Interrupt INTn A10 B10 +1V15_PG
System Bus Power Supply +1V8 A11 B11 GND System Ground
System Ground GND A12 B12 GND System Ground
SerDes Support Signals Reserve (for future use) SD_RSVD.A13 A13 B13 SD.RX._P SerDes Reserve (for future use)
SD_RSVD.A14 A14 B14 SD.RX._N
SD_RSVD.A15 A15 B15 SD.TX._P
SD_RSVD.A16 A16 B16 SD.TX._n
System Ground GND A17 B17 GND System Ground
Serial Management Interface Bus (Ethernet) SMI.MDC A18 B18 SGMII.TX._N SGMII (up to 2.5 Gbps)
Not Used NU A20 B20 SGMII.RX._N
Not Used NU A21 B21 SGMII.RX._P
System Ground GND A22 B22 GND System Ground
System and System Bus I2C I2C.SCL A23 B23 USB2._P USB 2.0 (for miniPCIe)
I2C.SDA A24 B24 USB2._N
Not Used NU A25 B25 PCIE.RX._N PCIe 2.0
Not Used NU A26 B26 PCIE.RX._P
System Ground GND A27 B27 GND System Ground
PCIe 2.0 Reset PCIE_RESETn A28 B28 PCIE.TX._N PCIe 2.0
PCIe 2.0 Clock Request PCIE_CLKREQ A29 B29 PCIE.TX._P
Not Used NU A30 B30 PCIE_CLK._P PCIe 2.0 Reference Clock
Not Used NU A31 B31 PCIE_CLK._N
System Ground GND A32 B32 GND System Ground

HW Schematics⚓︎

For all MOX modules we also provide schematics

NVMe adapter documents⚓︎

The following manufacturing documents pertain to the adapter intended for NVMe disks in B and G modules.

Declaration of Conformity⚓︎

Turris MOX adheres to EU legislation. You can get download Declaration of Conformity.

2022-11-11 2019-07-23