Device tree from scratch - Revision history

Ted: Adding key phrase "device tree Zephyr RTOS versus Linux use".

2022-08-18T17:34:21Z

Adding key phrase "device tree Zephyr RTOS versus Linux use".

Ted: /* ^ Overview */ adding anchor to local topic "device_tree_and_zephyr_versus_linux_use_of".

2022-08-18T17:33:21Z

^ Overview: adding anchor to local topic "device_tree_and_zephyr_versus_linux_use_of".

Ted: /* ^ Overview */

2022-08-18T17:31:58Z

^ Overview

Ted: /* ^ Synopsys SPI bindings required property */

2022-08-17T00:45:40Z

^ Synopsys SPI bindings required property

Ted: /* ^ Synopsys SPI bindings required property */

2022-08-17T00:33:34Z

^ Synopsys SPI bindings required property

Ted: /* ^ Reference */

2022-08-17T00:31:20Z

^ Reference

Ted: Add section "Synopsys SPI bindings required property".

2022-08-16T16:43:56Z

Add section "Synopsys SPI bindings required property".

Ted: Add links to closely related local pages.

2022-08-16T10:52:13Z

Add links to closely related local pages.

Ted: /* Reference */ - add reference to DPPI driver code.

2022-08-16T03:22:53Z

Reference: - add reference to DPPI driver code.

Ted: Add section for STMicro dts excerpts.

2022-08-15T22:48:04Z

Add section for STMicro dts excerpts.

