標籤: Module

Join Raytac at “Embedded World 2025″ – Experience Innovation at Our Booth!

發表於 由撰寫發表留言

Dear Valued Attendees,

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:

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.

For more details and a sneak peek of what we have in store, don’t forget to check out:
1. Our website: http://www.raytac.com
2. Our LinkedIn: https://www.linkedin.com/in/raytac/
3. Our WordPress Blog: https://raytac.blog/

We can’t wait to see you at the event and look forward to the opportunity to collaborate with you!

Edited by Account Manager: Ms. Dana Liu

Raytac Corporation 勁達國際電子股份有限公司
A Bluetooth, Wi-Fi, and LoRa Module Maker based on
Nordic nRF54; nRF53: nRF52; nRF51; nRF7002
Semtech: 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 Pre-Certified.
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208

How to use Raytac’s MDBT50Q-CX-40 dongle as a BLE sniffer?

發表於 由撰寫發表留言

Introduction

Uncertainties in Bluetooth Application Development
Bluetooth’s growing popularity comes with challenges during development. Common issues include hardware instability, software incompatibilities, and environmental interference.
Accurate issue identification and resolution are keys to successful development.

Common Uncertainties
Unstable Connections: Disruptions from wireless signals or physical obstacles.
Pairing Failures: Devices unable to establish connections.
Data Errors: Packet loss or corruption during transmission.
Compatibility Problems: Protocol version mismatches affecting interoperability.

Efficient Bluetooth Issue Analysis
Challenges like transmission speed limitations, data loss, connection failures, or protocol violations can arise. As Bluetooth signals travel wirelessly, precise analysis requires specialized tools.
Nordic offers firmware integrated with Wireshark, flashable onto the Raytac MDBT50Q-CX-40 Dongle, enabling engineers to capture and analyze Bluetooth broadcast signals via USB.
This setup streamlines issue identification and resolution.
Below’s how to configure the Dongle for Wireshark reception.


Flashing Firmware into MDBT50Q-CX-40
Step 1: Download and extract the nRF Sniffer for Bluetooth LE from Nordic:
https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE
Step 2: Locate the file: sniffer_nrf52840dongle_nrf52840_4.1.1.hex
This is the firmware to flash into MDBT50Q-CX-40.


Step 3: Press and hold the button on MDBT50Q-CX-40 and plug it into a PC USB port.
Bootloader mode will be activated after the LED light is turned on.
Then flash the firmware using nRF Programmer.

Step 4: Open the nRF Programmer and follow the below steps:
Select the Device:


The device will appear as the name shown in below:


Add Firmware File:


Load sniffer_nrf52840dongle_nrf52840_4.1.1.hex into the Programmer:


Press “Write" to flash the firmware.
After flashing, press “Select Device" again.
If the Device name appears as nRF Sniffer for Bluetooth, the flashing is successful.


Set Up Wireshark Software Environment
Step 1: Download & install nRF-Util: https://www.nordicsemi.com/Products/Development-tools/nRF-Util
Step 2: Open MS-DOS and use the command nrfutil list to check if the ble-sniffer item is available.
If not, install it using nrfutil install ble-sniffer.


Step 3: Download and Install Wireshark: https://www.wireshark.org/download.html.
Step 4: Open Wireshark and navigate to: Help → About Wireshark → Folders.
Step 5: Locate the string under Personal Extcap Path for the extcap directory, which will be an empty folder.


Step 6: Copy the files from nrf_sniffer_for_bluetooth_le_4.1.1\extcap (downloaded earlier) into Wireshark\extcap directory.


Step 7: After reopening, you should see an interface with a configurable icon next to the dongle.


Step 8: Edit → Configuration Profiles → Import → From Directory → Navigate to the directory nrf_sniffer_for_bluetooth_le_4.1.1\Profile_nRF_Sniffer_Bluetooth_LE and click “Select Folder".


Step 9: The profile will be imported. Click OK to confirm.


After all the above is done, the setup shall be completed.


Capturing and analyzing Bluetooth packets
After launching the program, you can see the following devices and Dongle settings.
Double-click to start the packet capture process:


