|Published (Last):||7 August 2004|
|PDF File Size:||15.18 Mb|
|ePub File Size:||14.40 Mb|
|Price:||Free* [*Free Regsitration Required]|
Notes: 1. CF Target Board Rev. An installer will automatically launch, allowing you to install the IDE software or read documentation by clicking buttons on the Installation Panel. Refer to the ReleaseNotes. After installing the software, see the following sections for information regarding the software and running one of the demo applications. Follow the steps to copy the driver files to the desired location.
The final window will give an option to install the driver on the target system. If selected, the driver installer will now launch, providing an option to specify the driver installation location. It will let you know when your system is up to date. The driver files included in this installation have been certified by Microsoft. Windows will automatically finish the driver installation.
Information windows will pop up from the taskbar to show the installation progress. See Section 5. The use of third-party compilers and assemblers is also supported. Keil Evaluation Toolset 3. Keil Assembler and Linker The Keil demonstration toolset assembler and linker place no restrictions on code size.
Keil Evaluation C51 C Compiler The evaluation version of the C51 compiler is the same as the full version with the following limitations: 1 Maximum 4 kB code generation, 2 There is no floating point library included. When installed from the CD-ROM, the C51 compiler is initially limited to a code size of 2 kB, and programs start at code address 0x Configuration Wizard 2 The Configuration Wizard 2 is a code generation tool for all of the Silicon Laboratories devices.
Code is generated through the use of dialog boxes for each of the device's peripherals. Figure 2. Configuration Wizard 2 Utility The Configuration Wizard utility helps accelerate development by automatically generating initialization source code to configure and enable the on-chip resources needed by most design projects. In just a few steps, the wizard creates complete startup code for a specific Silicon Laboratories MCU.
The program is configurable to provide the output in C or assembly language. For more information, refer to the Configuration Wizard documentation. Documentation and software is available on the kit CD and from the downloads webpage: www.
It allows the user to select the type of battery they are using in the system and enter the supply current profile of their application. Using this information, it performs a simulation and provides an estimated system operating time. The Battery Life Estimator is shown in Figure 3. Figure 3. The discharge profile is application-specific and describes the the supply current requirements of the system under various supply voltages and battery configurations.
The discharge profile is independent of the selected power source. Several read-only discharge profiles for common applications are included in the pulldown menu. The user may also create a new profile for their own applications.
To create a new profile: 1. Select the profile that most closely matches the target application or choose the "Custom Profile". Click Manage 3. Click Duplicate 4. The four text entry boxes on the left hand side of the form allow the user to specify the amount of time the system spends in each power mode. On the right hand side, the user may specify the supply current of the system in each power mode. Since supply current is typically dependent on supply voltage, the discharge profile editor provides two columns for supply current.
The V2 and V1 voltages at the top of the two columns specify the voltages at which the current measurements were taken. The Battery Life Estimator creates a linear approximation based on the input data and is able to feed the simulation engine with an approximate supply current demand for every input voltage.
The minimum system operating voltage input field allows the system operating time to stop increasing when the simulated battery voltage drops below a certain threshold. This is primarily to allow operating time estimates for systems that cannot operate down to 1. This is typically the "sample rate" in low power analog sensors.
Once the battery type and discharge profile is specified, the user can click the "Simulate" button to start a new simulation. The simulation engine calculates the estimated battery life when using one single-cell battery, two single-cell batteries in series, and two single-cell batteries in parallel. Figure 5 shows the simulation output window. Figure 5. Battery Life Estimator Utility Simulation Results Form The primary outputs of the Battery Life Estimator are an estimated system operating time and a simulated graph of battery voltage vs.
Additional outputs include estimated battery capacity, average current, self-discharge current, and the ability to export graph data to a comma delimited text file for plotting in an external graphing application. Vision2 and? Vision debug driver allows the Keil? In-system Flash memory programming integrated into the driver allows for rapid updating of target code.
Vision3 IDEs can be used to start and stop program execution, set breakpoints, check variables, inspect and modify memory contents, and single-step through programs running on the actual target hardware. For more information, refer to the? Vision driver documentation. The documentation and software are available on the kit CD and from the downloads webpage: www. Remove power from the target board and the USB Debug Adapter before connecting or disconnecting the ribbon cable from the target board.
Build the OMF absolute object file by calling the Keil tools at the command line e. The default configuration when using the Silicon Laboratories IDE project manager enables object extension and debug record generation. To build an absolute object file using the Silicon Laboratories IDE project manager, you must first create a project. A project consists of a set of files, IDE configuration, debug views, and a target build configuration list of files and tool configurations used as input to the assembler, compiler, and linker when building an output object file.
The following sections illustrate the steps necessary to manually create a project with one or more source files, build a program, and download it to the target in preparation for debugging. Creating a New Project 1. Create your source file s and save the file s with a recognized extension, such as. Select Add files to project. Select files in the file browser and click Open. Continue adding files until all project files have been added.
For each of the files in the Project Window that you want assembled, compiled and linked into the target build, right-click on the file name and select Add file to build. Each file will be assembled or compiled as appropriate based on file extension and linked into the build of the absolute object file. Select Add Groups to project. Add pre-defined groups or add customized groups. Right-click on the group name and choose Add file to group.
Select files to be added. Building and Downloading the Program for Debugging 1. Before connecting to the target device, several connection options may need to be set. Once all the selections are made, click the OK button to close the window. Download the project to the target by clicking the Download Code button in the toolbar. If errors occur during the build process, the IDE will not attempt the download. Save the project when finished with the debug session to preserve the current target build configuration, editor settings and the location of all open debug views.
Create a new name for the project and click on Save. These files may be used as a template for code development. Example applications include a blinking LED example which configures the green LED on the target board to blink at a fixed rate. The register and bit names are identical to those used in the CF93x-CF92x data sheet. These register definition files are also installed in the default search path used by the Keil Software tools. Refer to the source file for step-by-step instructions to build and test this example.
Target Board The CF Development Kit includes a target board with a CF device pre-installed for evaluation and preliminary software development. Figure 9 on page 14 shows the factory default shorting block positions. CF Target Board 12 Rev. See Figure 8. Use for one-cell or two-cell mode. Battery Holder for 1. Use for two-cell mode only. Figure 9 shows the positions of the factory default shorting blocks.
R15 J16 P1. The power options vary based on the configuration one-cell or two-cell mode selected by SW4. The power options are described in the paragraphs below.
Single/Dual Battery, 0.9–3.6 V, 64/32 KB, SmaRTClock, 10-Bit ADC MCU