Current debugging - Revision history

Ted: /* ^ C preprocessor macros and macro expansion rules */ - C preprocessor tokenization

2022-11-16T21:08:16Z

^ C preprocessor macros and macro expansion rules: - C preprocessor tokenization

Ted: Zephyr sample apps to showcase use of dts macros to obtain device nodes at run time

2022-11-11T21:09:22Z

Zephyr sample apps to showcase use of dts macros to obtain device nodes at run time

Ted at 21:04, 11 November 2022

2022-11-11T21:04:45Z

Ted: adding couple sections, initial notes on C preprocessor macros and Zephyr device tree macros

2022-11-11T20:58:23Z

adding couple sections, initial notes on C preprocessor macros and Zephyr device tree macros

Ted: C preprocessor macros, macro stringification

2022-11-11T19:35:20Z

C preprocessor macros, macro stringification

Ted: /* ^ Device Tree syntax and Undocumented DTS */

2022-11-10T19:35:20Z

^ Device Tree syntax and Undocumented DTS

Ted: Examples from Zephyr 3.2.0 of device structure pointer assignments

2022-11-10T19:30:55Z

Examples from Zephyr 3.2.0 of device structure pointer assignments

Ted: Add new section for current debugging device tree source notes, Undocumented DTS

2022-11-10T17:40:12Z

Add new section for current debugging device tree source notes, Undocumented DTS

Ted: Start of new page "current debugging"

2022-11-06T02:23:12Z

Start of new page "current debugging"

New page

2022-11-05 SAT

<pre>
[00:00:00.009,000] <err> IIS2DH: iis2dh@18: device ��rF�� is not ready
[00:00:00.017,000] <err> IIS2DH: Failed to initialize interrupts
*** Booting Zephyr OS build zephyr-v3.2.0 ***
- scoreboard - in setter function test val holds 0,
- scoreboard - setting test val to 5,
- DEV 1028 - symbol ST_IIS2DH got assigned 'DT_N_S_soc_S_peripheral_50000000_S_flexcomm_8a000_S_iis2dh_18'
- kd_thread_iis2dh - Success finding iis2dh device,
- kd_thread_iis2dh - WARNING - sensor device 'iis2dh@18' is not ready!
- kd_thread_iis2dh - INFO: device name (Zephyr compile time setting) found to be 'iis2dh@18'
- kd_thread_iis2dh - INFO: boot time Zephyr init result value holds 5,
- DEV 1101 - WHO_AM_I register 0x0F holds 0x33
- DEV 1101 - config register 0x22 holds 0x10
- FIFO control reg holds 0x4f
- updating this value to set watermark at 16 data entries . . .
- write_register() returns status of 0,
- following update, FIFO control reg holds 0x4f
- updating FIFO ctrl register to enable FIFO mode . . .
- reading back vale . . .
- FIFO ctrl register now holds 0x4F.
- kd_thread_iis2dh - unconditionally attempting to configure data ready (drdy-gpios) interrupt,
Waiting for triggers
- whoami register, ODR register, and ctrl reg 5 hold 0x33, 0x57, 0x40
- whoami register, ODR register, and ctrl reg 5 hold 0x33, 0x57, 0x40
- whoami register, ODR register, and ctrl reg 5 hold 0x33, 0x57, 0x40
</pre>

← Older revision		Revision as of 21:08, 16 November 2022
Line 120:		Line 120:

	* https://home.cs.colorado.edu/~main/cs1300/doc/gnu/cpp_1.html		* https://home.cs.colorado.edu/~main/cs1300/doc/gnu/cpp_1.html
		+
		+	C preprocessor tokenization . . .
		+
		+	* https://gcc.gnu.org/onlinedocs/gcc-7.5.0/cpp/Tokenization.html

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

@@ Line 129: / Line 129: @@
 #error "- DEV 1108 - Could not find in device tree source any sensor interrupt type node!"
 #endif
 <!-- comentario -->

