Zephyr rtos threads - Revision history

Ted: /* ^ Example Zephyr Thread Creation */ - rename section, remove some older content

2023-08-11T19:32:04Z

^ Example Zephyr Thread Creation: - rename section, remove some older content

Ted: /* ^ Example Zephyr Thread Creation */ - constraints on user created threads

2023-08-11T18:28:07Z

^ Example Zephyr Thread Creation: - constraints on user created threads

Ted: Starting new section 'latest'.

2022-03-11T21:56:44Z

Starting new section 'latest'.

Ted: 2021-11-11 - adding section of thread reporting and trace related APIs in Zephyr RTOS Project.

2021-11-12T05:24:24Z

2021-11-11 - adding section of thread reporting and trace related APIs in Zephyr RTOS Project.

Ted: /* ^ Issue with Counter Timer in Zephyr Thread - dwt.h */

2021-10-25T14:34:21Z

^ Issue with Counter Timer in Zephyr Thread - dwt.h

Ted: /* ^ Issue with Counter Timer in Zephyr Thread - dwt.h */

2021-10-09T05:27:00Z

^ Issue with Counter Timer in Zephyr Thread - dwt.h

Ted: /* ^ Issue with Counter Timer in Zephyr Thread - dwt.h */

2021-10-09T04:38:57Z

^ Issue with Counter Timer in Zephyr Thread - dwt.h

Ted at 04:37, 9 October 2021

2021-10-09T04:37:56Z

Ted: /* ^ OVERVIEW */

2021-10-07T05:54:12Z

^ OVERVIEW

Ted: /* ^ OVERVIEW */

2021-10-07T05:47:09Z

^ OVERVIEW

@@ Line 95: / Line 95: @@
 <!-- comment -->
