Si4010-DK

Rev. 0.1

17

3. The vLedOn() function code is bigger than simple GPIO_LED=1 and is not necessary for the Run part, so

conditional compilation for LED bug may still be an option.

One recommendation for using the vLedOn() function is that the user application would include monitoring of

several buttons pressed simultaneously. If that combination happens, then the vSys_Shutdown() is invoked and

the IDE chain would be able to connect to the part again. That would satisfy the power cycling requirement without

actually cycling the physical power to the device.

2.9. Notes about USB Adapter Use

The following facts are worth noting when using the IDE debug chain:

1.

Whenever the Reset button is pressed on the IDE, the system reset is invoked and the part goes through

a boot sequence.

2.

Every time the new code, in OMF or HEX format, is downloaded to the part through the IDE, the IDE

issues a system reset and the device reboots. The content of the RAM memories is not touched by the

boot, with the exception of the API reserved regions in CODE/XDATA and DATA/IDATA memories. The

register banks RB0, RB1, and RB3 are cleared by the boot routine.

3.

Whenever the ToolStick adapter is directly connected to the key fob design platform and the IDE is con-

necting to the part, the GPIO0 will be forcibly driven to 1 for about 260 ms around the beginning of the con-

nection sequence. In the Silicon Labs-provided key fob platform, the GPIO0 isolated by a resistor, then if

the user is pressing a GPIO0 button during the connection sequence, the GPIO0 value will be viewed as 1

by the internal CPU during the IDE connection to the device.

4.

It is recommended that the user uses the Burning adapter board along with the USB Debug Adapter.