ON Semiconductor RSL10 User manual

© SCILLC, 2018
Previous Edition © 2017
“All Rights Reserved”
Getting Started with RSL10
AND9697/D
Nov. 2018, Rev. P3

GETTING STARTED WITH RSL10
www.onsemi.com
2
Page
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.2 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 Manual Organization . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.5 Further Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2. Connecting the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Connecting the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.1 Preloaded Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2.2 Before First Use in a Low VBAT Situation . . . . . . . . . . . . . . . . . . 7
3. Installing RSL10 Software for Eclipse . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.3 Optional RSL10 CMSIS-Pack Installation Procedure . . . . . . . . . . . . . . . . 8
4. Building Your First Sample Application in Eclipse . . . . . . . . . . . . . . . . . . . .12
4.1 Launching the IDE . . . . . . . . . . . . . . . . . . . . . . . . . . .12
4.2 Import the Sample Code . . . . . . . . . . . . . . . . . . . . . . . . .12
4.2.1 Importing Sample Code Without CMSIS-Pack . . . . . . . . . . . . . . . . 12
4.2.2 Importing Sample Code With CMSIS-Pack . . . . . . . . . . . . . . . . . 14
4.3 Build the Sample Code . . . . . . . . . . . . . . . . . . . . . . . . . .16
4.4 Debugging the Sample Code . . . . . . . . . . . . . . . . . . . . . . . .18
4.4.1 Debugging with the .elf File . . . . . . . . . . . . . . . . . . . . . . 18
4.4.2 Peripheral Registers View with RSL10 IDE . . . . . . . . . . . . . . . . . 21
4.4.3 Arm® Cortex®-M3 Core Breakpoints . . . . . . . . . . . . . . . . . . . 23
4.5 Folder Structure of the RSL10 SDK Installation . . . . . . . . . . . . . . . . . .23
5. Installing and Working with RSL10 Software for Keil . . . . . . . . . . . . . . . . . . .25
5.1 Prerequisite Software . . . . . . . . . . . . . . . . . . . . . . . . . .25
5.2 RSL10 CMSIS-Pack Installation Procedure . . . . . . . . . . . . . . . . . . .25
5.3 Building Your First Sample Application in Keil . . . . . . . . . . . . . . . . . .27
5.3.1 Import the Sample Code . . . . . . . . . . . . . . . . . . . . . . . 27
5.3.2 Build the Sample Code. . . . . . . . . . . . . . . . . . . . . . . . 28
5.3.3 Debugging the Sample Code . . . . . . . . . . . . . . . . . . . . . . 29
5.3.3.1 Preparing J-Link for Debugging . . . . . . . . . . . . . . . . . . . 29
5.3.3.2 Debugging Applications . . . . . . . . . . . . . . . . . . . . . 29
5.3.3.3 Arm® Cortex®-M3 Core Breakpoints . . . . . . . . . . . . . . . . . 32
5.4 Folder Structure of the RSL10 CMSIS-Pack Installation . . . . . . . . . . . . . . .32
6. More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
6.1 More Information . . . . . . . . . . . . . . . . . . . . . . . . . . .33
6.2 Other Relevant Documentation . . . . . . . . . . . . . . . . . . . . . . .36
A. Arm Toolchain Support . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
A.1 Basic Installation . . . . . . . . . . . . . . . . . . . . . . . . . . .38
A.2 Configuring the Arm Toolchain in Eclipse . . . . . . . . . . . . . . . . . . .38
Table of Contents

ON Semiconductor
www.onsemi.com
3
A.3 Additional Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 38
B. Advanced Debugging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

