Si4010-DK

Rev. 0.1

11

2.6. Device Version

1.

The device ID information can be read through the IDE through Views

 Debug Windows  Si4010 

XREG Regs. The last item bREV_ID is the device revision. The user can also call the API function

bSys_GetRevId()

.

2.

The trim version can be read by the Silicon Labs IDE as External Memory through Views

 Debug Win-

dows -> External Memory at location 0x11D6. There is a macro bSys_TrimId_c defined in the headers

for use in customer code as well. The user needs to know the TrimId before writing any code, so the man-

ual access to it is adequate. The trim version will rarely change and customers will be notified about the

change.The provided NVM burner program reads both the bREV_ID device revision and the trim version

bSys_TrimId

in the [Device] tab after the burner is connected to the device.

2.7. Debugging Application which Drives LED

To maximize utilization of the package pins, the LED current driver output is shared with the debug chain clock

signal C2CLK. To share the functionality and be able to use the IDE for debugging there are some limitations to

note and rules to follow. The following figure shows the recommended connection of the USB 10-pin debug header

to the device in the user application.

Note: The LED must be isolated by the 470

 resistor for the debug chain to work.