Silicon Laboratories 4010-KFOBDEV-434 User manual

Rev. 0.1 6/12 Copyright © 2012 by Silicon Laboratories Si4010-DK
Si4010-DK
Si4010 DEVELOPMENT KIT USER’SGUIDE
1. Key Fob Development Platform
The Si4010 key fob development platform is a flexible platform for comfortably developing software and testing the
whole system using the Silicon Laboratories software development IDE. The platform also allows programming of
the NVM on chip. The kit has three versions: one for the 434 MHz band (P/N 4010-KFOBDEV-434), one for the
868 MHz band (P/N 4010- KFOBDEV-868) and one for the 915 MHz band (P/N 4010-KFOBDEV-915).
1.1. Kit Content
Table 1. Kit Content
Qty Part Number Description
4010-KFOBDEV-434 Si4010 Key Fob Development Kit 434 MHz
2 4010-KFOB-434-NF Si4010 key fob demo board 434 MHz w/o IC
1 MSC-DKPE1 SOIC/MSOP socketed development board
3 Si4010-C2-GS Si4010-C2-GS transmitter IC, SOIC Package
1 4010-DKPB434-BM Si4010 MSOP key fob development board 434 MHz, SMA
1 4355-LED-434-SRX Si4355 RFStick 434 MHz receiver board
1 MSC-PLPB_1 Key Fob Plastic Case (translucent grey)
1 MSC-BA5 Programming interface board
1 MSC-BA4 Burning adapter board
1 EC3 USB Debug Adapter
1 Toolstick_BA Toolstick Base Adapter
1 MSC-DKCS5 USB Cable
1 USB extender cable (USBA-USBA)
2 AAA AAA battery
2 CRD2032 CR2032 3 V coin battery
4010-KFOBDEV-868 Si4010 Key Fob Development Kit 868 MHz
2 4010-KFOB-868-NF Si4010 key fob demo board 868 MHz w/o IC
1 MSC-DKPE1 SOIC/MSOP socketed development board
3 Si4010-C2-GS Si4010-C2-GS transmitter IC, SOIC Package
1 4010-DKPB868-BM Si4010 MSOP key fob development board 868 MHz, SMA
1 4355-LED-868-SRX Si4355 RFStick 868 MHz receiver board

Si4010-DK
2 Rev. 0.1
1 MSC-PLPB_1 Key Fob Plastic Case (translucent grey)
1 MSC-BA5 Programming interface board
1 MSC-BA4 Burning adapter board
1 EC3 USB Debug Adapter
1 Toolstick_BA Toolstick Base Adapter
1 MSC-DKCS5 USB Cable
1 USB extender cable (USBA-USBA)
2 AAA AAA battery
2 CRD2032 CR2032 3 V coin battery
4010-KFOBDEV-915 Si4010 Key Fob Development Kit 915 MHz
2 4010-KFOB-915-NF Si4010 key fob demo board 915 MHz w/o IC
1 MSC-DKPE1 SOIC/MSOP socketed development board
3 Si4010-C2-GS Si4010-C2-GS transmitter IC, SOIC Package
1 4010-DKPB915-BM Si4010 MSOP key fob development board 915 MHz, SMA
1 4355-LED-915-SRX Si4355 RFStick 915MHz receiver board
1 MSC-PLPB_1 Key Fob Plastic Case (translucent grey)
1 MSC-BA5 Programming interface board
1 MSC-BA4 Burning adapter board
1 EC3 USB Debug Adapter
1 Toolstick_BA Toolstick Base Adapter
1 MSC-DKCS5 USB Cable
1 USB extender cable (USBA-USBA)
2 AAA AAA battery
2 CRD2032 CR2032 3 V coin battery
Table 1. Kit Content (Continued)

Si4010-DK
Rev. 0.1 3
1.1.1. Burning Adapter (P/N MSC-BA4)
The programming interface board serves as an interface in between the debug adapter and the Socketed Key Fob
Development Board or the Development Key Fob. It provides 6.5 V for NVM programming. The power source is
activated by a sliding switch on the board. It is required when the user wants to program the internal NVM memory
on the chip.
The programming interface board contains an 8-pin header, to which GPIO0 to GPIO5, along with power and
ground, are connected from the development boards. Therefore, the user can tap to that header to control or
monitor the chip pins.
1.1.2. Si4010 Socketed Key Fob Development Board (P/N MSC-DKPE1)
Socketed (both SOIC and MSOP) key fob board with SMA connector.