If you want to capture packets with PHY=125K, you can use the following settings:


Packet Analysis Method
In Wireshark, select the device from the “Device" menu to capture and analyze broadcast packets.

User Cases – What sniffer can offer
1. Disconnection when transmitting over 20 bytes between Tablet and Raytac’s AT-Command Module:
Through sniffer analysis, it was discovered that Raytac’s module requested a packet length of 251 bytes, but the tablet’s TX setting was limited to 27 bytes.


2. Broadcast Device Name containing invisible characters:
The device could connect using a mobile app but failed to connect using Central’s code.
From the sniffer interface shown below, the device name length is 11, but the Length field shows 13.
The actual data length (Type length + Device Name) = 1 + 11 = 12, indicating an issue with the program’s broadcast name length.


3. Incorrect parameter settings causing issues with throughput or packet reception:
Improper settings can lead to reduced throughput, incorrect data reception, or disconnections.
The diagram below shows a correct setup with high-volume data transmission. The Protocol Length is 251, and the data transmission intervals are consistent, achieving optimal throughput.


Summary
Mastering hardware and software setups and effectively using packet analysis tools can boost development efficiency and enable high-performance Bluetooth applications.

Resources:
https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE
https://docs.nordicsemi.com/bundle/nrfutil_ble_sniffer_pdf/resource/nRF_Sniffer_BLE_UG_v4.0.0.pdf
https://www.wireshark.org/download.html

User manual:
https://raytac.blog/2024/07/10/firmware-coding-dfu-onto-mdbt50q-rxuser-manual-of-mdbt50q-cx-nrf52840-usb-c-dongle/

Edited by Business Development Manager: Mr. Tony Yin
Technical guidance provided by R&D Manager: Mr. Stanley Huang


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

Bluetooth Specification: BT6.0 ; 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
email: sales@raytac.com
Tel: +886-2-3234-0208



Overview of Raytac’s nRF54L15 module – AN54L15 series & Channel Sounding preview (Bluetooth 6.0)

發表於 由撰寫發表留言

Raytac nRF54L15 Module Series (If you want to know more or register for samples, please click me)
Table of Contents:

  1. nRF54L15 SoC feature brief
  2. Comparison among nRF54L15/ nRF5340/ nRF52840/ nRF52832 SoC modules
  3. Get started with nRF54L15 development (NCS 2.8.0)
  4. Channel Sounding preview

Next Level multi-protocol SOC -nRF54L Series

A. NEW generation nRF54L15 Soc Series

Key Features:
– ARM Cortex M33 + RISC-V co-processor 128Mhz in Nordic SoC
– Ultra compact Soc variant QFN/WLCSP, 22nm
– 2x the processing power, 3x the processing efficiency
– Industry-leading power consumption for battery-critical applications
– Global RTC wake-up from system-off
– Compatible with Raytac WIFI module -AN7002Q series
– High throughput 4MB proprietary radio mode
– Bluetooth Specification 6.0 / Support Channel sounding (Pending firmware)
– PSA(Platform Security Architecture) security level 3 qualified

Raytac’s nRF54L15 Modules
– AN54LQ-15 (Regular) & AN54LV-15(Compact)


B. Comparison among nRF54L15/ nRF5340/ nRF52840/ nRF52832 SoC modules

If you are familiar with Nordic nRF52, nRF53 module series, you will have better idea to tell the difference heading to NRF54L series by referring to the chart as below. (Click on the picture to zoom in)


C. Get started with nRF54L15 development (NCS 2.8.0)

nRF54L15 SoC Spec  << access link
Nordic nRF54L15 DK  << access link
Raytac AN54LQ-DB-15   << access link to be updated

Photo of Nordic nRF54L15 DK


Preparation of Hardware:
1. 1x Nordic NRF54L15 DK (PCA10156-0.9.1)
(Note: If you have PDK (PCA10156-0.8.1) on hand, it can be done in trial phase)
2. 1x Raytac AN54LQ-DB-15
3. 1x IDC Ribbon wire
4. 2x USB-C connector wires (for powering the kit up)

