Specifications

Pin Configuration of an Si1000 in SNAP Engine Format (RF300/RF301)
EnginePin SNAPpyIO Name Description
1 GND PowerSupply
2 10 GPIO0ADC17P2.1 GPIO_0orADC17orI
2
CSDA
3 11 GPIO1ADC18P2.2 GPIO_1orADC18orI
2
CSCL
4 12 GPIO2ADC19P2.3 GPIO_2orADC19
5 13 GPIO3ADC20P2.4 GPIO_3orADC20
6 14 GPIO4ADC21P2.5 GPIO_4orADC21orSPIMOSI
7 15 GPIO5ADC22P2.6 GPIO_5orADC22orSPISCLK
8 0 GPIO6ADC0P0.0V
REF
 GPIO_6orADC0orINTorexternalvoltagereferenceorSPIMISO
9 4 GPIO7ADC5P0.5UARTRX GPIO_7orADC5orINTorUART0_RX
10 3 GPIO8ADC4P0.4UARTTX GPIO_8orADC4orINTorUART0_TX
11 2 GPIO9ADC3P0.3CTS GPIO_9orADC3orINTorUART0_CTS
12 1 GPIO10ADC2P0.2RTS GPIO_10orADC2orINTorUART0_RTS
13 (9) (GPIO11ADC16P2.0) NotAvailable
12
14 (8) (GPIO12ADC15P1.7) NotAvailable
15 (6) (GPIO13ADC13P1.5) NotAvailable
16 (7) (GPIO14ADC14P1.6) NotAvailable
13
17 5 GPIO15ADC6P0.6CNVSTR GPIO_15orADC6orINTorexternalconvertstartinputforADC0
18 16 GPIO16P2.7 GPIO_16
14
19 17 GPIO17(GPIO_0)
 15
GPIO_17
20 18 ANT_A GPIO_18(outputonly)
21 VCC PowerSupply
22 C2D BackgroundDebugCommunications
23 RESET* ModuleReset,ActiveLow
24 GND PowerSupply
12
Pins 13-16 are not available for use on the RF30x, and should not be tied to any hardware on devices you design. You
can load an RF30x with the Si100x firmware and have access to these pins, including SPI MOSI on GPIO_12, SPI SCLK
on GPIO_13, and SPI MISO on GPIO_14, with interrupts on those three pins as well. However you lose access to the
external memory on the RF30x, significantly reducing your available code space. If using the Si100x firmware, GPIO_4,
GPIO_5, and GPIO_6 do not have SPI capabilities.
13
The SNAP code will respond to attempts to read GPIO_14, and will even trigger GPIN-hooked events if monitored.
However if you connect external hardware to this pin, you might end up disabling the external memory on the RF30x,
rendering the chip inoperable. (Don’t do that.)
14
GPIO_16 has limited drive or sink strength, as it routes through a 1 KΩ resistor. The signal from (or to) GPIO_16 can
also be read from (or driven into) Engine pin 22, the debug pin, to route around this resistor instead.
15
This is GPIO_0 of the underlying radio hardware, and is unrelated to the GPIO_0 of the SNAP Engine. Refer to the
EZRadioPRO documentation for details.
Page 176 of 202 SNAP Reference Manual Document Number 600-0007K