A N 5 1 5
6
Rev 1.0
5. Silicon Labs IDE Run
To run the IDE, open a *.wsp file e.g. aes_demo\bin\aes_demo.wsp with Silabs_IDE\ide.exe. Then, associate the
*.wsp extension with the Silabs_IDE\ide.exe file. To run the Silicon Labs IDE in general, open the *.wsp project file
or run Silabs_IDE\ide.exe.
6. Keil Toolchain Integration
The project files in examples assume that the Keil toolchain is installed to: C:\Keil directory. The location of the Keil
toolchain can be easily changed in the project files. An evaluation version of the Keil toolchain can be downloaded
from the Keil web site,
http://www.keil.com/
. This free version has 2 kB code limitation and starts the code at
0x0800 address. The Keil free evaluation version can be unlocked to become a 4k version with no code placement
limitation by following the directions given in application note “AN104: Integrating Keil 8051 Tools into the Silicon
Labs IDE”, which covers Keil toolchain integration and license management. Contact your Silicon Laboratories
sales representative or distributor for application assistance.
7. Known Issues
There is an issue related to the LED driver, which demonstrates itself only under the following circumstances when
all three conditions are satisfied:
1. The device programming level is Factory or User. For those levels, the C2 debugging interface is enabled after
the boot by a boot routine.
2. The device has been disconnected from the Silicon Labs IDE. “Disconnected” is meant in the software sense
(not physically) using the Connect/Disconnect buttons on IDE, or the device is running the User code
automatically after the boot without ever being connected to the IDE.
3. The device is running a code that turns the LED on and off.
If all the conditions are satisfied, after the first LED blink when the LED is turned off, the GPIO4 stops working and
is no longer visible to the application.
If the device programming level is Run or the C2 debugging interface is internally disabled, there is no issue. The
LED can be turned on and off without affecting the device GPIO4 functionality.
The issue can be summarized as follows: Whenever the C2 debugging interface is enabled and the device is not
connected to the IDE and the LED is turned on and off, then the GPIO4 will stop functioning. Since, in Run mode,
the C2 is disabled after the boot process finishes, the GPIO4 is not affected.
Therefore, this issue only affects the software development process and inconveniences the developer. After the
application is finalized and the chip is programmed as Run, there is no issue.
There are several possible software workarounds; see details in the Si4010 key fob development kit user guide.
Summary of Contents for AN515 Si4010
Page 7: ...AN515 Rev 1 0 7 NOTES ...
