Hardware studies specific - Revision history

Ted: minor syntax fix.

2022-05-09T22:53:19Z

minor syntax fix.

Ted: Starting section on at_cmd_socket_thread.

2022-05-09T22:52:49Z

Starting section on at_cmd_socket_thread.

Ted: New section "Zephyr, ncs, and project files to review".

2022-05-04T18:54:41Z

New section "Zephyr, ncs, and project files to review".

Ted: /* Zephyr source i2c_nrfx_twim dot c */

2022-05-04T18:19:09Z

Zephyr source i2c_nrfx_twim dot c

Ted: /* Zephyr source i2c_nrfx_twim dot c */

2022-05-04T18:12:10Z

Zephyr source i2c_nrfx_twim dot c

Ted: Adding some notes to Zephyr and I2C run time configuation changes, pull up pull down pin settings changes dynamic.

2022-05-04T18:11:22Z

Adding some notes to Zephyr and I2C run time configuation changes, pull up pull down pin settings changes dynamic.

Ted: /* 3 */

2022-05-04T05:58:44Z

Ted at 05:57, 4 May 2022

2022-05-04T05:57:23Z

Ted: /* ^ Search For I2C Configuration Source Code */

2022-05-04T05:50:10Z

^ Search For I2C Configuration Source Code

Ted: /* ^ Search For I2C Configuration Source Code */

2022-05-03T23:12:05Z

^ Search For I2C Configuration Source Code

@@ Line 219: / Line 219: @@
 <!-- comentario -->