Note: Using Nordic nRF54L15DK / nRF54L15PDK as debugging tool and Raytac Demo board-AN54LQ-DB-15 as simulated carrier board(main board) to proceed the program of nRF54L15 for code compiling and development.

Tips: Please align the red edge of Ribbon at side of 1 in connector J1.


Step 1 —- Connected NRF54L15 DK and AN54LQ-DB-15 by IDC Ribbon wire
Step 2 —- Powering on both NRF54L15 DK and AN54LQ-DB-15 by USB-C connector


<<  Schematic of AN54LQ-DB-15(Updated on 21-Jan-2025)  >> (Click on the picture to zoom in)


Software Kits Resource & Preparation
Download nRF Connect For Desktop (Please Click Me)
Download nRF Command Line Tools (Please Click Me)


Preparation
1. Prepared with the latest version of nRF Connect for Desktop and Select version Windows 64-bit – 5.1.0
2. Prepared with the latest version of nRF Command Line Tools and Select version Windows x86 64-10.24.2
**Note: SEGGER J-LINK Upgrade message might pop up while you’re doing above download.

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

3. Locate all the necessary kits for programming in PC (Check Software/Application list)


Get started with building your program

Intro: The development tool of nRF Connect SDK(NCS) equipped with free VS (Visual Studio) Code IDE for firmware compile and programming.
Note: it is highly recommended to apply NCS 2.8.0 for advanced features of nRF54L15.

Step 1 —- Activate your “nRF Connect for Desktop”  >> “Toolchain Manager” >> “Open” >> “Install”


Step 2 —- You will find multiple options of NCS V x.x.x in the tool, we’re using NCS v2.8.0 as example to run sample code of nRF54L15.


Step 3 —- Make sure the NCS v2.8.0 is installed at same directory with compiling system. (the root of Open VS Code) (This is using C:\ncs  as example.)


In case to organize the files, do “Select directory’” and “Confirm”.


Step 4 —- After nRF Connect SDK v2.8.0 Download ready , go “Open VS Code”.


Step 5 —- Go “Open Existing Application” , and activate example code: Bluetooth > peripheral_uart


Step 6 —- Moving to program build & compiling by selecting dev kit: nrf54l15dk/nrf54l15/cpuapp


Step 7 —- You will get a .hex file after the above programming compiling process.


Step 8 —- Functions are available for during the code compiling process under “ACTIONS” in VS Code IDE
<< Build >>


<< Debug >>


<< Flash >>


Firmware Programming
It is feasible to do the firmware programming using nRFConnect SDK (NCS) tool.
Developer may use “Programmer” to do the firmware flashing with the candidate .hex file.

Step 1 —- Execute nRF Connect for Desktop >> Programmer >> Open


 “Select Device”


Select ”nRF54L15 DK”


“Add File”


Step 2 —- Select the candidate .hex file

Select “Erase & Write”


It indicates the programming process is on the way↓


The firmware programming process is done after seeing “Completed” in system Log field.


Step 3 —- Use the mobile App to make sure the Bluetooth broadcasting is functioning after the firmware flashing process is successfully done to the module.


D. Channel Sounding Preview

What is Channel Sounding? —- Advance the “Find My” feature into next level accuracy
Have you ever concerned about the distance accuracy when you’re using RSSI to get the distance between devices and to evaluate the transmission distance with legacy Bluetooth module?
Nordic NRF54 solution has taken us into next level with Channel Sounding feature that achieves the “centimeter-level” distance accuracy. Early implement achieves 10-20cm in the record.

Credit: Bluetooth Alliance


How does Bluetooth Channel Sounding work?
Bluetooth Channel Sounding implemented with Phased-Based Ranging (PBR) & Round-trip time (RTT)(the concept idea of TOF time of flight) algorithm to achieve a higher precision of measuring distance between 2 devices.

Phased-Based Ranging (PBR):
Signal has been sent between initiator and reflector with multiple frequency to increase measuring accuracy.