← Older revision		Revision as of 17:34, 18 August 2022
Line 8:		Line 8:

	How to Create Device Tree Files for New MCUs		How to Create Device Tree Files for New MCUs
		+
		+	Keywords: [[#device_tree_and_zephyr_versus_linux_use_of\|device tree Zephyr RTOS versus Linux use]]
		+

@@ Line 12: / Line 12: @@
 == [[#top|^]] Overview ==
-Starting local article on how to craft a correct and complete device tree file set for an MCU not yet supported by Zephyr RTOS.  First notes here will reference examples of device tree source files various supported MCUs, plus corresponding datasheet sections pertaining to given MCUs.  A couple of points worth noting on device tree with Zephyr RTOS - (1) Zephyr does not use nor load device tree blobs at run time, rather device tree source and device tree compile tools aid in assuring and helping developer correct device coding errors at compile time.  (2)  To point one the act of calling out a particular device tree "compatible" value will cause the device tree compiler to look for a device bindings file specific to that "compatible" string.  The bindings file in turn calls out, e.g. instructs us as to which device tree attributes are required, and often also which data types and bounds on data ranges are required to be assigned to both required and optional device attributes.  Helpful!
+Starting local article on how to craft a correct and complete device tree file set for an MCU not yet supported by Zephyr RTOS.  First notes here will reference examples of device tree source files various supported MCUs, plus corresponding datasheet sections pertaining to given MCUs.  <span id="device_tree_and_zephyr_versus_linux_use_of"></span>A couple of points worth noting on device tree with Zephyr RTOS - (1) Zephyr does not use nor load device tree blobs at run time, rather device tree source and device tree compile tools aid in assuring and helping developer correct device coding errors at compile time.  (2)  To point one the act of calling out a particular device tree "compatible" value will cause the device tree compiler to look for a device bindings file specific to that "compatible" string.  The bindings file in turn calls out, e.g. instructs us as to which device tree attributes are required, and often also which data types and bounds on data ranges are required to be assigned to both required and optional device attributes.  Helpful!
 == [[#top|^]] Nordic Semi nRF9160 ==

@@ Line 12: / Line 12: @@
 == [[#top|^]] Overview ==
-Starting local article on how to craft a correct and complete device tree file set for an MCU not yet supported by Zephyr RTOS.  First notes here will reference examples of device tree source files various supported MCUs, plus corresponding datasheet sections pertaining to given MCUs.
+Starting local article on how to craft a correct and complete device tree file set for an MCU not yet supported by Zephyr RTOS.  First notes here will reference examples of device tree source files various supported MCUs, plus corresponding datasheet sections pertaining to given MCUs.  A couple of points worth noting on device tree with Zephyr RTOS - (1) Zephyr does not use nor load device tree blobs at run time, rather device tree source and device tree compile tools aid in assuring and helping developer correct device coding errors at compile time.  (2)  To point one the act of calling out a particular device tree "compatible" value will cause the device tree compiler to look for a device bindings file specific to that "compatible" string.  The bindings file in turn calls out, e.g. instructs us as to which device tree attributes are required, and often also which data types and bounds on data ranges are required to be assigned to both required and optional device attributes.  Helpful!
 == [[#top|^]] Nordic Semi nRF9160 ==

← Older revision		Revision as of 00:45, 17 August 2022
Line 76:		Line 76:

	Ah turns out RP2040 dts node '&nvic' appears in file [workspace]/zephyr/dts/arm/armv6-m.dtsi.		Ah turns out RP2040 dts node '&nvic' appears in file [workspace]/zephyr/dts/arm/armv6-m.dtsi.
		+
		+	<!-- comentario -->
		+
		+	== [[#top\|^]] DMA device tree node properties ==
		+
		+	* https://android.googlesource.com/kernel/msm/+/android-wear-5.0.2_r0.1/Documentation/devicetree/bindings/dma/dma.txt

	<!-- comentario -->		<!-- comentario -->

@@ Line 74: / Line 74: @@
   interrupt-parent = < &nvic >;
 <!-- comentario -->
 == [[#top|^]] Reference ==

@@ Line 81: / Line 81: @@
 <ol>
 <li>  https://infocenter.nordicsemi.com/topic/ps_nrf9160/memory.html
@@ Line 86: / Line 87: @@
 <li>  https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/hal/nrf_dppi.h   link to hal_nordic code repository
-A reference to DPPI driver code in nRF module:
+<li>  https://github.com/nrfconnect/sdk-nrf/blob/v1.6.1/subsys/esb/esb.c#L563 . . . A reference to DPPI driver code in an nrf-sdk module.
-<ol>
-<li>  https://github.com/nrfconnect/sdk-nrf/blob/v1.6.1/subsys/esb/esb.c#L563
+<li>  ./dts/bindings/dma/snps,designware-dma.yaml:6:compatible: "snps,designware-dma" . . . RP2040 dtsi file authored by Yonatan Shachter calls out "snps,designware-i2c" for I2C device compatibility.
 </ol>

@@ Line 68: / Line 68: @@
 <!-- comentario -->
 == Reference ==
 <ol>
@@ Line 82: / Line 92: @@
 <li>  https://github.com/nrfconnect/sdk-nrf/blob/v1.6.1/subsys/esb/esb.c#L563
 </ol>

← Older revision		Revision as of 10:52, 16 August 2022
Line 1:		Line 1:
		+	<center>
		+	[[Device_tree_from_scratch]]   ::   [[Spi_device_tree_source_code]]   ::   [[Pico-sdk_studies]]
		+	</center>
		+
		+
		+
	2022-08-15 Monday		2022-08-15 Monday

← Older revision		Revision as of 03:22, 16 August 2022
Line 70:		Line 70:

	<li> https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/hal/nrf_dppi.h link to hal_nordic code repository		<li> https://github.com/zephyrproject-rtos/hal_nordic/blob/master/nrfx/hal/nrf_dppi.h link to hal_nordic code repository
		+	</ol>
		+
		+	A reference to DPPI driver code in nRF module:
		+	<ol>
		+	<li> https://github.com/nrfconnect/sdk-nrf/blob/v1.6.1/subsys/esb/esb.c#L563
	</ol>		</ol>

← Older revision		Revision as of 22:48, 15 August 2022
Line 44:		Line 44:
	</pre>		</pre>

		+	<!-- comentario -->

		+	== [[#top\|^]] STMicro stm32f091 device tree source ==

		+	<pre>
		+	spi2: spi@40003800 {
		+	compatible = "st,stm32-spi-fifo", "st,stm32-spi";
		+	#address-cells = <1>;
		+	#size-cells = <0>;
		+	reg = <0x40003800 0x400>;
		+	clocks = <&rcc STM32_CLOCK_BUS_APB1 0x00004000>;
		+	interrupts = <26 3>;
		+	status = "disabled";
		+	};
		+	</pre>

	<!-- comentario -->		<!-- comentario -->