Raytac and onceLabs Deepen Collaboration with Live Demo of Mobile‑to‑Embedded Bluetooth Channel Sounding

 A LinkedIn debut becomes a live showcase at Embedded World North America with Raytac’s Bluetooth LE module solution and Google Pixel 10.

[Anaheim, CA — November 2, 2025]
At embedded world North America — Raytac Corporation, a global leader in wireless modules, together with onceLabs, a U.S.-based global Nordic Design Partner specializing in custom embedded and mobile application software, will present a live demo of Bluetooth Channel Sounding. The demonstration showcases the accuracy and potential of the new Bluetooth 6.0 feature by combining Raytac’s Nordic-based nRF54L15 (AN54LQ-15) module with a Google Pixel 10 smartphone.

Bluetooth Channel Sounding adds a new dimension to wireless connectivity by combining secure data transfer with the low‑power, low‑cost Bluetooth technology already trusted worldwide — now extended to deliver precise location awareness. This evolution means IoT devices can gain both communication and ranging capabilities in a single, efficient platform. With tens of centimeter distance accuracy, Channel Sounding enables practical new use cases such as secure access, proximity‑based services, indoor navigation, and ‘Find My’ functionality.

Android 16 now supports Channel Sounding APIs, making it possible for developers to access this capability directly on flagship devices like the Pixel 10. With anticipated pervasive adoption across the mobile ecosystem, Channel Sounding is positioned to scale broadly and become a standard feature for IoT applications.

The onceLabs demo was reported as the first of its kind in August, gaining notability on LinkedIn(Post link) — and is now being shown for the first time in a public venue. onceLabs’ free BLE Hero app(Download Link) is a sniffer, analyzer, and development tool, available in app stores, and can be seen in action during the live demo. The Android version has been updated to capture and display Channel Sounding data, giving developers clear insight into ranging accuracy and system performance. Since 2018, Raytac and onceLabs have collaborated to bring new Bluetooth capabilities from specification to market‑ready solutions. Raytac’s proven hardware platforms and onceLabs’ application‑layer software expertise combine to accelerate adoption of emerging standards, showing how partnership can translate advanced technology into product‑ready functionality.

QR code on the left: watch the Channel Sounding Live Demo;
QR code on the right: download the BLE Hero app on Google Play.

“Our collaboration with onceLabs has always been about enabling customers to move quickly and confidently with the latest Bluetooth technology,” said Lyon Liu, CEO of Raytac Corporation. “This live demo of Channel Sounding is another example of how our partnership delivers not just modules, but complete solutions that inspire new applications.”

Together, Raytac and onceLabs are demonstrating how Bluetooth Channel Sounding can move from specification to practical demonstrations that product companies can act on.

“With Raytac providing the hardware foundation and onceLabs delivering the application software, we continue to support customers in translating new Bluetooth features into real use cases,” said Joseph Bakalor, President and CTO of onceLabs. “Channel Sounding is a perfect example — and with our expertise in Zephyr RTOS, developers can build on open, production‑ready software that scales from prototype to deployment.”

The Raytac + onceLabs demo will be featured in Raytac Booth 5067 at embedded world North America, November 4–6, 2025, at the Anaheim Convention Center. Attendees are invited to visit the booth to see the demo in action and learn how Raytac and onceLabs can support their next wireless product.

Raytac Product Change Notice(PCN) Announcement for Nordic SoC USB-A Dongle – MDBT50Q-RX Series

 Raytac Corporation would like to inform all customers and partners of an official Product Change Notice: PCN-25100801 regarding the following product series:

Affected Series
MDBT50Q-RX Series (nRF52840/833 based USB-A dongles)

Affected Models
MDBT50Q-RX (Product Link)
MDBT50Q-RX-33
MDBT50Q-RX-ATM (Product Link)
MDBT50Q-RX-ATMS

Reminder
This PCN involves:

1. Update of Raytac’s company logo on the nameplate, and
2. Addition of NCC logo on the back label.

There are no changes to product function, performance, quality, form factor, or safety compliances. All existing certifications and technical documentations remain valid.

We kindly invite our customers, distributors, and partners to update your records accordingly. For any questions or support regarding this update, feel free to reach out via: service@raytac.com.

Full details of the PCN please see below(Click on the images to zoom in).
Remark: Please take note of the final shipment date.

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 and 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 and merging built files

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.

---

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

Recently we have received the FAQ: how to write MAC address into the OTP memory of AN7002Q-P 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 isn’t loaded with a 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 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 MAC addresses(for both 2.4GHz & 5GHz) to every AN7002Q module.

*If customers don't have 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.