Credit: Bluetooth Alliance


Round-trip time (RTT): It’s the concept of utilizing TOA (Time of arrival). Using TOD(Time of departure) & TOA to measure the timing during the packet transmission between devices.

Credit: Bluetooth Alliance


Potential applications:
Personal item finding
Secure access control
Smart lock system
Digital Key
Asset Tracking

Reference:
Bluetooth Channel Sounding
nRF54L15 DK hardware
nRF Connect SDK Documentation
Nordic Dev Zone forum
AN54LQ-15 Module series

Edited by Business Development Manager: Ms. Jocelyn Tsai
Technical guidance provided by R&D Manager: Mr. MW Lee & Mr. Stanley Huang




Raytac Corporation 勁達國際電子股份有限公司
A Bluetooth, Wi-Fi, and LoRa Module Maker 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 Pre-Certified.
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208


Understanding LE Audio: BIS and CIS Explored

發表於 由撰寫發表留言

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

Bluetooth Specification: 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
email: sales@raytac.com
Tel: +886-2-3234-0208

Step-by-Step Guide to Purchasing MAC Addresses from IEEE for Your Devices

發表於 由撰寫發表留言

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)


★ Purchase process

1. Register for an IEEE Account
Visit IEEE’s official website to create an account.


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

Bluetooth Specification: 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
email: sales@raytac.com
Tel: +886-2-3234-0208

Secure DFU OTA for nRF52832 solution modules: Creating hex/zip file for implementation – Part 2(Combining/merging built files)

發表於 由撰寫發表留言

Following up – Part 1: Bootloader & Application (Click for article link),

We will be focusing on:

Part 2: Combining & merging built files

in this article.

IC: nRF52832
DK: PCA10040 (for nRF52832)
SDK: 16.0.0
Softdevice: s132_nrf52_7.0.1_softdevice.hex
IDE: Keil C
PC: Win 10


Part 2: Combining & merging built files


Step 1. Execute the combine batch file in bootloader (nrf52832_bootloader_setting_merge.bat) and generate file of nrf52832_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.

nrfutil pkg generate –hw-version 52 –sd-req 0xCB –application-version 0xFF –application
nrf52832_xxaa.hex –key-file private.pem nrf52832_xxaa.zip

The DFU OTA zip file will be derived.

※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

Bluetooth Specification: 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 Pre-Certified.
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208

Secure DFU OTA for nRF52832 solution modules: Guide to create hex/zip file for implementation – Part 1(Bootloader & Application)

發表於 由撰寫發表留言

Here are the guidelines for users to implement Secure DFU OTA(over-the-air) while using nRF52832 Solution modules. (Click on link for Raytac nRF52832 module series)

IC: nRF52832
DK: PCA10040 (for nRF52832)
SDK: 16.0.0
Softdevice: s132_nrf52_7.0.1_softdevice.hex
IDE: Keil C
PC: Win 10

Below are the guidelines to implement Secure DFU OTA by using Raytac’s nRF52832 modules, SDK16.0.0.
It consists of 2 parts:

Part 1: Bootloader & Application


Part 2: Combining and merging built files (Article link)

In this article, we will be focusing on Part 1: Bootloader & Application.

Bootloader


Path: ..\nRF5_SDK_16.0.0_98a08e2\examples\dfu\secure_bootloader\pca10040_s132_ble\arm5_no_packs
Specifically for nRF52832, programmers need to embed ECC(Elliptic Curve Cryptography) into the bootloader.


Step 1. ’micro_ecc_lib_nrf52.lib’ library can be found in the path below, but we need to boot it up first.


Step 2. Unzip ’micro-ecc-master.zip’ to the below path(create a new “micro-ecc” file first).


Step 3. Run ’gcc-arm-none-eabi-7-2018-q2-update-win32.exe’.


Step 4. Make sure the Environment variables in Win10 are set as below. (Follow the steps 1 to 6)


Step 5. Open DOS → run the “make” command under armgcc path → generate’micro_ecc_lib_nrf52.lib’


