undefined reference to `__device_dts_ord_88'

[Will_20241202]

Trying to migrate from SDK v2.7.0 to v2.8.0 and suddenly getting the build error 

undefined reference to `__device_dts_ord_88'

Based on other forum posts, I was able to track down more information using the <build target>\<project>\zephyr\include\generated\zephyr\devicetree_generated.h file which lists:

 *   88  /soc/radio@40001000/bt_hci_sdc

Reading around it looks like I need to add something along the lines of 

&bt_hci_sdc {
    status = "okay";
};

to the Device Tree, but I am struggling to figure out where, which file, and the exact syntax.  So far nothing I've cobbled together based on online searching has worked.  For completeness, my environment is:

• Windows 11
• VS Code w/ nRF Connect plugin
• toolchain / SDK v2.8.0
• custom PCB using an nRF52832 in the QFAA package
• sysbuild
• MCUBOOT

[Amanda Hsieh]

Hi, 

See 

https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs1/dts/arm/nordic/nrf52832.dtsi#L10

https://github.com/nrfconnect/sdk-zephyr/blob/v3.7.99-ncs1/dts/arm/nordic/nrf52832.dtsi#L104-L107 

Regards,
Amanda H.

[Will_20241202]

I'm still not clear on what is necessary and what isn't based on that file.  To simplify, I used the nRF Connect plugin to "Create a new board" and the files it generates do not look anything like the above.  The .dts file is just 

/dts-v1/;
#include <nordic/nrf52832_qfaa.dtsi>
#include "fake_board-pinctrl.dtsi"

/ {
	model = "Custom Board auto generated by nRF Connect for VS Code";
	compatible = "generic,fake-board";

	chosen {
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
		zephyr,code-partition = &slot0_partition;
	};
};

&flash0 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 DT_SIZE_K(48)>;
		};

		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000c000 DT_SIZE_K(220)>;
		};

		slot1_partition: partition@43000 {
			label = "image-1";
			reg = <0x00043000 DT_SIZE_K(220)>;
		};

		storage_partition: partition@7a000 {
			label = "storage";
			reg = <0x0007a000 DT_SIZE_K(24)>;
		};
	};
};

and the .dtsi file is just 

&pinctrl {
};

Neither have an "soc" section or anything even remotely similar.  Do I need to make one myself?  If yes, what is the bare minimum so I'm not enabling things I don't want/need (code size and power savings are CRITICAL in my project)?

This is one (of many) cases where the theory all make sense, but when it comes to putting it into practice everything is clear as mud.

[Amanda Hsieh]

You can upload via the toolbar -> Insert -> Image/video/file -> Upload

[Will_20241202]

When I try to use that tool it says "URL protocol is not allowed: D:/Projects/NordicExp/MyProject.zip"

I tried change the file extension to BMP, JPG, PNG, etc. and the error message doesn't change.

I originally tried using Windows style path with back slashes and it errors with "Invalid URL: D:\Projects\NordicExp\MyProject.zip"

[Amanda Hsieh]

You can upload with .7z

[Will_20241202]

I still get an error "URL protocol is not allowed: D:/Projects/NordicExp/MyProject.7z" when trying to upload.

[Amanda Hsieh]

Then, I would suggest you use that peripheral sample as the base for your application since you said you can build it without issue. 

Will_20241202 said:

I was able to build the 5734.peripheral.7z using VS Code without issue.