-== [[#top|^}] Files To Review ==
+== [[#top|^]] Files To Review ==
 The following files are from Zephyr, ncs, and or project `build` directory containing artifacts of the `west` directed, `ninja` based compilation:
@@ Line 232: / Line 232: @@
 <!-- comentario -->
-== [[#top|^}] Zephyr source i2c_nrfx_twim dot c ==
+== [[#top|^]] Zephyr source i2c_nrfx_twim dot c ==
 First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post 87549] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.
@@ Line 247: / Line 247: @@
 <!-- comentario -->
-== [[#top|^}] at_cmd_socket_thread ==
+== [[#top|^]] at_cmd_socket_thread ==
 This work relates to study of a Zephyr reported thread named 'at_cmd_socket_thread'.

@@ Line 219: / Line 219: @@
 <!-- comentario -->
-== Files To Review ==
+== [[#top|^}] Files To Review ==
 The following files are from Zephyr, ncs, and or project `build` directory containing artifacts of the `west` directed, `ninja` based compilation:
@@ Line 232: / Line 232: @@
 <!-- comentario -->
-== Zephyr source i2c_nrfx_twim dot c ==
+== [[#top|^}] Zephyr source i2c_nrfx_twim dot c ==
 First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post 87549] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.
@@ Line 242: / Line 242: @@
 *  https://github.com/nrfconnect/sdk-hal_nordic/blob/v1.5.2/nrfx/drivers/src/nrfx_twim.c#L315-L316

@@ Line 219: / Line 219: @@
 <!-- comentario -->
 == Zephyr source i2c_nrfx_twim dot c ==
@@ Line 234: / Line 246: @@
 <!-- comentario -->
 <center>

← Older revision		Revision as of 18:19, 4 May 2022
Line 223:		Line 223:

	First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post 87549] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.		First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post 87549] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.
		+
		+
		+	Some code line references pointing to github repo:
		+
		+	* https://github.com/nrfconnect/sdk-zephyr/blob/v2.7.99-ncs1-1/drivers/i2c/i2c_nrfx_twim.c#L309
		+
		+	* https://github.com/nrfconnect/sdk-hal_nordic/blob/v1.5.2/nrfx/drivers/src/nrfx_twim.c#L315-L316
		+
		+

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

@@ Line 222: / Line 222: @@
 == Zephyr source i2c_nrfx_twim dot c ==
-First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post nnnnn] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.
+First reply to [https://devzone.nordicsemi.com/f/nordic-q-a/87549/i2c1-status-ok-configures-internal-pull-up-or-similar Devzone post 87549] points us to study some Zephyr sources in `~/projects/zephyr-based/zephyr/drivers/i2c`.
 <!-- comentario -->

@@ Line 1: / Line 1: @@
--05-02 Monday
+This wiki article an effort to fully understand Zephyr RTOS facilities to fully configure, at start time and dynamically throughout run time I2C peripherals supported by Zephyr and given microcontroller Hardware Abstraction Layer (HAL) code.
 Search for Zephyr's I2C peripheral configuration code . . .
@@ Line 209: / Line 213: @@
 };
 </pre>
 <!-- comentario -->

← Older revision		Revision as of 05:58, 4 May 2022
Line 199:		Line 199:

	./zephyr/include/drivers/i2c.h:137:__subsystem struct i2c_driver_api {		./zephyr/include/drivers/i2c.h:137:__subsystem struct i2c_driver_api {
		+
		+	<pre>
		+	137 __subsystem struct i2c_driver_api {
		+	138 i2c_api_configure_t configure;
		+	139 i2c_api_full_io_t transfer;
		+	140 i2c_api_slave_register_t slave_register;
		+	141 i2c_api_slave_unregister_t slave_unregister;
		+	142 i2c_api_recover_bus_t recover_bus;
		+	143 };
		+	</pre>

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

@@ Line 148: / Line 148: @@
 <!-- comentario -->
 $ grep -nr z_vrfy_i2c_configure ./*
@@ Line 167: / Line 169: @@
 ./zephyr/include/drivers/i2c.h:310:static inline int z_impl_i2c_configure(const struct device *dev,
@@ Line 193: / Line 196: @@
 </pre>
 <!-- comentario -->

← Older revision		Revision as of 05:50, 4 May 2022
Line 139:		Line 139:

	And possibly `nrfxlib`.		And possibly `nrfxlib`.
		+
		+	<!-- comentario -->
		+
		+
		+
		+	./zephyr/drivers/i2c/i2c_handlers.c
		+
		+	<!-- comentario -->
		+
		+
		+
		+	$ grep -nr z_vrfy_i2c_configure ./*
		+
		+	./zephyr/drivers/i2c/i2c_handlers.c:11:static inline int z_vrfy_i2c_configure(const struct device *dev,
		+
		+	7 #include <drivers/i2c.h>
		+	8 #include <string.h>
		+	9 #include <syscall_handler.h>
		+	10
		+	11 static inline int z_vrfy_i2c_configure(const struct device *dev,
		+	12 uint32_t dev_config)
		+	13 {
		+	14 Z_OOPS(Z_SYSCALL_DRIVER_I2C(dev, configure));
		+	15 return z_impl_i2c_configure((const struct device *)dev, dev_config);
		+	16 }
		+	17 #in
		+
		+
		+
		+	./zephyr/include/drivers/i2c.h:310:static inline int z_impl_i2c_configure(const struct device *dev,
		+
		+	<pre>
		+	298 /**
		+	299 * @brief Configure operation of a host controller.
		+	300 *
		+	301 * @param dev Pointer to the device structure for the driver instance.
		+	302 * @param dev_config Bit-packed 32-bit value to the device runtime configuration
		+	303 * for the I2C controller.
		+	304 *
		+	305 * @retval 0 If successful.
		+	306 * @retval -EIO General input / output error, failed to configure device.
		+	307 */
		+	308 __syscall int i2c_configure(const struct device *dev, uint32_t dev_config);
		+	309
		+	310 static inline int z_impl_i2c_configure(const struct device *dev,
		+	311 uint32_t dev_config)
		+	312 {
		+	313 const struct i2c_driver_api *api =
		+	314 (const struct i2c_driver_api *)dev->api;
		+	315
		+	316 return api->configure(dev, dev_config);
		+	317 }
		+	</pre>
		+
		+

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

← Older revision		Revision as of 23:12, 3 May 2022
Line 131:		Line 131:
	</pre>		</pre>

		+	Out of these Zephyr modules built as part of our project the hal related ones appear to be:

		+	* cmsis
		+	* hal_nordic
		+	* st
		+	* libmetal
		+
		+	And possibly `nrfxlib`.

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