ON Semiconductor EVBUM2589 User manual

©Semiconductor Components Industries, LLC, 2015
September, 2019 −Rev. 4
1Publication Order Number:
EVBUM2589/D
EVBUM2589
Bluetooth)Low Energy IoT
Development Kit (B-IDK)
Getting Started Guide
INTRODUCTION
This document helps you get started with the Bluetooth Low Energy
IoT Development Kit (B−IDK). The B−IDK is a comprehensive
node−to−cloud and a modular IoT platform that allows development
of various BLE based use cases. Along with the hardware and
software, the B−IDK includes a mobile app to interact with sensors
and actuators.
The B−IDK features RSL10, Industry’s lowest power Bluetooth 5
SoC and comprises of a baseboard (BDK−GEVK) and several sensor
and actuator daughter cards. For a complete listing of available
daughter cards, please visit https://www.onsemi.com/B−IDK. The
daughter cards connect to the baseboard, via the two PMOD
connectors and/or the Arduino connector to enable various use cases.
Scope
This document covers the hardware setup, software architecture,
B−IDK documentation and provides instructions on downloading
firmware to the board. The details regarding the mobile app and cloud
connectivity are not covered in this document.
HARDWARE
•BDK−GEVK −B−IDK Baseboard
•Daughter Cards – Optional
•BDK−DCDC−GEVB – Power Shield For Use With Higher Power
Daughter Cards – Optional
Default Configuration
The BDK−GEVK is shipped with the following jumper
configuration. As the board supports OBD, there is no need for an
external debugger. In case an external debugger is used, connect it to
SWD header, J6.
Powering the Board
Multiple options are available to power the BDK−GEVK.
•USB
•Coin Cell (CR2032)
•External AC/DC Adapter plus power shield (BDK−DCDC−GEVB)
•External Supply
When higher power daughter cards (listed below) are attached to the
baseboard, external supply either using the power shield or direct is
required.
Higher Power Daughter Cards
•D−LED−B−GEVK Dual LED Ballast
•D−STPR−GEVK Dual Stepper Motor Driver
•BLDC−GEVK BLDC Motor Driver
www.onsemi.com
EVAL BOARD USER’S MANUAL
Figure 1. Board Photo

EVBUM2589
www.onsemi.com
2
USB
The B−IDK can be powered via the USB port when the use case doesn’t need any higher power daughter cards. An example
configuration with the baseboard and a couple of sensor boards is shown below.
Coin Cell
Once the firmware is flashed onto the baseboard, a coin cell (CR2032) may be used to power the system. Similar to USB
based power supply, this method of powering is for use cases that don’t utilize the higher power daughter cards. The jumper
configuration must match the below table to allow for various power modes.
Table 1. JUMPERS
J11 J12 Usage
IN X Programming and Power over USB
X IN After programming. Only RSL10 is powered.
IN IN After programming. Both RSL 10 and OBD Microcontroller are powered
External AC/DC Adapter Plus Power Shield
(BDK−DCDC−GEVB)
For use cases that utilize higher power daughter cards, an external AC/DC power supply (Ex: SMI24−12−V−P6) plus the
power shield (BDK−DCDC−GEVB) are needed to power the system. While the 3.3 V supply to the baseboard is provided by
the power shield via the Arduino connector, power cables (Green connector) are required between BDK−DCDC−GEVB and
the higher power daughter card. For firmware flashing and debugging, the USB cable may be plugged in simultaneously with
this mode as shown below.
External Supply
The B−IDK can be powered by an external supply via J13. In this mode, the battery cannot be installed. Jumpers J11 and
J12 must be installed.

EVBUM2589
www.onsemi.com
3
SOFTWARE
The B−IDK software allows for rapid development of various use cases. This section details the prerequisites and detailed
steps in downloading firmware onto the baseboard.
Prerequisites
1. Install 64−bit version of Java from https://www.java.com/en/download/
2. Install J−Link Version 6.32f or later from https://www.segger.com/downloads/jlink (select J−Link software and
documentation pack)
3. Download and install“On Semiconductor IDE Installer” from
https://www.onsemi.com/PowerSolutions/product.do?id=RSL10
a. Download the RSL10 SDK Getting Started Guide and RSL10 CMSIS pack under “RSL10 Software Package”
from the above site. All of these are highlighted in the picture below. Save the CMSIS pack in a folder, for
example, C:\cmsis_packs
4. Download the B−IDK CMSIS pack from https://www.onsemi.com/B−IDK and save it in the same folder as the
RSL10 CMSIS pack (see 3.a above)
5. CMSIS pack at item 4. is dependent on ARM CMSIS pack as well. Please install ARM CMSIS pack 5.5.1 or higher
after download from: https://github.com/ARM−software/CMSIS_5/releases
6. CMSIS pack at item 4. is also dependent on ARM CMSIS – FreeRTOS version 10.2.0 or higher for users exposed to
design the code under FreeRTOS with RSL10: https://github.com/ARM−software/CMSIS−FreeRTOS/releases
The next section provides details on importing the downloaded CMSIS packs into the SDK.
Importing CMSIS Packages
1. Launch the RSL10 SDK ON Semiconductor IDE
NOTE: Please import RSL10 CMSIS pack first as the B−IDK CMSIS pack (step 4 in the Prerequisites section) depends
on the RSL10.
2. Refer to Chapter 3 of RSL10 SDK Getting Started Guide (step 3.a) for step−by−step instructions on importing the
CMSIS packs.
3. Once all packs are successfully imported, they can be viewed in the CMSIS pack manager perspective as shown
below.

EVBUM2589
www.onsemi.com
4
Compiling and Flashing
1. Choose an example (for example, pr_shield_example) to flash by copying it to the workspace.
NOTE: Once the example is copied, it can be viewed under Project Explorer. All source files including main are located
in the src folder.

