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

This 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 write: 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 through 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)


Raytac’s nRF54L15 module Demo Board: AN54LQ-DB-15 is now officially supported in the Zephyr Project

We’re excited to announce that the Raytac AN54LQ-DB-15 development board is now listed and fully supported in the Zephyr Project’s official board documentation! This milestone provides developers with seamless access to hardware abstraction, sample code, and configuration tools—directly within the Zephyr RTOS environment.

Based on Nordic Semiconductor’s latest nRF54L15 SoC, this board offers a cutting-edge platform for developing Bluetooth® Low Energy and other 802.15.4 protocol-related applications. The features include:

– Module Demo Board built by AN54LQ-15 module
– Built-in debug interface for streamlined development and testing
– Compatibility with Zephyr’s device tree and board configuration system
– Antenna variants: Ceramic Chip / PCB Trace / u.FL Connector
– Nordic nRF54L15 Solution
– A recommended 3rd-party module by Nordic Semiconductor.
– Intended for BT specification BT6, including Channel Sounding features
– Pre-certified with FCC, IC, CE, Telec (MIC), KC, SRRC, NCC, RCM, WPC
– Intended for EU new Cyber Security Standard: EN 18031
– RoHS & Reach Compliant.
– 128 MHz ARM® Cortex™-M33 processor with TrustZone® technology
– 128 MHz RISC-V co-processor with TrustZone® technology
– 1.5MB Flash Memory / 256KB RAM
– 31 GPIO
– Interfaces: QSPI(Software), SPI, UART, I2C, I2S, PDM, PWM, ADC, and NFC
– Highly flexible multiprotocol, ideally suited for
Bluetooth® Low Energy, ANT+, Zigbee, Thread (802.15.4), and Matter ultra low-power wireless applications.


Reference:
AN54L15Q-DB Zephyr Documentation
nRF54L15 module: AN54LQ-15(Chip antenna)
nRF54L15 module: AN54LQ-P15(PCB antenna)
nRF54L15 module: AN54LQ-U15(u.FL connector for external antenna)
nRF54L15 module demo board: AN54LQ-DB-15
nRF54L15 ultra compact module: AN54LV-15(Chip antenna)
nRF54L15 ultra compact module: AN54LV-P15(PCB antenna)
Nordic Third-party modules/modems


By being integrated into the Zephyr ecosystem, developers gain direct access to well-maintained upstream code, continuous integration support, and community-driven updates. Whether you’re building IoT sensors, connected medical devices, or industrial automation systems, using the AN54LQ-DB-15 with Zephyr ensures a modern, scalable, and open-source-ready development experience.


Start building faster—with less setup and more confidence—thanks to this powerful combination of Raytac hardware and the Zephyr real-time operating system!


Our other Demo boards that are also listed on Zephyr:
MDBT50Q-DB-33 (nRF52833 module Demo Board)
MDBT50Q-DB-40 (nRF52840 module Demo Board)
MDBT53-DB-40 (nRF5340 module Demo Board)
MDBT53V-DB-40 (nRF5340 module Demo Board)


Edited by Business Development Manager: Mr. Tony Yin


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)


Understanding Wireless Certification and Compliance:A Guide to Module and Non-Module Approval Processes

Certification and compliance:

By obtaining wireless (Bluetooth) certification, manufacturers can demonstrate that their products comply with the required technical reliability. In another words, these certifications are like products’ passes, allow them legally entering the market and be able to import or export specific countries. Modular approval and Non-modular approval are two different approaches to the certification and regulatory processes for wireless communication devices.

Modular approval is a process in which a wireless device is certified as a modular component, such as a Bluetooth module, that can be integrated into multiple host devices without additional testing for each host device. Once certified, the module can be used in various host devices without undergo the same level of testing.

Non-modular approval is also known as end-product approval, is the traditional certification process for wireless devices, where the entire device needs to be tested and certified for compliance with wireless (Bluetooth) standards and regulations.

Countries follow and under modular approval such as FCC (USA), IC (Canada), Telec (Japan), KC (South Korea), NCC(Taiwan), SRRC(China)…etc.Meanwhile, countries are under non-modular approval, we have CE (Europe), RCM (Australia and New Zealand)…etc.

The elaboration and the easy steps on how the process we go through as you choose Raytac, detail for each as following:

Modular Approval:

FCC  (USA)
FCC ID Search | Federal Communications Commission
1. Part 15C –> Simply use our module FCC ID on product label
2. Part 15B (EMC) –> request lab to test on EMC, SDoc*
*Definition: SDoc(Supplier’s Declaration of conformity)
One way to show that a product, process or service to comply with a standard or technical regulation, in which a supplier provides written assurance of conformity to the specified requirements.

IC (Canada)
IndustryCanda Wireless ID Database (industrycanada.co)
1.Similar to FCC –> Simply use our module IC ID on product label.
2.–> request lab to test finished good on EMC (IC ES003).
Recommend combining test with FCC Part 15B

