SI4010-C2-GT Silicon Laboratories Inc, SI4010-C2-GT Datasheet - Page 80

• Manufacturer Part Number: SI4010-C2-GT
• Description: IC TX 27-960MHZ FSK 3.6V 10MSOP
• Manufacturer: Silicon Laboratories Inc
• Series: EZRadio®r
• Type: Crystalless SoC RF Transmitterr

Specifications of SI4010-C2-GT

• Package / Case: 10-MSOP
• Mfg Application Notes: SI4010 Calculator Spreadsheet AppNote
• Frequency: 27MHz ~ 960MHz
• Applications: Garage Openers, RKE, Security Alarms
• Modulation Or Protocol: FSK, OOK
• Data Rate - Maximum: 100 kBaud
• Power - Output: 10dBm
• Current - Transmitting: 19.8mA
• Data Interface: PCB, Surface Mount
• Antenna Connector: PCB, Surface Mount
• Memory Size: 4kB RAM
• Features: 8051 MCU Core, Crystal-less Operation
• Voltage - Supply: 1.8 V ~ 3.6 V
• Operating Temperature: -40°C ~ 85°C
• Operating Frequency: 27 MHz to 960 MHz
• Maximum Operating Temperature: + 85 C
• Mounting Style: SMD/SMT
• Operating Supply Voltage: 1.8 V to 3.6 V
• Supply Current: 14.2 mA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant, Lead free / RoHS Compliant
• Other names: 336-1997-5

Si4010-C2
Note that by using the unified CODE/XDATA memory and by mapping the IRAM to the boot process
address space the user can initialize both XDATA and IRAM variables directly from the User NVM load
without the need for running any startup code to do variable initializations, resulting in the saving of a code
size.
One application of the data initialization by a boot process could be copying of keys from the NVM to fixed
locations without any code intervention. The user can program all the chips with the same application in
the factory and then add only a very small, per chip, User block with keys, specifying where to the XDATA
and/or IRAM memories the boot process should copy the values of the keys.
For example, to initialize IRAM location 0x56 to 0xA4 value the user will provide and IntelHEX file specify-
ing that at the address 0x7056 the data value should be 0xA4.
24.10. NVM Programming
The user program/data is stored in the NVM memory in a proprietary form; therefore, the NVM program-
ming can be done only by the Silicon Labs provided composer and programmer utility. The data preparer
will take user generated application IntelHEX files, user settings (see below), and will generate data to be
programmed into the NVM. The NVM programmer then programs the data into the NVM.
During the composing/programming process the user will have control of the following:
1. Make Factory part a User part .. program User data into the NVM
2. Update User part .. add additional User data block to the existing User data already in NVM. This
3. Make User part a Run part .. mark a part as a final mission mode part. When making the part a Run
These steps can be combined into a single programming step. Step 2. is optional and is convenient when
part specific data needs to be added later to the NVM load.
To support the NVM programming Silicon Labs provides two utilities:


In addition, 3rd party programmer support is available for high-volume production programming. Silicon
Labs can also program parts directly for customers for high-volume production. Contact your Silicon Labs
representative for more details.
80
process can be done many times as long as there is a space in NVM.
part the user can decide whether the part retest will be allowed and if so, then what protection
restrictions the user is going to impose during the retest process.
NVM Programming Utility: The NVM configuration can be easily setup with this Microsoft Windows
based GUI. This application contains both the composer and burner functions. Please check the
application note AN511:NVM Programming User Guide for details
Command Line NVM programming application: This application can be integrated into the customer's
production line. This utility expects a composed NVM content file as an input (created by the NVM
Programming Utility). See the corresponding application note for details.
Rev. 1.0