ON Semiconductor RSL10, Начало работы

Страница: 48 / 51

www.onsemi.com
48
APPENDIX A
A.
Migrating to CMSIS-Pack
If you have an existing project and have not used the RSL10 CMSIS-Pack before, this section is for you. Starting
from SDK 3.0, the RSL10 firmware is no longer bundled with the Eclipse IDE. The RSL10 Eclipse IDE has been
optimized and rebranded as the ON Semiconductor IDE, and the RSL10-specific firmware is now delivered exclusively
as a separate CMSIS-Pack that can be imported into the IDE. For future RSL10 releases, you only need to download
and import the updated CMSIS-Pack. There is no need to re-install the Eclipse IDE if it has not been updated.
Existing Eclipse project files from previous SDK releases are not compatible with the new ON Semiconductor
IDE. Fortunately, migrating your existing project into the new IDE to take advantage of the CMSIS-Pack standard is a
straightforward process, as shown in the next section.
A.1 M
IGRATING AN
E
XISTING
E
CLIPSE
P
ROJECT TO THE
CMSIS-P
ACK
M
ETHOD
In order to tell whether your project is managed by CMSIS-Packs, check that a file with the
.rteconfig
extension is
present in the project folder. If not, your project is not managed by CMSIS-Packs and needs to be migrated. The easiest
way to migrate your existing Eclipse project to the new IDE is to start from one of the CMSIS-Pack RSL10 sample
projects, and follow these steps:
NOTE: This section assumes you know how to import the CMSIS-Pack and a sample application, as
shown in Chapter 3, “Getting Started with the Eclipse-Based ON Semiconductor IDE” on
page 7.
1. Decide on which CMSIS-Pack sample project to import. It is best to import a CMSIS-Pack project that looks
similar (in terms of libraries used) to the existing project you would like to migrate. For example, if your
existing application uses the Heart Rate Profile, you might want to import the
ble_peripheral_server_hrp
sample application as a reference.
2. Right-click the project and rename it as you wish.
3. Remove the source code from the sample project.
4. Copy over the source and header files from your existing project into the new one.
5. Open the RTE Configuration Wizard by double-clicking the
.rteconfig
file, and make sure all the software
components (libraries) required for your project are selected.
•
Pay special attention to the Bluetooth components, such as the Bluetooth Low Energy Stack, Kernel, and
Profiles. Ensure that these components have the correct variants selected (such as
release
,
release_light
, or
release_hci
).
• Some libraries might have been removed, such as the
weakprf.a
. This library has been replaced by the
stubprf.c
file that is automatically added together with the Bluetooth Low Energy Stack component, so
you no longer need to explicitly reference it.
• You can also remove (deselect) the software components that you do not need in your existing application.
• If you change the
.rteconfig
file, make sure to save it, so that it can update your project settings
automatically (such as the library paths, includes, etc.) to reflect the newly added or removed software
components.
6. Navigate to your project settings and add or remove the preprocessor
symbol
or
include
folders from your
existing project.
7. Build your application and make sure it builds correctly.
• In case of build errors related to missing components, files, or preprocessor symbols, go back to steps 5
and 6 and review your configuration carefully.
• If you encounter errors related to duplicated code, review the
RTE
folder in your application. Some files
that were common to multiple sample applications have been transformed into software components, such
as the BLE Abstraction, CMSIS-Drivers, etc.