Specifications

getInfo() Differences
On a getInfo(0) call, the parameter value of 0 requests a “vendor code.”
On a Synapse RFE, getInfo(0) returns 0 (meaning “Synapse”).
On a PAN4555, getInfo(0) returns 2 (meaning “Freescale”).
On a getInfo(3) call, the parameter value of 3 requests a “platform code.” The PAN4555 returns a
value of 5, indicating MC1321x (the chipset the PAN4555 is based on).
SNAPpy scripts can use the getInfo() function to adapt themselves to the board they find themselves
running on. See also section 5 of this document, where an alternate method is explained.
Sleep() considerations
For most efficient sleeping, it is important for all the chip’s pins to be configured before sleeping – not
just the pins brought out by the SNAP Engine. Refer to the initUnusedIO() function in the
synapse.PAN4555.py sample script as an example of how to do this.
For Advanced Users Only
Here are the exact pin changes from a Synapse RF100 to a Panasonic PAN4555 when using the
SNAPpy GPIO import scheme.
SNAPpy
GPIO
ProcessorpinusedonRFE Processorpinusedon
PAN4555
1 PortABit0 PortCBit3
2 PortABit1 PortCBit2
5 PortABit4 PortCBit5
12 PortBBit6 PortGBit1
13 PortBBit5 PortGBit2
14 PortBBit4 PortDBit6
15 PortBBit3 PortDBit4
SNAP Reference Manual Document Number 600-0007K Page 133 of 202