Zephyr building blocks - Revision history

Ted: Add section q Zephyr Shell q, and link to Zephyr API to obtain pointer to shell instance

2026-08-23T00:53:29Z

Add section q Zephyr Shell q, and link to Zephyr API to obtain pointer to shell instance

2022-12-08T15:06:46Z

^ OVERVIEW: - How to build your Zephyr app in standalone folder

2022-07-12T17:52:58Z

^ USART references

2022-03-09T04:59:39Z

Zephyr RTOS Logger and Backend Features

2022-03-09T04:57:53Z

Zephyr RTOS Logger and Backend Features

2022-02-24T06:54:03Z

^ Zephyr Latest Notes: - https://github.com/zephyrproject-rtos/zephyr/issues/22941

2022-02-22T08:03:01Z

^ Zephyr Modules

2022-02-21T18:36:27Z

^ Zephyr Latest Notes

2022-02-15T17:52:25Z

^ Zephyr Latest Notes

2022-02-14T21:48:52Z

^ Zephyr Latest Notes

@@ Line 302: / Line 302: @@
 <!-- comment -->
-== Zephyr RTOS Logger and Backend Features ==
+== [[#top|^]] Zephyr RTOS Logger and Backend Features ==
 *  https://docs.zephyrproject.org/2.6.0/reference/logging/index.html#logger-backend-interface
@@ Line 348: / Line 348: @@
 <!-- comentario -->
 == [[#top|^]] References ==

← Older revision		Revision as of 15:06, 8 December 2022
Line 25:		Line 25:
	'uart_poll_in()' Zephyr peripheral library routine:		'uart_poll_in()' Zephyr peripheral library routine:
	* https://docs.zephyrproject.org/2.6.0/reference/peripherals/uart.html?highlight=uart_poll_in#c.uart_poll_in		* https://docs.zephyrproject.org/2.6.0/reference/peripherals/uart.html?highlight=uart_poll_in#c.uart_poll_in
		+
		+
		+
		+	2022-12-08
		+
		+	We'll need to move, reorganize and clean up a bunch of Zephyr related notes, but for now here is a link which can / may go into a yet-to-create page "Zephyr Intermediate Topics" page:
		+
		+	* https://blog.golioth.io/how-to-build-your-zephyr-app-in-a-standalone-folder/ Golioth dot io blog post "How to build Zephyr app in standalone dir"

← Older revision		Revision as of 17:52, 12 July 2022
Line 157:		Line 157:
	</ul>		</ul>

		+
		+	2022-07-10 Note also there is a one-time `newtmgr` configuration step to inform this utility of the particular serial device to treat as the programmer to the targeted hardware. This set up step is mentioned in the first few exchanges of this Jared Wolff community forum post:
		+	<ul>
		+	* https://community.jaredwolff.com/d/34-running-or-debugging-in-vsc/21
		+	</ul>
		+	Also
		+	<ul>
		+	* https://github.com/zephyrproject-rtos/zephyr/issues/9509
		+
		+	* https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.6.1/mcuboot/readme-mynewt.html
		+	</ul>
		+	The `newtmgr` port configuration command on Linux hosts take the form, from Zephyr project issues 9509:
		+
		+	@bfrog An example of proper connection parameters.
		+	sudo ./mcumgr image list --conntype=serial --connstring='dev=/dev/ttyACM0,baud=115200'

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

@@ Line 299: / Line 299: @@
 #define THREAD_ANALYZER_PRINT(...) printk(__VA_ARGS__)
 #define THREAD_ANALYZER_FMT(str)   str "\n"
-#define THREAD_ANALYZER_VSTR(str)  (str)
+#define THREAD_ANALYZER_VSTR(str)  (str)~/projects/zephyr-based/nrf$ vi ./applications/pelion_client/configuration/nrf9160dk_nrf9160ns/app_ZDebug.conf
 #else
 #define THREAD_ANALYZER_PRINT(...) LOG_INF(__VA_ARGS__)
@@ Line 311: / Line 311: @@
 <pre>
 ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/zephyr$ grep -nr LOG_INF ./* | grep define
-./include/logging/log.h:61:#define LOG_INF(...)   Z_LOG(LOG_LEVEL_INF, __VA_ARGS__)
+./include/logging/log.h:61:#define LOG_INF(...)   Z_LOG(LOG_LEVEL_INF, __VA_ARGS__)~/projects/zephyr-based/nrf$ vi ./applications/pelion_client/configuration/nrf9160dk_nrf9160ns/app_ZDebug.conf
 </pre>
@@ Line 319: / Line 319: @@
 *  https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.2.0/zephyr/reference/logging/index.html#_CPPv414log_thread_set7k_tid_t
 </ul>
 <!-- comentario -->

@@ Line 314: / Line 314: @@
 </pre>
+-03-08 TUE -
 <!-- comentario -->

← Older revision		Revision as of 06:54, 24 February 2022
Line 30:		Line 30:

	== [[#top\|^]] Zephyr Latest Notes ==		== [[#top\|^]] Zephyr Latest Notes ==
		+
		+	Really good discussion of Zephyr device tree issues, answers some question (brings some bad news at least as of Zephyr at its 2020 Feb release) regarding devices not being un-initializable, re-initializable at run time. This means reboot is needed when device really fails to initialize . . . remember this github issue number 22941:
		+
		+	* https://github.com/zephyrproject-rtos/zephyr/issues/22941

	A post referring to nRF9160 low power and sleep modes:		A post referring to nRF9160 low power and sleep modes:

@@ Line 106: / Line 106: @@
 *  https://docs.zephyrproject.org/2.6.0/search.html?q=sensor_value&check_keywords=yes&area=default
 <b>Timing Facilities</b><br />
@@ Line 113: / Line 116: @@
 *  https://docs.zephyrproject.org/2.6.0/reference/timing_functions/index.html?highlight=kernel%20timing
 <b>STMicro IIS2DH sensor and SPI interface</b>

@@ Line 68: / Line 68: @@
 <ul>
    *  https://github.com/zephyrproject-rtos/zephyr/issues/38191
 </ul>

@@ Line 40: / Line 40: @@
 *  https://devzone.nordicsemi.com/f/nordic-q-a/51513/nrf9160-low-power/208052#208052
 </ul>
 - = * * * = -

@@ Line 33: / Line 33: @@
 A post referring to nRF9160 low power and sleep modes:
 <ul>
-*  https://devzone.nordicsemi.com/f/nordic-q-a/45690/nrf9160-sleep-mode <i>< over three years old but yet potentially helpful</i>
+*  https://devzone.nordicsemi.com/f/nordic-q-a/45690/nrf9160-sleep-mode <i>< - - over three years old but yet potentially helpful</i>
 *  https://devzone.nordicsemi.com/f/nordic-q-a/51513/nrf9160-low-power/208052#208052
 </ul>