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⚓︎

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

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.

MOXTET⚓︎

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.

HW Schematics⚓︎

For all MOX modules we also provide schematics

• MOX A
• MOX B
• MOX C
• MOX D
• MOX E
• MOX F
• MOX G
• MOX SDIO WiFi
• MOX PoE

NVMe adapter documents⚓︎

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

• PCB assembly layout
• Part references
• Various manufacturing definitions

Declaration of Conformity⚓︎

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