Specifications

Memory Usage
SNAP Protocol Memory Usage:
Global Buffer Pool: 20
UART Budget: 6
Mesh Routing Budget: 6
RPC Budget: 6
Radio Budget: 6
STDOUT Budget: 4
SNAPpy Virtual Machine Memory Usage:
Number of Tiny Strings: 14
Tiny String Size: up to 16 characters
Number of Medium Strings: 8
Medium String Size: up to 126 characters
Global Variables: 64
Concurrent Local Variables: 64
Maximum Call Stack Depth: 8
Platform Specific SNAPpy Built-In Functionality
Built-in function getInfo():
On a getInfo() call, a parameter value of 0 requests a “vendor code.”
On a ATmega128RFA1, getInfo(0) returns 4 (meaning “Atmel”).
On a getInfo() call, a parameter value of 3 requests a “platform code.” These are “per vendor” (not
global), so both RF Engines and ATmega128RFA1 nodes return a value of 0, indicating they are the
first platform from their respective vendors.
Built-in functions cbusRd() and cbusWr():
These functions have no effect on the ATmega128RFA1.
Built-in functions peekRadio() and pokeRadio():
These functions are not necessary on the ATmega128RFA1. The internal radio registers are in the
main memory space of the chip, and can be read or written using the regular peek() and poke()
functions.
Built-in function lcdPlot():
Built-in function lcdPlot() has no effect in ATmega128RFA1 builds.
Built-in function setPinSlew():
Built-in function setPinSlew() has no effect in ATmega128RFA1 builds.
Page 156 of 202 SNAP Reference Manual Document Number 600-0007K