Radio modules: deRFmega, deRFsam3 und deRFarm7
No, the circuit diagrams of the modules are generally not published. However, all information relevant to the user, including the internal wiring, is contained in the user manual. All available manuals can be found under Documentation or on the corresponding product page.
The Two-wire Serial EEPROM 'AT24C1024B' from Atmel is used. Its TWI address is determined by the external wiring of the two pins A1 and A2. This must be taken into account if the TWI bus is to be extended by further participants. Detailed information and the data sheet can be found on the Atmel-Webseite. The wiring of the EEPROM is described in the deRFmega128 User Manual.
The UART0 (TXD0 and RXD0) is available on the 6-pin connector of the deRFtoRCB adapter and Sensor Terminal Board.
The MAC address of the radio module is stored on the internal EEPROM of the ATmega128RFA1.
The start address is 0×00; the end address is 0×07.
The MAC address must be saved as follows:
EEPROM [0×00] = 55 (MSB MAC)
EEPROM [0×07] = 00 (LSB MAC)
Yes. This variant is offered in two versions: Either as deRFmega128-22A07 with U.FL socket or as deRFmega128-22A08 with chip-ceramic antenna. Due to the missing circuitry of the EEPROM, the following signals are available for free use with these modules:
- PD0 -> INT0/SCL (External Interrupt0 Input or TWI Serial Clock)
- PD1 -> INT1/SDA (External Interrupt1 Input or TWI Serial Data)
- PD6 -> T1 (Timer/Counter1 Clock Input)
The above mentioned pins are directly connected to the MCU in both versions.
Further Information: email@example.com
Two different quartz oscillators are available for clock generation:
- 16 MHz Quarz (on XTAL1 and XTAL2)
- 32,768 kHZ Quarz (on TOSC1 and TOSC2)
Especially for this purpose the deRFbreakout board is available. All electrical connections of the module can be used via the screw terminals. Appropriate pin headers are available for JTAG and TRACE. The deRFbreakout Board is suitable for all de radio modules.
Please refer to section 10.4 "Fuse Settings" in the User Manual.
Wireless Light Control
For questions about our products, simply visit the homepage of our brand.
Radio Controller Board und Sensor Terminal Board (RCB/STB)
No. The supply voltage VCC must not exceed 3.6 VDC.
VCC = 3,3 VDC
External sensors can thus be connected, provided they have the same operating voltage range.
For all products, except our wireless modules and USB sticks, circuit diagrams are available in the download area. Further information on the internal wiring of modules and USB sticks is available in the corresponding user manuals. If you cannot find what you are looking for there, please contact our support.
RCB230 V3.1 is equipped with the AT86RF230 Rev. A This type is discontinued and contains some hardware bugs. All errors are listed in the Errata Sheet 'doc5131' (see www.atmel.com) of the AT86RF230. RCB230 V3.2 on the other hand is equipped with AT86RF230 Rev. B Most of the errors have been fixed in this revision.
For this topic please contact our support: firstname.lastname@example.org!
Programming / Firmware
This procedure is described in detail in the corresponding programming manual.
Get all information here:
AVR-based (RCBs, deRFmega128 series):
with JTAG interface:
- Atmel AVR JTAGICE mkII (Programmer + Debugger)
- Atmel AVR Dragon (Programmer + Debugger)
with ISP interface:
- Atmel AVRISP mkII (Programmer)
ARM-based (USB radio sticks):
- Atmel AT91SAM-ICE JTAG Emulator (Programmer + Debugger)
- Segger J-Link (Programmer + Debugger)
- Amontec JTAGkey (Programmer + Debugger)
- OpenOCD USB adapter: e.g. from In-Circuit (Programmer + Debugger)
Yes, e.g. with Atmel AVRISP mkII (firmware V1.13). For example AVR Studio V4.18.700 (SP1 + SP2) can be used as programming software.
Unfortunately the 6-pin headers can not be used on the STB or the deRFtoRCB adapter. The connection between module and ISP programming adapter must be done by yourself. The following pins on the radio modules are necessary for ISP:
|Pin radio module
||Pin ISP Socket
|Pin 23 (DGND)||Pin 6 (GND)|
|Pin 17 (PDO/PB3)||Pin 1 (PDO)|
|Pin 15 (PDI/PB2)||Pin 4 (PDI)|
|Pin 13 (PB1/SCK)||Pin 3 (SCK)|
|Pin 5 (RSTN)||Pin 5 (Reset)|
|Pin 1 (VCC)||Pin 2 (VCC)|
SAMTEC SLM-123-01-L-S can be used. These are compatible with both deRFarm7 and deRFmega128. It is recommended to order them directly from www.samtec.com.
SAMTEC TMS-123-02-L-S are used for both the deRFarm7 and the deRFmega128. It is recommended to order them directly from www.samtec.com.
Yes, a corresponding library is available for download. The following modules are included:
Branding / License
There is no charge unless your product is sold as a member of the ZigBee Alliance with the appropriate logo and certification label (ZigBee Certified). ZigBee Alliance membership is required once the ZigBee logo is promoted on your product. Your product will then be subject to a paid review.
It is possible to apply a foreign label / logo to the metal lid. Our sales team will be pleased to submit you an individual offer.
Requirement: "Network open" must be activated in the WebApp.
|ID||0||extended pan id will be discovered during network search|
|SC||1FFE||scan on all channels for a network|
|ZS||2||ZigBee Stack Profile 2 (ZigBee PRO)|
|NK||0||Network Key will be transferred from trust center (or set here if known)|
|KY||5a6967426565416c6c69616e63653039||HA default trust center link key:|
One possibility is, for example, to permanently deactivate the device manually. As soon as your device is connected to the USB and the mouse starts "jumping", you have to navigate to the device manager by keyboard. The best way to do this is to press Windows key + pause. Afterwards, open the device manager in the control panel, also by keyboard. In the category "Mice and pointing devices" the wrongly detected device can now be permanently deactivated (not uninstalled!). To do this, select the entry in the context menu and choose "Deactivate". After plugging in the USB device again, you should be able to install the appropriate driver. The Microsoft Ballpoint should no longer be detected.
If this does not improve or solve the problem, please contact: email@example.com.
By modularization it is possible to include only those parts of the MAC used in the project in the firmware. Further dependencies result from the stack configuration (RFD/FFD, beacon support). If the stack is used fully with maximum functionality, the memory requirement is approx. 40 kByte flash memory.
Guide for AVR:
To develop software for Atmel AVR controllers using the Eclipse IDE, WinAVR is required. This package provides the compiler. During installation, make sure that WinAVR is added to the Windows PATH environment variable (will be queried during installation).
Optionally the AVR Eclipse Plugin can be installed.
A new empty project can now be created under Eclipse. At this point we will briefly explain how the Atmel MAC Stack is integrated as an Eclipse project.
Under Eclipse create a new C project with 'File -> New -> C Project'.
Under 'project type' select 'Makefile project' and below 'Empty project'. The tick in the box 'Use default location' must be removed. Via 'Browse' the unzipped MAC directory has to be selected. After the selection has been confirmed, the project can be created by clicking on the 'Finish' button after assigning a project name.
For each MAC stack example (e.g. Applications\PAL_Examples\Simple_Remote_LED_Control) is located within the respective platform (e.g:
ATMEGA128RFA1_deRFmega128_22X00_deRFtoRCB) the GCC directory where the Makefile can be found To execute a make with this Makefile, the following is necessary:
- open the corresponding window via 'Windows - > Show View - > Make Targets
- open the project and select the GCC folder in the corresponding example
- select the GCC folder and right click 'New' to create a new target
- here the targets 'all' and 'clean' have to be created
By means of the target 'all', the translation process is restarted when double-clicking. The target 'clean' deletes all newly created files. This process must be repeated for each example.
Instructions for ARM processors:
For setting up the toolchain for ARM7-based radio modules and USB sticks the following pages are available:
- Guide to setting up Eclipse and the ARM toolchain Yagarto
- very extensive tutorial about ARM and Eclipse
For the traceability of the internal calls of the stack the indexer has to be adapted (Project/Properties/C/C++ General/Indexer - > Select Indexer: Full Indexer). Since some symbols are only defined in the Makefile and thus not recognized by the indexer, it can help to define them additionally project-specific (Project/Properties/C/C++ General/Paths and Symbols -> Symbols -> GNU C -> Add). However, due to the stack-internal communication via queue (see MAC documentation), there are limits here as well.
Settings for transmitter and receiver:
(C) : Channel = 20 (any, but identical for transmitter and receiver)
(P) : Channel page = 0 (any, but identical for transmitter and receiver)
(W) : Tx power = 3 dBm
(N) : Number of test frames = 100 (or higher)
(L) : Frame length (PSDU) = 127
(A) : ACK request = no ACK requested
(F) : Frame retry enabled = false
(M) : CSMA enabled = false
(T/R/O/I) : Operating mode Tx/Rx/Off/Promiscuous = Tx
(T/R/O/I) : Operating mode Tx/Rx/Off/Promiscuous = Rx
The 2000 kbit/s is the gross data rate. This refers to the amount of data transmitted on the physical layer per time unit. Part of the transmission bandwidth is required for the transmission protocol itself. The remaining part is available for transmitting user data. The net data rate is approx. 1400 kbit/s, see data sheet ATmega128RFA1.