MNZB-DKC-900 MeshNetics, MNZB-DKC-900 Datasheet - Page 42

• Manufacturer Part Number: MNZB-DKC-900
• Description: KIT DEV ZIGBIT 900 COMPLETE 1YR
• Manufacturer: MeshNetics
• Type: 802.15.4/Zigbeer

Specifications of MNZB-DKC-900

• Frequency: 868MHz, 915MHz
• For Use With/related Products: MNZB-900-B0
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 758-1009

7. Programming with BitCloud API
© 2008 MeshNetics
7.1. API Overview
7.2. Using AVR Programming Tools
BitCloud internal architecture follows IEEE 802.15.4, ZigBee-defined separation of the
networking stack into logical layers. Besides the core stack containing protocol
implementation, BitCloud contains additional layers implementing shared services (e.g.
task manager, security, and power manager) and hardware abstractions (e.g. hardware
abstraction layer (HAL) and board support package (BSP)). The APIs contributed by these
layers are outside the scope of core stack functionality. However, these essential additions
to the set of APIs significantly help reduce application complexity and simplify integration.
BitCloud Stack Documentation [4] provides detailed information on all public APIs and
their use.
The topmost of the core stack layers, APS, provides the highest level of networking-
related APIs visible to the application. ZDO provides a set of fully compliant ZigBee Device
Object APIs which enable main network management functionality (start, reset, formation,
join). ZDO also defines ZigBee Device Profile types, device and service discovery
commands implemented by the stack.
There are three service "planes" including: task manager, security, and power manager.
These services are available to the user application, and may also be utilized by lower
stack layers. Task manager is the stack scheduler which mediates the use of the MCU
among internal stack components and user application. The task manager utilizes a
proprietary priority queue-based algorithm specifically tuned for multi-layer stack
environment and demands of time-critical network protocols. Power management routines
are responsible for gracefully shutting down all stack components and saving system state
when preparing to sleep and restoring system state when waking up.
Hardware Abstraction Layer (HAL) includes a complete set of APIs for using on-module
hardware resources (EEPROM, app, sleep, and watchdog timers) as well as the
reference drivers for rapid design-in and smooth integration with a range of external
peripherals (IRQ, I2C, SPI, UART, 1-wire). Board Support Package (BSP) includes a
complete set of drivers for managing standard peripherals (sensors, UID chip, sliders, and
buttons) placed on a MeshBean development board.
It is recommended that Atmel’s AVR Studio [16] is to develop custom applications based
on BitCloud API. This multiplatform Integrated Development Environment (IDE) provides
the options for editing source code, compilation, linking object modules with libraries,
debugging, making executable file automatically, and more. See Section 3.3 for the IDE
installation instructions. Refer to the AVR Studio User’s manual for further instructions.
AVR Studio can be integrated with WinAVR – a suite of software development tools for
the Atmel AVR series of RISC microprocessors hosted on the Windows platform [19].
WinAVR contains a set of utilities including AVR GCC compiler, linker, automatic Makefile
generator, system libraries, etc. GCC compiler is designed to be executed on the
Windows platform, and is configured to compile C or C++ codes. For description of GCC
compiler see WinAVR documentation. You can find command options for compilation and
linking specified in [20].
In AVR Studio, the development of an application is organized under particular project. All
the necessary information about a project is kept in project file. Such files assigned to the
AVR Studio have an *.aps extension, so they open in AVR Studio automatically when
double-clicked.
Z I G B I T ™ 9 0 0 D E V E L O P M E N T K I T 1 . 3
U S E R ’ S G U I D E
Page 42/56