User Manual of Raytac AN54LV-DB-15 (Nordic nRF54L15 Module DevKit) Development & Programming Environment

Want to get started quickly with Raytac's AN54LV-15 module? We provide a simple tutorial to guide you step-by-step through setting up the development and programming environment for the nRF54L15 module Development Board (AN54LV-DB-15) and nRF54L15-DK.

Table of Contents
1. Hardware Environment Setup
2. Software Development Kit Resources and Environment Setup
3. Software/Firmware Application Development
4. Flashing / Programming

Related products:
nRF54L15 SoC Spec  << access link
Nordic nRF54L15 DK  << access link
Raytac AN54LV-DB-15 (Development Kit used in this article) << access link
Zephyr documentation of AN54LV-DB-15 << access link
Raytac AN54LV-DB-U15 (Development Kit with u.FL Connector for external antenna) << access link
Raytac AN54LV-DB-K15 (Development Kit with antenna pin) << access link

User manual of Raytac AN54LQ-DB-15 << access linkNordic nRF54L15-DK

1. Hardware Environment Setup
The required equipments are as follows:

• 1 x Nordic nRF54L15-DK: PCA10156(1.0.0)
• 1 x AN54LV-DB-15 (Raytac nRF54L15 module Development Board)
• 1 x IDC Ribbon Cable
• 2 x USB Type-C Connection Cables

* Reminder: The "Nordic nRF54L15-DK" and "Raytac AN54LV-DB-15 Development Board" must be used together to proceed with application development and flashing firmware into the Raytac AN54LV-DB-15 development board.

Setup Steps:
Step 1: Connect the J-Link on the Nordic DK with the AN54LV-DB-15 using the IDC ribbon cable.

Make sure to match the red side of the IDC ribbon cable with "1" printed on the AN54LV-DB-15's J-Link socket.

Step 2: Use the Type-C USB cables to supply power to both the nRF54L15-DK and the AN54LV-DB-15.

The outcome should be same as the picture above.

Step 3: AN54LV-DB-15 Schematic(Click on the schematic to zoom in):

---

2. Software Development Kit Resources and Environment Setup
Software Tool kits & Download Links:
Download nRF Connect for Desktop: Download nRF Connect For Desktop (Please Click Me)
Download nRF Command Line Tools: Download nRF Command Line Tools (Please Click Me)
Download Visual Studio Code(VS Code): Download nRF Command Line Tools (Please Click Me)

Setup Steps:
Step 1: Download the latest version of nRF Connect for Desktop. Choose the Windows 64-bit - version 5.3.1 installer (nrfconnect-setup-5.3.1-x64.exe). Once finished, you will see " nRF Connect for Desktop" on your PC.

Step 2: Download the latest version of nRF Command Line Tools. Choose the Windows X86 64 - version 10.24.2 installer (nrf-command-line-tools-10.24.2-x64.exe)

* Reminder: During the installation of the above two programs, a window may pop up prompting that SEGGER J-LINK needs to be installed or updated concurrently.

If you’re initiating Segger Embedded Studio (SES) application, please check the guideline here(Click me)\

Step 3: Download the latest version of Visual Studio Code (VS Code). Choose Windows VSCodeUserSetup-x64 version 1.122 (VSCodeUserSetup-x64-1.122.1.exe). Once complete, you will see "Visual Studio Code" on your PC.

Step 4: After installation is complete, you can verify the installed packages in your PC's Control Panel under "Programs and Features":

---

3. Software/Firmware Application Development
You can develop application programs within the VS Code IDE development environment.
Below steps are how to install and select your target SDK version (nRF Connect SDK v3.3.0 in this article):

Step 1: Launch "VS Code"-> Select "nRF Connect" icon/extension on the side menu.

Click "Manage SDKs" and then select "Install SDK".

Step 2: Select "nRF Connect SDK".

Step 3: You will see several available versions of nRF Connect SDK vx.x.x. It is highly recommended to choose and install NCS v3.3.0 or later. In this guide, we select nRF Connect SDK(NCS) v3.3.0.

Step 4: Before starting the download for (NCS)v3.3.0, confirm your preferred target installation pathway.
By default, it is configured to c:\ncs\v3.3.0. Press 'Enter' to confirm.

Step 5: Once the nRF Connect SDK v3.3.0 environment setup finishes successfully, open the Bluetooth sample folder and select the "peripheral_uart" application template, then click "Open".

