Missing zephyr.dts source/origin comments in NCS flavor of zephyr

Situation

When using vanilla zephyr I get a very verbose generated zephyr.dts file where every line is annotated with the line's origin like the following:

/dts-v1/;

/* node '/' defined in zephyr/dts/common/skeleton.dtsi:9 */
/ {
	model = "Company Product MCU Application";	/* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:7 */
	compatible = "companc,product-app";		/* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:8 */
	#address-cells = < 0x1 >;			/* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:10 */
	#size-cells = < 0x1 >;				/* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:11 */

	/* node '/chosen' defined in zephyr/dts/common/skeleton.dtsi:12 */
	chosen {
		zephyr,entropy = &rng;            /* in zephyr/dts/arm/mcu_vendor/xxx/mcu.dtsi:27 */
		zephyr,flash-controller = &flash; /* in zephyr/dts/arm/mcu_vendor/xxx/mcu.dtsi:28 */
		zephyr,console = &usart1;         /* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:14 */
		zephyr,shell-uart = &usart1;      /* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:15 */
		zephyr,sram = &sram0;             /* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:16 */
		zephyr,flash = &flash0;           /* in zephyr/samples/hello_world/boards/company/product/product_mcu.dts:17 */
	};
	
...

However, when using NCS flavor of zephyr I get:

/dts-v1/;

/ {
	model = "Company Product MCU Application";
	compatible = "companc,product-app";
	#address-cells = < 0x1 >;
	#size-cells = < 0x1 >;

	chosen {
		zephyr,entropy = &rng;
		zephyr,flash-controller = &flash;
		zephyr,console = &usart1;
		zephyr,shell-uart = &usart1;
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
	};
	
...

instead.

Question

How can I have those source/origin comments in my generated zephyr.dts using NCS?

Parents Reply
  • I appreciate the debate about the missing'source/origin' comments in the NCS flavor of Zephyr. Complete documentation is crucial for sprunki game developers since it has a substantial impact on the debugging process and overall efficiency. In my most recent project with Zephyr, I had similar issues with poor documentation on device tree bindings, which impacted our integration timetable. Perhaps providing examples of where these comments are very powerful can assist others understand their significance.

Children
No Data
Related