summaryrefslogtreecommitdiff
path: root/include/env
AgeCommit message (Collapse)Author
9 daysinclude: env: ti: Use .env for environment variablesAnurag Dutta
Add omap common environment variables to .env. We retain the old-style C environment .h files to maintain compatibility with other omap devices that have not moved to using .env yet. Signed-off-by: Anurag Dutta <a-dutta@ti.com>
2025-07-22km: pg-wcom-ls102xa: add netdev in board env fileHolger Brunck
Upcoming boards will have different ethernet interfaces. So we move this variable out of the common code. Signed-off-by: Holger Brunck <holger.brunck@hitachienergy.com>
2025-07-22include: env: ti_common: remove bootm_sizeBryan Brattlof
As the size of 64b ARM kernels, DTs, vendor firmware, and initial ram disks continues to grow, the 256MB size limit set aside for image processing by the bootm command has become too small for some K3 reference boards. For ARMv7 removing this limit could introduce issues so move the bootm_size variable to ti_armv7_keystone2.env and remove the limit for any board using a TI K3 SoC. Signed-off-by: Bryan Brattlof <bb@ti.com>
2025-05-07include: env: phytec: k3_net: Use get_cmdDaniel Schultz
'net_fetch_cmd' is not defined by the K3 board files. They use the more common 'get_cmd' from NXP products. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2025-05-07include: env: phytec: k3_net: Remove net_apply_extensionsDaniel Schultz
Extensions are now handled by the board-code. Remove this non-existing function to proper boot from network. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2025-03-26Merge branch 'staging' of ↵Tom Rini
https://source.denx.de/u-boot/custodians/u-boot-tegra into next - More Tegra video improvements
2025-03-19board: ouya: add Ouya Game Console supportSvyatoslav Ryhel
The Ouya microconsole is build on Nvidia Tegra 3 (T33) SoC, featuring a quad-core 1.7 GHz ARM Cortex-A9 CPU and a ULP GeForce GPU, paired with 1GB of DDR3 RAM and 8GB of internal flash storage. Running a modified Android 4.1 (Jelly Bean) OS with a custom launcher, it aimed for open-source gaming via a digital storefront. This implementation is mostly based on upstream Linux device tree and fragments of work done by previous developers. Co-developed-by: Peter Geis <pgwipeout@gmail.com> Signed-off-by: Peter Geis <pgwipeout@gmail.com> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
2025-03-18Merge patch series "*** Various Improvements for phyCORE-AM62/A SoMs ***"Tom Rini
Wadim Egorov <w.egorov@phytec.de> says: This patch series syncs the phyCORE-AM62Ax feature-wise with our other K3-based SoMs by adding SoM overlay handling and capsule updates. It also introduces support for USBDFU boot and includes various minor fixes. Link: https://lore.kernel.org/r/20250305045838.3614661-1-w.egorov@phytec.de
2025-03-18board: phytec: phycore_am62x: Use custom k3_dfu.env fragmentWadim Egorov
TI's k3_dfu.env includes redundant dfu_alt_info_* data, some of which is incompatible with our board configuration. Replace it with a custom variant that better aligns with our setup, ensuring correct offsets and eliminating unnecessary entries. Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
2025-02-20include: configs: omap5: Add support for FDT overlaySinthu Raja
As AM57x uses overlays for display and camera interfaces, add support to load DT overlay files to MMC boot. Signed-off-by: Sinthu Raja <sinthu.raja@ti.com> Signed-off-by: Anurag Dutta <a-dutta@ti.com>
2025-02-14Kconfig: Move CONFIG_BOOTCOUNT_ALTBOOTCMD to KconfigTomas Peterka
Add CONFIG_BOOTCOUNT_ALTBOOTCMD so the developer is able to add custom altbootcmd via Kconfig when they enable BOOTCOUNT. With this now in Kconfig, we need to move it from environment files / config.h files and in to the defconfig file. This was done by generating u-boot-initial-env for all platforms before the Kconfig change, to extract altbootcmd values and then again after to compare the result. [trini: Perform migration to defconfigs, reword commit message] Signed-off-by: Tom Rini <trini@konsulko.com>
2025-02-10include: env: phytec: Add optargs to K3 filesNathan Morrisson
Add the optargs variable so that we can set optional arguments while booting. Signed-off-by: Nathan Morrisson <nmorrisson@phytec.com> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-10-13board: tegra: convert boards to text envSvyatoslav Ryhel
Convert boards to use text based env. This is the first stage of conversion, common inclusions should be converted next. Acked-by: Francesco Dolcini <francesco.dolcini@toradex.com> # Toradex Apalis TK1 Reviewed-by: Simon Glass <sjg@chromium.org> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
2024-10-02Merge patch series "Add Android 14 bootflow support for AM62X and AM62P board"Tom Rini
Guillaume La Roque <glaroque@baylibre.com> says: Ths patchset add support of Android 14 with boot image version 4 for : - AM62X-SK EVM: https://www.ti.com/tool/SK-AM62B - BeaglePlay: https://beagleplay.org/ - AM62PX-SK EVM: https://www.ti.com/tool/SK-AM62P-LP Android Images use to test this series are on the Official TI website: - AM62x/BeaglePlay: https://www.ti.com/tool/PROCESSOR-SDK-AM62X - AM62PX: https://www.ti.com/tool/PROCESSOR-SDK-AM62P
2024-10-02board: ti: am62x_evm: Add android bootflowGuillaume La Roque
Add Android bootflow support for AM62X SK EVM board with new android boot method. To build for AM62x for Android, we use the am62x_a53_android.config fragment when building A53 bootloaders: $ make am62x_evm_a53_defconfig $ make am62x_a53_android.config $ make Co-developed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Reviewed-by: Bryan Brattlof <bb@ti.com>
2024-09-10include: env: phytec: Add K3 boot logic for OSPI/QSPI flashesDaniel Schultz
This boot logic allows to boot a Kernel image, Device-Tree blob and a initramfs from an external OSPI/QSPI NOR flash. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: net: phytec: Add K3 network boot logicDaniel Schultz
This boot logic allows to boot a Kernel image, Device-Tree blob and overlays via tftp/dhcp (configurable with 'net_fetch_cmd'). Additionally, it loads a rootfs via NFS. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: env: phytec: Add raucinit to k3_mmc environmentDaniel Schultz
Initialize the environment for booting an RAUC image when 'doraucboot' is set to 1. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-09-10include: env: phytec: k3_mmc: Rename variablesDaniel Schultz
Add a mmc prefix to 'loadimage' and 'loadfdt' because we need similar variables for other boot sources. This will prevent name clashes and allows to implement similar boot logic. Also switch from loadaddr to kernel_addr_r. Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
2024-07-22include: env: phytec: k3_mmc: Apply overlays during bootDaniel Schultz
Include the overlays.env file and run the apply routine before booting the Kernel. Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: Add common mmc boot for K3 SoMsDaniel Schultz
This environment include can be used to boot from a MMC device for PHYTEC's K3-based SoMs. Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: renaming of variables according to bootstd docBenjamin Hahn
Rename existing environment variables according to the bootstd doc. Renamed variables are fdto_addr, bootenv_addr, fdt_addr. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de> Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-22include: env: phytec: Create env file for loading and applying overlaysBenjamin Hahn
The env scripts for loading and applying overlays are identical for many PHYTEC Boards. Create a common env that can be included. The env variables bootenv_addr and fdto_addr are board specific and need to be set in the board specific file. The env variable get_cmd also needs to be set in board specific files and can be set to tftp or dhcp. Signed-off-by: Benjamin Hahn <B.Hahn@phytec.de> Signed-off-by: Daniel Schultz <d.schultz@phytec.de> Reviewed-by: Teresa Remmet <t.remmet@phytec.de> Reviewed-by: Wadim Egorov <w.egorov@phytec.de>
2024-07-16include: env: ti_common: Remove findfdt from bootcmd_ti_mmcDhruva Gole
findfdt is used by bootcmd_ti_mmc by default which used to help populate the fdtfile. The users of findfdt from bootcmd_ti_mmc have migrated to ti_set_fdt_env for populating fdtfile; Hence, findfdt can be removed from bootcmd_ti_mmc having no-impact for any platform. Remove findfdt to not print out the warning that gets set after calling ti_set_fdt_env. viz. "echo WARN: fdtfile already set. Stop using findfdt in script" Signed-off-by: Dhruva Gole <d-gole@ti.com> Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
2024-07-16include: env: ti: mmc: Change name_fdt usage to fdtfileManorit Chawdhry
name_fdt is kept for backward compatibility but it depends on EEPROM detection logic and some of the TI K3 platforms don't have that anymore which causes boot failure in legacy boot flow using bootcmd_ti_mmc. K2g platforms which uses the same file have their own override causing this change to be no-impact for them. Replacing name_fdt usage to fdtfile as fdtfile is populated based on CONFIG_DEFAULT_DEVICE_TREE after using ti_set_fdt_env. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
2024-06-13env: ti: k3_dfu: Drup mmcpart for rootfsNeha Malcom Francis
According to [0], raw access to mmc should not have mmcpart in the entry. This was fixed in k3_dfu_combined.env but k3_dfu.env had been overlooked. [0] doc/usage/dfu.rst Fixes: 53b406369e9d ("DFU: Check the number of arguments and argument string strictly") Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
2024-06-07include: env: ti: Add support for secure firmwaresUdit Kumar
Secure firmwares must be loaded if SOC is secure, currently rproc framework chooses non-secure firmware always. So adding support to load secure firmware, when SOC is secure Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Udit Kumar <u-kumar1@ti.com> Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
2024-05-07arch: arm: Add Analog Devices SC5xx machine typeNathan Barrett-Morrison
Add support for the SC5xx machine type from Analog Devices. This includes support for the SC57x, SC58x, SC59x, and SC59x-64 SoCs, which have many common features such as common ADI IP blocks, and SHARC DSP cores. This commit introduces core functionality required for all boards using an SC5xx SoC, such as: - SPL configuration - Required CPU hooks such as reset - Boot ROM interaction to load the stage 2 bootloader in the reference configuration. Other options are possible but not officially supported at this time - SoC-common configuration expected to be reused by all boards - Early initialization for system clocks and DDR controller Co-developed-by: Greg Malysa <greg.malysa@timesys.com> Signed-off-by: Greg Malysa <greg.malysa@timesys.com> Co-developed-by: Ian Roberts <ian.roberts@timesys.com> Signed-off-by: Ian Roberts <ian.roberts@timesys.com> Signed-off-by: Vasileios Bimpikas <vasileios.bimpikas@analog.com> Signed-off-by: Utsav Agarwal <utsav.agarwal@analog.com> Signed-off-by: Arturs Artamonovs <arturs.artamonovs@analog.com> Signed-off-by: Nathan Barrett-Morrison <nathan.morrison@timesys.com>
2024-03-17include: env: Add phytec RAUC boot logicLeonard Anderweit
Add logic for booting systems with the RAUC update mechanism. This can be reused by other phytec boards. Signed-off-by: Leonard Anderweit <l.anderweit@phytec.de> Tested-by: Teresa Remmet <t.remmet@phytec.de>
2024-02-20include: env: ti: Drop default_findfdtNishanth Menon
We shouldn't need finfdt anymore. Drop the env script. Reviewed-by: Jonathan Humphreys <j-humphreys@ti.com> Reviewed-by: Roger Quadros <rogerq@kernel.org> Signed-off-by: Nishanth Menon <nm@ti.com>
2024-01-18include: env: ti: add default for do_main_cpsw0_qsgmii_phyinitManorit Chawdhry
By default this variable is unset and this causes the test condition to fail on devices that don't have this defined. Set a default value for this. => boot ## Error: "main_cpsw0_qsgmii_phyinit" not defined [...] Fixes: 0d72b0f2f83b ("include: env: ti: ti_common: Run main_cpsw0_qsgmii_phyinit conditionally") Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2024-01-18include: env: ti: ti_common: Fix a missing semicolonManorit Chawdhry
Fix a missing semicolon that leads to syntax error while booting j721s2. Importing environment from mmc1 ... syntax error at 'run'HUSH died! Fixes: 0d72b0f2f83b ("include: env: ti: ti_common: Run main_cpsw0_qsgmii_phyinit conditionally") Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-12-21include: env: ti: ti_common: Run main_cpsw0_qsgmii_phyinit conditionallyManorit Chawdhry
The main_cpsw0_qsgmii_phyinit command is defined only for certain TI SoCs which have the do_main_cpsw0_qsgmii_phyinit variable set. Add a check to ensure that the main_cpsw0_qsgmii_phyinit command is run only for such SoCs. Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-11-10tree-wide: Replace http:// link with https:// link for ti.comNishanth Menon
Replace instances of http://www.ti.com with https://www.ti.com Signed-off-by: Nishanth Menon <nm@ti.com>
2023-10-02Merge branch 'next'Tom Rini
Signed-off-by: Tom Rini <trini@konsulko.com>
2023-09-28env: ti: ti_common.env: Fix get_overlaystring for FIT ImageManorit Chawdhry
After the refactor with conf- nodes in fitImage, overlaystring wasn't didn't handle the new conf- nodes in FIT Booting. Fix get_overlaystring to handle conf- nodes. Fixes: 837833a724b7 ("environment: ti: Add get_fit_config command to get FIT config string") Reported-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Reviewed-by: Andrew Davis <afd@ti.com>
2023-09-08include: env: ti: Add a generic default_findfdt.envNishanth Menon
ti_mmc bootmethod uses a findfdt routine that is expected to be implemented by all platforms. Define a default findfdt based on configured DEFAULT_DEVICE_TREE option for u-boot. This saves duplication across multiple boards and handles architecture folder location changes centrally. TI ARMV7 platforms will need to override default_device_tree_subarch in the env file to point to the appropriate platform. Note: default "omap" is used to cater to "most common" default. Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-08include: env: ti: ti_armv7_common.env: Rename to ti_common.envNishanth Menon
ti_armv7_common does not make any more sense as it is used by armv7 and armv8 TI based platforms. Reported-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Reviewed-by: Tom Rini <trini@konsulko.com> Tested-by: Mattijs Korpershoek <mkorpershoek@baylibre.com> Signed-off-by: Nishanth Menon <nm@ti.com>
2023-09-08include: env: ti: mmc: envboot: Only attempt boot.scr if BOOTSTD is not enabledNishanth Menon
'script' bootmethod that should be used with CONFIG_BOOTSTD. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-09-08include: env: ti: mmc: envboot/mmcboot: Check result of mmc dev before ↵Nishanth Menon
proceeding If mmc dev reports that the device is not present, there is no point in proceeding further to attempt to load the files. Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
2023-08-09x86: Add a common include for environment settingsSimon Glass
Create a text-file version of x86-common.h which can be used by x86 boards. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
2023-08-09env: Use include/env for text-environment includesSimon Glass
The 'environment' word is too long. We mostly use 'env' in U-Boot, so use that as the name of the include directory too. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
generated by cgit v1.2.3 (git 2.0.4) at 2025-09-17 15:02:27 +0000