Raspberry Pi - Revision history

Kai: /* Processors and Architectures */

2025-04-13T23:01:49Z

Processors and Architectures

← Older revision		Revision as of 2025-04-13T23:01:49
Line 18:		Line 18:
	** Raspberry Pi 5 (Broadcom BCM2712 processor @ 2.4 GHz)		** Raspberry Pi 5 (Broadcom BCM2712 processor @ 2.4 GHz)
	** Compute Module 5 (Broadcom BCM2712 @ 2.4 GHz)		** Compute Module 5 (Broadcom BCM2712 @ 2.4 GHz)
	=== Microcontrollers ===		=== [[Raspberry_Pi_Microcontrollers \| Microcontrollers]] ===
	* [https://developer.arm.com/Processors/Cortex-M0-Plus Arm Cortex-M0+] with Armv6-M programming model
	** Raspberry Pi Pico (up to 133 MHz)
	* [https://developer.arm.com/Processors/Cortex-M33 Arm Cortex-M33] with Armv8-M programming model
	** Raspberry Pi Pico 2 (up to 150 MHz)
	<br />		<br />

Kai: /* Processors and Architectures */

2025-04-13T22:59:07Z

Processors and Architectures

Kai: Updated the listing of processors by adding Raspberry Pi 5, CM5, Pico 2

2025-04-13T22:57:00Z

Updated the listing of processors by adding Raspberry Pi 5, CM5, Pico 2

← Older revision		Revision as of 2025-04-13T22:57:00
Line 21:		Line 21:
	<br />		<br />

	* [https://developer.arm.com/Processors/Cortex-M0+ Arm Cortex-M0+] with Armv6-M programming model		* [https://developer.arm.com/Processors/Cortex-A76 Arm Cortex-A76] with 64-bit Armv8-A programming model
			** Raspberry Pi 5 (Broadcom BCM2712 processor @ 2.4 GHz)
			** Compute Module 5 (Broadcom BCM2712 @ 2.4 GHz)
			<br />

			* [https://developer.arm.com/Processors/Cortex-M0-Plus Arm Cortex-M0+] with Armv6-M programming model
	** Raspberry Pi Pico (up to 133 MHz)		** Raspberry Pi Pico (up to 133 MHz)

			* [https://developer.arm.com/Processors/Cortex-M33 Arm Cortex-M33] with Armv8-M programming model
			** Raspberry Pi Pico 2 (up to 150 MHz)
	<br />		<br />

Kai: Adding note on default settings for UART serial communication.

2025-04-07T19:03:07Z

Adding note on default settings for UART serial communication.

← Older revision		Revision as of 2025-04-07T19:03:07
Line 661:		Line 661:

	= Yocto Tips =		= Yocto Tips =
	== Connecting to the Raspberry Pi via the UART interface ==		== Connecting to the Raspberry Pi via the UART serial interface ==
	It is possible to configure the system image to enable a UART terminal interface on the target device. This allows for monitoring the boot messages and for logging in as root via UART (over USB) without configuring IP networking.		It is possible to configure the system image to enable a UART terminal interface on the target device. This allows for monitoring the boot messages and for logging in as root via UART (over USB) without configuring IP networking.

Line 670:		Line 670:
	which will result in the line "enable_uart=1" to be added to /boot/config.txt within the generated system image.		which will result in the line "enable_uart=1" to be added to /boot/config.txt within the generated system image.
	* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).		* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).
	* Using a terminal program (like ''gtkterm'', ''screen'', ''minicom'' or ''picocom'') connect to the USB serial TTY device. The terminal ~~should display the boot messages each time the target device boots.~~		* Using a terminal program (like ''gtkterm'', ''screen'', ''minicom'' or ''picocom'') connect to the USB serial TTY device. The default setting for serial communication is: 115200 baud rate, 8 data bits, no parity bit, 1 stop bit.
			<pre class="terminal">
			gtkterm -p /dev/ttyUSB0 -s 115200
			</pre>
	<pre class="terminal">		<pre class="terminal">
	screen /dev/ttyUSB0 115200		screen /dev/ttyUSB0 115200
	</pre>		</pre>
			<pre class="terminal">
			sudo picocom -b 115200 /dev/ttyUSB0
			</pre>
			The terminal should display the boot messages each time the target device boots.

	* Add the following line to the image configuration in order to enable logging into the target device as root without entering a password:		* Add the following line to the image configuration in order to enable logging into the target device as root without entering a password:
Line 679:		Line 686:
	EXTRA_IMAGE_FEATURES ?= "debug-tweaks empty-root-password"		EXTRA_IMAGE_FEATURES ?= "debug-tweaks empty-root-password"
	</pre>		</pre>
			Don't forget to disable these helpful image features in shipping production images.

	== Creating Kernel Patches for Compute Module 4 ==		== Creating Kernel Patches for Compute Module 4 ==

Kai: Adding GTKTerm to the list of suggested TTY terminal emulators.

2025-04-07T18:31:59Z

Adding GTKTerm to the list of suggested TTY terminal emulators.

← Older revision		Revision as of 2025-04-07T18:31:59
Line 670:		Line 670:
	which will result in the line "enable_uart=1" to be added to /boot/config.txt within the generated system image.		which will result in the line "enable_uart=1" to be added to /boot/config.txt within the generated system image.
	* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).		* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).
	* Using a terminal program (~~e.g.~~, ''screen'', ''minicom'', or ''picocom'') connect to the USB serial TTY device. The terminal should display the boot messages each time the target device boots.		* Using a terminal program (like ''gtkterm'', ''screen'', ''minicom'' or ''picocom'') connect to the USB serial TTY device. The terminal should display the boot messages each time the target device boots.
	<pre class="terminal">		<pre class="terminal">
	screen /dev/ttyUSB0 115200		screen /dev/ttyUSB0 115200

Kai: /* Connecting to the Raspberry Pi via the UART interface */

2025-04-07T18:28:28Z

Connecting to the Raspberry Pi via the UART interface

← Older revision		Revision as of 2025-04-07T18:28:28
Line 668:		Line 668:
	ENABLE_UART = "1"		ENABLE_UART = "1"
	</pre>		</pre>
			which will result in the line "enable_uart=1" to be added to /boot/config.txt within the generated system image.
	* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).		* Connect the development machine with the target device's UART pins, usually with a USB cable attached to a USB-to-serial converter board wired to the three UART pins of the GPIO headers of the Raspberry Pi (pin 8 for TXD; pin 10 for RXD; pin 6, 9 or 14 for Ground).
	* Using a terminal program (e.g., ''screen'', ''minicom'', or ''picocom'') connect to the USB serial TTY device. The terminal should display the boot messages each time the target device boots.		* Using a terminal program (e.g., ''screen'', ''minicom'', or ''picocom'') connect to the USB serial TTY device. The terminal should display the boot messages each time the target device boots.

