From 13a9f2d9d707d862586e79b6c3555b4e314d46ca Mon Sep 17 00:00:00 2001 From: jehlers42 Date: Fri, 25 Aug 2023 16:13:21 +0100 Subject: [PATCH 1/4] Added whitepapers --- .../accessories/display/display_intro.adoc | 14 +++++++++++ .../computers/compute-module/datasheet.adoc | 22 +++++++++++++++++ .../computers/config_txt/overclocking.adoc | 6 +++++ .../computers/configuration/hdmi-config.adoc | 7 ++++++ .../computers/getting-started/setting-up.adoc | 9 +++++++ .../computers/os/graphics-utilities.adoc | 9 +++++++ .../asciidoc/computers/os/updating.adoc | 5 ++++ .../raspberry-pi/bcm2711-bootloader.adoc | 24 +++++++++++++++++++ .../raspberry-pi/power-supplies.adoc | 7 ++++++ .../raspberry-pi/raspberry-pi-compliance.adoc | 9 +++++++ .../raspberry-pi/raspberry-pi-industrial.adoc | 4 ++-- .../rp2040/rp2040_based_boards.adoc | 8 ++++++- 12 files changed, 121 insertions(+), 3 deletions(-) diff --git a/documentation/asciidoc/accessories/display/display_intro.adoc b/documentation/asciidoc/accessories/display/display_intro.adoc index a676fe100..098021dc4 100644 --- a/documentation/asciidoc/accessories/display/display_intro.adoc +++ b/documentation/asciidoc/accessories/display/display_intro.adoc @@ -2,6 +2,13 @@ The Raspberry Pi Touch Display is an LCD display which connects to the Raspberry Pi through the DSI connector. In some situations, it allows for the use of both the HDMI and LCD displays at the same time (this requires software support). +[.whitepaper, title="Implementing a DSI Driver on the Raspberry Pi", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003472-WP/Using-a-DSI-display.pdf] +**** +This whitepaper is an introduction to writing a Display Serial Interface (DSI) driver for liquid crystal display (LCD) panels running under the Kernel Mode Setting (KMS) graphics system. It does not cover DSI drivers for the legacy graphics system, or Fake Kernel Mode Setting (FKMS). + +It assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS; Linux), and are fully up to date with the latest firmware and kernels. +**** + === Board Support The DSI display is designed to work with all models of Raspberry Pi, however early models that do not have mounting holes (the Raspberry Pi 1 Model A and B) will require additional mounting hardware to fit the HAT-dimensioned stand-offs on the display PCB. @@ -137,3 +144,10 @@ Read our troubleshooting steps, tips, and tricks here: xref:display.adoc#trouble * Outer dimensions: 192.96 × 110.76mm * Viewable area: 154.08 × 85.92mm * https://datasheets.raspberrypi.com/display/7-inch-display-mechanical-drawing.pdf[Download mechanical drawing (PDF)] + +[.whitepaper, title="Touch Display Enclosure Mechanical Design", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003473-WP/Touch-Display-Enclosure-Mechanical-Design.pdf] +**** +This whitepaper provides information for designing mechanical enclosures for the Raspberry Pi Touch Display. + +The Raspberry Pi Touch Display is dual-source manufactured, and there are very slight differences in the mechanical design between the two manufacturers. This document describes those differences and provides possible mitigation mechanisms for ensuring that enclosure designs can incorporate either version of the panel. For the purposes of this document, the two versions of the panel will be designated 'Supplier A' and 'Supplier B'. Raspberry Pi Ltd will not be publishing the names of the manufacturers used for the liquid crystal display (LCD) panel, or the panel datasheets. +**** \ No newline at end of file diff --git a/documentation/asciidoc/computers/compute-module/datasheet.adoc b/documentation/asciidoc/computers/compute-module/datasheet.adoc index 10d56e642..a84f21793 100644 --- a/documentation/asciidoc/computers/compute-module/datasheet.adoc +++ b/documentation/asciidoc/computers/compute-module/datasheet.adoc @@ -13,6 +13,28 @@ There is also a KiCad PCB design set available: * https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCad files] +[.whitepaper, title="Transitioning from CM3 to CM4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003469-WP/Transitioning-from-CM3-to-CM4.pdf] +[.whitepaper, title="Transitioning from CM 3 to CM 4S", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003478-WP/Transitioning-from-CM-3-to-CM-4S.pdf] +**** +This whitepaper is for those who wish to move from using a Raspberry Pi Compute Module (CM) 1 or 3 to a Raspberry Pi CM 4 or 4S. There are several reasons why this might be desirable: +• Greater computing power +• More memory +• Higher-resolution output up to 4Kp60 +• Better availability +• Longer product life (last time buy not before January 2028) + +From a software perspective, the move from Raspberry Pi CM 1/3 to Raspberry Pi CM 4S is relatively painless, as a Raspberry Pi operating system (OS) image should work on all platforms. If, however, you are using a custom kernel, some things will need to be considered in the move. The hardware changes are considerable, and the differences are described in a later section. +**** + +[.whitepaper, title="Configuring the Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003470-WP/Configuring-the-Compute-Module-4.pdf] +**** +The Raspberry Pi Compute Module 4 (CM 4) is available in a number of different hardware configurations. Sometimes it may be necessary to disable some of these features when they are not required. + +Disabling features also results in power saving, which can be important when CM 4 devices are used in battery environments or similar. + +This document describes how to disable various hardware interfaces, in both hardware and software, and how to reduce the amount of memory used by the Linux operating system (OS). +**** + === Older Products Raspberry Pi CM1, CM3 and CM3L are supported products with an End-of-Life (EOL) date no earlier than January 2026. The Compute Module 3+ offers improved thermal performance, and a wider range of Flash memory options. diff --git a/documentation/asciidoc/computers/config_txt/overclocking.adoc b/documentation/asciidoc/computers/config_txt/overclocking.adoc index 4e6fbd41e..e51915f0f 100644 --- a/documentation/asciidoc/computers/config_txt/overclocking.adoc +++ b/documentation/asciidoc/computers/config_txt/overclocking.adoc @@ -330,6 +330,12 @@ The GPU core, CPU, SDRAM and GPU each have their own PLLs and https://forums.ras To view the Raspberry Pi's current frequency in KHz, type: `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`. Divide the result by 1000 to find the value in MHz. Note that this frequency is the kernel _requested_ frequency, and it is possible that any throttling (for example at high temperatures) may mean the CPU is actually running more slowly than reported. An instantaneous measurement of the actual ARM CPU frequency can be retrieved using the vcgencmd `vcgencmd measure_clock arm`. This is displayed in Hertz. === Monitoring Core Temperature +[.whitepaper, title="Cooling a Raspberry Pi device", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003608-WP/Cooling-a-Raspberry-Pi-device.pdf] +**** +This whitepaper goes through the reasons why your Raspberry Pi may get hot and why you might want to cool it back down, and gives various options on achieving that cooling process. + +This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. +**** To view the Raspberry Pi's temperature, type `cat /sys/class/thermal/thermal_zone0/temp`. Divide the result by 1000 to find the value in degrees Celsius. Alternatively, there is a vcgencmd, `vcgencmd measure_temp` that interrogates the GPU directly for its temperature. diff --git a/documentation/asciidoc/computers/configuration/hdmi-config.adoc b/documentation/asciidoc/computers/configuration/hdmi-config.adoc index 48da3f2b0..1c184de80 100644 --- a/documentation/asciidoc/computers/configuration/hdmi-config.adoc +++ b/documentation/asciidoc/computers/configuration/hdmi-config.adoc @@ -15,6 +15,13 @@ If you are using legacy graphics drivers, or find yourself in circumstances wher NOTE: All the commands are documented fully in the xref:config_txt.adoc#video-options[config.txt] section of the documentation. +[.whitepaper, title="Troubleshooting KMS HDMI output", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004341-WP/Troubleshooting-KMS-HDMI-output.pdf] +**** +With the introduction of the KMS (Kernel Mode Setting) graphics driver, Raspberry Pi Ltd is moving away from legacy firmware control of the video output system and towards a more open source graphics system. This document is intended to help with any issues that might arise when moving to the new system. + +This whitepaper assumes that Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. +**** + === HDMI Groups and Mode HDMI has two common groups: CEA (Consumer Electronics Association, the standard typically used by TVs) and DMT (Display Monitor Timings, the standard typically used by monitors). Each group advertises a particular set of modes, where a mode describes the resolution, frame rate, clock rate, and aspect ratio of the output. diff --git a/documentation/asciidoc/computers/getting-started/setting-up.adoc b/documentation/asciidoc/computers/getting-started/setting-up.adoc index d75c837e2..059e7ee9f 100644 --- a/documentation/asciidoc/computers/getting-started/setting-up.adoc +++ b/documentation/asciidoc/computers/getting-started/setting-up.adoc @@ -20,6 +20,15 @@ For the Raspberry Pi 4 Model B and Raspberry Pi 400, you should use the https:// Finally, you'll need an xref:getting-started.adoc#sd-cards[SD card]; we recommend a minimum of 8GB micro SD card and use the https://www.raspberrypi.com/software/[Raspberry Pi Imager] to install an operating system onto it. +[.whitepaper, title="Transitioning from Pi 3 to Pi 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003475-WP/Transitioning-from-Pi-3-to-Pi-4.pdf] +**** +This whitepaper is for those who wish to move from using a Raspberry Pi 3B+ to the Raspberry Pi 4 device. + +From a software perspective, the move from the Raspberry Pi 3B+ to the Raspberry Pi 4B is relatively painless as a Raspberry Pi operating system (OS) image should work on all platforms. If, however, you are using a custom kernel, there are some things that will need to be considered in the move. + +The hardware changes are more extensive, and the differences are described in a later section. +**** + === Connecting a Display Unless you're setting up your Raspberry Pi to operate xref:configuration.adoc#setting-up-a-headless-raspberry-pi[headless], for regular use, you'll want to plug the Raspberry Pi into a display: either a computer monitor or a television. diff --git a/documentation/asciidoc/computers/os/graphics-utilities.adoc b/documentation/asciidoc/computers/os/graphics-utilities.adoc index 673e2da99..9272f1089 100644 --- a/documentation/asciidoc/computers/os/graphics-utilities.adoc +++ b/documentation/asciidoc/computers/os/graphics-utilities.adoc @@ -141,6 +141,15 @@ Returns the throttled state of the system. This is a bit-pattern - a bit being s Returns the temperature of the SoC as measured by its internal temperature sensor; on Raspberry Pi 4, `measure_temp pmic` returns the temperature of the PMIC. +[.whitepaper, title="Extra PMIC features on Raspberry Pi 4 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004340-WP/Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf] +**** +Raspberry Pi 4 and Raspberry Pi Compute Module 4 devices use a Power Management Integrated Circuit (PMIC) to supply the various voltages required by the various components on the PCB. They also sequence power ups to ensure the devices are started in the correct order. + +Over the duration of production of these models, a number of different PMIC devices have been used on both Raspberry Pi 4 and CM4. All the PMICs have provided extra functionality over and above that of voltage supply. This document describes how to access these features in software. + +This whitepaper assumes that the Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. +**** + ==== measure_clock [clock] This returns the current frequency of the specified clock. The options are: diff --git a/documentation/asciidoc/computers/os/updating.adoc b/documentation/asciidoc/computers/os/updating.adoc index fa3a88a80..bc759f631 100644 --- a/documentation/asciidoc/computers/os/updating.adoc +++ b/documentation/asciidoc/computers/os/updating.adoc @@ -118,6 +118,11 @@ sudo apt purge tree [[rpi-update]] === Using `rpi-update` +[.whitepaper, title="Updating Pi firmware", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003476-WP/Updating-Pi-firmware.pdf] +**** +In some circumstances it may be necessary to update the VideoCore firmware in a Raspberry Pi operating system (OS) image without going through the normal upgrade process. This whitepaper documents how to use the normal upgrade process, and also gives information on how to bypass the standard update process if it is not suitable. +**** + `rpi-update` is a command line application that will update your Raspberry Pi OS kernel and VideoCore firmware to the latest pre-release versions. WARNING: Pre-release versions of software are not guaranteed to work. You should not use `rpi-update` on any system unless recommended to do so by a Raspberry Pi engineer. It may leave your system unreliable or even completely broken. It should not be used as part of any regular update process. diff --git a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc index cf5082a82..2ff141154 100644 --- a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc @@ -244,6 +244,15 @@ The `Customer OTP` rows are OTP registers 36 to 43 in the `vcgencmd otp_dump` ou Default: "" +[.whitepaper, title="Changing MAC addresses", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003474-WP/Changing-MAC-addresses.pdf] +**** +This whitepaper describes how to set a specific media access control (MAC) address on your Raspberry Pi device. It applies to both Ethernet and wireless interfaces. + +Two mechanisms are described, one for devices up to the Pi 3 and one for the Pi 4/400 and CM 4. These latter three devices use the BCM2711 system on a chip (SoC), which has a built-in Ethernet port and hence defines its MAC addresses in a different way. + +This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. +**** + ==== Static IP address configuration If TFTP_IP and the following options are set then DHCP is skipped and the static IP configuration is applied. If the TFTP server is on the same subnet as the client then GATEWAY may be omitted. @@ -607,10 +616,25 @@ This option may be set to 0 to block self-update without requiring the EEPROM co Default: `1` === Secure Boot configuration properties in `config.txt` + +[.whitepaper, title="Raspberry Pi 4 Boot Security", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004651-WP/Raspberry-Pi-4-Boot-Security.pdf] +**** +This white paper describes Raspberry Pi Ltd’s approach to boot security on the Raspberry Pi 4 family of devices, based on +the BCM2711 system on a chip (SoC). +**** + +[.whitepaper, title="Boot security howto", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003466-WP/Boot-Security-Howto.pdf] +**** +This whitepaper describes how to implement secure boot on devices based on Raspberry Pi 4. For an overview of the secure boot implementation, please see the Raspberry Pi 4 Boot Security whitepaper. + +This whitepaper assumes that the Raspberry Pi running RPIBOOT is running Raspberry Pi OS (Linux), Bullseye version or later, and is fully up to date with the latest firmware and kernels. The secure boot system is intended for use with buildroot (or similar)-based OS images; using it with Raspberry Pi OS is not recommended or supported. +**** + The following `config.txt` properties are used to program the `secure-boot` OTP settings. These changes are irreversible and can only be programmed via `RPIBOOT` when flashing the bootloader EEPROM image. This ensures that `secure-boot` cannot be set remotely or by accidentally inserting a stale SD card image. For more information about enabling `secure-boot` please see the https://github.com/raspberrypi/usbboot/blob/master/Readme.md#secure-boot[secure-boot readme] and the https://github.com/raspberrypi/usbboot/blob/master/secure-boot-example/README.md[secure-boot tutorial] in the https://github.com/raspberrypi/usbboot[USBBOOT] repo. + [[program_pubkey]] ==== program_pubkey If this property is set to `1` then `recovery.bin` will write the hash of the public key in the EEPROM image to OTP. Once set, the bootloader will reject EEPROM images signed with different RSA keys or unsigned images. diff --git a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc index 8a060f1c3..baf5ece02 100644 --- a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc @@ -129,6 +129,13 @@ If you are seeing warnings, you should improve the power supply and/or cable, as Voltages can drop for a variety of reasons, for example if the power supply itself is inadequate, the power supply cable is made of too thin wires, or you have plugged in high demand USB devices. +[.whitepaper, title="Making a more resilient file system", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003610-WP/Making-a-more-resilient-file-system.pdf] +**** +Raspberry Pi Ltd devices are frequently used as data storage and monitoring devices, often in places where sudden power downs may occur. As with any computing device, power dropouts can cause storage corruption. This whitepaper provides some options on how to prevent data corruption under these and other circumstances by selecting appropriate file systems and setups to ensure data integrity. + +This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi (Linux) operating system (OS), and is fully up to date with the latest firmware and kernels. +**** + === Back-powering The USB specification requires that USB devices must not supply current to upstream devices. If a USB device does supply current to an upstream device then this is called back-powering. Often this happens when a badly-made powered USB hub is connected, and will result in the powered USB hub supplying power to the host Raspberry Pi. This is not recommended since the power being supplied to the Raspberry Pi via the hub will bypass the protection circuitry built into the Raspberry Pi, leaving it vulnerable to damage in the event of a power surge. diff --git a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc index 19b4e08d6..311d55333 100644 --- a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc @@ -21,3 +21,12 @@ The Powered by Raspberry Pi progamme provides a process for companies wanting to === Approved Design Partners Our list of https://www.raspberrypi.com/for-industry/design-partners/[approved design partners] provide a set of consultancies that we work closely with and support so they can provide paid for design services across hardware, software, and mechanical. + +[.whitepaper, title="Fleet management - A brief introduction", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003609-WP/Fleet-management-A-brief-introduction.pdf] +**** +The sheer range of applications that the Raspberry Pi devices are suitable for means any one company may have hundreds, thousands, or even tens of thousands of devices in their portfolio. All these devices need to be maintained and, as numbers increase, manual checking becomes extremely inefficient. This is where fleet management software comes into play. + +Raspberry Pi do not provide any sort of fleet management software, this is an area where there is a plethora of existing suppliers. This whitepaper attempts to show what these suppliers can do, and also provides a brief introduction to some that Raspberry Pi know work with Raspberry Pi devices. + +Please note that these are NOT recommendations; Raspberry Pi have not done any deep investigations into any of these products, simply ensured that Raspberry Pi devices are supported. It is down to the individual to ensure that any product or service matches their use case. Please also note that any suppliers listed are not the only suppliers of services that may be appropriate, i.e. the list is not exhaustive. +**** \ No newline at end of file diff --git a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc index 544e6780b..4cf548280 100644 --- a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-industrial.adoc @@ -4,12 +4,12 @@ The Raspberry Pi is often used as part of another product. This documentation de === One-Time Programmable Settings -[.whitepaper, title="Using the One-Time Programmable Memory on Raspberry Pi Single- Board Computers", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003611-WP/Using-the-One-time-programmable-memory-on-Raspberry-Pi-single-board-computers.pdf] +[.whitepaper, title="Using the One-Time Programmable Memory on Raspberry Pi Single-Board Computers", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003611-WP/Using-the-One-time-programmable-memory-on-Raspberry-Pi-single-board-computers.pdf] **** All Raspberry Pi single-board computers (SBCs) have an inbuilt area of one-time programmable (OTP) memory, which is actually part of the main system on a chip (SoC). As its name implies, OTP memory can be written to (i.e. a binary 0 can be changed to a 1) only once. Once a bit has been changed to 1, it can never be returned to 0. One way of looking at the OTP is to consider each bit as a fuse. Programming involves deliberately blowing the fuse — an irreversible process as you cannot get inside the chip to replace it! -This white paper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. +This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. **** There are a number of OTP values that can be used. To see a list of all the xref:raspberry-pi.adoc#otp-register-and-bit-definitions[OTP values], you can use: diff --git a/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc b/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc index b2921de95..6b11972ad 100644 --- a/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc +++ b/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc @@ -2,7 +2,6 @@ Designed by Raspberry Pi as both a development board, and as a reference design, the xref:raspberry-pi-pico.adoc[Raspberry Pi Pico] series is a family of RP2040-based boards. The Pico family currently consists of Raspberry Pi Pico (far left), Pico H (left), Pico W (right), and Pico WH (far right). - image::images/pico_family.jpg[width="75%"] The design files for Raspberry Pi Pico and Pico W are available openly, with no limitations. @@ -17,3 +16,10 @@ THE DESIGN IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGA === Other Boards Discussions around other third party RP2040-based boards can be found on the https://forums.raspberrypi.com/viewforum.php?f=147[Raspberry Pi forums]. + +[.whitepaper, title="Power switching RP2040 for low standby current applications", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004339-WP/Power-switching-RP2040-for-low-standby-current-applications.pdf] +**** +Even in deep sleep RP2040 draws a typical current of ~180μA, and sleep current is very dependent on PVT: process (current varies from chip to chip), voltage (current varies linearly with voltage), and temperature (current varies nonlinearly with temperature). + +For many use cases where minimal current draw is required, the best option is to power off the system (or the RP2040 part of the system) completely if possible. This application note gives a couple of options for how this can be done, and these circuits are simple enough that a designer can adjust them for their own use case. +**** \ No newline at end of file From 87659e4baa15f541617db454d062e0180ce6a681 Mon Sep 17 00:00:00 2001 From: jehlers42 Date: Fri, 25 Aug 2023 16:58:50 +0100 Subject: [PATCH 2/4] Remove 4S --- documentation/asciidoc/computers/compute-module/datasheet.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/documentation/asciidoc/computers/compute-module/datasheet.adoc b/documentation/asciidoc/computers/compute-module/datasheet.adoc index a84f21793..cceefe8ac 100644 --- a/documentation/asciidoc/computers/compute-module/datasheet.adoc +++ b/documentation/asciidoc/computers/compute-module/datasheet.adoc @@ -14,9 +14,8 @@ There is also a KiCad PCB design set available: * https://datasheets.raspberrypi.com/cm4io/CM4IO-KiCAD.zip[Compute Module 4 IO Board KiCad files] [.whitepaper, title="Transitioning from CM3 to CM4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003469-WP/Transitioning-from-CM3-to-CM4.pdf] -[.whitepaper, title="Transitioning from CM 3 to CM 4S", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003478-WP/Transitioning-from-CM-3-to-CM-4S.pdf] **** -This whitepaper is for those who wish to move from using a Raspberry Pi Compute Module (CM) 1 or 3 to a Raspberry Pi CM 4 or 4S. There are several reasons why this might be desirable: +This whitepaper is for those who wish to move from using a Raspberry Pi Compute Module (CM) 1 or 3 to a Raspberry Pi CM 4. There are several reasons why this might be desirable: • Greater computing power • More memory • Higher-resolution output up to 4Kp60 From 86dc11104b634cfb6a57fa0ed17d9ef0b218a218 Mon Sep 17 00:00:00 2001 From: jehlers42 Date: Thu, 7 Sep 2023 12:46:10 -0700 Subject: [PATCH 3/4] Applying changes --- .../asciidoc/accessories/display/display_intro.adoc | 13 ++----------- .../computers/compute-module/cm-emmc-flashing.adoc | 2 -- .../computers/compute-module/datasheet.adoc | 13 +++---------- .../asciidoc/computers/config_txt/overclocking.adoc | 2 -- .../computers/configuration/hdmi-config.adoc | 4 +--- .../computers/getting-started/setting-up.adoc | 9 --------- .../asciidoc/computers/os/graphics-utilities.adoc | 9 --------- .../computers/raspberry-pi/bcm2711-bootloader.adoc | 11 +---------- .../raspberry-pi/display-parallel-interface.adoc | 4 +--- .../computers/raspberry-pi/power-supplies.adoc | 11 +++++++++-- .../raspberry-pi/raspberry-pi-compliance.adoc | 11 +---------- .../rp2040/rp2040_based_boards.adoc | 7 ------- .../rp2040/technical_specification.adoc | 7 +++++++ 13 files changed, 25 insertions(+), 78 deletions(-) diff --git a/documentation/asciidoc/accessories/display/display_intro.adoc b/documentation/asciidoc/accessories/display/display_intro.adoc index 098021dc4..046338471 100644 --- a/documentation/asciidoc/accessories/display/display_intro.adoc +++ b/documentation/asciidoc/accessories/display/display_intro.adoc @@ -4,9 +4,7 @@ The Raspberry Pi Touch Display is an LCD display which connects to the Raspberry [.whitepaper, title="Implementing a DSI Driver on the Raspberry Pi", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003472-WP/Using-a-DSI-display.pdf] **** -This whitepaper is an introduction to writing a Display Serial Interface (DSI) driver for liquid crystal display (LCD) panels running under the Kernel Mode Setting (KMS) graphics system. It does not cover DSI drivers for the legacy graphics system, or Fake Kernel Mode Setting (FKMS). - -It assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS; Linux), and are fully up to date with the latest firmware and kernels. +This whitepaper is an introduction to writing a Display Serial Interface (DSI) driver for liquid crystal display (LCD) panels running under the Kernel Mode Setting (KMS) graphics system. **** === Board Support @@ -143,11 +141,4 @@ Read our troubleshooting steps, tips, and tricks here: xref:display.adoc#trouble * Outer dimensions: 192.96 × 110.76mm * Viewable area: 154.08 × 85.92mm -* https://datasheets.raspberrypi.com/display/7-inch-display-mechanical-drawing.pdf[Download mechanical drawing (PDF)] - -[.whitepaper, title="Touch Display Enclosure Mechanical Design", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003473-WP/Touch-Display-Enclosure-Mechanical-Design.pdf] -**** -This whitepaper provides information for designing mechanical enclosures for the Raspberry Pi Touch Display. - -The Raspberry Pi Touch Display is dual-source manufactured, and there are very slight differences in the mechanical design between the two manufacturers. This document describes those differences and provides possible mitigation mechanisms for ensuring that enclosure designs can incorporate either version of the panel. For the purposes of this document, the two versions of the panel will be designated 'Supplier A' and 'Supplier B'. Raspberry Pi Ltd will not be publishing the names of the manufacturers used for the liquid crystal display (LCD) panel, or the panel datasheets. -**** \ No newline at end of file +* https://datasheets.raspberrypi.com/display/7-inch-display-mechanical-drawing.pdf[Download mechanical drawing (PDF)] \ No newline at end of file diff --git a/documentation/asciidoc/computers/compute-module/cm-emmc-flashing.adoc b/documentation/asciidoc/computers/compute-module/cm-emmc-flashing.adoc index c7b99758a..067fe4816 100644 --- a/documentation/asciidoc/computers/compute-module/cm-emmc-flashing.adoc +++ b/documentation/asciidoc/computers/compute-module/cm-emmc-flashing.adoc @@ -5,8 +5,6 @@ The CM Provisioner is a web application designed to make programming a large number of Raspberry Pi Compute Module (CM) devices much easier and quicker. It is simple to install and simple to use. It provides an interface to a database of kernel images that can be uploaded, along with the ability to use scripts to customise various parts of the installation during the flashing process. Label printing and firmware updating is also supported. - -This whitepaper assumes that the Provisioner server, software version 1.5 or newer, is running on a Raspberry Pi. **** The Compute Module has an on-board eMMC device connected to the primary SD card interface. This guide explains how to write data to the eMMC storage using a Compute Module IO board. diff --git a/documentation/asciidoc/computers/compute-module/datasheet.adoc b/documentation/asciidoc/computers/compute-module/datasheet.adoc index cceefe8ac..b134b200d 100644 --- a/documentation/asciidoc/computers/compute-module/datasheet.adoc +++ b/documentation/asciidoc/computers/compute-module/datasheet.adoc @@ -15,22 +15,15 @@ There is also a KiCad PCB design set available: [.whitepaper, title="Transitioning from CM3 to CM4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003469-WP/Transitioning-from-CM3-to-CM4.pdf] **** -This whitepaper is for those who wish to move from using a Raspberry Pi Compute Module (CM) 1 or 3 to a Raspberry Pi CM 4. There are several reasons why this might be desirable: -• Greater computing power -• More memory -• Higher-resolution output up to 4Kp60 -• Better availability -• Longer product life (last time buy not before January 2028) - -From a software perspective, the move from Raspberry Pi CM 1/3 to Raspberry Pi CM 4S is relatively painless, as a Raspberry Pi operating system (OS) image should work on all platforms. If, however, you are using a custom kernel, some things will need to be considered in the move. The hardware changes are considerable, and the differences are described in a later section. +This whitepaper is for those who wish to move from using a Raspberry Pi Compute Module (CM) 1 or 3 to a Raspberry Pi CM 4. + +From a software perspective, the move from Raspberry Pi CM 1/3 to Raspberry Pi CM 4 is relatively painless, as Raspberry Pi OS should work on all platforms. **** [.whitepaper, title="Configuring the Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003470-WP/Configuring-the-Compute-Module-4.pdf] **** The Raspberry Pi Compute Module 4 (CM 4) is available in a number of different hardware configurations. Sometimes it may be necessary to disable some of these features when they are not required. -Disabling features also results in power saving, which can be important when CM 4 devices are used in battery environments or similar. - This document describes how to disable various hardware interfaces, in both hardware and software, and how to reduce the amount of memory used by the Linux operating system (OS). **** diff --git a/documentation/asciidoc/computers/config_txt/overclocking.adoc b/documentation/asciidoc/computers/config_txt/overclocking.adoc index e51915f0f..c1ff7e0d6 100644 --- a/documentation/asciidoc/computers/config_txt/overclocking.adoc +++ b/documentation/asciidoc/computers/config_txt/overclocking.adoc @@ -333,8 +333,6 @@ To view the Raspberry Pi's current frequency in KHz, type: `cat /sys/devices/sys [.whitepaper, title="Cooling a Raspberry Pi device", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003608-WP/Cooling-a-Raspberry-Pi-device.pdf] **** This whitepaper goes through the reasons why your Raspberry Pi may get hot and why you might want to cool it back down, and gives various options on achieving that cooling process. - -This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. **** To view the Raspberry Pi's temperature, type `cat /sys/class/thermal/thermal_zone0/temp`. Divide the result by 1000 to find the value in degrees Celsius. Alternatively, there is a vcgencmd, `vcgencmd measure_temp` that interrogates the GPU directly for its temperature. diff --git a/documentation/asciidoc/computers/configuration/hdmi-config.adoc b/documentation/asciidoc/computers/configuration/hdmi-config.adoc index 1c184de80..420d118f6 100644 --- a/documentation/asciidoc/computers/configuration/hdmi-config.adoc +++ b/documentation/asciidoc/computers/configuration/hdmi-config.adoc @@ -17,9 +17,7 @@ NOTE: All the commands are documented fully in the xref:config_txt.adoc#video-op [.whitepaper, title="Troubleshooting KMS HDMI output", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004341-WP/Troubleshooting-KMS-HDMI-output.pdf] **** -With the introduction of the KMS (Kernel Mode Setting) graphics driver, Raspberry Pi Ltd is moving away from legacy firmware control of the video output system and towards a more open source graphics system. This document is intended to help with any issues that might arise when moving to the new system. - -This whitepaper assumes that Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. +With the introduction of the KMS (Kernel Mode Setting) graphics driver, we are moving away from legacy firmware control of the video output system and towards a more open source graphics system. This document is intended to help with any issues that might arise when moving to the new system. **** === HDMI Groups and Mode diff --git a/documentation/asciidoc/computers/getting-started/setting-up.adoc b/documentation/asciidoc/computers/getting-started/setting-up.adoc index 059e7ee9f..d75c837e2 100644 --- a/documentation/asciidoc/computers/getting-started/setting-up.adoc +++ b/documentation/asciidoc/computers/getting-started/setting-up.adoc @@ -20,15 +20,6 @@ For the Raspberry Pi 4 Model B and Raspberry Pi 400, you should use the https:// Finally, you'll need an xref:getting-started.adoc#sd-cards[SD card]; we recommend a minimum of 8GB micro SD card and use the https://www.raspberrypi.com/software/[Raspberry Pi Imager] to install an operating system onto it. -[.whitepaper, title="Transitioning from Pi 3 to Pi 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003475-WP/Transitioning-from-Pi-3-to-Pi-4.pdf] -**** -This whitepaper is for those who wish to move from using a Raspberry Pi 3B+ to the Raspberry Pi 4 device. - -From a software perspective, the move from the Raspberry Pi 3B+ to the Raspberry Pi 4B is relatively painless as a Raspberry Pi operating system (OS) image should work on all platforms. If, however, you are using a custom kernel, there are some things that will need to be considered in the move. - -The hardware changes are more extensive, and the differences are described in a later section. -**** - === Connecting a Display Unless you're setting up your Raspberry Pi to operate xref:configuration.adoc#setting-up-a-headless-raspberry-pi[headless], for regular use, you'll want to plug the Raspberry Pi into a display: either a computer monitor or a television. diff --git a/documentation/asciidoc/computers/os/graphics-utilities.adoc b/documentation/asciidoc/computers/os/graphics-utilities.adoc index 9272f1089..673e2da99 100644 --- a/documentation/asciidoc/computers/os/graphics-utilities.adoc +++ b/documentation/asciidoc/computers/os/graphics-utilities.adoc @@ -141,15 +141,6 @@ Returns the throttled state of the system. This is a bit-pattern - a bit being s Returns the temperature of the SoC as measured by its internal temperature sensor; on Raspberry Pi 4, `measure_temp pmic` returns the temperature of the PMIC. -[.whitepaper, title="Extra PMIC features on Raspberry Pi 4 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004340-WP/Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf] -**** -Raspberry Pi 4 and Raspberry Pi Compute Module 4 devices use a Power Management Integrated Circuit (PMIC) to supply the various voltages required by the various components on the PCB. They also sequence power ups to ensure the devices are started in the correct order. - -Over the duration of production of these models, a number of different PMIC devices have been used on both Raspberry Pi 4 and CM4. All the PMICs have provided extra functionality over and above that of voltage supply. This document describes how to access these features in software. - -This whitepaper assumes that the Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. -**** - ==== measure_clock [clock] This returns the current frequency of the specified clock. The options are: diff --git a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc index 2ff141154..9b0cf636b 100644 --- a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc @@ -244,15 +244,6 @@ The `Customer OTP` rows are OTP registers 36 to 43 in the `vcgencmd otp_dump` ou Default: "" -[.whitepaper, title="Changing MAC addresses", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003474-WP/Changing-MAC-addresses.pdf] -**** -This whitepaper describes how to set a specific media access control (MAC) address on your Raspberry Pi device. It applies to both Ethernet and wireless interfaces. - -Two mechanisms are described, one for devices up to the Pi 3 and one for the Pi 4/400 and CM 4. These latter three devices use the BCM2711 system on a chip (SoC), which has a built-in Ethernet port and hence defines its MAC addresses in a different way. - -This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi operating system (OS), and is fully up to date with the latest firmware and kernels. -**** - ==== Static IP address configuration If TFTP_IP and the following options are set then DHCP is skipped and the static IP configuration is applied. If the TFTP server is on the same subnet as the client then GATEWAY may be omitted. @@ -627,7 +618,7 @@ the BCM2711 system on a chip (SoC). **** This whitepaper describes how to implement secure boot on devices based on Raspberry Pi 4. For an overview of the secure boot implementation, please see the Raspberry Pi 4 Boot Security whitepaper. -This whitepaper assumes that the Raspberry Pi running RPIBOOT is running Raspberry Pi OS (Linux), Bullseye version or later, and is fully up to date with the latest firmware and kernels. The secure boot system is intended for use with buildroot (or similar)-based OS images; using it with Raspberry Pi OS is not recommended or supported. +The secure boot system is intended for use with buildroot (or similar)-based OS images; using it with Raspberry Pi OS is not recommended or supported. **** The following `config.txt` properties are used to program the `secure-boot` OTP settings. These changes are irreversible and can only be programmed via `RPIBOOT` when flashing the bootloader EEPROM image. This ensures that `secure-boot` cannot be set remotely or by accidentally inserting a stale SD card image. diff --git a/documentation/asciidoc/computers/raspberry-pi/display-parallel-interface.adoc b/documentation/asciidoc/computers/raspberry-pi/display-parallel-interface.adoc index 06b40329e..1b52d2743 100644 --- a/documentation/asciidoc/computers/raspberry-pi/display-parallel-interface.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/display-parallel-interface.adoc @@ -2,9 +2,7 @@ [.whitepaper, title="Using a DPI Display on the Raspberry Pi", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003471-WP/Using-a-DPI-display.pdf] **** -Display Parallel Interface (DPI) displays can be connected to Raspberry Pi devices via the 40-pin general-purpose input/output (GPIO) connector as an alternative to using the dedicated Display Serial Interface (DSI) or High-Definition Multimedia Interface (HDMI) ports. Many third-party DPI displays have been made available to take advantage of this. The Buster (and earlier) Raspberry Pi operating system (OS) and the legacy display stack used Raspberry Pi-specific parameters in config.txt to configure DPI displays. With the move to Bullseye and its use of the Kernel Mode Setting (KMS) graphics driver by default, these config.txt entries are no longer relevant as all control of the display pipeline has shifted to the Linux kernel. - -This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi OS (Linux), and is fully up to date with the latest firmware and kernels. +Display Parallel Interface (DPI) displays can be connected to Raspberry Pi devices via the 40-pin general-purpose input/output (GPIO) connector as an alternative to using the dedicated Display Serial Interface (DSI) or High-Definition Multimedia Interface (HDMI) ports. **** An up-to-24-bit parallel RGB interface is available on all Raspberry Pi boards with the 40 way header and the Compute Modules. This interface allows parallel RGB displays to be attached to the Raspberry Pi GPIO either in RGB24 (8 bits for red, green and blue) or RGB666 (6 bits per colour) or RGB565 (5 bits red, 6 green, and 5 blue). diff --git a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc index baf5ece02..7d9ec02ad 100644 --- a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc @@ -121,6 +121,13 @@ This is the typical amount of power (in Ampere) drawn by different Raspberry Pi NOTE: For these measurements we used a standard Raspberry Pi OS image (current as of 26 Feb 2016, or June 2019 for the Raspberry Pi 4), at room temperature, with the Raspberry Pi connected to a HDMI monitor, USB keyboard, and USB mouse. The Raspberry Pi 3 Model B was connected to a wireless LAN access point, the Raspberry Pi 4 was connected to Ethernet. All these power measurements are approximate and do not take into account power consumption from additional USB devices; power consumption can easily exceed these measurements if multiple additional USB devices or a HAT are connected to the Raspberry Pi. +[.whitepaper, title="Extra PMIC features on Raspberry Pi 4 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004340-WP/Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf] +**** +A number of different PMIC devices have been used on both Raspberry Pi 4 and CM4. All the PMICs have provided extra functionality over and above that of voltage supply. This document describes how to access these features in software. + +This whitepaper assumes that your Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. +**** + === Power Supply Warnings On all models of Raspberry Pi since the Raspberry Pi B+ (2014) except the Zero range, there is low-voltage detection circuitry that will detect if the supply voltage drops below 4.63V (+/- 5%). This will result in an entry added to the kernel log. @@ -131,9 +138,9 @@ Voltages can drop for a variety of reasons, for example if the power supply itse [.whitepaper, title="Making a more resilient file system", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003610-WP/Making-a-more-resilient-file-system.pdf] **** -Raspberry Pi Ltd devices are frequently used as data storage and monitoring devices, often in places where sudden power downs may occur. As with any computing device, power dropouts can cause storage corruption. This whitepaper provides some options on how to prevent data corruption under these and other circumstances by selecting appropriate file systems and setups to ensure data integrity. +Raspberry Pi devices are frequently used as data storage and monitoring devices, often in places where sudden power downs may occur. As with any computing device, power dropouts can cause storage corruption. -This whitepaper assumes that the Raspberry Pi is running the Raspberry Pi (Linux) operating system (OS), and is fully up to date with the latest firmware and kernels. +This whitepaper provides some options on how to prevent data corruption under these and other circumstances by selecting appropriate file systems and setups to ensure data integrity. **** === Back-powering diff --git a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc index 311d55333..dcb99e1e9 100644 --- a/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/raspberry-pi-compliance.adoc @@ -20,13 +20,4 @@ The Powered by Raspberry Pi progamme provides a process for companies wanting to === Approved Design Partners -Our list of https://www.raspberrypi.com/for-industry/design-partners/[approved design partners] provide a set of consultancies that we work closely with and support so they can provide paid for design services across hardware, software, and mechanical. - -[.whitepaper, title="Fleet management - A brief introduction", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-003609-WP/Fleet-management-A-brief-introduction.pdf] -**** -The sheer range of applications that the Raspberry Pi devices are suitable for means any one company may have hundreds, thousands, or even tens of thousands of devices in their portfolio. All these devices need to be maintained and, as numbers increase, manual checking becomes extremely inefficient. This is where fleet management software comes into play. - -Raspberry Pi do not provide any sort of fleet management software, this is an area where there is a plethora of existing suppliers. This whitepaper attempts to show what these suppliers can do, and also provides a brief introduction to some that Raspberry Pi know work with Raspberry Pi devices. - -Please note that these are NOT recommendations; Raspberry Pi have not done any deep investigations into any of these products, simply ensured that Raspberry Pi devices are supported. It is down to the individual to ensure that any product or service matches their use case. Please also note that any suppliers listed are not the only suppliers of services that may be appropriate, i.e. the list is not exhaustive. -**** \ No newline at end of file +Our list of https://www.raspberrypi.com/for-industry/design-partners/[approved design partners] provide a set of consultancies that we work closely with and support so they can provide paid for design services across hardware, software, and mechanical. \ No newline at end of file diff --git a/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc b/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc index 6b11972ad..eb45f3943 100644 --- a/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc +++ b/documentation/asciidoc/microcontrollers/rp2040/rp2040_based_boards.adoc @@ -16,10 +16,3 @@ THE DESIGN IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGA === Other Boards Discussions around other third party RP2040-based boards can be found on the https://forums.raspberrypi.com/viewforum.php?f=147[Raspberry Pi forums]. - -[.whitepaper, title="Power switching RP2040 for low standby current applications", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004339-WP/Power-switching-RP2040-for-low-standby-current-applications.pdf] -**** -Even in deep sleep RP2040 draws a typical current of ~180μA, and sleep current is very dependent on PVT: process (current varies from chip to chip), voltage (current varies linearly with voltage), and temperature (current varies nonlinearly with temperature). - -For many use cases where minimal current draw is required, the best option is to power off the system (or the RP2040 part of the system) completely if possible. This application note gives a couple of options for how this can be done, and these circuits are simple enough that a designer can adjust them for their own use case. -**** \ No newline at end of file diff --git a/documentation/asciidoc/microcontrollers/rp2040/technical_specification.adoc b/documentation/asciidoc/microcontrollers/rp2040/technical_specification.adoc index 26197933c..1d43449f1 100644 --- a/documentation/asciidoc/microcontrollers/rp2040/technical_specification.adoc +++ b/documentation/asciidoc/microcontrollers/rp2040/technical_specification.adoc @@ -35,6 +35,13 @@ Key features: ** USB 1.1 controller and PHY, with host and device support ** 8 PIO state machines +[.whitepaper, title="Power switching RP2040 for low standby current applications", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004339-WP/Power-switching-RP2040-for-low-standby-current-applications.pdf] +**** +Even in deep sleep RP2040 draws a typical current of ~180μA, and sleep current is very dependent on PVT: process (current varies from chip to chip), voltage (current varies linearly with voltage), and temperature (current varies nonlinearly with temperature). + +For many use cases where minimal current draw is required, the best option is to power off the system (or the RP2040 part of the system) completely if possible. This application note gives a couple of options for how this can be done, and these circuits are simple enough that a designer can adjust them for their own use case. +**** + === Why is the chip called RP2040? The post-fix numeral on RP2040 comes from the following, From 66827d65bb2381f868d52822e0cb3eb9ba54d79a Mon Sep 17 00:00:00 2001 From: jehlers42 Date: Thu, 14 Sep 2023 12:57:54 -0700 Subject: [PATCH 4/4] Resolving change requests --- .../asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc | 2 +- .../asciidoc/computers/raspberry-pi/power-supplies.adoc | 2 -- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc index 9b0cf636b..c7bb098d8 100644 --- a/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/bcm2711-bootloader.adoc @@ -610,7 +610,7 @@ Default: `1` [.whitepaper, title="Raspberry Pi 4 Boot Security", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004651-WP/Raspberry-Pi-4-Boot-Security.pdf] **** -This white paper describes Raspberry Pi Ltd’s approach to boot security on the Raspberry Pi 4 family of devices, based on +This whitepaper describes Raspberry Pi Ltd’s approach to boot security on the Raspberry Pi 4 family of devices, based on the BCM2711 system on a chip (SoC). **** diff --git a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc index 7d9ec02ad..8bd4a2858 100644 --- a/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc +++ b/documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc @@ -124,8 +124,6 @@ NOTE: For these measurements we used a standard Raspberry Pi OS image (current a [.whitepaper, title="Extra PMIC features on Raspberry Pi 4 and Compute Module 4", subtitle="", link=https://pip.raspberrypi.com/categories/685-whitepapers-app-notes/documents/RP-004340-WP/Extra-PMIC-features-on-Raspberry-Pi-4-and-Compute-Module-4.pdf] **** A number of different PMIC devices have been used on both Raspberry Pi 4 and CM4. All the PMICs have provided extra functionality over and above that of voltage supply. This document describes how to access these features in software. - -This whitepaper assumes that your Raspberry Pi is running Raspberry Pi OS, and is fully up to date with the latest firmware and kernels. **** === Power Supply Warnings