Step 6. Add ’micro_ecc_lib_nrf52.lib’ into folder: nRF_micro-ecc


Step 7. An error may occur while building bootloader without a public key:
(Shown in red frames in below screenshot)


Step 8. How to generate the public key file in Bootloader?
A. Visit DOS at path: ..\Python27\Scripts
B. Then execute:

nrfutil keys generate private.pem
nrfutil keys display --key pk --format code private.pem --out_file public_key.c


Step 9. Copy the pk[64] code from (public_key.c) into (dfu_public_key.c)
(Shown in red frames in below screenshot)

※Note: Make sure to save the 3 generated files:
private.pem
public_key.c
dfu_public_key.c


Step 10. Generate the bootloader file: nrf52832_xxaa_s132.hex after re-compiling the code files.

Application


Path:
..\nRF5_SDK_16.0.0_98a08e2\examples\ble_peripheral\ble_app_uart\pca10040\s132\arm5_no_packs
Before building Application code , some amendments need to be made regarding DFU-related settings and code inside Application:


Step 1. Add code in definition in C/C++ :
BL_SETTINGS_ACCESS_ONLY NRF_DFU_SVCI_ENABLED NRF_DFU_TRANSPORT_BLE=1
(Total 3 steps definitions need to be set up)


Step 2. Add the 3 paths shown below in C/C++ to make DFU work.


Step 3. Add the .c files inside red frame in (Screenshots 1 & 2)
and add the 2 groups of (nRF_DFU & nRF_SVC)(Screenshot 4) under Project(Screenshot 3)


Step 4. Add code into main.c file in Application (..\examples\ble_peripheral\ble_app_uart\main.c)
(Please refer to: main.c file at: ..\examples\ble_peripheral\ ble_app_buttonless_dfu)


Step 5.
The code of file: sdk_config.h (..\examples\ble_peripheral\ble_app_uart\pca10040\s132\config\sdk_config.h)
inside Application needs to be modified.


Step 6. Adjust the IRAM1 value in Target after implementing DFU service:
Make sure the IRAM1 Value of *p_app_ram_start is modified from default: 0x20002AD8 0xD528 to
0x20002AE8 0xD518, as shown in the red frame in the bottom right corner.
In this case, the program should run/advertise successfully.


Step 7. Create a file of: nrf52832_xxaa.hex after building application code files.



Step 8. Create a bootloader setting file of nrf52832_bootloader_secure_settings.hex via DOS.
nrfutil settings generate –family NRF52 –application nrf52832_xxaa.hex –application-version 3 —
bootloader-version 2 –bl-settings-version 1 nrf52832_bootloader_secure_settings.hex –no-backup

※Stay tuned for Part 2: Combining and merging built files in the next article, scheduled release in next week(04-Sep-2024).

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

Bluetooth Specification: 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 Pre-Certified.
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208

FAQ: How to write MAC address into the OTP memory of Raytac’s nRF7002 Wi-Fi module/AN7002Q-DB-5340 DevKit

發表於 由撰寫發表留言

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



==================================================================================

Case study 1. SCAN code example

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.

https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/wifi/radio_test/ficr.html

wifi_radio_ficr_prog otp_write_params 0x120 0xDDCCBBAA 0xFFEE

wifi_radio_ficr_prog otp_write_params 0x128 0xDDCCBBAA 0xFFEE


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.

==================================================================================

Case study 2. Shell code example

SDK Wi-Fi example test – Running Shell Code on AN7002Q-DB-5340:
Scenario:
An error occurs while running Shell code on AN7002Q-DB-5340.

Solution:
The AN7002Q-DB-5340 is paired with nRF5340 DK for development,
but neither of the 2 boards has an external MX25R64 (Serial NOR Flash) component.
So far, only the nRF7002DK board is equipped with the MX25R64.

Therefore, while running the original Wi-Fi shell code, the program will enable SPI NOR.

When using AN7002Q-DB-5340, you should add CONFIG_SPI_NOR=n in the prj.conf file to disable SPI NOR, to turn off any configurations related to it.

