MCookie Upin27 说明
每个mCookie模块都有Upin27引脚。
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. 。 下面的表格说明了某些模块会有特殊作用的引脚。这些引脚可以复用,但是某些情况下堆叠使用一些模块可能会造成引脚的冲突,需要注意一下。
无色:正常使用的引脚 红色:特殊功能引脚,可能会冲突 灰色:特殊功能引脚,但是默认不使用 蓝色:特殊功能引脚,但是不会引起冲突
目录
Notes
- Each stack-able mCookie module uses a set of 27 pins.
每个堆叠到一起的mCookie都是27pin的
- Core modules provides pins to other modules.
核心模块
- Only one Core module type should exist in a build / project.
在一个例程中有且只能有一个核心
- A Core module acts as a brain of a project where almost all pins need to be connected to in order to be accessible / functional.
核心模块就像一个程序的大脑一样,所余的引脚都需要连接到核心才能保证控制信号的正常传输
使用电池盒或者DUO这种类似模块可以降低模块堆叠的高度但是这些模块依然是跟核心模块连接在一起的
- Core Programmers are needed to upload a program to a Core module (except for CoreUSB, as there is an integrated programmer).
上传模块 上传模块是上传程序到核心必用的模块(CoreUSB除外)
- Core programmers use RX_ [pin D0] & TX_ [pin D1] on a Core module for programming.
- RX_ [pin D0] & TX_ [pin D1] are also used for Serial communication with the Serial Monitor from the Core module to the Computer.
上传程序给核心的时候会用到RX(D0引脚)TX(D1引脚).这两个引脚同时也是串口监视器数据传输的引脚。(上传核心监测到的数据给电脑)
- Programming and Serial Monitor does not cause a conflict.
上传程序跟串口监视不能同时进行(IDE上传程序的时候会自动屏蔽串口监视器,但是mixly打开串口监视器的时候上传按钮是不可点击的状态,一般情况两者不会产生冲突,但是如果使用了第三方的串口监视器软件可能会造成上传程序失败)
- RX_ [pin D0] & TX [pin D1] are also typically used by Communication modules such as Bluetooth and WiFi. Please be aware of this possible conflict.
RX与TX同时一般也是蓝牙跟WiFi的通讯端口,因此上传程序的时候不要叠加这两个模块以防造成冲突导致上传程序失败。
- Re-wiring on the Communication module may be needed in order to use a different pin set.
可以通过修改跳线的方法来避免跟核心通讯的冲突
- Other modules (non-Core modules) uses pins provided by Core modules
其他模块.(除去)
- Once a pin is being used / occupied, it should not be used by other modules. Unexpected behavior or interference can and will likely occur when there is a pin overlap.
当一个引脚被一个模块的特殊功能占用之后一般来讲就不能被其他模块使用了,否则会带来不可预期的问题。
- Pin names for a non-Core module are sometimes repeated.
有的模块管脚名字直接被特殊功能名称代替了(如图标所示)
- The default configuration is in not parenthesis, while a re-wiring alternative is in parenthesis.
- Some modules need to be re-wired in order to avoid pin conflicts. See individual pages for re-wiring information.
有些模块可以修改跳线来避免管脚冲突。请参见模块页面 (WiFi 蓝牙等模块) 修改跳线之后模块本来被占用的引脚将得到释放。
- Power is provided by power supplying modules such as mBattery, Battery Management, etc. The power pins 5V, 3V3 and GND are share-able across all modules and do not cause a conflict.
电源由mBattery,电池管理等供电模块提供。电源引脚5V,3V3和GND可以跨所有模块共享,不会引起冲突。
- Share-able communication pins such as I2C (SDA [pin A4] & SCL [pin A5]), and SPI (MISO [pin D11], MOSI [pin D12] & SCK [pin D13]) will not cause a conflict between modules. As they are designed to work as a share-able communication bus.
- If the pins for I2C and SPI are not used in their intended share-able communication bus mode. Then the pins will follow the typical pin conflict rules.
通信引脚如I2C(SDA [引脚A4]和SCL [引脚A5])和SPI(MISO [引脚D11],MOSI [引脚D12]和SCK [引脚D13])共用的时候不会冲突,IIC总线跟SPI总线本来就是可以连接多个设备的 但是当作IIC或者SPI总线使用的时候就不能当作模拟(数字)输入输出管脚使用了。
- Non share-able communication pins such as UART (TX_ & RX_) will cause a conflict between modules that attempt to use the same pins. As UART is not a shared communication bus.
但是UART总线只能连接一个设备因此如果共用之后会引起冲突。
- The Sensor Hub makes Sensors / Trinkets connectable to a Core module.
传感器接口模块
- It provides connectivity to almost all of the pins on the Core module.
几乎把核心所有引脚都做成了接口形式,用于连接传感器到核心模块以便控制。
- Be cautious when connecting a Sensor / Trinket to the Sensor Hub as that particular pin could be used by a non-Core module in the build / project.
需要注意,尽量不要把传感器连接到特殊功能的引脚,否则会引起冲突。
- Visit the Sensor Hub page for information on how a Sensor / Trinket will map to a Core module based on the labeling.
更多信息请查看传感器接口模块页面。
Known Conflicts
已知可能会冲突的地方
mCookie Programmers, mCookie WiFi and mCookie Bluetooth
程序上传模块与WiFi 蓝牙模块
- 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.
程序上传过程中会用到D0与D1,因此上传程序不能与串口监视同时工作。
- 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.
上传程序过程中如果叠加了WiFi或者蓝牙模块的话 也会产生冲突导致程序上传失败。
- 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.
可以通过修改跳线的方法把WiFi或者蓝牙的通讯端口改到D2 D3以避免上传程序产生的冲突。
mCookie Motor
- mCookie SD - Pin D7
电机模块会用到D7引脚,这个会与SD卡模块冲突
mCookie SD
冲突原理同上
引脚使用案例
案例一
- 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.
使用core作为核心的时候,如果用到电机模块,会占用掉D5 D6 D7 D8引脚,可以正常使用。 这些引脚将不可在作为输入输出端口使用。
案例二
- 核心模块使用的是 mCookie 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.
使用core作为核心的,同时用到了电机模块以及audiopro模块,因为电机模块会占用D5678,同时audiopro会用到D8 11 12 13,D8是电机模块的控制信号线同时也是audiopro调用SD卡模块的信号线,因此会产生冲突,不可以同时使用