www.onsemi.com
4
CHAPTER 1
1.Introduction
1.1 PURPOSE
RSL10 is a multi-protocol, Bluetooth® 5 certified, radio System on Chip (SoC), with the lowest power
consumption in the industry. It is designed to be used in devices that require advanced wireless features, with minimal
system size and maximized battery life. The RSL10 Software Development Kit (SDK) includes firmware, software,
example projects, and documentation; which are all incorporated into an Integrated Development Environment (IDE) to
support the development of your applications.
Starting at version 2.0, the RSL10 IDE has been upgraded to the Eclipse Oxygen version with support for
CMSIS-Packs. The new environment is backward compatible with projects from RSL10 SDK 1.4, so the migration to
the CMSIS-Pack standard is not mandatory.
The RSL10 CMSIS-Pack is provided separately, and can be optionally imported into the RSL10 IDE 2.3. By using
the CMSIS-Pack, you can enjoy new features:
• Future releases of the RSL10 CMSIS-Pack can be imported side-by-side on the RSL10 SDK 2.3 or Keil, not
requiring the re-installation of the full SDK.
• Documentation can be accessed from inside the IDE.
• Sample projects can be imported more easily, through the pack manager.
• The setup of new projects is simplified by the RTE configuration wizard, where RSL10 software components,
such as libraries and source code, can be selected.
This document helps you to get started with the RSL10 SDK. It guides you through the process of connecting your
hardware, installing the software with the option of applying the CMSIS-Pack, configuring your environment, and
building and debugging your first RSL10 application.
1.2 INTENDED AUDIENCE
This manual is for people who intend to develop applications for RSL10. It assumes that you are familiar with
software development activities.
1.3 CONVENTIONS
The following conventions are used in this manual to signify particular types of information:
monospace Commands and their options, file and path names, error messages, code samples and code
snippets.
mono bold A placeholder for the specified information. For example, replace filename with the actual
name of the file.
bold Graphical user interface labels, such as those for menus, menu items and buttons.
italics File names and path names, or any portion of them.
1.4 MANUAL ORGANIZATION
Getting Started with RSL10 contains the following chapters and appendices:

ON Semiconductor
www.onsemi.com
5
•Chapter 1: Introduction describes the purpose of this guide and how the book is organized, and gives a list of
suggested reading for more information.
•Chapter 2: Connecting the Hardware explains how to connect the RSL10 Evaluation and Development
Board to a computer running Windows®.
•Chapter 3: Installing RSL10 Software for Eclipse describes the steps for installing the RSL10 SDK,
including the steps for applying the CMSIS-Pack for Eclipse Oxygen.
•Chapter 4: Building Your First Sample Application in Eclipse shows how to import and build a sample
application, with or without CMSIS-Pack, as a practical introduction to using the SDK.
•Chapter 5: Installing and Working with RSL10 Software for Keil describes the steps for importing the
CMSIS-Pack for Keil, and explains how to build your first sample application.
•Chapter 6: More Information lists additional sources of information about using the RSL10 SDK, and
additional tools.
•Appendix A: Arm Toolchain Support explains what to do if your IDE cannot find the correct toolchain
because you have other versions of the GNU toolchain installed.
•Appendix B: Advanced Debugging describes an extra configuration step to do when you are trying to debug
an application that does not start at the first address of flash memory.
1.5 FURTHER READING
For more information, refer to the following documents:
• See Chapter 6, “More Information” on page 33 for a list of additional information sources.

www.onsemi.com
6
CHAPTER 2
2.Connecting the Hardware
2.1 Prerequisites
The following items are needed before you can make connections:
• RSL10 Evaluation and Development Board and a USB to Micro-USB cable
• A computer running Windows
2.2 CONNECTING THE HARDWARE
To connect the Evaluation and Development Board to a computer:
1. Check the jumper positions:
Ensure that the jumper CURRENT is connected and POWER OPTIONS is selected for USB. Also, connect the
jumpers TMS, TCK and SWD. Finally, connect the headers P7, P8, P9 and P10 to 3.3 V, as highlighted in
Figure 1.
Figure 1. Evaluation and Development Board with Pins and Jumpers for Connection Highlighted
2. Once the jumpers are in the right positions, you can plug the micro USB cable into the socket on the board.
The LED close to the USB connector flashes green during the first time plugging in, then turns a steady green
once the process is finished.

