New U.S. Headquarter Address: 17800 Castleton Street, Suite 238, City of Industry, CA 91748, USA Phone: 626.328.3827 Our new location strengthens our operational capabilities in the United States, enabling faster logistics, enhanced customer support, and expanded service coverage. We look forward to continuing to serve our partners and customers from our new facility.
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
Raytac has advanced the dev kit version of bundle offer – WIFI+BLE: AN7002Q-DB- 5340-M with an on-board flash memory(MX25R64) to create easy evaluation for Wi-Fi project developments.
Table of Content———————————————————————————————————
Hardware Set Up A. Project WITHOUT External Flash MX25R64 needed B. Project WITH External Flash MX25R64 needed
Software Resources & Preparations
Firmware Build & Compile A. Project WITHOUT External Flash MX25R64 needed B. Project WITH External Flash MX25R64 needed
Note: Pease make sure to have both “Nordic nRF5340-DK” and “AN7002Q-DB-5340-M”connected and running during the WIFI+BLE (nRF7002+nRF5340) project development.
Hardware Network: IDC Ribbon Wire(J-Link Cable): Connect nRF5340-DK to AN7002Q-DB-5340-M USB Wire –Type C USB: Power supply to AN7002Q-DB-5340-M through USB TYPE-C USB Wire-Micro USB: Power supply to nRF5340-DK through Micro USB
A. Project WITHOUT External Flash MX25R64 needed – Allocate QSPI for communication between MDBT53 (BLE) and AN7002Q (WIFI) – External flash MX25R64 flash memory is not activated – NO additional resistor swapping needed, keep it as it is on board now. The Resistors on board align with the Nordic board definition (same as nRF7002-DK). – Please closely follow the definition chart printed on back side of board AN7002Q-DB-5340-M. “Component Options Table” > “AN7002Q active with QSPI (Typ)”
– Photo showing the resistor allocation:
– Schematic of the AN7002Q-DB-5340-M(Click on the image to zoom in):
B. Project WITH External Flash MX25R64 needed – Allocate SPI for communication between MDBT53 (BLE) and AN7002Q (WIFI) – Allocate QSPI for XIP: External flash MX25R64 is activated – It is REQUIRED to reallocate resistors to swap the QSPI and SPI on the AN7002Q-DB-5340-M in order to activate the circuit for MX25R64. – Do necessary resistors swapping manually (closely follow the definition chart printed on back side of board AN7002Q-DB-5340-M.) “Component Options Table” > “External flash and AN7002Q active with SPI enable”
– Photo showing the resistor allocation: Detach the resistor -R27 “Component Options Table” > “External flash and AN7002Q active with SPI enable” <<< Necessary resistors swapping manually needed ↓ >>>
– Schematic of the AN7002Q-DB-5340-M(Click on the image to zoom in): Modify the above resistors swapped and necessary component based on the chart: “Component Options Table” > “External flash and AN7002Q active with SPI enable”
!! Important Note:!! The circuit of SW1(p1.08)/SW2(p1.09)/LED1(p1.06) on AN7002Q-DB-5340-M is NOT COMPATIBLE to Nordic WI-FI Control Pin of swctrl1(p1.08)/host_irq(p1.09)/grant(p1.06). In this case, if you’re working with external flash MX25R64 for the WIFI project, Please avoid pin SW1/SW2/LED1 usage while LED2(p1.07) remains available as normal usage. For the design perspective of mother board/carrier board /target board (mounted with AN7002Q & MDBT53 modules), it is required to design the circuit align to SW1(p0.23)/SW2(p0.24)/LED1(p0.28).
Step 1: Prepared with the latest version of nRF Connect for Desktop, using Windows 64-bit – 5.2.0 Step 2: Prepared with the latest version of Command Line Tools, using Windows X86 64 – 10.24.2
**Note: SEGGER J-LINK Upgrade message might pop up while you’re doing above downloads.
Step 3: Locate all the necessary kits for programming in PC
3. Firmware Build & Compile After you download and set up nRFConnect SDK (NCS), you will be able to apply free VS (Visual Studio) Code IDE as firmware programming tool. Here’re the guidelines to developing programs without/with External Flash MX25R64.
A. Project WITHOUT External Flash MX25R64 needed You can directly build/compile on Nordic NCS without any additional configurations/modifications needed.
B. Project WITH External Flash MX25R64 needed – Allocate SPI for communication between MDBT53 (BLE) and AN7002Q (WIFI) – Allocate QSPI for XIP: External flash MX25R64 is activated
The below example uses NCS v3.1.1 and runs the under: C:\ncs
Step 1: Start with a Wi-Fi Scan project and run the program under: C:\ncs\v3.1.1\raytac <<Create a new application and Copy a sample>>
Step 2: Select SDK v3.1.1 to copy the sample
Step 3: Select example by entering keyword: wifi scan(Wi-Fi Scan)
Step 4: Enter application location and name the project as: wifi_scan_uart_dfu
Step 5: Open an existing application and find the registered project: wifi_scan_uart_dfu
★★How to activate the Devicetree setting of Wi-Fi nRF7002 and Create file:nrf5340dk_nrf5340_cpuapp.overlay Code example is as follows: / { chosen { aliases { /delete-node/ leds; /delete-node/ buttons; }; };
Step 7: It is required to do MCUBoot before working with DFU using External Flash Please do the code configuration in sysbuild.conf as following reference code.
SB_CONFIG_BOOTLOADER_MCUBOOT=y # DFU with UART SB_CONFIG_MCUBOOT_MODE_SINGLE_APP=n
# DFU with external flash SB_CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y
Step 8: It is required to do MCUMGR before working with DFU over UART Please do the code configuration in prj.conf as following reference code.
# Enable QSPI driver for Application CONFIG_NORDIC_QSPI_NOR=y
# Enable mcumgr DFU in application CONFIG_MCUMGR=y CONFIG_NET_BUF=y CONFIG_ZCBOR=y CONFIG_CRC=y
# Enable mcumgr management for both OS and Images CONFIG_MCUMGR_GRP_OS=y CONFIG_MCUMGR_GRP_IMG=y CONFIG_FLASH=y CONFIG_IMG_MANAGER=y CONFIG_STREAM_FLASH=y CONFIG_FLASH_MAP=y
# Configure MCUMGR transport to UART CONFIG_MCUMGR_TRANSPORT_UART=y CONFIG_BASE64=y
Step 9: Add with MCUBoot setting , and create a root for sysbuild ; Build with file mucboot.overlay & file mcuboot.conf
9A. With mucboot.overlay &mx25r64 { status = “okay"; };
Step 10: Create a VERSION file by referencing the following code when testing DFU over UART. VERSION_MAJOR = 99 VERSION_MINOR = 0 PATCHLEVEL = 0 VERSION_TWEAK = 0 EXTRAVERSION =
Step 14: Generate a Merged.hex file after compiling the program
Step15: You can choose Build/Debug/Flash under ACTIONS during development << Build >>
<< Debug >>
<< Flash >>
Step 16: Go to ACTIONS >> Memory report
Now you can see partitions available in the system. mcu_secondary has already been located in MX25R64 flash memory.
4. Test/Validate DFU Process & WIFI SCAN After the firmware programmed to MDBT53 module on board, we use the USB to UART adaptor board for connection AN7002Q-DB-5340-M through: A. MCUMGR UART to PC and through: B. WiFi Scan UART to PC respectively. Note: We suggest you finish connecting A. and B. before running tests.
Now we can run the tests.
A. DFU over UART – Using AuTerm Program 1. We can locate Image version=V99.0.0 under the current VERSION file
It also indicates Image version: 99.0.0 in MCUmgr-Slot 0.
2. Try to modify the file version from V99 to V100 under VERSION file: VERSION_MAJOR = 100
VERSION_MINOR = 0
PATCHLEVEL = 0
VERSION_TWEAK = 0
EXTRAVERSION =
And go with “Pristine Build”
3. We’re about to run DFU over UART , Please DO NOT do “Flash” or “Erase”.
Proceed with “Force reboot”
4. It’s now Version 100.0.0 in Slot 0 under MCUgr ⭢ DFU over UART successfully done!
Before it was Version 99.0.0 in Slot 1 under MCUgr.
B. WIFI SCAN – PuTTY Console WIFI SCAN credentials can be located under PC Console – PuTTY.
[New Taipei, Taiwan / Los Angeles, USA] We’re thrilled to announce that Raytac Group, including Raytac Corporation(USA) and abietec Inc., will be joining Embedded World North America 2025, in November 4-6 at the Anaheim Convention Center, CA. Come find us at Booth #5067!
This year, we’re bringing lots of exciting news: From Raytac:
Brand-new Nordic nRF54L series modules: AN54LQ and AN54LV(Product Link), built for Bluetooth® LE 6.0 with ultra-low power and strong RF performance.
A full Channel Sounding demo on how precise measurement of multipath and distance can enhance real-time location accuracy, improve signal reliability, and optimize antenna placement.
Introducing you to our Ecosystem, including all our partners and technologies used in various applications.
Discover how our modules can reduce development time and costs, making your projects more efficient.
One-on-one consultations with our experts to help you find the right solutions for your needs.
From abietec:
ODM/OEM design services for everything wireless: Bluetooth®, Wi-Fi, mmWave, LoRa, NB-IoT… You name it!
More importantly, Stop by our booth to explore new products, join fun interactive games, and win prizes!
Let Raytac & abietec be your bridge to product success, connecting great ideas with real-world wireless solutions.
We’re waiting for you at: Hall C – Level 1 Booth 5067
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:
Hardware Set Up
Software Kits resource download & install
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
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.
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
[2025.02.19] Raytac Corporation is proud to announce that our application for Wi-Fi Alliance (WFA) certification on the AN7002Q series(based on Nordic’s nRF7002 IC) has been successfully approved. This achievement reinforces our commitment to providing high-quality, reliable, and standard-compliant wireless solutions. By leveraging this certification, our modules ensure seamless interoperability, enhanced security, and superior performance for a wide range of IoT applications.
Advantages of Using Raytac Modules with WFA Certification:
Reliable and Secure Connectivity – Ensures seamless communication with other Wi-Fi-certified devices while meeting industry-leading security standards for stable and secure data transmission. Faster Time-to-Market – Pre-certified modules simplify compliance processes, reducing development time. Global Market Access – Certification helps meet regulatory requirements in multiple regions, expanding business opportunities. Significant Cost-Saving – Compared to the chip-on-board approach, using Raytac’s Wi-Fi module allows direct access to the Derivative programs(please click here for more descriptions), leveraging Raytac’s CID to minimize certification costs and save time-to-market.
To learn more about Wi-Fi certifications and Wi-Fi + BLE applications, feel free to contact us anytime at sales@raytac.com.
Edited by Account Manager: Ms. Mandy Chao
Raytac Corporation 勁達國際電子股份有限公司 A Bluetooth, Wi-Fi, and LoRa Module Maker based on Nordic nRF54; nRF53: nRF52; nRF51; nRF7002 Semtech Specification: SX1262
We are thrilled to announce that Raytac Corporation will be participating in Embedded World 2025 from March 11 to March 13, 2025, at the Nuremberg Exhibition Centre in Germany.
IoT and Wireless technologies such as Bluetooth Low Energy (BLE), Wi-Fi, and LoRa…etc. continue to reshape industries worldwide, that’s why Raytac is at the forefront, providing cutting-edge solutions that accelerate product development. Together with our partner, Nordic Semiconductor, we offer a comprehensive range of modules designed to meet the increasing demands of today’s connected world.
This year, we have exciting innovations to showcase:
Unveiling our new service: Customized OEM/ODM designing for customers.
These are just a few of the groundbreaking solutions we’ll be unveiling. You won’t want to miss the chance to experience these with us!
What to Expect at Our Booth:
Live demonstrations showing how Raytac’s modules can be implemented in multiple industries.
Discover how our modules can reduce development time and costs, making your projects more efficient.
One-on-one consultations with our experts to help you find the right solutions for your needs.
Stop by and visit us at: HALL 3 Booth 3-111 M2M Area
We would love to connect with you and discuss how Raytac can support your next project. Whether you’re an engineer, developer, or business decision-maker, we have something for everyone at Embedded World 2025.
LE Audio, introduced with Bluetooth 5.2, brings significant advancements to audio technology by using the Low Complexity Communication Codec (LC3). Compared to older codecs like SBC, LC3 provides better audio quality while reducing power consumption, making it ideal for devices like wireless earphones and hearing aids. In this article, we’ll explore two key modes in LE Audio: Broadcast Isochronous Stream (BIS) and Connected Isochronous Stream (CIS). These modes cater to different use cases, offering flexible audio experiences.
What is Broadcast Isochronous Stream (BIS)?
BIS enables one-way audio broadcasting from a single source to multiple devices simultaneously without pairing. Several BIS streams can form a Broadcast Isochronous Group (BIG), allowing synchronized multi-stream transmission, ideal for environments where many users need access to the same audio content, such as events or museum tours. Any device that supports LE Audio can receive the broadcast, making it an accessible and versatile solution for shared audio experiences.
Here’s a chart including BIS and BIG:
Example Use Case: Concerts and Events Imagine attending a large outdoor concert where BIS technology is used to broadcast live music directly from the stage to the audience’s devices, such as smartphones and wireless earphones. BIS can broadcast live music from the stage directly to attendees’ devices, ensuring everyone hears the performance in real-time, regardless of location.
Example Use Case: Museum Tours In a museum setting, Broadcast Isochronous Stream (BIS) can be used to deliver audio guides directly to visitors’ smartphones or rented devices. Visitors can receive synchronized audio guides on their smartphones, enriching their experience and offering multi-language support.
What is Connected Isochronous Stream (CIS)? CIS focuses on direct, device-to-device connections. The audio stream is transmitted between paired devices with two-way communication, creating a connected and dedicated audio experience. It’s ideal for personalized experiences like hearing aids or wireless earphones. Multiple CIS streams can be synchronized using a Connected Isochronous Group (CIG) for simultaneous audio transmission while maintaining the benefits of a personalized connection.
Here’s a chart including CIS and CIG:
Example Use Case: Wireless Earphones Imagine a user connecting their wireless earphones to a smartphone via CIS. When two Bluetooth earphones are connected simultaneously, multiple CIS streams can be grouped into a Connected Isochronous Group (CIG) to achieve synchronized audio transmission across both devices and also enables high-fidelity audio streaming, ensuring clear and immersive sound. With CIS, each user can adjust volume or equalizer settings independently without impacting others, creating a truly personalized listening experience. CIS provides a significant upgrade over traditional Bluetooth audio by delivering richer sound quality with lower latency.
Example Use Case: Hearing Aids Connected Isochronous Stream (CIS) is especially beneficial for hearing aids, allowing individuals with hearing impairments to directly connect their devices to a TV, smartphone, or other audio sources. CIS enables real-time adjustments to improve speech clarity or reduce background noise, ensuring the audio is clear and effective. Users can have a closer and more immersive audio experience, which is crucial for enhancing social interactions and supporting daily activities.
How BIS and CIS are grouped into BIG and CIG
Summary
BIS vs. CIS: Which Fits Your Needs?
BIS is suitable for shared audio experiences, such as public events and guided tours, where multiple users need simultaneous access.
CIS is designed for personalized audio, offering low-latency and high-quality sound for individual users or synchronized multi-device setups.
LE Audio is set to change everyday audio experiences with richer, more versatile audio solutions. Whether it’s concerts, museums, or hearing aids, BIS and CIS provide innovative ways to enhance audio quality and efficiency.
Edited by Sales Manager: Ms. Mandy Chao
Raytac Corporation 勁達國際電子股份有限公司 A Bluetooth, Wi-Fi, and LoRa Module Maker based on Nordic nRF54; nRF53: nRF52; nRF51; nRF7002 Semtech Specification: SX1262
Currently, the Nordic Wifi module – AN7002Q on Raytac’s AN7002Q-DB-5340 board isn’t loaded with a Wi-Fi MAC address. You can choose to use your own MAC address or request one from Raytac. Below is a complete tutorial for users who would like to purchase MAC addresses themselves.
Note: Raytac provides two free Wi-Fi MAC addresses (2.4GHz & 5GHz bands) for each AN7002Q module. If you have a Raytac AN7002Q-DB-5340 demo board but have not received the Wi-Fi MAC addresses, please contact us at sales@raytac.com.
★ What is a MAC Address?
A MAC address (Media Access Control address) is a unique identifier used to identify network devices. It is typically composed of six groups of two hexadecimal digits, for example, 00:1A:2B:3C:4D:5E. The first six characters are known as the Organizationally Unique Identifier (OUI), which identifies the manufacturer or supplier of the MAC address. Manufacturers can use the OUI to identify the producer of the device.
Each network device’s MAC address should be unique. It is an important identifier used for unique identification among network devices, ensuring that devices can communicate correctly within a local area network. However, it is important to note that MAC addresses can be modified within a local network, so they should not be relied upon as the sole basis for security.
★ How to Obtain a MAC Address?
The application and distribution of MAC addresses are managed by IEEE (Institute of Electrical and Electronics Engineers). Here’s how to apply for a MAC address from IEEE: Currently, MAC addresses can only be purchased directly from the IEEE Standards Association in the United States. Depending on the quantity, they can be categorized as:
MA-L (approximately 16 million addresses) MA-M (approximately 1 million addresses) MA-S (4096 addresses)
2. Log in and go to the MAC Address Purchase Page After logging in, navigate to the MAC address purchase page:IEEE MAC Address Purchase
3. Select the number of MAC Addresses to purchase.
4. Fill in your purchase information by providing the required details.
5. Confirm confidentiality Confirm whether the MAC address purchase is confidential. If you are purchasing publicly registered MA-L, select “No" for this option.
6. Choose payment method IEEE accepts several payment methods, including mailing a U.S. bank draft, wire transfer in U.S. dollars, and online credit card payment.
7. Receive your OUI Within 7 working days, IEEE will send an email to the registered email address containing the purchased OUI.
After obtaining the OUI, you can retrieve all the purchased MAC addresses using code and then import them into a database or Excel for management.
Edited by Sales Manager: Ms. Vicky Huang
Raytac Corporation 勁達國際電子股份有限公司 A Bluetooth, Wi-Fi, and LoRa Module Maker based on Nordic nRF54; nRF53: nRF52; nRF51; nRF7002 Semtech Specification: SX1262
Step 1. Execute the combine batch file in bootloader (nrf52832_bootloader_setting_merge.bat) and generate file ofnrf52832_bootloader_secure_combin_settings.hex :
@echo off title = [ J-Link Tool ] %CD% set nrfDir=C:\Program Files (x86)\Nordic Semiconductor\nrf5x\bin set BS= nrf52832_bootloader_secure_settings.hex set BL= nrf52832_xxaa_s132.hex set BSBLCombind= nrf52832_bootloader_secure_combin_settings.hex set path=%nrfDir%;%path% pause echo ———–merge image file——————- mergehex.exe -m %BS% %BL% -o %BSBLCombind% pause
Step 2. Create a Final.hex file by 3-in-1 batch file(nrf52832_3in1_merge.bat) ※Note : This hex file is created for the production line to pre-load firmware into modules prior to shipment.
@echo off title = [ J-Link Tool ] %CD% set nrfDir=C:UsersuserDesktopNordic BLEnRF5_merge toolsnRF52 bin set SD= s140_nrf52_7.2.0_softdevice.hex set BLT= nrf52832_bootloader_secure_combin_settings.hex set APP= nrf52832_xxaa.hex set SD_BLT=SD_BLT.hex set Finalfile=Final.hex set path=%nrfDir%;%path% pause echo ———–merge image file——————- mergehex.exe -m %SD% %BLT% -o %SD_BLT% pause mergehex.exe -m %SD_BLT% %APP% -o %Finalfile% pause
Step 3. Create a DFU(OTA).zip file of nrf52832_xxaa.zip ※Note : This zip file is created for end device DFU(OTA) implementation.
※Note : The “0xCB" appeared in the above DOS code(in red font) is the FWID(Firmware ID) for s140_nrf52_7.2.0_softdevice.hex; FWID can be found from the soft device documents on the Nordic website.
Step 4: Run DFU OTA (On mobile in this example)
4A. Install the nRF Connect APP on mobile, with DFU OTA file: nrf52832_xxaa.zip.(Download link)
4B. Send nrf52832_xxaa.zip via email to mobile device after combination is done on PC, then download it.
4C. Open nRF Connect APP and run connection;
4D. Execute DFU and select “Distribution packet(ZIP)", thus starting the DFU OTA process.
4E. Start DFU OTA → exit the APP after DFU OTA is completed → restart the mobile device.
Secure DFU OTA for nRF52832 solution modules: Guide to create hex/zip file for implementation Detailed links of articles: Part 1: Bootloader & Application (Click for article link) Part 2: Combining & merging built files
Technical guidelines provided by R&D Manager: Mr. MW Lee Edited by Sales Manager: Ms. Mandy Chao
Raytac Corporation 勁達國際電子股份有限公司 Raytac Corporation: A Bluetooth, Wi-Fi, and LoRa Module Maker based on Nordic nRF54; nRF53: nRF52; nRF51; nRF7002 Semtech Specification: SX1262
Recently we have received the FAQ: how to write MAC address into the OTP memory of Raytac’s AN7002Q-P Nordic Wi-Fi module? In this article, we’ll get this question explained to give customers a more smooth experience using the AN7002Q-nRF5340 Demo Board(AN7002Q-DB-5340).
Is there an existing Wi-Fi MAC address in the AN7002Q part on the DevKit?
Currently, the AN7002Q module on Raytac’s AN7002Q-DB-5340 board has no Wi-Fi MAC address.
When running Wi-Fi Scan code/Station code/Shell code…etc. on NCS v2.6.0 (and later versions), the AN7002Q module must have a programed Wi-Fi MAC address to function properly.
Therefore, it’s necessary to follow the below process: 1. Program the original Wi-Fi radio test code (..\nrf\samples\wifi\radio_test) into the MDBT53 section, 2. Then write the Wi-Fi MAC address in to the AN7002Q section(nRF7002 IC) via command.
After this, program the original Wi-Fi Scan code/Station code /Shell code … into the 5340, and it will function properly.
**Raytac will assign 2 Wi-Fi MAC addresses(for both 2.4GHz & 5GHz) to every AN7002Q module. *If customers don’t have Wi-Fi MAC addresses for DevKit development yet, please reach out to service@raytac.com
Scenario: Following error occurred when building the SCAN example code, flash it onto the AN7002Q-DB-5340 board, and run the test.
Solution:
When running Wi-Fi scan code on NCS v.2.6.0 or later version, the OTP memory in the AN7002Q module must have a Wi-Fi MAC address programmed in for the Wi-Fi scan functionality to work properly.
(Note: OTP is a One-Time programmable memory, which means the value can only be written once. The customer must aware of this before performing the OTP operation.)
1. Program the original Wi-Fi radio test code (..\nrf\samples\wifi\radio_test) into the MDBT53 section, then manually input and execute the following OTP read command.
wifi_radio_ficr_prog otp_read_params
If you see both MAC0 and MAC1 display a value of 0xFF, as shown in above, it means that you haven’t written the Wi-Fi MAC address into the AN7002Q’s OTP.
2. Manually issue the OTP write command to write the Wi-Fi MAC address into the OTP.
After you complete the above, use the OTP read command in below to check if the Wi-Fi MAC address value was written. The MAC0 and MAC1 should display the value you’ve input from the OTP write command.
wifi_radio_ficr_prog otp_read_params
3. Program the original Wi-Fi SCAN code back into the MDBT53, the Wi-Fi scan functionality should work properly.
Raytac Corporation 