Specifications

10. Supported Platform Details
In the remainder of this document, we present some of the low-level details of each platform (physical
environment) you might be writing SNAPpy scripts for.
Some variations are due to differences in physical I/O (both quantity and capability). Each platform
specific section starts with information about the physical pins.
Other variations between platforms are due to the varying amounts of RAM available. Here is a high-
level overview of the types of memory management that is going on “behind the scenes.”
SNAP Buffers: The SNAP Protocol Stack uses a pool of “packet buffers.”
Buffer Budgets: The “buffer pool” is shared between the various data sources, but no single source is
allowed to use up all of the buffers. These numbers refer to how many buffers an individual data
source is allowed to request.
Dynamic Strings: Two pools of “string buffers” are used to service all the string operations.
The last variations presented are focused around differences in the various SNAPpy built-ins.
These are the currently supported platforms:
• Synapse RF100 SNAP Engine
• Freescale MC1321x chip
• Panasonic PAN4555 module
• Panasonic PAN4561 module
• Panasonic PAN4555 SNAP Engine
• Panasonic PAN4561 SNAP Engine
• CEL ZIC2410 chip
• CEL ZIC2410 SNAP Engine
• ATMEL ATmega128RFA1 chip
• Synapse RF200 SNAP Engine
• Synapse SM200 Surface Mount module
• Synapse RF266 module
• Silicon Labs Si100x chip
• Synapse RF300 SNAP Engine
• Synapse SM300 Surface Mount module
• Synapse RF301 SNAP Engine
• Synapse SM301 Surface Mount module
• Freescale MC13224 chip
• Synapse SM700 Module
• ST STM32W108CB chip
• ST STM32W108HB chip
SNAP Reference Manual Document Number 600-0007K Page 119 of 202