Difference between revisions of "MCookie Upin27 Layout"

From Microduino Wiki
Jump to: navigation, search
Line 5: Line 5:
 
When a module uses a pin, it can be thought of as consuming or occupying a pin, which would make other modules attempting to use the same pin unusable. Although, care is taken to avoid conflicts with pin usage. Sometimes pin functionalities overlap between different modules.  
 
When a module uses a pin, it can be thought of as consuming or occupying a pin, which would make other modules attempting to use the same pin unusable. Although, care is taken to avoid conflicts with pin usage. Sometimes pin functionalities overlap between different modules.  
  
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.
+
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 | Known Conflicts]] to see a list of already known conflicts.
  
  

Revision as of 18:19, 16 May 2017

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

The pins usually connect to a Core module's pins. Core modules provide the pins. While other modules (non-Core modules) uses / consumes / occupies a pin. This enables the Core module to control, communicate, etc with the stacked module.

When a module uses a pin, it can be thought of as consuming or occupying a pin, which would make other modules attempting to use the same pin unusable. Although, care is taken to avoid conflicts with pin usage. Sometimes pin functionalities overlap between different modules.

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

Micromodule BUS I2CAddr (7bit) D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 A0 A1 A2 A3 SDA SCL A6 A7 5V 3V3 RST AREF
Core RX0 TX0 MISO MOSI SCK A4 A5 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
CoreBLE RX0 TX0 (A2) (A3) MISO MOSI SCK (D2) (D3) SDA SCL DC DD IN RST
CoreSTM RX0 TX0 RX1 TX1 DIO TCK MISO MOSI SCK SDA SCL IN IN RST
CoreMSP RX0 TX0 MISO MOSI SCK SDA_S SCL_S DIO (TCK)
USBTTL UART TX RX OUT OUT OUT
BLE Upload UART TX RX IN OUT
Ethernet(WIZ) SPI IRQ CS MISO MOSI SCK IN RST
Ethernet(ENC) SPI IRQ CS MISO MOSI SCK IN RST
RS485 UART (TX) (RX) (TX) (RX) (TX) (RX) IN
USBHOST SPI (INT) CS MISO MOSI SCK OUT IN RST
nRF SPI (IRQ) CSN CE MISO MOSI SCK IN
SmartRF SPI DO0 DO2 CS MISO MOSI SCK IN
Zigbee UART (TX) (RX) (TX) (RX) TX RX (RST) IN (RST)
BLE UART TX RX (TX) (RX) (TX) (RX) IN
WIFI,CC3000 SPI IRQ EN CS MISO MOSI SCK IN
WIFI,ESP UART (TX) (RX) TX RX IN RST
GPRS UART (TX) (RX) TX RX (DTR)
NFC I2C 0x24 SDA SCL IN
LED Matrix DI (DI) (DI) IN
RTC I2C 0x51(pcf) 0x50(eep) INT (INT) SDA SCL (IN) IN
SD SPI CS MISO MOSI SCK (CD) IN
Amplifier (RIN) (LIN) IN
Audio UART (TX) (RX) TX RX (TX) (RX) ADKEY OUT IN
Motion I2C 0x68(MPU) 0x1E(HMC) 0x77(BMP) (INT) (INT) SDA SCL IN
GPS UART (TX) (RX) TX RX IN
BM Li-ion (PD) (PD) (PD) OUT OUT
BM WirelessPower (PD) (PD) (PD) OUT OUT

Known Conflicts