Essential Tips for nRF54L15 HEX File Verification

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.

Before building your own .hex file on Raytac's nRF54L15 modules(Product link), please configure some settings(shown below) in advance.

In VS Code:

1. Go to Add Build Configuration
2. Find System Build (sysbuild) ➝ Choose Build System Default
3. 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.

For more details behind this suggestion, please refer to the Nordic DevZone link below.
https://devzone.nordicsemi.com/f/nordic-q-a/120313/how-to-modify-the-name-of-the-merged-hex-file

Suggested path:
1. ..\nrf\samples\bluetooth\application-name\build\merged.hex

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


For more information, please contact:
Raytac Contact Form: https://www.raytac.com/contact/
Raytac Sales email: sales@raytac.com
abietec Service email: service@abietec.com

Edited by Account Manager: Ms. Elfreda Guo


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


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/RoHS/Reach Pre-Certified.
http://www.raytac.com
https://www.raytac.com/contact/
email: sales@raytac.com
Tel: +886-2-3234-0208(TW)/+1-626-217-3139(USA)

Bluetooth Project: How to program your firmware to module

After setup been done, here comes the next question: How to program the firmware in to the module. We are using some simple instruction in below for reader's quick reference.

Hardware

You will need a Nordic nRF5X DK or a Segger J-link as programmer to load the firmware. To use Nordic nRF5X DK to debug the SoC as well, you will need to order corresponding nRF5X DK to match the SoC number. For example, order nRF52840 DK to debug nRF52840 SoC or order nRF52 DK to debug nRF52832/52810 SoC. But if you are only using it as programmer, any version of nRF5X DK will work as we only use the J-link on this board.

Software

Please download Nordic nRFGo Studio or Nordic nRF Connect for Desktop for programming. Remember to install nRF5X Command Line Tools if the board was not detected by nRFGo Studio. Once they are all connected, you can then start programming. Please make sure to “erase all” every time before programming.


For more tutorials and demo of sample code, please visit Nordic’s DevZone and Infocenter where have ample resources to utilize. 

Programing 

Case A. SoftDevice + Application

1. If Softdevice and Application code separately
Erase all first. Then program Softdevice and follow by Application code.
   

2. If Softdevice and Application combined code is available (Recommend)

Erase all first. Then program the combined code

   

 **Raytac module comes with testing code programmed. Please erase the testing code as the first step and then start the programming.

Case B. SoftDevice + Bootloader+ Application

1. Softdevice+Bootloader 

Erase all first. Program the Softdevice and follow by Bootloader. Then use DFU to update the application code.

2. Softdevice+Application+Bootloader combined code is available (Recommend)

Erase all First and follow by programming the combined code.

 **Raytac module comes with testing code programmed. Please erase the testing code as the first step and then start the programming.

*Remark
Bootloader is needed for DFU (OTA) Function.
SDK 11 (included) and before - a legacy DFU method, which is simple but less security
SDK 12 (Included) and after - a latest DFU method, which has higher security.

To easy customer's IoT device mass production, Raytac provide code pre-program service into module before shipment.  There are requirements listed in below for customers who need the service!

1. A single, combined hex file is required. Please combine softdevice and application or/and bootloader (depending on your firmware design) together before programming. This will shorten programming time and help to manage your code easier.
2. Need a simple method to check programming status. The easiest way is to check the device name if device will broadcast device name after programming is done; or use I/O to trigger LED and its behavior. This does not aim to test any or full function of your device, only a simple method for the operator to know programming status.

Raytac Corporation 勁達國際電子有限公司

A BT5 & BT 4.2 & BTv4.1 module maker based on Nordic nRF51 & nRF52 solution 

(nRF51822 & nRF51422 & nRF52832 & nRF52810 & nRF52840)

www.raytac.com          email: cs@raytac.com          Tel: +886.2.3234.0208