ON Semiconductor
www.onsemi.com
7
2.2.1 Preloaded Sample
The Evaluation and Development Boards come with one of the following preloaded sample applications:
• “Peripheral Device with Sleep Mode” is on boards with a serial number lower than 1741xxxxx.
• “Peripheral Device with Server” is on boards with a serial number higher than 1741xxxxx.
The serial number is on a sticker on the back of every board.
Another way to tell the difference is that LED1 blinks about 5 to 10 times per second with “Peripheral Device with
Sleep Mode” loaded, and blinks about 2 times per second with “Peripheral Device with Server” loaded.
For more information about “Peripheral Device with Sleep Mode” or “Peripheral Device with Server”, go to the
source/samples folder and see the /peripheral_server_sleep/readme_peripheral_server_sleep.txt file or /
peripheral_server_sleep/readme_peripheral_server.txt available in the RSL10 software development tools, or refer to
the RSL10 Sample Code User’s Guide. Alternatively, you can load a simpler sample application as described in
Chapter 4, “Building Your First Sample Application in Eclipse” on page 12.
2.2.2 Before First Use in a Low VBAT Situation
CAUTION: If you intend to use a low VBAT power supply (< 1.30 V), you first need to change the value of the
LOCK_INFO_SETTING word in the NVR3 sector of the flash memory while using a higher VBAT power supply;
otherwise, the system can fail to boot.
The default value of LOCK_INFO_SETTING is 0xFFFFFFFF. We strongly recommend that you replace it with
0xB3909CB5 DBG_ACCESS_UNLOCK (unlock debug port access).
Using this value enables debug access. Do not make the value of LOCK_INFO_SETTING all zeroes or all ones,
because in that case the system would require high VBAT to start.
For more information about why this change is needed and how to do it, see the RSL10 Hardware Reference
manual, in the section titled “IP Protection”.

www.onsemi.com
8
CHAPTER 3
3.Installing RSL10 Software for Eclipse
3.1 PREREQUISITE SOFTWARE
• Install the 64-bit variant of the most recent Java version, choosing the Java Runtime Environment (JRE).
• Install J-Link version 6.34h. It is available from the SEGGER website: https://www.segger.com/downloads/
jlink.
• Download the RSL10 Software Development Kit (SDK) Installer from the.ON Semiconductor RSL10
website.
3.2 INSTALLATION PROCEDURE
Install the RSL10 Software Development Kit (SDK) by running RSL10_SDK_Installer.msi. The RSL10 software
development tools are installed in this location by default: C:\Program Files (x86)\ON Semiconductor\RSL10 SDK. If
you have a previous RSL10 SDK version installed:
1. Uninstall it.
2. Check if the RSL10 SDK folder is still there; if it is, delete it.
3. Install your new RSL10 SDK.
The release version and build number are stored in the REVISION text file at the root of the installed RSL10 SDK
software development tools.
If you are going to work in this environment, see Chapter 4, “Building Your First Sample Application in Eclipse”
on page 12 for the next steps. To work in a CMSIS-Pack environment, see Section 3.3, “Optional RSL10 CMSIS-Pack
Installation Procedure”.
3.3 OPTIONAL RSL10 CMSIS-PACK INSTALLATION PROCEDURE
If you want to take advantage of supporting code written in different future releases of the RSL10 SDK, you will
want to install the RSL10 CMSIS-Pack. It will allow you to develop and debug code written in different releases of
RSL10 starting with Release 2.0 and going forward.
NOTE: You must do the procedure in Section 3.2, “Installation Procedure” first.
1. Download the RSL10 SDK CMSIS Pack from https://www.onsemi.com/PowerSolutions/
supportDoc.do?type=software&rpn=RSL10 and save it in any temporary folder.
2. Open your IDE and choose the desired location for your new workspace — for example, c:\workspace — and
click OK.
3. Once the IDE is open, navigate to Window > Preferences. On the left panel, select CMSIS Packs. In the
CMSIS Pack root folder field, type/choose a location where you would like your CMSIS-Packs to be
installed — for example, c:\cmsis_packs — and click Apply and Close (Figure 2).

ON Semiconductor
www.onsemi.com
9
Figure 2. Configuring the CMSIS-Pack root folder
4. On the top right corner, click on the Open Perspective icon, select CMSIS Pack Manager, and click OK (see
Figure 3).
Figure 3. Opening the CMSIS-Pack Manager Perspective
5. Click on the Import existing packs icon, select your pack file ONSemiconductor.RSL10.version.pack,
where version is a number such as 2.3.27, and click Open (see Figure 4).