After recompiling and flashing, the shell code function
( e.g., Wi-Fi scan/Wi-Fi connect/net ping ..) should work properly.

Edited by Sales Manager: Ms. Mandy Chao
Technical guidance provided by R&D Manager: Mr. MW Lee
Keyword: nRF7002 MAC address

Raytac Corporation 勁達國際電子股份有限公司 
Bluetooth & WiFi module maker based on Nordic nRF54, nRF53, nRF52, nRF7002 solution
BT5.4 &BT5.3 & BT5.2 & BT5.1 Qualified, FCC/IC/CE/Telec/KC/RCM/SRRC/NCC Pre-Certified.
Bluetooth Solution: nRF54, nRF5340, nRF52840, nRF52833, nRF52832, nRF52820, nRF52811, nRF52810, nRF52805, nRF51822
WiFi Solution: nRF7002
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208

Transition tips for program from MDBT50Q-RX (USB-A) to MDBT50Q-CX (USB-C)  with current NRF52840 project

發表於 由撰寫發表留言

Intro:

This is a guidance provided for those who is going to transit (or replicate) their project from Raytac MDBT50Q-RX (USB-A Dongle) to MDBT50Q-CX(USB-C Dongle).  In addition to the hardware spec change (Compact Size , LED, Button, Pin definition change) , the key firmware configuration should be made with changes to fit new USB-C Dongle MDBT50Q-CX.

RX-1                    CX-1

    MDBT50Q-RX                           MDBT50Q-CX

  

 Table of Contents:

1. Comparison chart: MDBT50Q-RX(USB-A) & MDBT50Q-CX(USB-C)

2. Firmware configuration

3. Create a merged hex file (2 in 1 or 4 in 1)

4. Firmware flashing process

1. Comparison chart: MDBT50Q-RX & MDBT50Q-CX

Comparison chart

2. Firmware configuration : MDBT50Q-RX → MDBT50Q-CX

Edit your current MDBT50Q-RX firmware with configuration change to align the PIN change to accommodate the hardware change.

Option 1. Using nRF5 SDK:

Make the definition set up of LED, BUTTON pin in the highlighted 4 sections.

Firmware configuration-nRF5


Option 2. Using NCS V2.6.X:

Use the board name: nrf52840dongle_nrf52840 and add the overlay file:

nrf52840dongle_nrf52840.overlay to the program (Devicetree Overlays)，

then configure the below code definition into the overlay file:

/ {
   leds {
             compatible = “gpio-leds";
             led0_green: led_0 {
                      gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
                      label = “Green LED 0″;
             };
             led1_red: led_1 {
                     gpios = <&gpio0 8 GPIO_ACTIVE_LOW>;
                     label = “Red LED 1″;
             };
};

  buttons {
  compatible = “gpio-keys";
  button0: button_0 {
                  gpios = <&gpio1 6(GPIO_PULL_UP | GPIO_ACTIVE_LOW)>;
                  label = “Push button switch 0″;
                                   };
};
};

Firmware configuration-NCS

3. Create a merged hex file (2-in-1 or 4-in-1 hex file)


3A. Bootloader public key product

nrfutil keys generate public_key.pem → for zipping new firmware

nrfutil keys display –key pk –format code public_key.pem –out_file public_key.c

→ include public key to compile bootloader hex file

3A-1

3A-2


3B. Examples Demo

nRF5 SDK: nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_uart\pca10056\s140

NCS V2.6.X: ncs\v2.6.0\nrf\samples\bluetooth\peripheral_uart


3C. How to generate bootloader setting file (if you need bootloader):

nrfutil.exe settings generate –family NRF52840 –application nrf52840_xxaa.hex –application-version 255 –bootloader-version 2 –bl-settings-version 1 bootloader_settings.hex


3D. Merge and create a 2-in-1 or 4-in-1 hex file

a). Merge 2-in-1 (no Bootloader file required):

mergehex.exe -m s140_nrf52_7.2.0_softdevice.hex nrf52840_xxaa.hex -o merge.hex

3D-a


b). Merge 4-in-1 (with Bootloader file & Bootloader settings file required):

