I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Fri, 13 Feb 2026 14:34:50 GMT

thanks. lots of code later I have it working...

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

Susheel Nuguru — Fri, 08 Nov 2024 07:57:31 GMT

For the sdh_stack errors, you can refer to this thread to see how to fix those errors.

The errors with nrf_section_iter_init and nrf_section_iter_next are usually due to issues with section variables in the nRF5 SDK. Here’s a simpler breakdown of what might be happening and how to fix it:

The file nrf_section_iter.c might not be added to your project. This file includes the code for these functions and is typically found in the SDK under components/libraries/experimental_section_vars/. Adding it to your build may resolve the problem.

Make sure that NRF_SECTION_ITER_ENABLED is set to 1 in your sdk_config.h file. This turns on the section iterator module, which includes the needed functions

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 07 Nov 2024 23:03:42 GMT

ok, almost there

I am adding stuff from another project that uses softdevice for ble.

build works, but link fails

```text

Linking 'DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS.elf'

"/Applications/SEGGER/SEGGER Embedded Studio 8.14a/gcc/arm-none-eabi/bin/ld" -X --omagic -eReset_Handler -EL --gc-sections "-T/Users/sam/Downloads/DWM3001CDK DK Software, Sources, Tools and Developer Guide 3/DWM3001CDK DK/DWM3001CDK_SDK/Sources/DWM3001CDK-DW3_QM33_SDK-FreeRTOS_0_1_1/DWM3001CDK-DW3_QM33_SDK-FreeRTOS/Projects/DW3_QM33_SDK/FreeRTOS/DWM3001CDK/ses/Output/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS Common/Obj/$(FolderName)/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS.ld" -Map "/Users/sam/Downloads/DWM3001CDK DK Software, Sources, Tools and Developer Guide 3/DWM3001CDK DK/DWM3001CDK_SDK/Sources/DWM3001CDK-DW3_QM33_SDK-FreeRTOS_0_1_1/DWM3001CDK-DW3_QM33_SDK-FreeRTOS/Projects/DW3_QM33_SDK/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS.map" -u_vectors -o "/Users/sam/Downloads/DWM3001CDK DK Software, Sources, Tools and Developer Guide 3/DWM3001CDK DK/DWM3001CDK_SDK/Sources/DWM3001CDK-DW3_QM33_SDK-FreeRTOS_0_1_1/DWM3001CDK-DW3_QM33_SDK-FreeRTOS/Projects/DW3_QM33_SDK/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS.elf" --emit-relocs --start-group "@/Users/sam/Downloads/DWM3001CDK DK Software, Sources, Tools and Developer Guide 3/DWM3001CDK DK/DWM3001CDK_SDK/Sources/DWM3001CDK-DW3_QM33_SDK-FreeRTOS_0_1_1/DWM3001CDK-DW3_QM33_SDK-FreeRTOS/Projects/DW3_QM33_SDK/FreeRTOS/DWM3001CDK/ses/Output/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS Common/Obj/$(FolderName)/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS_files.ind" --end-group --whole-archive ../../../../../Libs/niq/libniq-m4-hfp-1.1.0.0.a ../../../../../Libs/dwt_uwb_driver/lib/libdwt_uwb_driver-m4-hfp-6.0.14.a ../../../../../Libs/uwbstack/uwbstack_lib/lib/cmsis_v1/uci/uci_backend/libuci_backend_coordinator_arm-m4-hfp_R11.9.2.a ../../../../../Libs/uwbstack/uwbstack_lib/lib/cmsis_v1/uci/uci_backend/libuci_backend_arm-m4-hfp_R11.9.2.a ../../../../../Libs/uwbstack/uwbstack_lib/lib/cmsis_v1/uci/uci_core/libuci_core_arm-m4-hfp_R11.9.2.a ../../../../../Libs/uwbstack/uwbstack_lib/lib/cmsis_v1/embedded_mac/libembedded_mac_arm-m4-hfp_R11.9.2.a --no-whole-archive

Output/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS Common/Obj/common/nrf_sdh.o: in function `nrf_sdh_evts_poll':

(.text.SWI2_EGU2_IRQHandler+0x8): undefined reference to `nrf_section_iter_init'

(.text.SWI2_EGU2_IRQHandler+0x18): undefined reference to `nrf_section_iter_next'

Output/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS Common/Obj/common/nrf_sdh.o:(.rodata.sdh_stack_observers+0x0): undefined reference to `__start_sdh_stack_observers'

Output/DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS Common/Obj/common/nrf_sdh.o:(.rodata.sdh_stack_observers+0x4): undefined reference to `__stop_sdh_stack_observers'