Kai: Adding instruction to connect to the target device via UART

2025-04-07T17:52:44Z

Adding instruction to connect to the target device via UART

@@ Line 661: / Line 661: @@
 = Yocto Tips =
 == Creating Kernel Patches for Compute Module 4 ==
 A compute module does not know what hardware components its carrier board provides unless the default device tree is modified to include the interfaces to these hardware components. Instead of providing a different complete device tree, you would normally [[Yocto#Patching_A_Device_Tree | create a patch]] for the device tree source file provided by a lower Yocto layer.

Kai: Updated instructions for installing and using rpiboot.

2025-04-07T16:29:48Z

Updated instructions for installing and using rpiboot.

← Older revision		Revision as of 2025-04-07T16:29:48
Line 74:		Line 74:
	<br />		<br />

	== Installing the System Image on eMMC ==		== Installing the System Image on eMMC using rpiboot ==
	Some Raspberry Pi models, like the Compute Module 4, come with an embedded MultiMediaCard (eMMC) storage component. A switch or jumper on the carrier board serves to make the Raspberry Pi bootloader boot the compute module into USB mass storage mode. In this mode you can attach the compute module to an external computer via USB. On Ubuntu you can use the		Some Raspberry Pi models, like the Compute Module 4, come with an embedded MultiMediaCard (eMMC) storage component. A switch or jumper on the carrier board serves to make the Raspberry Pi bootloader boot the compute module into USB mass storage mode. In this mode you can attach the compute module to an external computer via USB. On Ubuntu you can use the
	<pre class="terminal">		<pre class="terminal">
Line 81:		Line 81:
	command to list all connected USB devices. The Compute Module 4, for example, should show up as "Broadcom Corp. BCM2711 Boot".		command to list all connected USB devices. The Compute Module 4, for example, should show up as "Broadcom Corp. BCM2711 Boot".
	<br />		<br />
	To make the operating system recognize the USB device as a mass storage device, we need to install Raspberry Pi's ''rpiboot'' tool.		<br />
			To make the operating system recognize the USB device as a mass storage device, we need to install Raspberry Pi's '''rpiboot''' tool.
	<pre class="terminal">		<pre class="terminal">
	sudo apt install rpiboot		sudo apt install rpiboot
Line 91:		Line 92:
	cd usbboot		cd usbboot
	make		make
	sudo ./rpiboot		make install
			</pre>
			Finally, run rpiboot as with root permissions:
			<pre class="terminal">
			sudo rpiboot
	</pre>		</pre>
			<br />
	On Ubuntu, ''lsusb'' will now list the Compute Module 4 as "Broadcom Corp. Compute Module". The compute module will also show up in the ''Disks'' app as ''RPi-MSD-0001''.		On Ubuntu, ''lsusb'' will now list the Compute Module 4 as "Broadcom Corp. Compute Module". The compute module will also show up in the ''Disks'' app as ''RPi-MSD-0001''.
	<br />		<br />

Kai: /* Installing the System Image on eMMC */

2025-04-07T16:16:44Z

Installing the System Image on eMMC

← Older revision		Revision as of 2025-04-07T16:16:44
Line 81:		Line 81:
	command to list all connected USB devices. The Compute Module 4, for example, should show up as "Broadcom Corp. BCM2711 Boot".		command to list all connected USB devices. The Compute Module 4, for example, should show up as "Broadcom Corp. BCM2711 Boot".
	<br />		<br />
	To make the operating system recognize the USB device as a mass storage device, we need to ~~build and run~~ Raspberry Pi's ''rpiboot'' tool.		To make the operating system recognize the USB device as a mass storage device, we need to install Raspberry Pi's ''rpiboot'' tool.
			<pre class="terminal">
			sudo apt install rpiboot
			</pre>
			Alternatively, rpiboot can be built from source:
	<pre class="terminal">		<pre class="terminal">
	sudo apt install libusb-1.0-0-dev		sudo apt install libusb-1.0-0-dev

Kai: Adds note about missing dsi entry in Compute Module 4 default dts.

2022-12-26T09:09:16Z

Adds note about missing dsi entry in Compute Module 4 default dts.

← Older revision		Revision as of 2022-12-26T09:09:16
Line 522:		Line 522:
	<br />		<br />
	<br />		<br />
	Below is an example configuration for a Compute Module 4 in which a MIPI CSI-2 camera and a MIPI DSI display are ~~accessed at specific I<sup>2</sup>C pins:~~		Below is an example configuration for a Compute Module 4, in which the I<sup>2</sup>C pins for accessing a MIPI CSI-2 camera and a MIPI DSI display are set. Applying this pin configuration is sufficient to make the camera available to user space applications because the device tree, ''bcm2711-rpi-cm4.dts'', already includes a ''csi'' entry. The ''dsi'' entry for the display, however, needs to be added.
	<pre class="code">		<pre class="code">
	/dts-v1/;		/dts-v1/;

← Older revision		Revision as of 2025-04-13T22:59:07
Line 4:		Line 4:
	<br />		<br />
	= Processors and Architectures =		= Processors and Architectures =
			=== Application Processors ===
	* [https://developer.arm.com/Processors/Cortex-A7 Arm Cortex-A7] with 32-bit Armv7 programming model		* [https://developer.arm.com/Processors/Cortex-A7 Arm Cortex-A7] with 32-bit Armv7 programming model
	** Raspberry Pi 2 B (Broadcom BCM2836 processor @ 900 MHz)		** Raspberry Pi 2 B (Broadcom BCM2836 processor @ 900 MHz)
	~~<br />~~

	* [https://developer.arm.com/Processors/Cortex-A53 Arm Cortex-A53] with 64-bit Armv8-A programming model.		* [https://developer.arm.com/Processors/Cortex-A53 Arm Cortex-A53] with 64-bit Armv8-A programming model.
	** Raspberry Pi 2 B rev 1.2 (Broadcom BCM2837 processor @ 900 MHz)		** Raspberry Pi 2 B rev 1.2 (Broadcom BCM2837 processor @ 900 MHz)
Line 14:		Line 12:
	** Raspberry Pi 3 B+ (Broadcom BCM2837B0 processor @ 1.4 GHz)		** Raspberry Pi 3 B+ (Broadcom BCM2837B0 processor @ 1.4 GHz)
	** Raspberry Pi Zero 2 W (@ 1 GHz)		** Raspberry Pi Zero 2 W (@ 1 GHz)
	~~<br />~~

	* [https://developer.arm.com/Processors/Cortex-A72 Arm Cortex-A72] with 64-bit Armv8-A programming model		* [https://developer.arm.com/Processors/Cortex-A72 Arm Cortex-A72] with 64-bit Armv8-A programming model
	** Raspberry Pi 4 (Broadcom BCM2711 processor @ 1.5 GHz)		** Raspberry Pi 4 (Broadcom BCM2711 processor @ 1.5 GHz)
	** Compute Module 4 (Broadcom BCM2711 @ 1.5 GHz)		** Compute Module 4 (Broadcom BCM2711 @ 1.5 GHz)
	~~<br />~~

	* [https://developer.arm.com/Processors/Cortex-A76 Arm Cortex-A76] with 64-bit Armv8-A programming model		* [https://developer.arm.com/Processors/Cortex-A76 Arm Cortex-A76] with 64-bit Armv8-A programming model
	** Raspberry Pi 5 (Broadcom BCM2712 processor @ 2.4 GHz)		** Raspberry Pi 5 (Broadcom BCM2712 processor @ 2.4 GHz)
	** Compute Module 5 (Broadcom BCM2712 @ 2.4 GHz)		** Compute Module 5 (Broadcom BCM2712 @ 2.4 GHz)
	~~<br />~~		=== Microcontrollers ===

	* [https://developer.arm.com/Processors/Cortex-M0-Plus Arm Cortex-M0+] with Armv6-M programming model		* [https://developer.arm.com/Processors/Cortex-M0-Plus Arm Cortex-M0+] with Armv6-M programming model
	** Raspberry Pi Pico (up to 133 MHz)		** Raspberry Pi Pico (up to 133 MHz)

	* [https://developer.arm.com/Processors/Cortex-M33 Arm Cortex-M33] with Armv8-M programming model		* [https://developer.arm.com/Processors/Cortex-M33 Arm Cortex-M33] with Armv8-M programming model
	** Raspberry Pi Pico 2 (up to 150 MHz)		** Raspberry Pi Pico 2 (up to 150 MHz)