Si4010-DK
4 Rev. 0.1
1.1.3. Si4010 MSOP Key Fob Development Board 434 MHz, SMA (P/N 4010-DKPB434-BM)
This development board has an unburned soldered Si4010, five push buttons, matched 50 SMA RF output,
battery clip, and battery switch. This board allows running user application from RAM during program development
even while board is disconnected and powered by the battery. The SMA output connector allows wired
measurements of the RF output signal.
Note: Instead of this board, some 434 MHz development kits may contain the pcb antenna version of this board, described in
"1.2.2. Si4010 Key Fob Development Board 434 MHz" on page 7.
1.1.4. Si4355 RFStick 434MHz receiver board (P/N 4355-LED-434-SRX)
Receiver board factory programmed with the simple receiver program srx_demo. Can be used for link testing with
Si4010 programmed with the rke_demo.
1.1.5. Programming Interface Board (P/N MSC-BA5)
Adapter board for interfacing customer PCB to the debug adapter.

Si4010-DK
Rev. 0.1 5
1.1.6. 4010 Key Fob Demo Board 434 MHz without IC (P/N 4010-KFOB-434-NF)
1.1.7. Key Fob Plastic Case (translucent grey) (P/N MSC-PLPB_1)
1.1.8. Toolstick Base Adapter (P/N Toolstick_BA)
Debugging adapter compatible with Si4355 RFstick receiver board and the Si4010 development boards.
1.1.9. Si4010 sample, SOIC package (P/N Si4010-C2-GS)
1.1.10. USB Cable (P/N MSC-DKCS5)
Cable to connect EC3 Debug Adapter to PC.

Si4010-DK
6 Rev. 0.1
1.1.11. EC3 Debug Adapter (P/N EC3)
Silicon Labs debugging adapter, used by other Silicon Labs’ MCU products as well, compatible with the
development platform.

Si4010-DK
Rev. 0.1 7
1.2. Other Boards
The following boards are not part of the development kit but can be ordered separately from Silicon Labs.
1.2.1. Si4010 SOIC Key Fob Development Board 434 MHz, SMA
This board is similar to the board described in “1.1.3. Si4010 MSOP Key Fob Development Board 434 MHz, SMA
(P/N 4010-DKPB434-BM)” but contains the SOIC package version of the Si4010.
1.2.2. Si4010 Key Fob Development Board 434 MHz
This is also a key fob development board, but with a pcb antenna instead of the SMA connector.
Part Number Description
4010-DKPB434-BS Si4010 SOIC key fob development board 434 MHz, SMA
4010-DKPB_434 Si4010 key fob development board 434 MHz
4010-DKMX_434 Si4010 matrix keyboard development board 434 MHz
4010-KFOB-315-NF Si4010 key fob demo board 315 MHz w/o IC

Si4010-DK
8 Rev. 0.1
1.3. Usage of the Key Fob Development Platform
The Silicon Labs IDE communicates with the USB Debug Adapter through the USB bus. The following debugging
scenarios are possible:
1. EC3 debug adapter Burning adapterSi4010 socketed key fob development board
This setup is suitable for downloading, running, and debugging the program in RAM or burning the program in the
NVM and running it. The antenna or measuring instrument can be connected through an SMA connector. Since
sockets on board allow use of unsoldered ICs, this is the ideal scenario for burning the NVM memory of Si4010.
2. EC3 debug adapter Burning adapterSi4010 MSOP key fob development board
This setup is suitable for downloading, running, and debugging the program in RAM. This board has a PCB
antenna and battery, so after downloading the program and starting the execution by disconnecting in the IDE, the
board can be physically disconnected from the programming interface and tested in mobile form. A switch is
provided on the board to connect/disconnect the battery. The Toolstick Base Adapter can be also used in the two
above scenarios as a debug adapter. It can be connected to the pcb edge connector of the burning adapter.
Note: Although burning is also possible with this setup, it is not practical since Si4010 is soldered on the key fob development
board.