Build failed, exit status 0x1

```

looking for nrf_section_iter_init, __start_sdh_stack_observers, __stop_sdh_stack_observers

all referenced from nrf_sdh.c

softdevice

I don't see the LINK source for those, and I think they should be added in the mergehex step that adds the softdevice binary to the firmware binary

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 07 Nov 2024 20:58:05 GMT

well it turns out that the compiler include path list has to have all those directories included explicitly.

still digging thru the errors to find the missing pieces

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Wed, 06 Nov 2024 22:06:26 GMT

so I have the projects building as distributed. I want to add BLE to one.

I have checked and changed the sdk_config.h in the target project

the embedded sdk file tree has the files (c and h) , but the project in Segger doesn't show them,

I can copy from one project to another, and the C files are processed, but the h files are not found.

another different sdk/IDE config I expect

update:

errors here are cauced by the include files not in the preprocessor include list...

still can't see .h in segger but it doesn't impact build if u have the right paths setup

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Wed, 06 Nov 2024 19:53:57 GMT

turns out this was a path problem.. inside segger there was no path to mergehex, adding the full path solve that..

removing the SDK_BSP folder from the project and using full links to the sdk instead of relative (../../....) builds using the direct package sdk. altho link fails, I think because link is still using the relative path(haven't fond that one in config yet) , and maybe the sdk_config.h not being correct

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Wed, 06 Nov 2024 07:34:40 GMT

Issue seems to be related to the mergehex operation so downgrading might be a good way to debug here. Could you try to not merge the files.

Regards,
Jonathan

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Tue, 05 Nov 2024 18:21:23 GMT

Ok, so I put the sdk somewhere else and changed the paths in the segger IDE to point to that source
compile works ok on the two kits..
one kit uses mergehex, as a postbuild step which is failing, rc -1
if I run it manually outside segger build it works ok

I am running
```

mergehex -v

mergehex version: 10.24.2

```

on macos.. some suggest downgrading to 9.8.0 ,

but it works taking the preprocessor expanded filenames that are shown in the error

```

mergehex -m /Users/sam/Downloads/Qorvo_Nearby_Interaction_3_2_0/Software/Accessory/Sources/QANI-All-FreeRTOS_QNI_3_0_0/Projects/Projects/QANI/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-QANI-FreeRTOS.hex /Users/sam/Downloads/nRF5_SDK_17.1.0_ddde560/components/softdevice/s113/hex/s113_nrf52_7.2.0_softdevice.hex -o /Users/sam/Downloads/Qorvo_Nearby_Interaction_3_2_0/Software/Accessory/Sources/QANI-All-FreeRTOS_QNI_3_0_0/Projects/Projects/QANI/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-QANI-FreeRTOS_full.hex