Step 6: In the "nRF Connect" layout, go to "Applications" --> "Add build configuration".

Under "Board target", look up and select "nrf54l15dk/nrf54l15/cpuapp" --> "Generate and Build".

* Note: You can also choose the board name “raytac_an54lv_db_15/nrf54l15/cpuapp” for subsequent building and development.

After completing the configuration, you will see "Build complete".

Step 7: Compilation completed. Once completed, a binary file named "zephyr.hex" will be generated in your "build" directory.

Step 8: Under the "ACTIONS" interface, you can switch between Build, Debug, and Flash functionalities dynamically.

Build

Debug

Flash

Step 9: CRITICAL BEFORE FLASHING/DEBUGGING: You have to change the VDD voltage configuration on the nRF54L15-DK board to 3.3V.

To do this: Launch "nRF Connect for Desktop" -> choose "Board Configurator" -> click "Open"

Change the VDD target selection value to "3.3V" -> click "Write config".

---

4. Flashing / Programming
The nRF Connect SDK (NCS) natively supports direct programming.
You can utilize the "Programmer" application tool to flash the compiled zephyr.hex binary file onto the target chip.
The exact procedure is detailed below:

Step 1: Open "nRF Connect for Desktop" -> select "Programmer" and click "Open".

Click "Select Device" and choose "nRF54L15DK".

Click "Add file".

Step 2: Select your compiled target ".hex" file.

Click "Erase & write" to initiate the programming/flashing process.

While flashing, a progress diagonal pattern will display on the right-hand panel.

When the LOG shows a "completed" status text, it means that the programming/flashing is successfully done.

Step 3: After the flash operation completes, you can download the "nRF Connect for Mobile" app to scan and verify that the Raytac AN54LV-DB-15 development board is advertising normally.

"nRF Connect for Mobile" app download link: https://www.nordicsemi.com/Products/Development-tools/nRF-Connect-for-mobile

Useful References
nRF Connect SDK Documentation: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/3.3.0/nrf/index.html

Nordic DevZone(technical support forum): Nordic Devzone for technical issue discussion

---

Edited by Account Manager: Christine Huang
Technical Guidance by R&D Manager: MW Lee

Raytac Corporation 勁達國際電子股份有限公司 / Raytac Corporation (USA) / abietec Inc.
A Bluetooth, Wi-Fi, and LoRa Module Maker/ODM & OEM Manufacturer based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Infineon: CYW55912
NXP: RW610, RW612
Semtech: SX1262

Bluetooth Specification: BT6 ; BT5.4 ; BT5.3 ; BT5.2.
Wi-Fi Specification: Wi-Fi 6
LoRa Specification: LoRaWAN
Zephyr Project Silver Member

All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC/RoHS/Reach Pre-Certified.

http://www.raytac.com
https://www.raytac.com/contact/
https://www.abietec.com/
email: sales@raytac.com
Tel: +886-2-3234-0208(TW)/+1-626-328-3827(USA)

Essential Tips for nRF54L15 HEX File Verification

Hi readers, did you know that Raytac offers a special service exclusively for our customers? 😉

We offer support services: HEX file verification and flashing firmware into modules per customer's requests.
Compared to the series nRF52 and nRF53’s 2 in 1 or 3 in 1 merged hex files, nRF54L15 requires something slightly different. Following are the tips and suggestions.

Before building your own .hex file on Raytac's nRF54L15 modules(Product link), please configure some settings(shown below) in advance.

In VS Code:

1. Go to Add Build Configuration
2. Find System Build (sysbuild) ➝ Choose Build System Default
3. Click Generate and Build

Starting from NCS v2.8.0 (including later versions), the .hex file can be generated in two different paths.
1. ..\nrf\samples\bluetooth\application-name\build\merged.hex
2. ..\nrf\samples\bluetooth\application-name\build\application-name\zephyr\zephyr.hex

---

Using the AN54LQ/AN54LV series as an example:
When you provide the programming file (.hex) for production, please ensure that the file is taken from the following path:
1. ..\nrf\samples\bluetooth\application-name\build\merged.hex
And we also do not recommend renaming the merged HEX file due to Nordic suggestions.

For more details behind this suggestion, please refer to the Nordic DevZone link below.
https://devzone.nordicsemi.com/f/nordic-q-a/120313/how-to-modify-the-name-of-the-merged-hex-file

Suggested path:
1. ..\nrf\samples\bluetooth\application-name\build\merged.hex

