MCookie Upin27 Layout

From Microduino Wiki
Revision as of 22:49, 23 May 2017 by Sonny (talk) (Notes)
Jump to: navigation, search

Each stack-able mCookie module uses a set of 27 pins.

Below is the chart which shows which pins are used for each specific module and can be used to find overlaps. If a conflict or overlap exist it is unlikely that both modules will be usable at the same time for a project.

See section Known Conflicts to see a list of already known conflicts.

Upin27 Layout

The Chart

Pin Color Legend
Color Meaning
Green Provides pin.
Red Occupies pin. Will conflict.
Grey Alternative pin for labeled name. Or unconnected pin.
Blue Uses pin, but does not conflict.


Module BUS I2CAddr (7bit) D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 A0 A1 A2 A3 A4 A5 A6 A7 5V 3V3 RST AREF
Core Modules
Core RX0 TX0 MISO MOSI SCK SDA SCL IN (IN) RST AREF
Core+ RX0 TX0 RX1 TX1 MISO MOSI SCK SDA SCL IN (IN) RST AREF
CoreUSB RX1 TX1 MISO MOSI SCK SDA SCL IN OUT RST AREF
CoreRF RX0 TX0 RX1 TX1 MISO MOSI SCK SDA SCL IN IN RST AREF
Core Programmers
BLE Upload UART TX RX IN OUT
mBattery UART TX RX OUT OUT OUT
USBTTL UART TX RX OUT OUT OUT
USBttlC UART TX RX OUT OUT OUT
Function Modules
Audio UART (TX) (RX) TX RX (TX) (RX) ADKEY OUT IN
AudioPro SPI MIDI DERQ MISO MOSI SCK DCS CS IN
Battery Management OUT OUT OUT
GPS UART (TX) (RX) TX RX IN
mBattery UART TX RX OUT OUT OUT
Motion I2C 0x68(MPU) 0x1E(HMC) 0x77(BMP) (INT) (INT) SDA SCL IN
SD SPI CS MISO MOSI SCK CD IN
RTC I2C 0x51(pcf) 0x50(eep) INT (INT) SDA SCL (IN) IN
Communication Modules
Bluetooth (BLE) UART TX RX (TX) (RX) (TX) (RX) IN
BLE Upload UART TX RX IN OUT
NFC I2C 0x24 SDA SCL IN
WiFi UART TX RX (TX) (RX) IN RST
Extension Modules
Amplifier RIN LIN IN
Hub Conflicts will occur if a Sensor / Trinket is connected to a pin used by another non-Core module. Read about Hub module. IN IN
Motor 2A 1A 2B 1B IN
LED Matrix DI (DI) (DI) IN
OLED I2C 0x3C SDA SCL IN

Known Conflicts

mCookie Programmers, mCookie WiFi and mCookie Bluetooth

  • mCookie Core Programmers uses pin D0, and pin D1 for programming and Serial communication (serial port from Core modules to Computer via Serial Monitor). Programming and Serial Monitor occurs at separate times, which means these will not conflict with each other.
  • mCookie WiFi and mCookie Bluetooth uses (by default) pin D0 and pin D1 for communicating to and from a Core module.
  • A conflict occurs on Core modules (Core, Core+, CoreRF) between mCookie Core Programmers and Communication modules such as mCookie WiFi and mCookie Bluetooth as they use the same pins (pin D0 and pin D1). Refer to chart to see overlap.
  • These conflicts can be avoid by rewiring the mCookie WiFi or mCookie Bluetooth module to a different set of pins by cutting the trace under the board and creating the appropriate solder bridge.

mCookie Motor

  • mCookie SD - Pin D7

mCookie SD

  • mCookie Motor - Pin D7

Pin Usage Examples

Example 1

  • A mCookie Core module is picked as a Core module. mCookie Core provides the pins for functionality.
  • A mCookie Motor is stacked. mCookie Motor uses pins D5, D6, D7, and D8 from the mCookie Core module. D5, D6, D7, D8 are now used / consumed / occupied by the mCookie Motor module.
  • No conflicts exists.

Example 2

  • A mCookie Core module is picked as a Core module. mCookie Core provides the pins for functionality.
  • A mCookie Motor is stacked. mCookie Motor uses pins D5, D6, D7, and D8 from the mCookie Core module. D5, D6, D7, D8 are now used / consumed / occupied by the mCookie Motor module.
  • A mCookie AudioPro is stack. mCookie AudioPro uses pins D13, D12, D11, D8.
  • Pin D8 is now conflicted. D8 on mCookie Motor is used for motor control. D8 on mCookie SD is used to select the SD card module in SPI mode. Therefore, both modules will not work correctly because of the overlapping pin.