DATASHEET SEARCH SITE | WWW.ALLDATASHEET.COM
Document overview
- Manufacturer or author: Provided By ALLDATASHEET.COM(FREE DATASHEET DOWNLOAD SITE)
- PDF pages: 22
Technical content
Rev. 0.1 2/12 Copyright © 2012 by Silicon Laboratories AN667 AN667 GETTING S TARTED WITH THE S ILICON L ABS PRECISION 32™ IDE 1. Introduction This application note describes the Precision32™ Integrated Development Environment (IDE) for the Silicon Labs 32-bit microcontrollers (SiM3xxxx). This IDE is based on the Eclipse platform. 2. Key Points Importing and building projects with the Precision32 IDE IDE Overview Debugging with the Precision32 IDE Getting Started: Blinky Example 3. Relevant Documentation Precision32 Help: In the Precision32 IDE, go to HelpHelp Contents Eclipse documentation: http://help.eclipse.org/indigo/index.jsp 4. Hardware Requirements The Precision32 IDE has the following hardware requirements: A standard x86 PC with 1 GB RAM minimum (2 GB recommended) and 500 MB+ of available disk space, running one of the following operating systems (both 32-bit and 64-bit systems are supported): Microsoft® Windows XP (SP2 or greater) Microsoft® Windows Vista Microsoft® Windows 7 An internet connection is required to request and activate license keys.
the workspace will be copied to this location if the copy projects into workspace option is selected. workspace, either browse to an existing workplace or select a new workspace location. Figure 1. Selecting a Workspace To change the workspace while the IDE is open, go to FileSwitch Workspace.
- Activating Precision32 IDE
process will require an internet connection.
- In the IDE, go to HelpProduct ActivationCreate Serial Number and Activate.
- Write down the displayed serial number or copy it to the clipboard.
- Press OK and a web browser will open on the Activations page. A mysilabs account is required to enter the
- Complete the rest of the form and press the button to request the activation code.
- Copy the activation code.
Product ActivationEnter Activation Code.
- Enter the activation code and press OK.
Once activated, the landing page will update and all features are available. Figure 2. Registered Landing Page
Figure 4. Automatically Opening a New Workspace
Quickstart view. Figure 8 shows the Clean menu option. Figure 8. Cleaning a Project
Rev. 0.1 9 8. Build Options Each project stores the project build settings . These settings can be accessed through the ProjectProperties menu or by right clicking in the Project Explorer view and selecting Properties. 8.1. Settings The C/C++ BuildSettings section contains most of the build settings for the project. The View build options for ‘project’ option in the Build and Settings section of the Quickstart view is another way to open this same build settings view. The C/C++ BuildSettingsTool Settings view has many options for optimization levels, display warnings, and other build settings. The C/C++ BuildSettingsBuild Steps view has options for pre- and post-build steps. These settings will not need to change for most applications. 8.2. Paths and Symbols The C/C++ GeneralPaths and Symbols section has settings for the project include paths for each configuration and language combination. When adding a path, select the Add to all configurations and Add to all languages options unless the paths should be omitted from configurat ions or languages. This settings view also contains libraries and library path information. 8.3. Build Configurations A build configuration is a named colle ction of build options. The Precision32 has two build configurations by default: Debug and Release. The Debug build configuration has no optimization and includes all debug symbols in the build. The Release build option has high optimization and includes no debug symbols in the build.
view windows and areas are completely configurable. Figure 9. Precision32 IDE Layout Overview After a successful build, Binaries includes the binary files associated with the project. Includes contains the external include files outside the project structure. The Debug folder contains the build information, include make files, object files, and other build outputs. The src folder contains all of the project source files. folder indicates that the file didn’t build correctly. In addition, icons indicate when linked resources cannot be found. Double clicking any files in the Project Explorer will open that file in the Code Editor view. one of these will jump to the corresponding line in the file.
future to include more features and tasks. easiest way to navigate the development tasks in the IDE. a function will display the first few lines of the function. Search view in the Status view. the mouse cursor provides more information about the problem. Figure 10. Code Editor Tags
highlighted in the upper-right corner of the IDE view as shown in Figure 13. Additional perspectives can be added. Figure 13. IDE Perspectives
not marked with blue are ineligible for breakpoints. without removing them. Double-clicking on breakpoint jumps to the related code in the Code Editor view. Figure 17. Breakpoint View or add variables to the Expressions watch view.
such as the NVIC are included with the peripherals. Figure 20. Core Registers View
- Getting Started: Blinky Example
- Open the Precision32 IDE.
- (Optional) Register the IDE using the steps listed in “6. Activating Precision32 IDE”.
- Set the Silicon Labs SDK path (C:\\SiLabs\\32bit\\si32-x.y by default) in the drop-down menu at the bottom
- Import the Blinky example project:
a. Click the Import SI32 SDK example(s) link in the Quickstart view. b. Select the checkbox for the Blinky project. c. Select the Copy projects into workspace checkbox.
- Select the Blinky project in the Project Explorer view.
- Build the project by selecting Quickstart
- Connect the Silicon Labs Debug Adapter ribbon cable to the header on the MCU card.
- Connect the Silicon Labs Debug Adapter to the PC.
- Start a debug session by selecting QuickstartDebug ‘Blinky’ [Debug].
- Press the DebugResume button to run the code. The LEDs on the MCU card will blink and the
Console view will print the status of the switches. Figure 22. Blinky Example
22 Rev. 0.1 CONTACT INFORMATION Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701 Tel: 1+(512) 416-8500 Fax: 1+(512) 416-9669 Toll Free: 1+(877) 444-3032 Please visit the Silicon Labs Technical Support web page: https://www.silabs.com/support/pages/contacttechnicalsupport.aspx and register to submit a technical support request. Silicon Laboratories and Silicon Labs are trademarks of Silicon Laboratories Inc. Other products or brandnames mentioned herein are trademarks or registered trademarks of their respective holders. The information in this document is believed to be accurate in all respects at the time of publication but is subject to change without notice. Silicon Laboratories assumes no responsibility for errors and omissions, and disclaims responsibility for any consequences resulting from the use of information included herein. Additionally, Silicon Laboratories assumes no responsibility for the functioning of undescribed features or parameters. Silicon Laboratories reserves the right to make changes without further notice. Silicon Laboratories makes no warranty, rep- resentation or guarantee regarding the suitability of its products for any particular purpose, nor does Silicon Laboratories assume any liability arising out of the application or use of any product or circuit, and specifically disclaims any and all liability, including without limitation conse- quential or incidental damages. Silicon Laboratories products are not designed, intended, or authorized for use in applications intended to support or sustain life, or for any other application in which the failure of the Silicon Laboratories product could create a situation where per- sonal injury or death may occur. Should Buyer purchase or use Silicon Laboratories products for any such unintended or unauthorized ap- plication, Buyer shall indemnify and hold Silicon Laboratories harmless against all claims and damages.