Si4010-DK
Rev. 0.1 9
3. EC3 debug adapter Programming adapterUser’s own application
In this setup, the user can incorporate the debugging capabilities into the final application using a cheap 4-pin
header connection.
2. Debugging an Application
To debug an application the user is provided with the Silicon Laboratories IDE (Integrated Development
Environment). The IDE has an integral help. This section is not a user manual for the IDE, but highlights the items
which are important when working with the IDE.
2.1. Installing the IDE and USB Debug Adapters
Download the Silicon Labs IDE (Integrated Dvelopment Environment) from the following URL:
http://www.silabs.com/products/mcu/Pages/SiliconLaboratoriesIDE.aspx and install it on your computer. The IDE
gets installed into its own directory. The main executable file is IDE.exe. The IDE works with the USB Debug
Adapter or the Toolstick Base Adapter, shown in the section above. When the IDE recognizes the Silicon Labs USB
debug adapters, it queries whether its internal firmware is compatible with the Si4010. If not, then it notifies the user
and requests permission to update the adapter's firmware. Silicon Labs also provides a program,
usb_debug_adapter_firmware_reset.exe, to clear the adapter's firmware manually before connection to
the IDE. The program resides in the same directory as the IDE main executable.
With the Si4010 debugging chain it is required that the manual adapter firmware clearing is done for each USB
adapter before using the key fob debugging chain. That operation needs to be done only once per USB Debug
Adapter. The IDE will then program the correct firmware into the adapter.
The reset firmware executable will scan USB ports and give the user a list of connected Silicon Labs USB
adapters. The USB Debug Adapter name starts with EC. Users can have more than one USB adapter connected
to the computer.
2.2. Keil toolchain integration
The project files in examples assume that the Keil toolchain is installed into: C:\Keil directory. The location of
the Keil toolchain can be easily changed in the Silabs IDE in the Project—Tool Chain Integration menu. An
evaluation version of the Keil toolchain can be downloaded from the Keil website at http://www.keil.com/. This free
version has a 2 kB code limitation and starts the code at the 0x0800 address. The Keil free evaluation version can
be unlocked to become a 4 kB version with no code placement limitation by following the directions given in
application note AN104 about Keil toolchain integration and license management. Unlock code can be found on
the WDS CDROM in the root folder in the Keil_license_number.txt file. Contact your Silicon Laboratories sales
representative or distributor for application assistance.

Si4010-DK
10 Rev. 0.1
2.3. IDE Features
The IDE allows the following:
1. Download the OMF-51 linker output format (Keil BL51 linker output, for example) and match the source
code lines with the compiled file. This allows source code debugging, including variable value viewing, set-
ting breakpoints, single-stepping, etc. Note that the output of the Keil LX51 linker is not understood by the
IDE.
2. Download the IntelHEX file for the application. When using the IntelHEX file the source code debugging is
not available. The user can set a breakpoint for a specific code address by going through the
Debug Breakpoints (Alt+B) menu item. The user can also single-step through the disassembly of the
loaded code.
3. Setting at least 4 breakpoints with a possible maximum of 8. The actual number of breakpoints available is
determined by the IDE from the factory setting of the chip.
4. Single-stepping through the disassembly of the code. If the OMF file is loaded, the single-stepping is
matched with the source code.
5. Viewing and changing variables, SFR registers, XREG registers, and the contents of both DATA/IDATA
RAM and CODE/XDATA RAM on the fly during debugging. When the changes are made by the user in the
corresponding windows, the user must press the Refresh Values (Alt+R) button on the toolbar to update
the values in the device. Just changing values in the IDE will not automatically update them in the device.
2.4. IDE Debugging Session
The typical IDE debugging session consists of the following sequence:
1. Connect the IDE to the chip by hitting the Connect or invoking menu Debug Connect menu item.
2. Download the OMF file either by hitting the Download code (Alt+D) toolbar button or from the
Debug Download object code menu item. The latter also allows IntelHEX download, but without the
source code debugging capability.
3. After the code download, the device is automatically halted at address 0x0000 in CODE/XDATA RAM.
Then the user can set breakpoints, single-step, animate, etc.
4. The user can hit the Reset (Ctrl+R) toolbar button any time the device is halted (not running). The internal
digital system level reset is invoked and the device goes through the boot sequence. The previously
loaded code by the user into the CODE/XDATA RAM is preserved and the device is halted at the address
0x0000 of CODE/XDATA RAM.
5. When a bug is found, the user can download a new OMF file whenever the device is halted. There is no
need to disconnect the device from the debug chain or to hit reset. The download, item 2 above, will auto-
matically reset the device after the OMF/IntelHEX new code download is finished. It is very important to
note that whenever the Disconnect toolbar button is hit or the Debug Disconnect menu item is
invoked, the debugging chain does the following:
• Enables the LED driver. During the debugging sessions the LED current driver is forcibly disabled.
• Clears all the breakpoints.
• Releases the device from halt and lets it run from the point when it was halted.
2.5. Important Note about Single-Stepping Over ROM Code
Single-stepping through the ROM code is disabled. Whenever the user encounters the call to the ROM API
functions he or she should use the Step Over (F10) toolbar button rather than the Step (F11) or Multiple Step
button.
Even though single-stepping through the ROM API function using the Step (F11) button works from the user’s
point of view, the CPU timing is modified and real-time performance is not guaranteed when using the Step (F11)
or Multiple Step buttons over the ROM API functions. Therefore, it is highly recommended to use the Step Over
(F10) toolbar button when stepping over the ROM API functions in IDE.
Single-stepping over the bMtp_Write() function using Step (F11) or Multiple Step buttons may yield
unpredictable results in the MTP (EEPROM) and is highly discouraged. One should use the Step Over (F10) tool,
run to cursor, or setting a breakpoint when debugging around the MTP write function.