Getting Started with RSL10
www.onsemi.com
10
Figure 4. Installing the RSL10 CMSIS-Pack
6. The IDE prompts you to read and accept our license agreement, and then installs the RSL10 CMSIS-Pack in
the specified pack root folder.
7. After installation, click on the Reload Packs icon (see Figure 5) to update your list of installed packs.
Figure 5. Reload Packs Icon
8. The RSL10 CMSIS-Pack now appears in the list of installed packs. In the Devices tab, if you expand All
Devices > ONSemiconductor > RSL10 Series you can see RSL10 listed there. You can manage your
installed packs in the Packs tab. Expanding ONSemiconductor.RSL10 makes the Pack Properties tab display
the details of the RSL10 CMSIS-Pack. Figure 6 on page 11 illustrates what the Pack Manager perspective
looks like after installation.

ON Semiconductor
www.onsemi.com
11
Figure 6. Pack Manager Perspective after RSL10 CMSIS-Pack is Installed
For the next steps of working with a sample application, see Chapter 4, “Building Your First Sample
Application in Eclipse” on page 12.

www.onsemi.com
12
CHAPTER 4
4.Building Your First Sample Application in Eclipse
This section guides you through importing and building your first sample application, named blinky. This
application makes the LED (DIO6) blink on the Evaluation and Development Board. The following procedure assumes
you have installed the SDK.
For more information about the sample applications, see the RSL10 Sample Code User’s Guide.
4.1 LAUNCHING THE IDE
To use the IDE for the first time, follow the steps below:
1. To start the IDE, go to the Windows Start menu, and select ON Semiconductor > RSL10 SDK IDE.
2. When you open the IDE for the first time, you are prompted to select a workspace for the session. The
workspace is the work area for all your IDE projects.
The procedures in this chapter are written on the assumption that you are looking at the Workbench perspective.
4.2 IMPORT THE SAMPLE CODE
Depending on whether you installed the CMSIS-Pack or not, choose one of the procedures in the following
subsections. If you have chosen to install the CMSIS-Pack, jump to Section 4.2.2, “Importing Sample Code With
CMSIS-Pack” on page 14 to learn how to import code in that environment. Otherwise, continue to Section 4.2.1,
“Importing Sample Code Without CMSIS-Pack”.
4.2.1 Importing Sample Code Without CMSIS-Pack
To import the Simple GPIO I/O sample code (affectionately known as blinky):
1. Click on the File menu item and select Import. An Import dialog opens.
2. Select the General folder and click on Existing Projects into Workspace, as shown in Figure 7.
IMPORTANT: Create a new workspace for your version of the RSL10 IDE. Re-using an existing workspace
originally created with other Eclipse-based IDE may not be compatible.

ON Semiconductor
www.onsemi.com
13
Figure 7. Importing an Existing Project
3. Click Next, and the Import Projects dialog appears. Select the Copy projects into workspace check box, as
shown in Figure 8 on page 13.
Figure 8. Import Projects Dialog Box

Getting Started with RSL10
www.onsemi.com
14
4. Browse to the folder blinky, as shown in Figure 9 on page 14, and click OK. The sample code is in the RSL10
installation directory (C:\Program Files (x86)\ON Semiconductor\RSL10 SDK by default) under
source\samples
Figure 9. Select a Project to Import
5. On the Import Projects dialog, click Finish. This creates a new project in your workspace called blinky. The
project appears in the left side of Project Explorer, as shown in Figure 10.
Figure 10. Newly Imported Project
4.2.2 Importing Sample Code With CMSIS-Pack
1. In the Pack Manager perspective, click on the Examples tab to list all the example projects included in the
RSL10 CMSIS-Pack.
2. Choose the example project called blinky, and click the Copy button to import it into your workspace (see
Figure 11 on page 15).