```

the target file and permissions(from the manual execution of mergehex)

-rw-r--r-- 1 sam staff 1267521 Nov 5 12:06 /Users/sam/Downloads/Qorvo_Nearby_Interaction_3_2_0/Software/Accessory/Sources/QANI-All-FreeRTOS_QNI_3_0_0/Projects/Projects/QANI/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-QANI-FreeRTOS_full.hex

the mergehex fails, no output file is created

the two input files exist

Mac-mini:sam$ ls -laF /Users/sam/Downloads/Qorvo_Nearby_Interaction_3_2_0/Software/Accessory/Sources/QANI-All-FreeRTOS_QNI_3_0_0/Projects/Projects/QANI/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-QANI-FreeRTOS.hex

-rw-r--r-- 1 sam staff 956835 Nov 5 12:26 /Users/sam/Downloads/Qorvo_Nearby_Interaction_3_2_0/Software/Accessory/Sources/QANI-All-FreeRTOS_QNI_3_0_0/Projects/Projects/QANI/FreeRTOS/DWM3001CDK/ses/Output/Common/Exe/DWM3001CDK-QANI-FreeRTOS.hex

Mac-mini:sam$ ls -laF /Users/sam/Downloads/nRF5_SDK_17.1.0_ddde560/components/softdevice/s113/hex/s113_nrf52_7.2.0_softdevice.hex

-rw-rw-r--@ 1 sam staff 310854 Jul 31 2020 /Users/sam/Downloads/nRF5_SDK_17.1.0_ddde560/components/softdevice/s113/hex/s113_nrf52_7.2.0_softdevice.hex

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Thu, 31 Oct 2024 10:08:35 GMT

You can either reference to the SDK by having the SDK under the example\package from vendor, or you can add the entire SDK above or put the example in the SDK.

So it is possible to add the files that include the softdeivce to the project.

Regards,
Jonathan

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Sat, 26 Oct 2024 21:53:28 GMT

thanks.. one more question.. (maybe more!)
so the package I have from the vendor has the NRF sdk embedded.. but there are no sdk files for softdevice, ble, ... I don't know what happens with the sdk when you configure it, can you extract JUST taht set of files?

(image from above)

if I save their sdk_config.h

can I just plop the whole sdk back in the package?

i see sdk_config.h all over the place when I seach for it in the sdk tree..

which makes no sense to me..

and the java sdk config tool reading the sdk_config.h from their package doesn't seem to detect what is enabled.

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Fri, 25 Oct 2024 12:24:41 GMT

[quote user="rexxdad"]i don't understand Softdevice.[/quote]

The SoftDevice is a protocol stack, made by nordic. https://docs.nordicsemi.com/bundle/ug_gsg_ses/page/UG/gsg/softdevices.html
In the Zephyr based SDK you have the option to use nordic's solution or the Zephyr provided option.

In short you need it to get BLE.

Here is what we have as extra material, https://docs.nordicsemi.com/bundle/ug_gsg_keil/page/UG/gsg/related_docs.html

You will need to dig in to the documentation for specifics on the errors or warnings that you are getting. https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/index_1.html

And we also do have some guides : https://devzone.nordicsemi.com/guides/short-range-guides/ most might not be relevant.

Regards,
Jonathan

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Fri, 25 Oct 2024 11:21:15 GMT

thanks. but i want more info on what the settings in the config file mean, and what tasks a developer has to complete to make a particular configuration work.

i see critical sections and encryption functions.ii see linker errors which i think are sdk code, not implementor code. and i cant tell if i have incomplete settings or if the provider stripped the sdk files down to save space.

i don't understand Softdevice. it looks like i need competing versions to make my scenarios work

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Fri, 25 Oct 2024 07:54:50 GMT

Thanks for all the extra details.

So the best example I have to offer here is the FreeRTOS example with Hart Rate Monitor: https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/ble_sdk_app_hrs_freertos.html

It is probably the closes example that shows how BLE is implemented compared to what you want.

Regards,
Jonathan

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 24 Oct 2024 15:06:40 GMT

architectural drawing

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 24 Oct 2024 14:33:35 GMT

no... I want to add the BLE services to this build.. on the 840 peripheral(really server in pairing style to talk to my phone app) and central (to be UCI controller), and on the 833, peripheral only(to control UCI controllee)

I do NOT want to rewrite the UWB support..
I asked an earlier question here about migrating this to the new sdk under VS, and was told, No, we don't have that.

in the future (after I get this working with my app) I would do a pure BT implementation using
ble between phone and localdevice , and bt(master) with CS to BT(slaves) wi CS

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Thu, 24 Oct 2024 14:14:56 GMT

[quote user="rexxdad"]i am extending the qorvo uwb build which uses the 1.7.0 sdk.[/quote]

Image showes using nRF5 SDK v17.1.0 it seems.

Ref https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/index.html

So If I understand correctly you want to port the nRF5 SDK project to NCS SDK?

Regards,
Jonathan

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 24 Oct 2024 13:47:36 GMT

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

rexxdad — Thu, 24 Oct 2024 13:35:13 GMT

i am extending the qorvo uwb build which uses the 1.7.0 sdk. its supports the 833 and 840 already.

i will do similar with the nrf sdk for cs, but hardware not available yet

RE: I am trying to extend an older 1.7.0 SDK to add functional BT support, which currently only has serial port communications. i don't really understand the terms for the functional parts, and understand the sdk is replaced with new..

JONATHAN LL — Thu, 24 Oct 2024 13:26:41 GMT

Hi,

I would recommend that you look in to using NRF Connect SDK that is based on Zephyr as the building blocks for a project that you want to future proof as you are looking at Channel sounding and Bluetooth 6, and use NCS 2.7.0.

If I understood correctly,

You are working with a product that needs to get some new features, the current product and its SW is provided and that is what you want to modify ?

You should be able to get the programs to work with both the 840 and the 833.

But I am a bit unsure what SDK you are talking about if it is the nRF5 SDK or the NCS

BLE samples can be found here: https://docs.nordicsemi.com/bundle/ncs-2.7.99-cs2/page/nrf/samples/bl.html

Regards,
Jonathan