Telec (MIC)(Japan)
MIC ICT Policy (soumu.go.jp)
1.–> Simply use our module Telec ID on product label
2.Different from the USA and Canada –> EMC is optional in Japan, upon on end customer’s request.

KC  (South Korea)
South Korea – Labeling/Marking Requirements (trade.gov)
1. Wireless test can be continued to use module report, new test is not required.
2. EMC KN301489(same rule as CE EN301489)
–> to be tested based on final goods under EMC test policy. Same rules as FCC and IC.
Recommend combining test with FCC Part 15B.
3. If product obtain additional cable IO port, test on KN3235 is required.
4. To be KC certified, the new test is required, certification no. cannot be continued to use from other policy. And the test must be done locally.

NCC (Taiwan)
NATIONAL COMMUNICATIONS COMMISSION (ncc.gov.tw)
1. Products is compliant with platform policy –> lab submit photo and add product under Raytac NCC no.
2. Products is not compliant with platform policy –> product must be tested as final goods at the lab to be certified.
*Definition: platform policy: product itself has it’s own function before Bluetooth was installed. For example, a Bluetooth installed pen has a new function; it vibrates when the switch is on. In this scenario, pen originally has it’s own function, and now the addition function; vibration has been added to this device. We say this product is compliant with platform policy.

SRRC (China)
State Radio Regulation of China (srrc.org.cn)
1. –>Simply use our module SRRC ID on product label.
2. Products doesn’t under the category of home electronics / office supplies, SRRC test must be implemented.

Non-Modular Approval:

CE  (Europe)
CE Marking (trade.gov)
1. Wireless test: EN300328
–> Conducted test could continue to use Raytac ‘s CE report.
–> Radiated test is required to be tested based on final goods under wireless regulation.
2. EN301489 (EMC) –> Same rules as FCC and IC. Recommend combining test with FCC Part 15B
3. Safety test: EN60950 (EN62368)–> safety test is required to be tested based on final goods under regulation.

RCM (Australia and New Zealand)
The Regulatory Compliance Mark (RCM) (General) – EESS
1. Products is CE certified –>lab can copy CE report to apply RCM
2. Products is not CE certified –> go through the same test as CE regulations.

Overall, it’s important to note that the certification process and requirements may vary across different regions. Manufacturers should consult the relevant certification authorities to determine the specific requirements for their wireless devices.
Raytac already took a step ahead gone through complex procedures of obtaining certifications, and we also have strong IT team to support for best solutions.Choosing Raytac would allow you to work more efficient and it will be your key in success for all the projects.

Edited by Sales Manager: Mandy Chao

Raytac Corporation 勁達國際電子有限公司
A Bluetooth & WiFi module maker based on Nordic nRF54, nRF53, nRF52, nRF7002 solution 
www.raytac.com email: service@raytac.com Tel: +886.2.3234.0208           

 

nRF52833 Module MDBT50Q By Raytac Has Extended To 105°C Ambient Temperature

nRF52833 Module MDBT50Q By Raytac Has Extended To 105°C Ambient Temperature

Raytac announced both MDBT50Q-512K & MDBT50Q-P1M modules has extended the ambient temperature up to 105°C, following Nordic’s nRF52833’s specification.

nRF52833 Module MDBT50Q By Raytac Has Extended To 105°C Ambient Temperature
nRF52833 Module MDBT50Q By Raytac Has Extended To 105°C Ambient Temperature

Unlike a single component like SoC, modules acted as an integrated equipment which includes some other related components. To secure the module works under the latest environment request while Nordic nRF52833 released, Raytac ensured all related components meet the new temperature requirement with RF efficiency secured.

Today, we are pleased to announce nRF52833 modules:

MDBT50Q-512K: Chip Antenna

MDBT50Q-P512K: PCB Antenna

Both have successfully extended ambient temperature to 105°C which are the most ideal devices for a wide range of commercial and industrial applications.

Raytac Corporation 勁達國際電子有限公司

A BT5.2 & BT5.1 & BT5 & BT 4.2 module maker based on Nordic nRF52 & nRF51 solution 

(nRF52840 & nRF52833 & nRF52832 & nRF52820 & nRF52810 & nRF52811 & nRF51822)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

Nordic nRF52820 solution, MDBT50 series Module by Raytac

Nordic announced their 6th multi-protocol solution of nRF52 series with nRF52820, which supports Bluetooth Low Energy (BLE), Bluetooth mesh, Thread, Zigbee and 2.4GHz proprietary wireless connectivity.

Like other nRF52 siblings, nRF52820 highlights a powerful  64MHz 32bit Arm Cortex-M4 processor, includes 256Kb Flash Memory and 32Kb RAM, features of Bluetooth 5.2, 5.1 and 5 including long range and high-throughput of 2Mbits per second, as well as direction finding, low energy power control and low energy isochronous channels.

