[08/14/2025, California, USA] To better support our customers in the United States, Raytac Corporation(USA) now offers inland domestic shipping and a local support team based in California.
By bringing our services closer to U.S. clients, we can provide faster assistance for ongoing projects, significantly shorten lead times, and maintain the high quality and global compliance standards Raytac is known for.
Hi readers, did you know that Raytac offers a special service exclusively for our customers? 😉 We offer support services: HEX file verification and flashing firmware into modules per customer’s requests. Compared to the series nRF52 and nRF53’s 2 in 1 or 3 in 1 merged hex files, nRF54L15 requires something slightly different. Following are the tips and suggestions.
Find System Build (sysbuild) ➝ Choose Build System Default
Click Generate and Build
Starting from NCS v2.8.0 (including later versions), the .hex file can be generated in two different paths. 1. ..\nrf\samples\bluetooth\application-name\build\merged.hex 2. ..\nrf\samples\bluetooth\application-name\build\application-name\zephyr\zephyr.hex
Using the AN54LQ/AN54LV series as an example: When you provide the programming file (.hex) for production, please ensure that the file is taken from the following path: 1. ..\nrf\samples\bluetooth\application-name\build\merged.hex And we also do not recommend renaming the merged HEX file due to Nordic suggestions.
Not recommended path: 2. ..\nrf\samples\bluetooth\application-name\build\application-name\zephyr\zephyr.hex The zephyr.hex file is not recommended to be used for flashing or verification in the production process.
Thank you all for your patience in reading! Best wishes for your projects – your success is Raytac’s success! 😊
AN54LQ-X05 Series (nRF54L05, red PCB): Product page
Just like traffic lights that direct every journey safely and efficiently, Raytac’s nRF54L series modules guide your wireless development—keeping you on the right path with cutting-edge performance and exceptional power savings.
🚦 Each light signals a different member of the nRF54L15 / nRF54L10 / nRF54L05 module family—showcasing a clear path for your Bluetooth Low Energy (LE) applications, no matter which industry you’re from and where you’re headed.
These modules are now available for your design-in, offering: ✅ Powerful performance ✅ Ultra-low power consumption ✅ Compact footprints ✅ Full Global certifications: FCC/IC/CE/UKCA/Telec/KC/NCC/SRRC/RCM/WPC ✅ BT 6.0 certified ✅ Full Nordic nRF54 Series compatibility ✅ Pin-to-pin compatible amongst AN54LQ series
Whether you’re building for consumer IoT, industrial sensors, healthcare, or wearables—Raytac’s modules deliver the reliability you need and the efficiency you expect.
Before building Application code , some amendments need to be made regarding DFU-related settings and code inside Application:
Step 1.
1A. 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)
1B. Add “include path” in C/C++
1C. Add the .c files inside red frame in (Screenshots 1 & 2) and the 2 groups of (nRF_DFU & nRF_SVC)(Screenshot 3) under Project(Screenshot 4)
1D. 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)
1E. The code of file: sdk_config.h (..\examples\ble_peripheral\ble_app_uart\pca10056\s140\config\ sdk_config.h) inside Application needs to be modified.
1F. Adjust the IRAM1 value in Target after implementing DFU service: Check on the IRAM1 Value of *p_app_ram_start to be modified from default: 0x20002AE8 0x3D518 to 0x20002AF8 0x3D508, as shown in the red frame in the bottom right corner. In this case, the program should run successfully.
1G: Create a file of:nrf52840_xxaa.hex after building application code files.
Step 2. Create a bootloader setting file of nrf52840_bootloader_secure_settings.hex :(via DOS)
Raytac Corporation, a Nordic-recommended third-party module manufacturer based in Taiwan, today announces the upcoming release of the AN54H20 modules, which are built on the base of Nordic’s nRF54H20 SoC.
The AN54H20 module comes in a 9.8 x 13.8 x 1.8mm (0.37 by 0.53 by 0.07 inches) dimension factor and offers 3 versions of high-performance antennas, including ceramic chip antenna, PCB-mounted antenna, and uFL connector for external antenna. Output power is adjustable up to +10 dBm and data rate is adjustable up to 4Mbps to maximize RF performance.
Powered by multiple processors, AN54H20 modules provide the IoT field with access to a whole set of improved features, including 2MB flash memory/1MB RAM and bigger processing power for more complicated computations. It also enhances protection against security threats, providing developers with protection while building technologically advanced IoT applications.
Hardware wise, AN54H20 inherits nRF54H20’s set of versatile, advanced, and low-power peripherals alongside DMA support, including high-speed USB, CAN-FD controller, 14-bit ADC, 2 x I3C and plenty more. What’s more revolutionary is that AN54H20 brings power efficiency to a whole new level through accurately controlling currency consumptions under various modes, allowing smaller batteries to be implemented in the applications while increasing its life expectancy.
“We see the AN54H20 series as a potential market changer. The compact size gives developers a seamless switch from the previous generation modules to AN54H20, and the remarkable power efficiency and characteristics AN54H20 brings will offer a magnificent effect to the inescapable hot trend of IoT and other various industries." – Lyon Liu, President of Raytac Corporation.
Raytac Corporation 