AN672 Просмотр технического описания (PDF) - Silicon Laboratories
Номер в каталоге
Компоненты Описание
Список матч
AN672 Datasheet PDF : 30 Pages
| |||
AN672
2. Relevant Documentation
Precision32 Application Notes are listed on the following website: www.silabs.com/32bit-mcu.
AN664: Precision32™ CMSIS and HAL User’s Guide
AN673: Precision32™ Software Development Kit (SDK) Overview
3. Examples
The examples for the si32Library install with the Precision32 package to the si32-x.y\Examples\si32Library
directory, where x is the major SDK version number and y is the minor SDK version directory. Some of these
examples are simple demonstrations of how to use the components, and some are full application examples like a
HID USB-to-UART bridge interface.
4. Component Architecture
The si32Library is structured as a collection of independent and cooperating components. A component is a
collection of related objects with a header file that includes any other components it may require, as well as any
internal objects or sub-components that it provides. Therefore, to use a component in an application or another
component, it is sufficient to include that component's header file and add the component's sources and its
dependencies to the project.
All components are named according to the form somethingComponent, where something is a meaningful
name like USB. The only exception is si32Library, which is the top level and does not have the Component suffix.
Every component is represented in the source tree as a directory. That directory contains the following types of
files:
* .h: The component and object header files collectively comprise the interface. All of the documentation
about the interface is here and not in the .c files.
* .c: The individual source files collectively comprise the implementation for the component. There may be
more than one implementation of any given interface. Documentation relevant to a specific implementation
is found here.
Some component directories contain subdirectories whose names also end in Component. These are sub-
components and follow the same structure recursively. Sub-components are used to provide logical groupings of
components.
There are some specific files that each application must possess. These files contain various elements that are
necessary for a build, but that are specific to each individual application.
myBuildOptions.h contains all of the build options. It allows the application developer to enable or disable
various compile time options, including assertions and debug logging.
myLinkerOptions_<chain>.<ext> contains the definitions for application specific configuration options
such as the desired stack and heap sizes. This file is included by the tool chain during compilation and is
used to configure the stack and heap. The supported <chain>.<ext> pairs are _p32.ld, _arm.sct, _iar.icf.
Applications do not include the myBuildOptions.h file directly because the si32BaseComponent of the
si32Library includes it. It is the very first file included because it specifies the build options for the si32Library.
Changes to this file to specify different build options require recompliation of the library. This allows each individual
application to configure the si32Library as desired without needing to modify any of the library code.
Figure 3 shows the dependencies of an si32Library-based application.
Rev. 0.1
3
Share Link: 