ON Semiconductor
www.onsemi.com
15
Figure 11. Pack Manager Perspective: Examples Tab
3. The C/C++ perspective opens and displays your newly copied project. In the Project Explorer panel, you can
expand your project folder and explore the files inside your project. On the right side, the blinky.rteconfig file
displays software components. If you expand Device > Libraries, you will see the System library (libsyslib)
and the Startup (libcmsis) components selected for blinky (see Figure 12 on page 16).
NOTE: Sample projects are preconfigured with Release versions of RSL10 libraries, which are
distributed as object files. In the RTE configuration, you can switch to the Source variant to
include the source code of the library directly into your project (see Figure 12 on page 16).

Getting Started with RSL10
www.onsemi.com
16
Figure 12. RTE Configuration for the Blinky Example Project in Eclipse IDE
4.3 BUILD THE SAMPLE CODE
1. Right click on the folder for blinky and click Build Project. Alternatively, you can select the project and click
the hammer icon shown in Figure 13.

ON Semiconductor
www.onsemi.com
17
Figure 13. Starting to Build a Project in Eclipse IDE
2. When the build is running, the output of the build is shown in the Eclipse C/C++ Development Tooling (CDT)
Build Console, as illustrated in Figure 14.
Figure 14. Example of Build Output
3. The key resulting output in Project Explorer includes:
•blinky.hex: HEX file for loading into Flash memory
•blinky.elf: Arm® executable file, run from RAM, used for debugging
•blinky.map: map file of the sections and memory usage
These files are shown in Figure 15 on page 18.
NOTE: You might need to refresh the project to see the three built output files. To do so, right-click on
the project name blinky and choose Refresh from the menu.

Getting Started with RSL10
www.onsemi.com
18
Figure 15. Output Files from Building a Sample Project
NOTE: If the Eclipse IDE has trouble finding the GNU toolchain, it might be caused by having other
GNU toolchains installed. See Appendix A, “Arm Toolchain Support” on page 38 for more
information.
4.4 DEBUGGING THE SAMPLE CODE
4.4.1 Debugging with the .elf File
Debug the application using the .elf file as follows:
1. Within the Project Explorer, right-click on the blinky.elf file and select Debug As > Debug
Configurations…
2. When the Debug Configurations dialog appears, right-click on GDB SEGGER J-Link Debugging and
select New. A new configuration for blinky appears under the GDB SEGGER heading, with new
configuration details in the right side panel.
3. Change to the Debugger tab, and enter RSL10 in the Device field. Ensure that SWD is selected as the target
interface (as shown in Figure 16).

ON Semiconductor
www.onsemi.com
19
Figure 16. Setting Up a GDB Launch Configuration, Debugger Tab
NOTE: If you want to debug an application that does not start at the first address of flash memory, see
Appendix B, “Advanced Debugging” on page 40.
4. Once the updates to the configuration are completed, make sure the Evaluation and Development Board is
connected to the PC via a micro USB cable, and click Debug. J-Link automatically downloads the blinky
sample code to RSL10’s flash memory.

Getting Started with RSL10
www.onsemi.com
20
NOTE: If J-Link does not automatically write your program to RSL10’s flash memory, make sure you
are using the J-Link version specified in Section 3.1, “Prerequisite Software” on page 8.
5. Eclipse asks if you would like to open the Debug perspective. Answer Yes, and click on Remember my
decision so that the question is not asked again.
6. The Debug perspective opens and the application runs up to the first breakpoint in main, as shown in Figure 17
on page 21. You can press F6 multiple times to step through the code and observe that the LED changes its
state when the application executes the function Sys_GPIO_Toggle(LED_DIO).
IMPORTANT: If the preloaded sample “Peripheral Device with Sleep Mode” is currently on your board (see
Section 2.2.1, “Preloaded Sample” on page 7 for help determining what your preloaded sample is), and you are
having difficulty connecting to the board, do the following:
a. Connect DIO12 to ground.
b. Press the RESET button (this restarts the application, which will pause at the start of its
initialization routine).
c. Repeat step 4 above. After successfully downloading blinky to flash memory, disconnect DIO12
from ground, and press the RESET button so that the application will work properly.
Alternatively, use the Stand-Alone Flash Loader (available with its own manual in the
RSL10_Utility_Apps.zip file) to erase the “Peripheral Devices with Sleep Mode” application from the
board’s flash memory.