Pico-sdk studies - Revision history

Ted: /* ^ Zephyr Support for RPi Pico */ - add link to Zephyr latest boards subdirectory for RPi Pico board

2024-01-30T14:24:23Z

^ Zephyr Support for RPi Pico: - add link to Zephyr latest boards subdirectory for RPi Pico board

Ted: /* ^ How To Program RPi Pico Board */

2024-01-30T14:17:56Z

^ How To Program RPi Pico Board

Ted: /* ^ DMA driver details */

2023-06-23T05:16:25Z

^ DMA driver details

Ted: /* ^ How To Program RPi Pico Board */ - minor formatting

2023-04-22T05:17:09Z

^ How To Program RPi Pico Board: - minor formatting

Ted: /* ^ How To Program RPi Pico Board */

2023-04-22T05:16:39Z

^ How To Program RPi Pico Board

Ted: Add section "How to program . . ."

2023-04-22T05:16:16Z

Add section "How to program . . ."

Ted: color adjustment

2023-04-20T20:41:14Z

color adjustment

Ted: wiki indent adjustment on sections to review

2023-04-20T20:37:49Z

wiki indent adjustment on sections to review

Ted: adding clunky left bar color indictor, green timely content, yellow ok, red needs review

2023-04-20T20:33:20Z

adding clunky left bar color indictor, green timely content, yellow ok, red needs review

Ted: /* ^ Overview */ - minor formatting

2023-04-20T20:13:38Z

^ Overview: - minor formatting

← Older revision		Revision as of 14:24, 30 January 2024
Line 86:		Line 86:

	* https://docs.zephyrproject.org/3.1.0/boards/arm/rpi_pico/doc/index.html		* https://docs.zephyrproject.org/3.1.0/boards/arm/rpi_pico/doc/index.html
		+
		+	And as of 2024-01-30, in Zephyr RTOS latest boards directory at github:
		+
		+	* https://github.com/zephyrproject-rtos/zephyr/tree/main/boards/arm/rpi_pico

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

@@ Line 39: / Line 39: @@
 (4)  reconnect RPi Pico USB cable to computer where .uf2 image file resides<br />
 (5)  copy the .uf2 image file to the directory which appears under your username's media directory<br />
 <br />

