DW3_QM33_SDK_1.0.2 build, what build image to flash and how

Wireless Connectivity Ultra-Wideband
1

I am extending the firmware, using the Murata Type2AB .. I have the build,
it has hex, bin, elf outputs (building on linux)

I don’t have a JFLASH provided adapter, just a mini, just a single guy.
the VS menu wants to load elf. my license doesn’t support elf.

I want to load hex, the sdk supplied hex (in binaries) works
my VS built hex does not. (it is bigger than provided, as expected)
I can use JFlashLite (Which supports hex, but not elf)
My new code entry is commented out, light on 2ab doesn’t come on after flash of hex file

anyone have any suggestions how I can move forward?

end of build output

[ 99%] Building C object CMakeFiles/Type2AB_EVB-DW3_QM33_SDK_UCI-FreeRTOS.elf.dir/home/sam/Downloads/DW3_QM33_SDK_1.0.2/SDK/Firmware/Projects/DW3_QM33_SDK/FreeRTOS/DW3_QM33_SDK-FreeRTOS-Common/main_uci.c.obj
[100%] Building C object CMakeFiles/Type2AB_EVB-DW3_QM33_SDK_UCI-FreeRTOS.elf.dir/home/sam/Downloads/DW3_QM33_SDK_1.0.2/SDK/Firmware/Projects/DW3_QM33_SDK/FreeRTOS/DW3_QM33_SDK-FreeRTOS-Common/hooks.c.obj
[100%] Linking C executable Type2AB_EVB-DW3_QM33_SDK_UCI-FreeRTOS.elf
Memory region         Used Size  Region Size  %age Used
             RAM:      124496 B       256 KB     47.49%
           FLASH:      457600 B      1016 KB     43.98%
       CALIB_SHA:          32 B         4 KB      0.78%
           CALIB:          4 KB         4 KB    100.00%
[100%] Built target Type2AB_EVB-DW3_QM33_SDK_UCI-FreeRTOS.elf

file manager view of buildoutput

Screenshot at 2025-06-17 09-24-35
Screenshot at 2025-06-17 09-24-35856×117 24.8 KB

2

as a test i used the objcopy command , but it produced the same hex as already present out from the build (cmp says the files match)

3

I am adding BLE thru SoftDevice.. if that makes any difference.

this is the base of the adjusted ld linker file

MEMORY
{
/* SoftDevice requires about 152K of flash (0x26000) and 8K (0x2000) of RAM */
RAM (rwx)      : ORIGIN = 0x20002000, LENGTH = 256K - 8K  /* Reserve 8K for SoftDevice */
FLASH (rx)     : ORIGIN = 0x00026000, LENGTH = 1M - 152K - 4K - 4K /* 1M minus SoftDevice (152K) and calib_sha/calib sections (8K). */
CALIB_SHA (rw) : ORIGIN = 0x000FE000, LENGTH = 4K
CALIB (rw)    : ORIGIN = 0x000FF000, LENGTH = 4K
}

SECTIONS
{
  /* start with interrupt vectors - place at app start address (after SoftDevice) */
    .isr_vectors (ORIGIN(FLASH)) :
    {
4

I installed the NRF connect sdk which has a programmer graphical interface

the prebuilt binary
after loading

Screenshot at 2025-06-18 08-51-07
Screenshot at 2025-06-18 08-51-071576×906 59.7 KB

and my new firmware

Screenshot at 2025-06-18 08-57-29
Screenshot at 2025-06-18 08-57-291576×906 74.5 KB

so, something is different

5

if I comment out (ifdef) calling my new code, but it is in the build, and I have the image layed out simiar to the QNI image that also uses softdevice. my image does not boot up.

I have no prior experience on this hardware stack. I’ve got ESP and Arduino.
but I don’t know the side effects on loading Softdevice in addition to the existing USB support

no one from Nordic will help as this is the old SDK

hoping someone here can give me some hints to follow the yellow brick road..