mergehex.exe -m bootloader.hex bootloader_settings.hex  s140_nrf52_7.2.0_softdevice.hex nrf52840_xxaa.hex -o merge.hex

3D-b

4. Firmware flashing process

MDBT50Q-RX(USB-A)：Manual wiring is required to have the firmware uploaded.

Please refer to the article: Firmware Coding & DFU onto MDBT50Q-RX

MDBT50Q-CX(USB-C)：Built-in open bootloader included for simple DFU process..

Please refer to the article: User Manual of MDBT50Q-CX (nRF52840/nRF52833-based USB-C Dongle)


Edited by Sales Manager: Ms. Jocelyn Tsai
Technical guidance provided by Firmware Deputy Manager: Mr. Stanley Huang

Raytac Corporation 勁達國際電子股份有限公司
Bluetooth & WiFi & LoRa module maker based on Nordic nRF54, nRF53, nRF52, nRF7002 solution
BT5.4 &BT5.3 & BT5.2 & BT5.1 Qualified, FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC Pre-Certified.
Bluetooth Solution: nRF54, nRF5340, nRF52840, nRF52833, nRF52832, nRF52820, nRF52811, nRF52810, nRF52805, nRF51822
WiFi Solution: nRF7002
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208

User Manual of MDBT50Q-CX (nRF52840/nRF52833-based USB-C Dongle)

發表於 由撰寫1 則迴響

MDBT50Q-CX is an advanced version of Raytac’s MDBT50Q-RX(USB-A Dongle).

MDBT50Q-CX has a more compact size, equips an up-to-date Type C USB Connector, and it has a built-in open bootloader for simple DFU process.

If you’ve been developing projects using MDBT50Q-RX in the past, you can find out in this manual how MDBT50Q-CX makes firmware compiling and loading much easier than before.

If you want to load firmware into MDBT50Q-CX, no wiring is needed. 

Simply plug the dongle into your device and USB DFU will be available.

MDBT50Q-CX (USB-C Dongle, nRF52840/nRF52833 solution): Product link

Size: 15.10 x32.85mm (0.59×1.29inches)

Table of Contents

A. Hardware intro

B. Software development environment setup

C. Firmware Implementation with NCS (nRF Connect SDK) or NRF5 SDK

D. Execute DFU (Device Firmware Update)

A. Hardware Intro

 <Pin Allocation>

2

< Schematic> (Click on the image to redirect to product page for Higher resolution photo)

Schematic Spec_MDBT50Q-CX_-240806

B.  Software development environment setup

Option 1. Compile in NCS(nRF Connect SDK)

(1) Install nRF Connect for Desktop:

B1

(2) Install Toolchain Manager and Programmer

B2

(3) Install nRF Connect SDK (NCS) → V2.6.0 is recommended.

B3

Option2. Compile in nRF5 SDK

(1) Download open source nRF5 SDK (Recommend: download the latest version:  17.1.0)

B4

(2) Install Segger Embedded Studio v5.42a (Recommended version)

https://www.segger.com/downloads/embedded-studio/

B5

※Welcome to contact Raytac sales team for v5.42a file of Segger Embedded Studio.

C. Implement firmware in NCS (nRF Connect SDK) or NRF5 SDK

We will use the two example codes below for this demo:

C1. NCS (nRF Connect SDK):

Example code path: \v2.6.0\nrf\samples\bluetooth\peripheral_uart

C2. nRF5 SDK:

Example code path: \nRF5_SDK_17.1.0_ddde560\examples\peripheral\usbd_ble_uart

C1. NCS (nRF Connect SDK): (Using nRF Connect SDK V2.6.0)

Step C1-1. Add build configuration to Board name: nrf52840dongle_nrf52840

C1

Step C1-2. Disable DCDC & DCDCHV by adding the below code into  prj.conf  file

CONFIG_BOARD_ENABLE_DCDC=n

CONFIG_BOARD_ENABLE_DCDC_HV=n

C2

Step C1-3. Fix the VDD power to 3.0V or 3.3V in board.c  file