← Older revision		Revision as of 05:16, 23 June 2023
Line 108:		Line 108:


		+	==== [[#top\|^]] UART with DMA ====

		+	* https://forums.raspberrypi.com/viewtopic.php?t=337698

	Another instructive Pico sample app is the [https://github.com/raspberrypi/pico-examples/blob/master/dma/control_blocks/control_blocks.c DMA control block sample] which uses two DMA channels to transfer a series of data blocks.		Another instructive Pico sample app is the [https://github.com/raspberrypi/pico-examples/blob/master/dma/control_blocks/control_blocks.c DMA control block sample] which uses two DMA channels to transfer a series of data blocks.

@@ Line 32: / Line 32: @@
 == [[#top|^]] How To Program RPi Pico Board ==
-One manner in which to program RPi Pico board is through its USB interface.  The RPi Pico is typically powered via its USB port.  The steps to flashing a program to the Pico board are in short:
+One manner in which to program RPi Pico board is through its USB interface.  The RPi Pico is typically powered via its USB port.  The steps to flashing a program to the Pico board are in short:<br />
 (1)  compile a Zephyr or other RPi Pico project which results in a "dot uf2" type file<br />
@@ Line 39: / Line 39: @@
 (4)  reconnect RPi Pico USB cable to computer where .uf2 image file resides<br />
 (5)  copy the .uf2 image file to the directory which appears under your username's media directory<br />
 On Ubuntu 20.04 LTS work stations, the USB sub-system or a part of it recognizes RPi Pico boards in boot select mode as an external media device.  The Ubuntu driver side behavior is to create a directory having the path /media/${USERNAME}/RPI-RP2 or similar.  This happens when an RPi Pico board is powered up via USB connected to the Ubuntu host, and the Pico board's boot select button is pressed and held closed.  Most RPi tutorials talk about dragging and dropping the .uf2 image file to the media folder's icon on a graphical desktop.  A shell based copy command, such as `cp -pv image.uf2 /media/${USERNAME}/RPI-RP2` does the same thing.  Once the image copy action completes, the media directory `RPI-RP2` becomes unwriteable or unavailable.

@@ Line 34: / Line 34: @@
 One manner in which to program RPi Pico board is through its USB interface.  The RPi Pico is typically powered via its USB port.  The steps to flashing a program to the Pico board are in short:
-(1)  compile a Zephyr or other RPi Pico project which results in a "dot uf2" type file
+(1)  compile a Zephyr or other RPi Pico project which results in a "dot uf2" type file<br />
-(2)  disconnect RPi Pico board's USB cable to power down board
+(2)  disconnect RPi Pico board's USB cable to power down board<br />
-(3)  press and hold down Pico board's BOOTSEL button
+(3)  press and hold down Pico board's BOOTSEL button<br />
-(4)  reconnect RPi Pico USB cable to computer where .uf2 image file resides
+(4)  reconnect RPi Pico USB cable to computer where .uf2 image file resides<br />
-(5)  copy the .uf2 image file to the directory which appears under your username's media directory
+(5)  copy the .uf2 image file to the directory which appears under your username's media directory<br />
 On Ubuntu 20.04 LTS work stations, the USB sub-system or a part of it recognizes RPi Pico boards in boot select mode as an external media device.  The Ubuntu driver side behavior is to create a directory having the path /media/${USERNAME}/RPI-RP2 or similar.  This happens when an RPi Pico board is powered up via USB connected to the Ubuntu host, and the Pico board's boot select button is pressed and held closed.  Most RPi tutorials talk about dragging and dropping the .uf2 image file to the media folder's icon on a graphical desktop.  A shell based copy command, such as `cp -pv image.uf2 /media/${USERNAME}/RPI-RP2` does the same thing.  Once the image copy action completes, the media directory `RPI-RP2` becomes unwriteable or unavailable.

← Older revision		Revision as of 05:16, 22 April 2023
Line 28:		Line 28:
	* https://github.com/andrei-edward-popa/zephyr		* https://github.com/andrei-edward-popa/zephyr

		+	<!-- odne komentar -->
		+
		+	== [[#top\|^]] How To Program RPi Pico Board ==
		+
		+	One manner in which to program RPi Pico board is through its USB interface. The RPi Pico is typically powered via its USB port. The steps to flashing a program to the Pico board are in short:
		+
		+	(1) compile a Zephyr or other RPi Pico project which results in a "dot uf2" type file
		+	(2) disconnect RPi Pico board's USB cable to power down board
		+	(3) press and hold down Pico board's BOOTSEL button
		+	(4) reconnect RPi Pico USB cable to computer where .uf2 image file resides
		+	(5) copy the .uf2 image file to the directory which appears under your username's media directory
		+
		+	On Ubuntu 20.04 LTS work stations, the USB sub-system or a part of it recognizes RPi Pico boards in boot select mode as an external media device. The Ubuntu driver side behavior is to create a directory having the path /media/${USERNAME}/RPI-RP2 or similar. This happens when an RPi Pico board is powered up via USB connected to the Ubuntu host, and the Pico board's boot select button is pressed and held closed. Most RPi tutorials talk about dragging and dropping the .uf2 image file to the media folder's icon on a graphical desktop. A shell based copy command, such as `cp -pv image.uf2 /media/${USERNAME}/RPI-RP2` does the same thing. Once the image copy action completes, the media directory `RPI-RP2` becomes unwriteable or unavailable.
		+
		+	The Pico board may need to be powered cycled once more for the latest image to start executing. <i>( Need to test this - TMH )</i>
		+
		+	<!-- odne komentar -->

	<!-- A source code excerpt to review and move:		<!-- A source code excerpt to review and move:

@@ Line 11: / Line 11: @@
 <!-- odne komentar -->
-{|- style="cellpadding=30px;"   <!-- #e6ffcc is light green, #ffffcc light yellow,  -->
+{|- style="cellpadding=30px;"   <!-- #e6ffcc is light green, #ffffcc light yellow, ... RGB GYR 79d279, ffff66, ff8080 -->
 |-
-| style="background:#e6ffcc; valign=top; padding:10px;" | <!-- #ffffcc is light yellow -->
+| style="background:#79d279; valign=top; padding:10px;" | <!-- #ffffcc is light yellow -->
 | style="background:#f0f0f0; color:black; padding:10px; width:100%;" |

@@ Line 7: / Line 7: @@
 Pico SDK Studies
-_TOC_
+__TOC__
 <!-- odne komentar -->
@@ Line 28: / Line 28: @@
 *  https://github.com/andrei-edward-popa/zephyr
 <!-- A source code excerpt to review and move:
@@ Line 56: / Line 52: @@
 -->
-== [[#top|^]] Zephyr Support for RPi Pico ==
+|-
 *  https://docs.zephyrproject.org/3.1.0/boards/arm/rpi_pico/doc/index.html
@@ Line 66: / Line 72: @@
 | style="background:#f0f0f0; color:black; padding:10px; width:100%;" |
-== [[#top|^]] DMA driver details ==
+=== [[#top|^]] DMA driver details ===
 -08-18
@@ Line 92: / Line 98: @@
 <!-- comentario -->
-== [[#top|^]] Pico assert.h definitions ==
+=== [[#top|^]] Pico assert.h definitions ===
 RPi Pico SDK assert() definition is included in a section of this nn wiki page, as this Pico header file is included by both RPi Pico DMA driver and RPi Pico SPI driver.  It is likely included by other Pico drivers and modules.  We also include mention of this definition as recent studies of Zephyr third party drivers reveal that various projects each provide their own definitions of the C assert() construct.
@@ Line 181: / Line 187: @@
 <!-- comentario -->
-== [[#top|^]] Study of DMA routine check_dma_channel_param() ==
+=== [[#top|^]] Study of DMA routine check_dma_channel_param() ===
 The routine `check_dma_channel_param()` appears in file dma.c at line 24.  In file dma.c references to this routine appear three three times and there is a conditionally compiled definition for it at line 97.  There is a second place in Pico SDK where this routine is defined, in header file dma.h.  The two definitions read as follows:
@@ Line 255: / Line 261: @@
 <!-- comentario -->
-== [[#top|^]] * ==
+=== [[#top|^]] * ===
 <!-- comentario -->
-== [[#top|^]] Pico SDK start up APIs ==
+=== [[#top|^]] Pico SDK start up APIs ===
 In studying hello_dma sample app, first Pico SDK call is to API stdio_init_all().  This appears to be defined in two places of the SDK . . .
@@ Line 346: / Line 352: @@
 <!-- comentario -->
-== [[#top|^]] Pico rp2_common headers versus host headers ==
+=== [[#top|^]] Pico rp2_common headers versus host headers ===
 Pico SDK "host" header files are designed to support running RPi Pico projects on non-rpi hardware.  This would be useful if an app is too large to fit in an RPi Pico, or if for some reason an RPi Pico board is not available during all development times.
@@ Line 352: / Line 358: @@
 <!-- comentario -->
-== [[#top|^]] * ==
+=== [[#top|^]] * ===
 <!-- comentario -->
-== [[#top|^]] RPi Pico exploration project paths -06-txt ==
+=== [[#top|^]] RPi Pico exploration project paths -06-txt ===
 <pre>
@@ Line 363: / Line 369: @@
 /home/ted/projects/zephyr-based/workspace-rpi-pico-work/rpi-pico-zephyr-exploration/src
 /home/ted/projects/zephyr-based/workspace-rpi-pico-work/rpi-pico-zephyr-exploration/boards
+/
 /home/ted/projects/zephyr-based/workspace-rpi-pico-work/pico-sdk
@@ Line 374: / Line 374: @@
 /home/ted/projects/zephyr-based/workspace-rpi-pico-work/pico-sdk/src/rp2_common/pico_stdio
 /home/ted/reference/rpi-pico-sdk/src/host/pico_stdio/include/pico
 </pre>
 <!-- comentario --><!-- comentario -->
-== [[#top|^]] RPi Pico SDK code in Zephyr modules ==
+=== [[#top|^]] RPi Pico SDK code in Zephyr modules ===
 Zephyr modules directory contains hal_rpi_pico references, see file [workspace]/modules/hal/rpi_pico/zephyr/module.yaml.  What do stanzas cmake-ext and kconfig-ext mean?  How possible that we do not find actual source files on the github Zephyr RTOS Project repository for RPi Pico SDK sources, but that these sources appear to be downloaded into the local Zephyr modules dir?
@@ Line 415: / Line 399: @@
 <!-- comentario -->
-== [[#top|^]] hello_dma Build Messages ==
+=== [[#top|^]] hello_dma Build Messages ===
 Pico sample application "hello_dma" build messages using pico build framework or method:  first create a dir named 'build' at top directory of pico-examples project.  From within this directory named 'build' execute `cmake ..`.  This creates many new files and directories for all example projects, including GNU makefiles per project which permit building the sample apps into .uf2 format binaries.  Messages from building hello_dma:
@@ Line 662: / Line 646: @@
 <!-- comentario -->
-== [[#top|^]] Where Defined PICO_WEAK_FUNCTION_DEF ==
+=== [[#top|^]] Where Defined PICO_WEAK_FUNCTION_DEF ===
 PICO_WEAK_FUNCTION_DEF defined in file:
@@ Line 670: / Line 654: @@
 <!-- comentario -->
-== * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * ==
+=== * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * &nbsp;   * &nbsp; * &nbsp; * &nbsp; * ===
-<!-- == [[#top|^]] * == -->
 <!-- comentario -->

@@ Line 16: / Line 16: @@
 A 2023 Q2 good starting point may well be one Andrei-Edward Popa's presentation on using Zephyr with RPi Pico board.  Two links here to his works:
 *  https://ocw.cs.pub.ro/courses/iothings/proiecte/2021/zephyr
 *  https://github.com/andrei-edward-popa/zephyr