User Tools

Site Tools


m0dul

This is an old revision of the document!


The r0ket can easily be extended by pluggable m0dules.

See m0dules for existing m0dules.

Hardware

Please keep in mind that power is a very limited resource on the r0ket. The more a m0dule consumes the less fun you have!

Interface

A m0dule can be either connected via the m0dulebus or the hackerbus. All connectors are in 2.54mm/100mil spacing where only the m0dulebus is prepopulated with female sockets. If available a stackthrough connector should be used to interface with the m0dulebus. The hackerbus is intended for tinkering, a m0dule should use the m0dulebus only.

Please be aware that above the m0dulebus connectors the LCD and button is located - this area should not be covered by your m0dule.

As the m0dulebus and hackerbus connectors are not reverse polarity protected, you should document (eg marking your connector with a 1) how your m0dule should be plugged onto the r0ket.

The m0dul A and m0dul B connectors are rotated 180 degrees to each other. If your m0dule is symmetric and has no orientation requirements, it can be plugged both ways. Keep in mind though that the chip select pins on A and B differ (that should be configurable via defines in your software).

m0dul A m0dul B
SS0 SS3
SS1 SS4
SS2 SS5

Links: Eagle

M0dulebus

Connector: 2×06 female socket (2.54mm/100mil)

Pin Description
+3V3_EXP Fixed 3.3V
VCC Battery voltage (3.7-3.3V)
GND Ground
SCL, SDA I2C bus
MISO, MOSI, SCK SPI bus
SSx Chip select for SPI or general purpose IO
BUSINT Active LOW open-drain interrupt

Hackerbus

Connector: Optional (not prepopulated) 1×06 female socket (2.54mm/100mil)

Pin Description
+3V3_EXP Fixed 3.3V
VCC Battery voltage (3.7-3.3V)
GND Ground
HBx General purpose IO

Software

m0dul.1308489930.txt.gz · Last modified: 2011/06/19 15:25 by kiu