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
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! 😊
Raytac Corporation 