Zephyr driver demo - Revision history

Ted: 2023-06-13 - Ted retiring page, marking for eventual removal

2023-06-13T22:13:24Z

2023-06-13 - Ted retiring page, marking for eventual removal

Ted: /* ^ Memfault Article Review and CheckList of Macros */

2023-04-03T18:09:41Z

^ Memfault Article Review and CheckList of Macros

Ted: /* ^ Memfault Article Review and CheckList of Macros */ memfault blog post de Jared Wolff

2022-07-15T22:22:10Z

^ Memfault Article Review and CheckList of Macros: memfault blog post de Jared Wolff

Ted: /* ^ Memfault Article Review and CheckList of Macros */

2021-10-12T20:35:34Z

^ Memfault Article Review and CheckList of Macros

Ted: /* ^ Memfault Article Review and CheckList of Macros */

2021-10-12T20:35:09Z

^ Memfault Article Review and CheckList of Macros

Ted: /* ^ Useful Commands To Manage Zephyr Project Details */

2021-10-01T23:15:57Z

^ Useful Commands To Manage Zephyr Project Details

Ted: /* ^ AQW Example Sensor Structs and Data Fetch Functions */

2021-09-13T18:37:40Z

^ AQW Example Sensor Structs and Data Fetch Functions

Ted: Updating local page overview to mention salient Zephyr driver project.

2021-09-13T18:27:09Z

Updating local page overview to mention salient Zephyr driver project.

Ted: Ted moved page Zephyr driver demo v0p0 to Zephyr driver demo: Mediawiki's default page title font renders zero '0' characters like lower case 'o', misleading.

2021-09-13T18:13:01Z

Ted moved page Zephyr driver demo v0p0 to Zephyr driver demo: Mediawiki's default page title font renders zero '0' characters like lower case 'o', misleading.

Ted: /* ^ Programmatic Chain From main Function To Print Sensor Readings */

2021-09-13T17:55:12Z

^ Programmatic Chain From main Function To Print Sensor Readings

← Older revision		Revision as of 22:13, 13 June 2023
Line 1:		Line 1:
	Zephyr Driver and Separate Demo		Zephyr Driver and Separate Demo
		+
		+	<center>
		+	<font size="6" color="#ff0000">
		+	LOCAL PAGE RETIRED 2023-06-13
		+	</font>
		+	</center>

	- OVERVIEW -		- OVERVIEW -

