u-boot.git/include/environment, branch v2020.07-rc1

env: ti: boot: Fix Android boot on AM57x EVM

2020-03-03T07:38:14+00:00

When applying DTBO on top of DTB (with "fdt apply" command) on AM57x EVM
board, there is not enough memory reserved in RAM for DTB blob. Hence,
DTBO can't be merged in DTB. It leads to inability to boot Android with
next error message:

    failed on fdt_overlay_apply(): FDT_ERR_NOSPACE

To overcome that issue let's provide 512 KiB of space to keep DTB and
all merged DTBO blobs. To do so, "length" parameter should be specified
for "fdt addr" command:

    => fdt addr $fdtaddr 0x80000

512 KiB is the maximum size we can use for this, because next address
after $fdtaddr is 512 KiB ahead of it:

    fdtaddr=0x88000000
    rdaddr=0x88080000

Also add size variables to 'adtimg' command invocations, to avoid
cluttering the console with DTBO blob sizes.

Signed-off-by: Sam Protsenko 
Reviewed-by: Eugeniu Rosca

arm: ti: boot: Use correct dtb and dtbo on Android boot

2020-02-04T03:37:24+00:00

Read correct dtb blob from boot.img/recovery.img and apply correct dtbo
blobs from dtbo partition.

Signed-off-by: Sam Protsenko 
Signed-off-by: Lokesh Vutla

env: ti: boot: Boot Android with dynamic partitions

2020-02-04T03:37:24+00:00

Changes:
  - use boot.img instead of boot_fit.img
  - use .dtb from boot.img v2
  - implement recovery boot
  - always boot ramdisk from boot.img, we can't mount system as root
    now, as system is a logical partition inside of super partition
  - don't add "skip_initramfs" to cmdline anymore
  - to boot into recovery, use boot image from recovery partition
  - prepare partition table:
    - A/B scheme
    - use 'super' partition instead of 'system' and 'vendor'
    - add dtbo partitions
    - introduce metadata partition

Not implemented: reading and applying dtbo blobs from dtbo partition.

Signed-off-by: Sam Protsenko 
Signed-off-by: Lokesh Vutla

env: ti: boot: Respect slot_suffix in AVB commands

2020-02-04T03:37:24+00:00

Signed-off-by: Sam Protsenko 
Signed-off-by: Lokesh Vutla

configs: ti: Factor out call to 'args_mmc' into MMC common environment

2020-01-20T04:40:28+00:00

Both 'loadfit' and 'mmcloados' start with a call to 'args_mmc' so this
can be factored out to before eithers only call site. This also allows us
to remove that call from 'loadfit', which should not have been calling it
anyway as that command should not be MMC specific. Without the call to
'args_mmc' the command 'loadfit' becomes just a call to 'run_fit' so
remove the indirection and call 'run_fit' directly, this removes the need
for 'loadfit' command (which was misnamed anyway). Drop it.

Signed-off-by: Andrew F. Davis 
Reviewed-by: Lokesh Vutla 
Signed-off-by: Lokesh Vutla

board: ti: beagleboneai: enable in am57xx_evm_defconfig

2020-01-20T04:40:28+00:00

Adding the configurations to the evm_defconfig file

Signed-off-by: Jason Kridner 
Signed-off-by: Caleb Robey 
Signed-off-by: Lokesh Vutla

environment: ti: Add DFU environment variables k3_dfu.h

2020-01-20T04:40:28+00:00

Setup env variables for updating firmwares on eMMC/OSPI/MMC via DFU

Signed-off-by: Vignesh Raghavendra 
Signed-off-by: Lokesh Vutla

mtd: rename CONFIG_NAND -> CONFIG_MTD_RAW_NAND

2019-12-04T04:04:10+00:00

Add more clarity by changing the Kconfig entry name.

Signed-off-by: Miquel Raynal 
[trini: Re-run migration, update a few more cases]
Signed-off-by: Tom Rini 
Reviewed-by: Boris Brezillon

env: ti: Add environment variables to boot from UFS

2019-10-24T00:47:12+00:00

Add environment variables to boot kernel from a filesystem contained in
the 2nd UFS LUN. The user can boot from a ufs filesystem just by
entering the following commands.

=> setenv boot ufs
=> boot

Signed-off-by: Faiz Abbas

env: ti: k3_rproc: Add common rproc environment variables

2019-10-11T14:07:35+00:00

Add a new file include/environment/ti/k3_rproc.h that defines
common environment variables useful for booting various remote
processors from U-Boot. This file is expected to be included in
the board config files with the EXTRA_ENV_RPROC_SETTINGS added
to CONFIG_EXTRA_ENV_SETTINGS and DEFAULT_RPROCS macro overwritten
to include the actual list of processors to be booted.

The 'boot_rprocs' variable just needs to be added to the board's
bootcmd to automatically boot the processors, and runtime control
can be achieved through the 'dorprocboot' variable.

The variables are currently defined to use MMC as the boot media,
and can be expanded in the future to include other boot media.
The immediate usage is intended for K3 J721E SoCs.

Signed-off-by: Jean-Jacques Hiblot 
Signed-off-by: Suman Anna