The default power is 3.0V if you use board name: nrf52840dongle_nrf52840.

In this case, you don’t need to alter the power.

C3

Step C1-4. Click the rebuild icon to reconfigure the program.

C4

Step C1-5. The program will be saved automatically in the path below:

C:\ncs\v2.6.0\nrf\samples\bluetooth\peripheral_uart\build\zephyr\zephyr.hex

C2. nRF5 SDK:

Step C2-1. Open the program under:

\nRF5_SDK_17.1.0_ddde560\examples\peripheral\usbd_ble_uart\pca10056\s140\ses\ usbd_ble_uart_pca10056_s140.emProject

Step C2-2.  Fix the VDD power supply to 3.0V or 3.3V.

C2-1

Step C2-3. Start editing the project by opening the solution in Editor.

C2-2

Change the board name from PCA10056(nRF52840-DK) to PCA10059(nRF52840 dongle).

Save and re-compile the program after the amendment.

C2-3

Click the program file name and save the modified project.

C2-4

Press “Yes” to re-load the new set up value into configuration.

C2-5

The default code in sdk_config.h is: NRF_LOG_BACKEND_UART_ENABLED 1 (in red frame);

Please change 1 to 0 to make the LED light work.

Stanley修改內容_20240806

Press “Rebuild Solution” to make sure all the parameters you’ve modified are reconfigured.

C2-6

Step C2-4. The program will be saved automatically under the path below:

V:\nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral\ble_app_uart\pca10056\s140\ses\Output\Release\Exe\ble_app_uart_pca10056_s140.hex

D. Execute DFU (Device Firmware Update)

Reminder: 

No extra bootloader can be programmed into MDBT50Q-CX until you manually wire the pins on the PCB and erase the built-in bootloader.  You can simply operate DFU using MDBT50Q-CX’s bootloader.

Step D1. How to enable DFU?

(1) Press the button on MDBT50Q-CX

(2) Plug MDBT50Q-CX into your device while pressing the button

(3) Press and wait for approx.1 second until the LED light turns on. → DFU is activated.

(4) Release the button

※When Bootloader mode is enabled, the LED light on MDBT50Q-CX will twinkle continuously. 

D1

Step D2. Open the built-in DFU Bootloader

nRF Connect Desktop →  Programmer  → SELECT DEVICE  → Open DFU Bootloader

D2

You have successfully entered bootloader mode after you see the screen as below.

D3

Step D3. Add ready firmware file into the Programmer

(The program completed and saved during Step C1-5(NCS) or Step C2-4(nRF5 SDK))

※If you’re using nRF5 SDK, you need to add the soft device file into your program for loading firmware.

※Soft device path:

nRF5_SDK_17.1.0_ddde560\components\softdevice\s140\hex\s140_nrf52_7.2.0_softdevice.hex

D4

Step D4. Load the firmware and write it into the MDBT50Q-CX

D5

Step D5. Process FW DFU

D6

Step D6.  DFU Completed. The appointed firmware is successfully loaded into MDBT50Q-CX.

D7

※Any failure during the DFU process will leave you under bootloader mode.

Last-failure

If this happens, simply restart the firmware writing process from Step D4 to reload your firmware into MDBT50Q-CX.

 

Edited by Sales Manager: Ms. Jocelyn Tsai
Technical guidance provided by Firmware Deputy Manager: Mr. Stanley Huang

Raytac Corporation 勁達國際電子股份有限公司
Bluetooth & WiFi & LoRa module maker based on Nordic nRF54, nRF53, nRF52, nRF7002 solution
BT5.4 &BT5.3 & BT5.2 & BT5.1 Qualified, FCC/IC/CE/Telec/KC/RCM/SRRC/NCC/WPC Pre-Certified.
Bluetooth Solution: nRF54, nRF5340, nRF52840, nRF52833, nRF52832, nRF52820, nRF52811, nRF52810, nRF52805, nRF51822
WiFi Solution: nRF7002
http://www.raytac.com
email: sales@raytac.com
Tel: +886-2-3234-0208