← Older revision		Revision as of 18:09, 3 April 2023
Line 306:		Line 306:

	<i>To come: list of important Zephyr driver API macros and features</i>		<i>To come: list of important Zephyr driver API macros and features</i>
		+
		+	<!-- comentario -->
		+
		+	== [[#top\|^]] References ==
		+
		+	Linux driver for KX022A, close relative of KX132 and appears to be authored by Rohm developers:
		+	* https://github.com/torvalds/linux/blob/148341f0a2f53b5e8808d093333d85170586a15d/drivers/iio/accel/kionix-kx022a.c#L141

← Older revision		Revision as of 22:22, 15 July 2022
Line 299:		Line 299:

	== [[#top\|^]] Memfault Article Review and CheckList of Macros ==		== [[#top\|^]] Memfault Article Review and CheckList of Macros ==
		+
		+	Keyword and key phrases: memfault blog post de Jared Wolff

	[ <span id="nn-anchor-interrupt-dot-memfault-dot-com">Interrupt dot memfault dot com</span> ]<br />		[ <span id="nn-anchor-interrupt-dot-memfault-dot-com">Interrupt dot memfault dot com</span> ]<br />

@@ Line 300: / Line 300: @@
 == [[#top|^]] Memfault Article Review and CheckList of Macros ==
-<span id="nn-anchor-interrupt-dot-memfault-dot-com">Interrupt dot memfault dot com</span>
+[ <span id="nn-anchor-interrupt-dot-memfault-dot-com">Interrupt dot memfault dot com</span> ]<br />
 [https://interrupt.memfault.com/blog/building-drivers-on-zephyr#driver-smarts Jared Wolff's post] about Zephyr drivers mentions the macro <code>DEVICE_AND_API_INIT</code> among other key Zephyr driver code features.  But we don't have this macro present Kionix driver work.  Yet the driver is working.  Are we employing an older or different way to initialize our Kionix driver?  Has <code>DEVICE_AND_API_INIT</code> been superceded by something newer? . . .

@@ Line 300: / Line 300: @@
 == [[#top|^]] Memfault Article Review and CheckList of Macros ==
+<span id="nn-anchor-interrupt-dot-memfault-dot-com">Interrupt dot memfault dot com</span>
 [https://interrupt.memfault.com/blog/building-drivers-on-zephyr#driver-smarts Jared Wolff's post] about Zephyr drivers mentions the macro <code>DEVICE_AND_API_INIT</code> among other key Zephyr driver code features.  But we don't have this macro present Kionix driver work.  Yet the driver is working.  Are we employing an older or different way to initialize our Kionix driver?  Has <code>DEVICE_AND_API_INIT</code> been superceded by something newer? . . .

← Older revision		Revision as of 23:15, 1 October 2021
Line 92:		Line 92:

	In the above excerpt the argument to `git merge` is the start of the commit hash of the detached head commit history which, for some reason `west` meta-tool creates whenever developer issues `west update` in a local Zephyr application project. The commit hash here is arbitrary. It will be different pretty much every time a developer updates local code from remote repositories. Important to make a note of most recent hash before checking out a named branch!		In the above excerpt the argument to `git merge` is the start of the commit hash of the detached head commit history which, for some reason `west` meta-tool creates whenever developer issues `west update` in a local Zephyr application project. The commit hash here is arbitrary. It will be different pretty much every time a developer updates local code from remote repositories. Important to make a note of most recent hash before checking out a named branch!
		+
		+	2021-10-01 Friday
		+
		+	Message from `west update` when dependency third party repo changed:
		+
		+	<pre>
		+	=== updating zephyr-driver-work-v2 (kionix-drivers):
		+	--- zephyr-driver-work-v2: fetching, need revision main
		+	From https://github.com/tedhavelka/zephyr-driver-work-v2
		+	* branch main -> FETCH_HEAD
		+	HEAD is now at 6466b94 Adding code to fetch and provide copy of KX132-1211 numeric part ID.
		+	WARNING: left behind zephyr-driver-work-v2 branch "sensor-configuration-routines-work-001"; to switch back to it (fast forward):
		+	git -C ../kionix-drivers checkout sensor-configuration-routines-work-001
		+	</pre>
		+

	<!-- comment -->		<!-- comment -->

← Older revision		Revision as of 18:37, 13 September 2021
Line 281:		Line 281:
	* https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/blob/main/lib/aqw.c		* https://github.com/circuitdojo/air-quality-wing-zephyr-drivers/blob/main/lib/aqw.c

		+	<!-- comment -->
		+
		+	== [[#top\|^]] Memfault Article Review and CheckList of Macros ==
		+
		+
		+	[https://interrupt.memfault.com/blog/building-drivers-on-zephyr#driver-smarts Jared Wolff's post] about Zephyr drivers mentions the macro <code>DEVICE_AND_API_INIT</code> among other key Zephyr driver code features. But we don't have this macro present Kionix driver work. Yet the driver is working. Are we employing an older or different way to initialize our Kionix driver? Has <code>DEVICE_AND_API_INIT</code> been superceded by something newer? . . .

−	<!-- ~~comment~~ -->	+	<i>To come: list of important Zephyr driver API macros and features</i>
		+
		+
		+	<br />
		+	<br />
		+
		+	<center>
		+	[[#top\|- - - top of page - - -]]
		+	</center>
		+
		+
		+
		+	<!-- EOF -->

@@ Line 3: / Line 3: @@
 - OVERVIEW -
 Here list and begin to describe key, salient features of a Zephyr RTOS based driver and separately build-able demo to exercise given driver.  Driver for first version 0p0 is "out of tree", in other words outside of Zephyr project's source tree.
 <!-- comment -->

← Older revision	Revision as of 18:13, 13 September 2021
(No difference)

@@ Line 166: / Line 166: @@
 <!-- comment -->
-== [[#top|^]] Programmatic Chain From main Function To Print Sensor Readings ==
+== [[#top|^]] Chain From Main To Print Not Applicable ==
 This section aims to capture a clear sequence of C-based routines and routine calls, from <code>int main()</code> to an effective printf() type of function in a Zephyr RTOS application.  In part this wiki page section is motivated by Zephyr's multiple ways of obtaining programmatic handles or pointers to devices, and what appear to be at least two distinct but strictly guided ways of connecting app code to a sensor driver API.