EVBUM2589
www.onsemi.com
5
2. Right click and build the project. This creates binaries to be flashed to BDK−GEVK.
NOTE: If the binaries are not seen, press F5 (refresh).
3. Once the build is done, the code is ready to be flashed to the BDK−GEVK. Select the project (pir_shield_example),
and go to the debug configurations as shown below.

EVBUM2589
www.onsemi.com
6
4. Double click GDB Segger J−Link Debugging to create the debug configuration for the selected example.
NOTE: The debug configuration for the selected example is automatically saved and there’s no need to re−create it.
5. On the Debugger tab, set RSL10 as the device name. Click Debug to launch the code.
6. For application debugging, confirm perspective switch by clicking Yes.
7. The debug session is now launched. Click Resume (F8) to start the target CPU.

EVBUM2589
www.onsemi.com
7
Compiling and Flashing
1. Choose an example (for example, pr_shield_example) to flash by copying it to the workspace.
NOTE: Once the example is copied, it can be viewed under Project Explorer. All source files including main are located
in the src folder.

EVBUM2589
www.onsemi.com
8
2. Right click and build the project. This creates binaries to be flashed to BDK−GEVK.
NOTE: If the binaries are not seen, press F5 (refresh).
3. Once the build is done, the code is ready to be flashed to the BDK−GEVK. Select the project (pir_shield_example),
and go to debug configurations as shown below.

EVBUM2589
www.onsemi.com
9
4. Double click GDB Segger J−Link Debugging to create the debug configuration for the selected example.
NOTE: The debug configuration for the selected example is automatically saved and there’s no need to re−create it.
5. On the Debugger tab, set RSL10 as the device name. Click Debug to launch the code.
6. For application debugging, confirm perspective switch by clicking Yes.

EVBUM2589
www.onsemi.com
10
7. The debug session is now launched. Click Resume (F8) to start the target CPU.
Logging/Debugging
The following options are available to log/debug the downloaded firmware:
•Eclipse RTT Console
•J−Link RTT
•AX8052F100 UART−SPI bridge
This section provides instructions for each of the above options.
Using Eclipse Console
1. Click the Open a Terminal Icon

EVBUM2589
www.onsemi.com
11
2. Enter the values shown below and launch the session. The incoming events are printed on the terminal window.

EVBUM2589
www.onsemi.com
12
Using Eclipse Serial Console via UART−SPI Bridge.
When you do not want to use the Segger RTT viewer as serial console, the BDK−GEVK board is equipped with UART−SPI
uC AX8052F100 flashed with special firmware, taking care of the entire serial communication with values returned on
Terminal.
3. Click on the example’s rteconfig file and choose under Device/BDK/Output redirection, SPI Bridge AXEM. Save,
compile and flash the whole project.
4. When the project runs, Click the Open a Terminal Icon.
5. Enter the appropriate COM port as shown below, and launch the session. The incoming events are entered on the
terminal window.

EVBUM2589
www.onsemi.com
13
NOTE: You may reset (PB_RST) the BDK−GEVK (shown below) to launch the RTT terminal without needing to launch
Eclipse.

EVBUM2589
www.onsemi.com
14
Using J−Link RTT
6. After step 14 is done, open J−Link RTT viewer (should be installed when J−Link software package was installed per
Step 2).
7. Select USB and click OK.

EVBUM2589
www.onsemi.com
15
8. RTT prompts you to select the appropriate microcontroller. Select RSL10 and click OK. The serial terminal is ready
to use and the events from RSL10 can be observed by clicking the All Terminals Window.

EVBUM2589
www.onsemi.com
16
NOTE: You may reset (PB_RST) the BDK−GEVK (shown below) to launch RTT terminal without needing to launch
Eclipse.
Using Eclipse Serial Console via UART−SPI Bridge
The BDK−GEVK board is equipped with UART−SPI microcontroller AX8052F100 flashed with special firmware, to enable
serial communication with values returned to Terminal.
9. Click on example’s rteconfig file and choose “SPI Bridge AXEM” under Device/BDK/Output redirection.
Save, compile and flash the whole project.

EVBUM2589
www.onsemi.com
17
10. When the project runs, Click the Open a Terminal Icon.
11. Enter the appropriate COM port as shown below and launch the session. The incoming events are printed on the
terminal window.

EVBUM2589
www.onsemi.com
18
SOFTWARE ORGANIZATION
For users modifying the example code and building new projects, the following sections detail the B−IDK software
organization. The stack overview is shown below.
B−IDK CMSIS Software Organization
CMSIS pack and the associated software components handle multiple evaluation boards as different bundles of the
standardized Board Support Cclass.
•This bundle shows only components supported by ON
Semiconductor for a given board
•No confusing component variants
Common libraries and HAL are in a separate group within the Device class

EVBUM2589
www.onsemi.com
19
Board Support
•Libraries to support BDK−GEVK, GPIO Expander, Various daughter cards and custom protocol (required for the
mobile app)
Components
•Libraries attached to board support
Device
•Abstraction layers for interfaces, timers, AES, serial re−direction, etc.
BLE
•Peripheral Server Support

EVBUM2589
www.onsemi.com
20
CONFIGURATION SETUP
System settings can be configured directly from within the CMSIS pack. Each example is equipped with basic system
configuration that covers three main categories. These are accessible in the RTE/BDK folder within the project. Each system
configuration starts with “RTE_”. As shown below, opening the RTE_... header files using the CMSIS configuration wizard
(right click on the header file), displays the configuration table. Various application specific parameters can be set. This allows
pre−configuration of RSL10 without the need for explicit programming.
A brief description on the header files is given below.