Not recommended path:
2. ..\nrf\samples\bluetooth\application-name\build\application-name\zephyr\zephyr.hex
The zephyr.hex file is not recommended to be used for flashing or verification in the production process.

Thank you all for your patience in reading!
Best wishes for your projects - your success is Raytac’s success! 😊


For more information, please contact:
Raytac Contact Form: https://www.raytac.com/contact/
Raytac Sales email: sales@raytac.com
abietec Service email: service@abietec.com

Edited by Account Manager: Ms. Elfreda Guo


Raytac Corporation 勁達國際電子股份有限公司 / Raytac Corporation (USA) / abietec Inc.
A Bluetooth, Wi-Fi, and LoRa Module Maker/ODM & OEM Manufacturer based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Semtech Specification: SX1262


Bluetooth Specification: BT6 ; BT5.4 ; BT5.3 ; BT5.2.
Wi-Fi Specification: Wi-Fi 6
LoRa Specification: LoRaWAN


All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC/RoHS/Reach Pre-Certified.
http://www.raytac.com
https://www.raytac.com/contact/
email: sales@raytac.com
Tel: +886-2-3234-0208(TW)/+1-626-217-3139(USA)

MCUboot DFU Guide For Raytac MDBT50Q-DB-40 (Using NCS V2.9.1)

 is guide teaches you how to use MCUboot for DFU (Device Firmware Update),

Combined with nRF Connect SDK (NCS) V2.9.1 to upgrade firmware on Raytac's MDBT50Q series modules.

---

Table of contents:

1. Hardware Set Up
2. Software Kits resource download & install
3. Compile and load the program
   a. Open VS Code
   b. Project setup
   c. Setup the situation for DFU over UART or DFU over USB
   d. Start compiling your project
   e. Load your compiled program into the MDBT50Q-DB-40 demo board
   
   
4. DFU to MDBT50Q-DB-40 over UART / USB
5. Execute USB DFU using AuTerm
6. DFU using your custom keys

---

1. Hardware setup
- Equip Raytac's MDBT50Q-DB-40 development board
- Ensure the board is connected via USB to your PC

---

2.Software Kits resources download & install
- Resources download:
nRF Connect for Desktop - Download nRF Connect for Desktop (Please Click Me)
nRF Command Line Tools - Download nRF Command Line Tools (Please Click Me)
Visual Studio Code - Download Visual Studio Code(Please Click Me)

Install nRF Connect for Desktop ➔ install Programmer and Toolchain Manager.

Open Toolchain Manager and install SDK V2.9.1.

Install Visual Studio Code

---

3. Compile and load the program
a. Open VS Code(Visual Studio Code)

Note:
If it's your first time using the software: after installing all the extensions, you should see the same on your screen.

b. Project setup
b.1 Create an example code(In this article: peripheral_uart)
Please refer to the following steps:
Create a new application ➔ Copy a sample ➔ NCS V2.9.1

b.2 Name the Project: peripheral_uart
Input peripheral_uart and the corresponding example program will appear in the options section below.

Note: We named the project peripheral_uart_mcuboot to distinguish it.
This project will create a directory named peripheral_uart_mcuboot.

c. Build an environment for DFU over UART or DFU over USB

- Create a new application ➔ Open

Right click on the project name you just created (peripheral_uart_mcuboot), a pop-up menu will appear. Select the first option "Show in Explorer" from the pop-up menu to display all project files.

Then select New File to create a sysbuild.conf file.

Select sysbuild.conf, left-click on it, and a blank box will show.

Input the file name and define: SB_CONFIG_BOOTLOADER_MCUBOOT=y

Parameters and instructions
Add a new file mcuboot.conf, in the sysbuild folder, and input the following parameters into the file. (Add relevant parameters according to UART or USB)
(Note: Please be informed if you want to use DFU over UART in the end, you should use UART when you first create the environment. Similarly, if you want to use DFU over USB, you should create the USB environment at the beginning.)

For DFU over UART
# Enable logging for MCUboot
CONFIG_LOG=y
CONFIG_MCUBOOT_LOG_LEVEL_WRN=y
# Enable Serial Recovery over UART
CONFIG_MCUBOOT_SERIAL=y
# Disable UART, since Serial Recovery uses it
CONFIG_UART_CONSOLE=n
# Configure the bootloader to use two slots
CONFIG_SINGLE_APPLICATION_SLOT=n
# Turn on a LED so we can see when Serial Recovery mode is active
CONFIG_MCUBOOT_INDICATION_LED=y

