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

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

www.onsemi.com
50
APPENDIX B
B.
Arm Toolchain Support
There are several ways in which the ON Semiconductor IDE determines which Arm GNU toolchain to use when
building. Understanding how this works can help prevent confusion and frustration, when the development machine has
several versions of GNU toolchains installed.
B.1 B
ASIC
I
NSTALLATION
The ON Semiconductor IDE supports the Arm toolchain by installing it in the
arm_tools
directory within the
installed RSL10 software tools location. The build tools
RM
and
Make
are also included with the toolchain, to allow for
an easier building experience out of the box.
When the user starts the ON Semiconductor IDE with the
IDE.exe
program (whose shortcut is located in Windows
menu items), the
arm_tools\bin
directory is added to the path, to give the ON Semiconductor IDE access to the
toolchain installed with the RSL10 software tools.
Conflicts with toolchain versions can occur in the ON Semiconductor IDE, if an Arm-based toolchain has been
installed elsewhere or already exists on the path, and the IDE selects that toolchain rather than the one included in
arm_tools
.
B.2 C
ONFIGURING THE
A
RM
T
OOLCHAIN IN THE
ON S
EMICONDUCTOR
IDE
All toolchain location options can be accessed by right clicking on the project in the Project Explorer view,
selecting Properties at the bottom of the pop-up menu, and choosing the Toolchains tab. The scope of the toolchain
path support is described below.
Global Path:
This is the path used by all workspaces/projects. The global path can be set in the Toolchains
tab of the project.
Workspace Path:
This is the path used by all projects in the current workspace.
Project Path:
This is the path used by the current project for its toolchain.
B.3 A
DDITIONAL
S
ETTINGS
Additional settings (other than the toolchain paths) are located within the MCU preference. These are:
• The Build Tools path (global, workspace, project-based) for tools such as
Make
and
RM
• The Segger JLink path (global, workspace, project-based) for the location of the Segger JLink executables.
This replaces the Run/Debug string substitutions for JLink previously used
.