summaryrefslogtreecommitdiffstats
path: root/recipes-bsp
Commit message (Collapse)AuthorAgeFilesLines
* raspberrypi-firmware: Update to 2021-02-25Mike Looijmans2021-03-161-3/+3
| | | | | | | | | This version is compatible with the 5.10.17 kernel https://github.com/raspberrypi/firmware/commit/5985247fb75681985547641d66196c77499f26b9 Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl> (cherry picked from commit 0b4a73ebad2d0d81632df7c68e5f57bbd1f6004d) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-cmdline: remove unnecessary spaces from cmdline.txtBartłomiej Burdukiewicz2021-03-161-1/+1
| | | | | | | | | | | | With current recipe formatting CMDLINE variable contains many unnecessary white spaces. This patch allow to drop unnecessary spaces at the moment of writing them to cmdline.txt. This will improve readability of cmdline.txt, /proc/cmdline and dmesg output. Signed-off-by: Bartłomiej Burdukiewicz <bartlomiej.burdukiewicz@gmail.com> (cherry picked from commit f5fe02c30cc82e3f47c36de76d7b73d2482018bf) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* raspberrypi-firmware.inc: upgrade to latest for 5.10.13 kernelMartin Jansa2021-03-161-3/+3
| | | | | | | | https://github.com/raspberrypi/firmware/commit/7d91570f20378afc9414107dccdad70705a8a342 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> (cherry picked from commit b52d47c048c524d1a0ccb3c6ee99141561668b93) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-config: Add support for CM4 host USBAurelian Zanoschi2021-03-161-0/+6
| | | | | | | | | | By default in case of CM4 IO board, the USB ports (header + built-in) are disabled. In order to enable them the DWC2 mode needs to be set to host. Signed-off-by: Aurelian Zanoschi <aurelian17@gmail.com> (cherry picked from commit 71938572843428cb881948e8151742d8493ee89e) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-config: use CONFIG shell variableMartin Jansa2021-03-161-73/+74
| | | | | | | | | * instead of repeating //config.txt so many times, to make it a bit less error prone (as shown in previous commit) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> (cherry picked from commit 17eb1a2f00b6d15c073e318181ab0d34b1b5c965) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-config: fix do_deployMartin Jansa2021-03-161-1/+1
| | | | | | | | | * in https://github.com/agherzan/meta-raspberrypi/pull/678 this line was acidentally changed from "${BOOTFILES_DIR_NAME}" to "bcm2835-bootfiles", causing do_deploy to fail finding config.txt Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> (cherry picked from commit 5c9309de874a42291d19f8e03169ea00eab4a655) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-config: Relocated "start_x=1" in config.txtSCVready2021-03-161-2/+5
| | | | | | | | | It seems like "start_x=1" needs to be earlier in the file to work properly on the Rapberry Pi 4 B. Fixes: #670 Signed-off-by: SCVready <alejandro.solozabal@outlook.com> (cherry picked from commit 74deec51ded5b22b31b69b30537a6e9ed0997aea) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-bootfiles: Rename recipe to avoid ambiguityPaul Barker2021-03-161-0/+0
| | | | | | | | | The name `bootfiles` is too generic, we should use `rpi-bootfiles` instead. Signed-off-by: Paul Barker <pbarker@konsulko.com> (cherry picked from commit ba3a417fbbccb5f6af9ac036eac97c87dcf4c1b7) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* bootfiles: Use BOOTFILES_DIR_NAME variablePaul Barker2021-03-161-6/+6
| | | | | | | | | | | This variable is set in rpi-base.inc and referenced by other recipes which need to know the location of the bootfiles. If this is overridden for any reason we need to ensure that the bootfiles recipe deploys to the correct path. Signed-off-by: Paul Barker <pbarker@konsulko.com> (cherry picked from commit b8440b3d26fc0b59acd48ed6f3e39e00cd867f6c) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-cmdline: Move cmdline.txt generation to a separate recipePaul Barker2021-03-162-2/+51
| | | | | | | | | | | | | | | | | Instead of generating cmdline.txt in the kernel recipe, it is generated in a standalone recipe and pulled in as a dependency of the bootfiles recipe. This simplifies the process of using a linux-yocto, linux-mainline or similiar kernel recipe instead of linux-raspberrypi. In the rpi-cmdline recipe the command line is built from fragments which can all be easily overridden. The variables `SERIAL` and `CMA` are renamed to `CMDLINE_SERIAL` and `CMDLINE_CMA` for consistency. The cmdline.txt file is created in the do_compile step to allow further customisation via do_compile_append if needed. Signed-off-by: Paul Barker <pbarker@konsulko.com> (cherry picked from commit 8827040d9c218f68ae3ee6a5814929888ed61581) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* rpi-u-boot-scr: drop hard-coded 'arm'Ming Liu2021-03-161-2/+2
| | | | | | | | | Let's inherit kernel-arch and use ${UBOOT_ARCH} to replace the hard-coded 'arm'. Signed-off-by: Ming Liu <liu.ming50@gmail.com> (cherry picked from commit 26a888d669b2d73c251c9107bd7e9871751a1ab6) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* armstubs: Always use gcc compilerKhem Raj2021-03-161-0/+2
| | | | | | | | | | | | | | it uses assembly files .S which needs to be processed with gcc alone until they are made portable use gcc Fixes | armstub7.S:175:2: error: instruction requires: thumb | cbz r6, 9f @ Skip this section if we are core 0 | ^ Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit 5db97b41a84296d4bbc8fd7ffc228124af774cf1) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* raspberrypi-tools: Update to latest on masterKhem Raj2021-03-161-3/+3
| | | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit dcdd0e4a20d8eb87e03ac492dbf308c34bef92e4) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* raspberrypi-firmware: Update to latest to take 5.4.79 prebuiltsKhem Raj2021-03-161-3/+3
| | | | | | Signed-off-by: Khem Raj <raj.khem@gmail.com> (cherry picked from commit 6a53db2fb689d372c6acbb429f1a2211eca40aa5) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* libcamera: Enabled camera overlays define basedMadhavan Krishnan2021-03-161-0/+6
| | | | | | | | | | | | | | | Added imx219.dtbo file in the overlays, and added dtoverlay in /boot/config.txt define based. To enable Sony Raspberry pi camera imx219 sensor, need to set the variable RASPBERRYPI_CAMERA_V2 as 1. In future, we can add any camera overlays here to support and use them with libcamera. Signed-off-by: Madhavan Krishnan <madhavan.krishnan@linaro.org> (cherry picked from commit b70c7b9021e37ec765f4db9aac0e0e76f617cbac) Signed-off-by: Ricardo Salveti <ricardo@foundries.io>
* u-boot: Fix booting raspberrypi CM3 moduleMarek Belisko2020-10-212-0/+54
| | | | | | | | | With stock u-boot v2020.01 which we use from poky CM3 module won't boot. We need to apply this patch in order to have platform again working. Add it only for cm3 to not break anything else. Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
* raspberrypi-tools: Update to latest snapshot as of 20200803Khem Raj2020-10-051-4/+4
| | | | | | Use date in PV, makes is good candidate for always increasing PV Signed-off-by: Khem Raj <raj.khem@gmail.com>
* raspberrypi-firmware: Update to 20201002 snapshotKhem Raj2020-10-051-3/+3
| | | | | | | | | Brings in fixes for errors seen in kernel boot log e.g. https://github.com/raspberrypi/linux/issues/3878 Signed-off-by: Khem Raj <raj.khem@gmail.com>
* raspberrypi-{firmware,tools}: set downloadfilenameMartin Jansa2020-09-172-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * otherwise we end with big archives in downloads directory without clear indication from where they came * e.g. in one of my jenkins builds I've noticed: -rw-rw-r-- 1 jenkins jenkins 178M Jun 30 15:45 downloads/23548e550a757d368d3d5220373fe829b5961c42.tar.gz -rw-rw-r-- 1 jenkins jenkins 152M Sep 5 2019 downloads/7163480fff007dc98978899b556dcf06f8a462c8.tar.gz -rw-rw-r-- 1 jenkins jenkins 179M Jul 23 01:34 downloads/7e74bcb4f9706f36f752d1c3d3164628ccf2aae5.tar.gz -rw-rw-r-- 1 jenkins jenkins 178M Jun 5 12:34 downloads/7eff9f6774bb43bfd61e749a0b45ffddc98c2311.tar.gz -rw-rw-r-- 1 jenkins jenkins 177M Apr 23 14:49 downloads/84523e0b9a9e78aa69fca1f1a8d75b2bdb5155fc.tar.gz -rw-rw-r-- 1 jenkins jenkins 178M Jan 13 2020 downloads/9d6be5b07e81bdfb9c4b9a560e90fbc7477fdc6e.tar.gz -rw-rw-r-- 1 jenkins jenkins 463 Jul 1 03:58 downloads/23548e550a757d368d3d5220373fe829b5961c42.tar.gz.done -rw-rw-r-- 1 jenkins jenkins 141 Jan 16 2020 downloads/7163480fff007dc98978899b556dcf06f8a462c8.tar.gz.done -rw-rw-r-- 1 jenkins jenkins 463 Aug 1 15:40 downloads/7e74bcb4f9706f36f752d1c3d3164628ccf2aae5.tar.gz.done -rw-rw-r-- 1 jenkins jenkins 463 Jun 6 09:54 downloads/7eff9f6774bb43bfd61e749a0b45ffddc98c2311.tar.gz.done -rw-rw-r-- 1 jenkins jenkins 463 May 16 03:35 downloads/84523e0b9a9e78aa69fca1f1a8d75b2bdb5155fc.tar.gz.done -rw-rw-r-- 2 jenkins jenkins 141 Aug 7 22:10 downloads/9d6be5b07e81bdfb9c4b9a560e90fbc7477fdc6e.tar.gz.done * unfortunately using git fetcher is still problematic because of git repo size: 15G firmware 1,6G tools -rw-rw-r-- 1 jenkins jenkins 180M Sep 17 13:59 downloads/raspberrypi-firmware-a490197f0672d948860b2b807884ae65eabc4d4f.tar.gz -rw-rw-r-- 1 jenkins jenkins 463 Sep 17 14:09 downloads/raspberrypi-firmware-a490197f0672d948860b2b807884ae65eabc4d4f.tar.gz.done -rw-rw-r-- 1 jenkins jenkins 324M Sep 17 14:10 downloads/raspberrypi-tools-b0c869bc929587a7e1d20a98e2dc828a24ca396a.tar.gz -rw-rw-r-- 1 jenkins jenkins 463 Sep 17 14:10 downloads/raspberrypi-tools-b0c869bc929587a7e1d20a98e2dc828a24ca396a.tar.gz.done Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-09-121-3/+3
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: Upgrade to 20200819Khem Raj2020-08-241-4/+3
| | | | | | Includes 5.4.59 bumps Signed-off-by: Khem Raj <raj.khem@gmail.com>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-08-131-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* Generalize the naming of the bootfiles deploy directoryJeff Ithier2020-08-062-75/+75
| | | | | | | | | | The raspberry pi 4 variant has a BCM2711 chip, however it still uses the same boot files as the BCM2835 used in previous generations. This change generalizes the naming of the directory generated in the $DEPLOY_DIR to avoid the implication that the files are only meant for the BCM2835. Signed-off-by: Jeff Ithier <ithijme@gmail.com>
* rpi-config: Add CAN_OSCILLATOR variable to set mcp2515 crystal frequencyJakub Luzny2020-07-291-3/+5
| | | | | | Current configuration (16MHz) is made for the PiCAN2 board that uses 16MHz crystal. This setting allows for use of Waveshare RS485 CAN HAT that has 8MHz crystal soldered (although according to Waveshare there is also a 12MHz crystal version of the board). Signed-off-by: Jakub Luzny <jakub@luzny.cz>
* u-boot: Move fw_env.config to u-boot appendFabio Berton2020-07-272-12/+11
| | | | | | | | | | | | | | The u-boot-env is provided by u-boot recipe and not by libubootenv, so right recipe to append is the u-boot. Adding the rpi-u-boot-scr in DEPENDS variable is wrong because it is forcing rpi-u-boot-scr to be a dependency, but it'll fail if I have another recipe that provides bootscript, once both recipes provide the same file. The default value of u-boot-default-script is rpi-u-boot-scr, so right way is to use u-boot-default-script and change the PREFERRED_PROVIDER_u-boot-default-script if needed. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
* rpi-config_git: Added ENABLE_DUAL_CAN build configurationcolin2020-07-231-1/+6
| | | | | | | | | | Currently ENABLE_CAN adds mcp2525-can0 to the dtoverlay. ENABLE_DUAL_CAN was added to also add mcp2515-can1 to the dtoverlay. This will allow a user to enable dual CAN when using a hat like the PiCAN 2 Duo board. Signed-off-by: Colin McAllister <colinmca242@gmail.com>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-07-141-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* libubootenv_%.bbappend: Add fw_env.configLeon Anavi2020-07-032-0/+13
| | | | | | | | | Add fw_env.config that uses at run-time /boot/uboot.env generated through the boot scripts (specifically boot.cmd.in) from recipe rpi-u-boot-scr. This configuration file is required to successfully run fw_printenv from the user space. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* rpi-u-boot-scr: Create uboot.env via boot.cmd.inLeon Anavi2020-07-031-0/+1
| | | | | | | | Modify boot.cmd.in from recipe rpi-u-boot-scr to create uboot.env in the /boot partition when using U-Boot. This change is required to successfully run fw_printenv from the user space. Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* rpi-config: Add ENABLE_IR variable for infraredLeon Anavi2020-06-241-0/+9
| | | | | | | | | | | | | | Users who want infrared device tree overlays gpio-ir and gpio-ir-tx to be set in config.txt can now easily do it through variable ENABLE_IR, for example in local.conf: ENABLE_IR = "1" By default the GPIO pin for gpio-ir is set to 18 and the pin for gpio-ir-tx is 17. Both pins can be easily changed by modifying variables GPIO_IR and GPIO_IR_TX (for example in local.conf). Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-06-051-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-05-091-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-04-181-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* rpi-u-boot-scr: Set u-boot-default-script as providerFabio Berton2020-04-032-1/+3
| | | | | | | | | Add u-boot-default-script to the PROVIDES variable to make easier to replace boot script in another layer just by changing PREFERRED_PROVIDER_u-boot-default-script variable. Set rpi-u-boot-scr as the default provider for meta-raspberrypi. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-03-271-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-03-081-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: update to current HEADPierre-Jean Texier2020-02-241-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* raspberrypi-firmware: bump to version 20200205Pierre-Jean Texier2020-02-081-4/+4
| | | | Signed-off-by: Pierre-Jean Texier <pjtexier@koncepto.io>
* Add support for PiTFT 2.8" with capacitive touchErik Botö2020-01-141-0/+6
| | | | | | | | Add support for the Adafruit PiTFT Plus 320x240 2.8" TFT with Capacitive Touchscreen, using the same patterns used for the other versions of the PiTFT screens. Signed-off-by: Erik Botö <erik.boto@gmail.com>
* armstubs: Define the new symbols use in MakefileAndrei Gherzan2020-01-141-0/+4
| | | | | | | | The tools repository renamed the CC, LD etc symbols to CC7, LD7 etc. See: https://github.com/raspberrypi/tools/commit/b0c869bc929587a7e1d20a98e2dc828a24ca396a Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-tools: Update to current HEADAndrei Gherzan2020-01-141-3/+3
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware: Update to current HEADAndrei Gherzan2019-12-202-5/+5
| | | | | | | | | | | | This RaspberryPi firmware update includes a change in the license file as well[1]. This change is for supporting customisation program. [1] https://github.com/raspberrypi/firmware/commit/dd9e9ebb5d5306e91acb135db890cf18f3a5eea2 As a result of this change, we update the hash in the bcm2835-bootfiles recipe as well. Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-tools: Update to current HEADAndrei Gherzan2019-11-081-3/+3
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* raspberrypi-firmware: Update to current HEADAndrei Gherzan2019-11-081-4/+4
| | | | Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
* bcm2835-bootfiles: Clarify license conditionsPaul Barker2019-10-241-1/+1
| | | | | | | We define a new 'Broadcom-RPi' license and include the full text in our custom-licenses directory. Signed-off-by: Paul Barker <paul@betafive.co.uk>
* armstubs: License is BSD-3-ClausePaul Barker2019-10-241-1/+1
| | | | | | | | All source files in the armstubs directory have a 3-clause BSD license. The Makefile doesn't appear to use any files from outside this directory during the build. Signed-off-by: Paul Barker <paul@betafive.co.uk>
* linux-raspberrypi=4.19.80 bcm2835-bootfiles=20191021Martin Jansa2019-10-241-4/+4
| | | | | | | | | * Upgrade the kernel to latest with corresponding firmware. * This VC4 firmware is compatible with network boot described here: https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/raspberry_pi4_network_boot_beta.md Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* u-boot: drop patches for RPi4 merged upstream.Patrick Vacek2019-10-2310-511/+0
| | | | Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
* bcm2835-bootfiles: tighten up dep on rpi-configChris Laplante2019-10-091-0/+2
| | | | | | | | | | Intuitively, bcm2835-bootfiles:do_deploy should depend on rpi-config:do_deploy. This indirectly resolves a missing dep between rpi-config:do_deploy and do_image_rpi_sdimg (on an image recipe inheriting from sdcard_image-rpi.bbclass). This manifested as changes to rpi-config (e.g. setting or unsetting ENABLE_* variables) not triggering a rebuild of the SD card image. Signed-off-by: Chris Laplante <mostthingsweb@gmail.com>
* u-boot-fw-utils: apply the same rpi4 patches as for u-boot recipeMartin Jansa2019-09-093-12/+16
| | | | | | | | | | | | | | | | * otherwise u-boot-fw-utils build for rpi4 fails with: scripts/kconfig/conf --defconfig=arch/../configs/rpi_4_defconfig Kconfig *** *** Can't find default configuration "arch/../configs/rpi_4_defconfig"! *** scripts/kconfig/Makefile:128: recipe for target 'rpi_4_defconfig' failed * cannot include/require u-boot_2019.07.bbappend directly in u-boot-fw-utils_2019.07.bbappend, because then it fails with: "u-boot_2019.01.bbappend: not a BitBake file" Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>