For DFU over USB
# Enable logging for MCUboot
CONFIG_LOG=y
CONFIG_MCUBOOT_LOG_LEVEL_WRN=y
# Enable Serial Recovery over UART
CONFIG_MCUBOOT_SERIAL=y
# Disable UART, since Serial Recovery uses it
CONFIG_UART_CONSOLE=n
# Configure bootloader to use two slots
CONFIG_SINGLE_APPLICATION_SLOT=n
# Turn on a LED so we can see when Serial Recovery mode is active
CONFIG_MCUBOOT_INDICATION_LED=y
# Configure serial recovery to use CDC_ACM, which by default uses the USB
CONFIG_BOOT_SERIAL_CDC_ACM=y
# Increase flash space for the MCUboot image to fit USB drivers
CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

Create a new file: mcuboot.overlay and add the following parameters.

For DFU over UART
/* Configure button and LED for Serial Recovery */
/ {
    aliases {
          mcuboot-button0 = &button0;
          mcuboot-led0 = &led0;
    };
  };

For DFU over USB
/* Configure button and LED for Serial Recovery */
/ {
    aliases {
          mcuboot-button0 = &button0;
          mcuboot-led0 = &led0;
    };
  };
/* Configure CDC ACM */
&zephyr_udc0 {
            cdc_acm_uart0: cdc_acm_uart0 {
                        compatible = "zephyr,cdc-acm-uart";
            };
};

Note: if you use DFU over USB, please enable the USB subsystem in prj.conf.

After all the setup is completed, you can start compiling your project.

d. Start compiling your project
Add Build Configuration ➔ Select target board ➔ In this example, choose raytac_mdbt50q_db_40/nrf52840.

Start compiling by clicking "Generate and Build" at the bottom-right corner.

e. Load your compiled program into the MDBT50Q-DB-40 demo board
After compiling without error, select the flash function to load your program into the MDBT50Q-DB-40 demo board.

If the below is shown, it means that you have successfully loaded your program into the demo board.

---

4. DFU to MDBT50Q-DB-40 over UART / USB
DFU over UART
Hold the SW2 button then plug the power into the USB connector.
The system will enter the bootloader mode.
You can then DFU the new firmware via the UART.

DFU over USB
If you update your firmware through USB, please also hold the SW2 button and connect the USB cable.

---

5. Execute USB DFU using AuTerm
AuTerm is a free-for-download PC software on Windows.
It allows you to update your new firmware on the MDBT50Q-DB-40 demo board.
Download link:
https://github.com/thedjnK/AuTerm/releases/download/v0.35a-pre/AuTerm_test_Win_x64_v0.35a.7z

Steps:
Select the tab Config to set the correct COM port.

Follow the sequences in the below screenshot.

You can use the file peripheral_uart_mcuboot.signed.bin for testing.
It is located in peripheral_uart_mcuboot/build.
Then follow the sequences in the below screenshot.
DFU will be completed when the progress reaches 100%.

---

6. DFU using your custom keys
When you compile the code, you will see the below warning.
Reason: It's required to have your own private key to ensure your product's security.
Following are the steps to enable security features.

Step 1. Create the key
First, install the imgtool program using pip.

Then use the following command to generate your private key in your project folder.
After the private key is generated, you can access it in your directory.

Step 2. Configure the project to use this key in sysbuild.conf

# Add MCUboot
SB_CONFIG_BOOTLOADER_MCUBOOT=y
#Add private key for MCUboot
SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="\${APP_DIR}/private_key.pem"
# Configure key type
SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y

Step 3. Build and flash the project again. Your firmware will have security features.

---

Edited by Account Manager: Mr. Welson Kuo

---

Raytac Corporation 勁達國際電子股份有限公司 / Raytac Corporation (USA)
A Bluetooth, Wi-Fi, and LoRa Module Maker/ODM & OEM Manufacturer based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Semtech Specification: SX1262

Bluetooth Specification: BT6.1 ; BT6 ; BT5.4 ; BT5.3 ; BT5.2.
Wi-Fi Specification: Wi-Fi 6
LoRa Specification: LoRaWAN

All products are FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC Pre-Certified.
http://www.raytac.com
https://www.raytac.com/contact/
email: sales@raytac.com
Tel: +886-2-3234-0208(TW)/+1-626-217-3139(USA)