← Older revision		Revision as of 21:04, 11 November 2022
Line 1:		Line 1:

	2022-11-05 SAT		2022-11-05 SAT
		+
		+	== [[#top\|^]] Overview ==
		+
		+	In our current debugging we want to make sure we understand Zephyr device tree macros, and in particular how to use these macros to obtain device tree nodes which can be correctly passed to C based, Zephyr sensor API functions. It appears that there are at least some use cases where a pair of macros is needed, and these must be called out in a certain order so that macro expansions take place soon enough to provide correct device tree source tokens for use in the code.
		+
		+	A couple of things we'll want to cover -- not covered yet -- include (1) Zephyr's small set of macros to obtain a device tree node: DT_ALIAS, DT_NODELABEL, DT_PATH, DT_INST, and (2) use of device status or node property tests, as in:
		+
		+	#define SENSOR_INT1_NODE DT_ALIAS(sensorinterrupt1)
		+	#if !DT_NODE_HAS_STATUS(SENSOR_INT1_NODE, okay)
		+
		+
		+	Code excerpt from ~11/7, Zephyr device initialization failing before void main(void) yet sensor returns data later:

	<pre>		<pre>

@@ Line 39: / Line 39: @@
-<!-- comentario -->
+<!-- comentario -->[[#top|^]]
 Examples from Zephyr 3.2.0 of device structure pointer assignments:
@@ Line 56: / Line 56: @@
   *
   * SPDX-License-Identifier: Apache-2.0
-  */
+  */[[#top|^]]
 #include <zephyr/drivers/gpio.h>
@@ Line 102: / Line 102: @@
 <!-- comentario -->
 C preprocessor macros, macro stringification . . .
 *  https://home.cs.colorado.edu/~main/cs1300/doc/gnu/cpp_1.html

@@ Line 100: / Line 100: @@
 "./boards/arm/nrf9160dk_nrf9160/nrf52840_reset.c" 67L, 1609C
 </pre>
 <!-- comentario -->

← Older revision		Revision as of 19:35, 10 November 2022
Line 50:		Line 50:


		+	Excerpt from Nordic sample source code:
		+	<pre>
		+	1 /*
		+	2 * Copyright (c) 2019 Nordic Semiconductor ASA.
		+	3 *
		+	4 * SPDX-License-Identifier: Apache-2.0
		+	5 */
		+	6
		+	7 #include <zephyr/drivers/gpio.h>
		+	8 #include <zephyr/drivers/uart.h>
		+	9 #include <zephyr/device.h>
		+	10 #include <zephyr/devicetree.h>
		+	11
		+	12 #define RESET_NODE DT_NODELABEL(nrf52840_reset)
		+	13
		+	14 #if DT_NODE_HAS_STATUS(RESET_NODE, okay)
		+	15
		+	16 #define RESET_GPIO_CTRL DT_GPIO_CTLR(RESET_NODE, gpios)
		+	17 #define RESET_GPIO_PIN DT_GPIO_PIN(RESET_NODE, gpios)
		+	18 #define RESET_GPIO_FLAGS DT_GPIO_FLAGS(RESET_NODE, gpios)
		+	19
		+	20 int bt_hci_transport_setup(const struct device *h4)
		+	21 {
		+	22 int err;
		+	23 char c;
		+	24 const struct device *const port = DEVICE_DT_GET(RESET_GPIO_CTRL);
		+	25
		+	26 if (!device_is_ready(port)) {
		+	27 return -EIO;
		+	28 }
		+	29
		+	30 /* Configure pin as output and initialize it to inactive state. */
		+	31 err = gpio_pin_configure(port, RESET_GPIO_PIN,
		+	32 RESET_GPIO_FLAGS \| GPIO_OUTPUT_INACTIVE);
		+	33 if (err) {
		+	34 return err;
		+	35 }
		+	36
		+	37 /* Reset the nRF52840 and let it wait until the pin is inactive again
		+	38 * before running to main to ensure that it won't send any data until
		+	39 * the H4 device is setup and ready to receive.
		+	40 */
		+	41 err = gpio_pin_set(port, RESET_GPIO_PIN, 1);
		+	42 if (err) {
		+	43 return err;
		+	44 }
		+	45
		+	46 /* Wait for the nRF52840 peripheral to stop sending data.
		+	"./boards/arm/nrf9160dk_nrf9160/nrf52840_reset.c" 67L, 1609C
		+	</pre>
	<!-- comentario -->		<!-- comentario -->

@@ Line 17: / Line 17: @@
 - FIFO control reg holds 0x4f
 - updating this value to set watermark at 16 data entries . . .
-- write_register() returns status of 0,
+- write_register() returns status of 0,./tests/subsys/pm/device_power_domains/src/main.c:14:	const struct device *const reg_0 = DEVICE_DT_GET(DT_NODELABEL(test_reg_0));
 - following update, FIFO control reg holds 0x4f
 - updating FIFO ctrl register to enable FIFO mode . . .
@@ Line 34: / Line 37: @@
 *  https://elinux.org/Device_Tree_Mysteries#explain_some_more
 <!-- comentario -->

← Older revision		Revision as of 17:40, 10 November 2022
Line 28:		Line 28:
	- whoami register, ODR register, and ctrl reg 5 hold 0x33, 0x57, 0x40		- whoami register, ODR register, and ctrl reg 5 hold 0x33, 0x57, 0x40
	</pre>		</pre>
		+
		+	<!-- comentario -->
		+
		+	== [[#top\|^]] Device Tree syntax and Undocumented DTS ==
		+
		+	* https://elinux.org/Device_Tree_Mysteries#explain_some_more
		+
		+
		+	<!-- comentario -->