A full speed (12Mbits per second) USB 2.0 interface and 1.7~5.5V operation voltage bring a wide range of commercial and industrial wireless applications to nRF52820. To support nRF52820’s development, Nordic released SoftDevice S112, a new memory-optimized central stack. S112 now released as a alpha and will have full SDK (SDK V16.0.0) support coming in Q2 2020.

Raytac nRF52820 Module, MDBT50 Series
Nordic nRF52820 Modules by Raytac, MDBT50 Series

Raytac nRF52833 Series Module MDBT50Q & Demo Board Now Are Available

Just right at the start of 2020, we are happy to announce nRF52833 modules are now available!

Raytac’s nRF52833 series modules are introduced in 3 kinds of antenna options (Chip Ceramic / PCB / u.FL connector for external antenna) brings the best usability to meet different implements.

Chip Antenna Version: MDBT50Q-512K

PCB Antenna Version: MDBT50Q-P512K

u.FL Connector Version: MDBT50Q-U512K

Nordic nRF52833 Module Series.jpg

Raytac Product Change Notice (PCN) Announcement for Nordic nRF52832 Solution Module

Raytac would like to announce Product Change Notice (PCN-19121601) for all nRF52832 module lines include MDBT42Q / MDBT42 / MDBT42V series.


There is no panic for this PCN,  it is refer to module’s appearance changes only but no others. Raytac will remove YELLOW DOT marking on shielding for all modules produced based on Nordic nRF52832 (Build Code: EXX) V.2 SoC since 2020 (Date Code from 001).

In case there is anything unclear for this PCN , please do not be hesitated to contact Account Manger for further assistance.

Raytac Corporation 勁達國際電子有限公司

A BT5.1 & BT5 & BT 4.2 module maker based on Nordic nRF52 & nRF51 solution 

(nRF52840 & nRF52833 & nRF52832 & nRF52810 & nRF52811 & nRF51822)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208

How to update nRF DeviceFamilyPack version to 8.27.1

From the article “Change to nRF52833 module? What the Hardware & Firmware Setting Need To Review?“, Raytac has highlighted Keil users need to update nRF Device Family Pack version to 8.27.1 for SDK16

Here introduced how to change the nRF DeviceFamilyPack version.

Modify nRF DeviceFamilyPack version to V8.27.1
Modify nRF DeviceFamilyPack version to V8.27.1

Change to nRF52833 module? Introduce What the Hardware & Firmware Perspective Need To Review!

Developer who currently are using nRF52840 based modules must be excited waiting for nRF52833’s distribution. Most developers are aware that nRF52833 supports long range, multi protocol and USB interface but has less RAM and Flash memory rather than nRF52840 and no doubt is the best alternative to have cost effective without extra efforts.

Raytac has released 3 models of nRF52833 based modules just at the same time when Nordic released, MDBT50Q-512K / MDBT50Q-P512K / MDBT50Q-U512K. Both nRF52840 and nRF52833 module are based on same form factor and pin out. To have quick visual identification finding the difference, Raytac’s nRF52833 modules are built by Green PCB but nRF52840 modules are Blue.

Raytac BLE Module-nRF52840 & nRF52833

Raytac Released nRF52833 Module / MDBT50Q Series

Nordic’s nRF52833 is an advanced mulitiprotocol SoC solution which supporting not only Bluetooth mesh, Thread, Zigbee but also latest BT5.1 direction finding capable radio. The solution is built around 64MHz Arm Cortex-M4 FPU, 512KB flash memory, and 128KB RAM memory with an extended industrial standard working temperature range of -40 °C to 105°C which is an ideal solution for commercial and industrial applications.

Raytac Corporation, a Taiwan based Bluetooth module maker, has selected Nordic nRF52833 solution building up MDBT50Q series modules. MDBT50Q series modules provide 3 kinds of antenna options (Chip Ceramic / PCB / u.FL connector for external antenna) brings the best usability to meet different implements. The modules have BT5.1 certification and FCC/IC/CE/RCM/Telec/KC/SRRC/NCC/WPC pre-certified, which are the optimized solution that makes it attractive in a very wide range of applications from a performance, time-to-market efficiency, and minimal Bill of Material (BOM) perspective.

MDBT50Q /nRF52833 modules is expected to have mass production by 2019/11, customer who are interested in nRF52833 series module may visit Raytac website for more information.

nRF52833 series module

Chip Antenna Version: MDBT50Q-512K

PCB Antenna Version: MDBT50Q-P512K

u.FL Connector Version: MDBT50Q-U512K

Raytac BLE Module-MDBT50Q-nRF52833

Raytac Corporation 勁達國際電子有限公司

A BT5.1 & BT5 & BT 4.2 module maker based on Nordic nRF52 & nRF51 solution 

(nRF52840 & nRF52833 & nRF52832 & nRF52810 & nRF52811 & nRF51822)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208