-== [[#top|^]] Example Zephyr Thread Creation ==
+== [[#top|^]] Zephyr Thread Creation ==
--08-11 note - Threads in Zephyr may be created a couple of ways.  One involves an API call, and the other way involves a macro which expands to the thread creation code at compile time.  There are some constraints on creating threads via the API, that is at run time rather than compile time, which also generally implies that a user side or application
+-08-11 note - Threads in Zephyr may be created a couple of ways.  One involves an API call, and the other way involves a macro which expands to the thread creation code at compile time.  There are some constraints on creating threads via the API, that is at run time rather than compile time, which also generally implies that a user side or application.  These constraints detailed at:
 *  https://docs.zephyrproject.org/3.4.0/kernel/services/threads/index.html#user-mode-constraints
 <!-- comment -->

@@ Line 96: / Line 96: @@
 == [[#top|^]] Example Zephyr Thread Creation ==
 Rough search narrowing in on specific thread creation and use in aws_iot sample project from nRF Connect SDK:
 <pre>

← Older revision		Revision as of 21:56, 11 March 2022
Line 9:		Line 9:
	Also worth noting Zephyr provides a [https://docs.zephyrproject.org/2.6.0/guides/flash_debug/thread-analyzer.html thread analyzer module] for Zephyr based apps.		Also worth noting Zephyr provides a [https://docs.zephyrproject.org/2.6.0/guides/flash_debug/thread-analyzer.html thread analyzer module] for Zephyr based apps.

		+
		+	<!-- comment -->
		+
		+	== [[#top\|^]] Latest ==
		+
		+	0311
		+	* https://docs.zephyrproject.org/2.6.0/reference/kernel/threads/system_threads.html

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

← Older revision		Revision as of 05:24, 12 November 2021
Line 9:		Line 9:
	Also worth noting Zephyr provides a [https://docs.zephyrproject.org/2.6.0/guides/flash_debug/thread-analyzer.html thread analyzer module] for Zephyr based apps.		Also worth noting Zephyr provides a [https://docs.zephyrproject.org/2.6.0/guides/flash_debug/thread-analyzer.html thread analyzer module] for Zephyr based apps.

		+
		+	<!-- comment -->
		+
		+	== [[#top\|^]] New Zephyr Project Documentation Pages to Learn ==
		+
		+	* https://docs.zephyrproject.org/apidoc/latest/group__thread__stack__api.html
		+
		+	* https://docs.zephyrproject.org/apidoc/latest/group__task__wdt__api.html
		+
		+	* https://docs.zephyrproject.org/apidoc/latest/group__thread__analyzer.html
		+	<ul>
		+	* https://docs.zephyrproject.org/apidoc/latest/group__thread__analyzer.html#ga9ff07e2eff100f4b8c79440483c89836
		+	</ul>
		+
		+
		+	<!-- comment -->

	<b>Passing data between Zephyr threads:</b><br />		<b>Passing data between Zephyr threads:</b><br />

← Older revision		Revision as of 14:34, 25 October 2021
Line 206:		Line 206:
	* https://devzone.nordicsemi.com/f/nordic-q-a/75041/error-dwt-implements-no-cycle-counter-cannot-be-used-for-cycle-counting		* https://devzone.nordicsemi.com/f/nordic-q-a/75041/error-dwt-implements-no-cycle-counter-cannot-be-used-for-cycle-counting

		+	<!-- comment -->

		+	== [[#top\|^]] Project Files Which Change With Addition Of A Thread ==
		+
		+	Added a header and a source file to implement given new thread. Updated `CMakeLists.txt` to include new dot c source file. Updated main.c to include new dot h file and to call the new thread's initialization routine:
		+
		+	<pre>
		+	Memory region Used Size Region Size %age Used
		+	FLASH: 34988 B 1 MB 3.34%
		+	SRAM: 9744 B 64 KB 14.87%
		+	IDT_LIST: 0 GB 2 KB 0.00%
		+	ted@localhost:~/projects/zephyr-based/z4-sandbox-kionix-work/kionix-driver-demo$ git status
		+	On branch cli-dev-work-002
		+	Changes to be committed:
		+	(use "git restore --staged <file>..." to unstage)
		+	new file: src/thread_simple_cli.c
		+	new file: src/thread_simple_cli.h
		+
		+	Changes not staged for commit:
		+	(use "git add <file>..." to update what will be committed)
		+	(use "git restore <file>..." to discard changes in working directory)
		+	modified: CMakeLists.txt
		+	modified: src/main.c
		+	modified: src/thread_simple_cli.c
		+	modified: src/thread_simple_cli.h
		+	<pre>


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

@@ Line 202: / Line 202: @@
 </pre>
-What does this mean?
+What does this mean?  Hello, a Nordic Devzone post and reply from Sigurd of Nordic provides an answer to this specific problem:
 <!-- comment -->

← Older revision		Revision as of 04:38, 9 October 2021
Line 175:		Line 175:
	</pre>		</pre>

		+	Looking at `dwt.h`:
		+
		+	<pre>
		+	88
		+	89 /**
		+	90 * @brief Initialize and Enable the DWT cycle counter
		+	91 *
		+	92 * This routine enables the cycle counter and initializes its value to zero.
		+	93 *
		+	94 * @return 0
		+	95 */
		+	96 static inline int z_arm_dwt_init_cycle_counter(void)
		+	97 {
		+	98 /* Clear and enable the cycle counter */
		+	99 DWT->CYCCNT = 0;
		+	100 DWT->CTRL \|= DWT_CTRL_CYCCNTENA_Msk;
		+	101
		+	102 /* Assert that the cycle counter is indeed implemented. */
		+	103 __ASSERT((DWT->CTRL & DWT_CTRL_NOCYCCNT_Msk) != 0,
		+	104 "DWT implements no cycle counter. "
		+	105 "Cannot be used for cycle counting\n");
		+	106
		+	107 return 0;
		+	108 }
		+	109
		+	</pre>
		+
		+	What does this mean?


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

← Older revision		Revision as of 04:37, 9 October 2021
Line 146:		Line 146:


		+	<!-- comment -->

−	z	+	== [[#top\|^]] Issue with Counter Timer in Zephyr Thread - dwt.h ==
		+
		+	<pre>
		+	5��_�_yϗ��Uߗ��5�_]����Օ��}��ߧ�߿��׍ϯ��U��u��u��U��u��땥��]��w��w��w��u�7�w�U��u��W� *
		+	The AWS IoT sample started, version: v1.0.0
		+	Zephyr thread create routine returns 536955992 for LED blink thread,
		+	- SUCCESS - found Kionix accelerometer and device is ready
		+	uart task at loop iteration 0x00000000
		+	LTE cell changed: Cell ID: -1, Tracking area: -1
		+	uart task at loop iteration 0x00000001
		+	uart task at loop iteration 0x00000002
		+	thread_kionix_accel - Kionix sensor reports manufacturer ID string: " K i o n "
		+	( spaces added around characters, ID four bytes long. )
		+
		+	***
		+	*** TEST 2p1
		+	*** X accel 184, Y accel 65341, Z accel 16409
		+	***
		+	ASSERTION FAIL @ WEST_TOPDIR/zephyr/arch/arm/include/aarch32/cortex_m/dwt.h:103
		+	E: r0/a1: 0x00000004 r1/a2: 0x00000067 r2/a3: 0x00000001
		+	E: r3/a4: 0x00000000 r12/ip: 0xa0000000 r14/lr: 0x00027439
		+	E: xpsr: 0x41000000
		+	E: Faulting instruction address (r15/pc): 0x00039590
		+	E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
		+	E: Current thread: 0x20014d88 (unknown)
		+	</pre>
		+
		+
		+
		+	<!-- comment -->

← Older revision		Revision as of 05:54, 7 October 2021
Line 19:		Line 19:

	* https://docs.zephyrproject.org/2.6.0/reference/kernel/index.html?highlight=pass%20data		* https://docs.zephyrproject.org/2.6.0/reference/kernel/index.html?highlight=pass%20data
		+
		+	Zephyr queues:
		+	* https://docs.zephyrproject.org/2.6.0/reference/kernel/data_passing/queues.html

← Older revision		Revision as of 05:47, 7 October 2021
Line 15:		Line 15:

	* https://docs.zephyrproject.org/1.9.0/kernel/data_passing/data_passing.html		* https://docs.zephyrproject.org/1.9.0/kernel/data_passing/data_passing.html
		+
		+	* https://docs.zephyrproject.org/latest/reference/kernel/index.html?highlight=pass%20data
		+
		+	* https://docs.zephyrproject.org/2.6.0/reference/kernel/index.html?highlight=pass%20data