| Age | Commit message (Collapse) | Author |
|---|
|
Increase the SPL_MAX_SIZE to 0x6ce00 as J7AEN SRAM has larger
loadable memory space for SBL (0x7e000).
This also ensures that the SPL does not go beyond the limit while
having a single defconfig for different boot modes.
Correspondingly, increase CONFIG_SPL_BSS_START_ADDR from 0x43c4b000
to 0x43c7b000 ensuring no overlap in memory.
SRAM memory allocation map:
┌─────────────────────────────────────┐ (0x43c00000)
│ SPL (0x6ce00) │
├─────────────────────────────────────┤ (0x43c6ce00)
│ EMPTY (0x50) │
├─────────────────────────────────────┤ (0x43C6CE50)
│ STACK │
│ SPL_SIZE_LIMIT_PROVIDE_STACK=0x5000 │
├─────────────────────────────────────┤ (0x43C71E50)
│ Global data │
│ sizeof(struct global_data) = 0x1ac |
| (+0x4) │
├─────────────────────────────────────┤ (0x43C72000)
│ HEAP │
│ CONFIG_SYS_MALLOC_F_LEN = 0x9000 │
├─────────────────────────────────────┤ CONFIG_SPL_BSS_START_ADDR
│ SPL BSS │ (0x43c7b000)
│ CONFIG_SPL_BSS_MAX_SIZE = 0x3000 │
├─────────────────────────────────────┤ (0x43c7e000)
│ ROM Boot parameter table │
└─────────────────────────────────────┘CONFIG_SYS_K3_BOOT_PARAM_TABLE_INDEX
(0x43c7f290)
Fixes: b5d58d70642f ("configs: introduce configs needed for the J722S")
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
|
|
We need the I2C GPIO drivers to detect expansion cards.
Gets rid of below error message at R5 SPL on AM64-EVM
"Failed to lookup gpio gpio@38_0: -22"
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
Adds the default config for K3_OPP_LOW in J7200
Reviewed-by: Udit Kumar <u-kumar1@ti.com>
Signed-off-by: Reid Tonking <reidt@ti.com>
|
|
Introduce the initial configs needed to support the J722S SoC family.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
|
|
RC Release 09.01.00.008
|
|
Disable CONFIG_SPL_LOAD_FIT_APPLY_OVERLAY, this is not required nor used
on verdin am62, disable it to save precious binary size.
Update defconfig using savedefconfig, this adds CONFIG_OF_LIBFDT_OVERLAY
explicitly.
Upstream-Status: Submitted [https://lore.kernel.org/all/20231211134520.162773-1-francesco@dolcini.it/]
Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Signed-off-by: Emanuele Ghidoli <emanuele.ghidoli@toradex.com>
|
|
Size of malloc was standardized to 2M for all am6*_r5_*_defconfigs, but
USB MSC defconfig was missed, update this config option now.
Fixes: 794614311a6 (configs: am6*_r5_defconfig: Standardize SPL_STACK_R_MALLOC_SIMPLE_LEN to 2M)
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
|
|
Size of malloc was standardized to 2M for all am6*_r5_defconfigs, but
USB DFU defconfig was missed, update this config option now.
The following warning can be seen with usb-dfu boot:
SPL possible initial stack overflow detected!!
so increase SIZE_LIMIT_PROVIDE_STACK to match the default defconfig.
Fixes: 794614311a6 (configs: am6*_r5_defconfig: Standardize SPL_STACK_R_MALLOC_SIMPLE_LEN to 2M)
Fixes: beee2418683 (configs: am62ax: Add a new USB DFU defconfig)
Signed-off-by: Judith Mendez <jm@ti.com>
|
|
Size of malloc was standardized to 2M for all am6*_r5_defconfigs, but
USB DFU defconfig was missed, update this config option now.
Fixes: 794614311a6 (configs: am6*_r5_defconfig: Standardize SPL_STACK_R_MALLOC_SIMPLE_LEN to 2M)
Signed-off-by: Judith Mendez <jm@ti.com>
|
|
Enable UHS support in the am62p5 defconfigs, allowing us to enter
the UHS modes for mmc1.
Signed-off-by: Judith Mendez <jm@ti.com>
|
|
Enable AVS in config and probing of AVS node.
Signed-off-by: Udit Kumar <u-kumar1@ti.com>
|
|
Increasing SPL_STACK_R_MALLOC_SIMPLE_LEN to 16M seems to break
USB DFU boot. The default of 4M seems to be OK for NAND case
as well so stick to defaults.
Reported-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Fixes: b1ba64d9bab0 ("configs: am64x_evm_a53_defconfig: add SPL_LOAD_FIT_APPLY_OVERLAY")
Signed-off-by: Roger Quadros <rogerq@kernel.org>
Reviewed-by: Judith Mendez <jm@ti.com>
Tested-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
RC Release 09.01.00.006
|
|
OSPI Flashes have 256K sector size, match the DFU buffer size to the
same so that entire sector can be written at once.
W/o this OSPI DFU update fails with timeouts like
=> setenv dfu_alt_info ${dfu_alt_info_ospi}; dfu 0 sf 0:0;
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
Enable NAND support for DFU.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
Enables configuration required for NAND in SPL and u-boot.
Enable MTD Driver model and MTD + UBI command line utilities.
Add mtdids/mtdparts for NAND as it is required for u-boot's
MTD subsystem commands to recognize NAND partitions.
Add u-boot partition location.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
We want SPL to apply DTB overlays (e.g. NAND card overlay) so
enable SPL_LOAD_FIT_APPLY_OVERLAY.
Increase SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ and
SPL_STACK_R_MALLOC_SIMPLE_LEN. Without this SPL hangs.
Signed-off-by: Roger Quadros <rogerq@kernel.org>
|
|
Enable support for using PHY mode in cadence-qspi driver for better data
rate.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
EMMC boot is broken for AM64x platform. This is due to the size of
tiboot3.bin growing beyond the 500KB of memory allocated in eMMC.
There was effort to move the offsets and give more space to tiboot3.bin,
but the offsets in defconfig were not updated. Update offsets in
defconfig to load each binary from the correct adress in eMMC according
to the following eMMC layout:
boot0/1 partition
0x0+----------------------------------+
| tiboot3.bin (1 MB) |
0x800+----------------------------------+
| tispl.bin (2 MB) |
0x1800+-----------------------------------+
| u-boot.img (4 MB) |
0x3800+-----------------------------------+
| environment (128 KB) |
0x3900+-----------------------------------+
Signed-off-by: Judith Mendez <jm@ti.com>
|
|
The u-boot environment variable emmc_android_boot total size increased
to more than 1KB. U-boot hangs when the emmc_android_boot variable is
reused in the u-boot prompt as the maximum size of the u-boot commandÂ
line buffer is 1KB. Increase the CB_SIZE to 2KB for AM57x SoC family
Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
|
|
Add UUU fastboot support to make it possible to download files with
UUU tool from A53 U-boot instead of DFU A53 SPL for verdin am62.
Upstream-Status: Pending
Signed-off-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
|
|
The am62px utilizes the same 32k crystal for a more accurate RTC clock
source. Enable the configuration to set this up for Linux.
Signed-off-by: Bryan Brattlof <bb@ti.com>
|
|
The am62x utilizes the same 32k crystal for a more accurate RTC clock
source. Enable the configuration to set this up for Linux.
Signed-off-by: Bryan Brattlof <bb@ti.com>
|
|
The am62ax utilizes the same 32k crystal for a more accurate RTC clock
source. Enable the configuration to set this up for Linux.
Signed-off-by: Bryan Brattlof <bb@ti.com>
|
|
Add new R5 defconfig for USB MSC boot support based on usbdfu_defconfig
USB Host boot is supported only from USB0 port. By default USB0
is configured in peripheral mode to support DFU. Inorder to support
USB Host boot, "dr_mode" property needs to be changed from "peripheral"
to "host" in the device tree.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
Add support for USB DFU bootmode by having a separate config
file.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
Add configs to enable AM62 USB wrapper.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
Introduce the initial configs needed to support the am62px SoC family
[bb@ti.com: rebased on TI's 2023.10 uboot]
Signed-off-by: Bryan Brattlof <bb@ti.com>
|
|
Disable FIT_SINGATURE_ENFORCE config as it's not needed.
Upstream-Status: Inappropriate [configuration]
This configuration does not exist on mailine U-Boot.
Signed-off-by: Hiago De Franco <hiago.franco@toradex.com>
|
|
Add support for R5F remote proc driver.
Signed-off-by: Hari Nagalla <hnagalla@ti.com>
|
|
Similar to other K3 platforms, drop specifying source of env to avoid
picking up stale env. This enables proper FitImage boot on HS-SE
devices which used to fail due to stale env from older releases.
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
|
|
Enable ESM & PMIC ESM configs
Signed-off-by: Keerthy <j-keerthy@ti.com>
|
|
Enable ESM & PMIC ESM configs
Signed-off-by: Keerthy <j-keerthy@ti.com>
|
|
Enable the configs for J784S4 EVM OSPI NAND support.
Signed-off-by: Apurva Nandan <a-nandan@ti.com>
|
|
Enable CONFIG_TI_I2C_BOARD_DETECT inorder to probe the daughter
cards plugged in and update the "eth", "name_overlays" environment
variables.
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
|
|
To build the Beagle Play bootloaders:
for r5:
defconfig: am62x_evm_r5_defconfig
fragments: am625_beagleplay_r5.config am625_beagleplay_android_r5.config
for a53:
defconfig: am62x_evm_a53_defconfig
fragments: am625_beagleplay_a53.config
am62x_android_a53.config
am625_beagleplay_android_a53.config
Then run the usual build instructions applying the fragments:
make $defconfig $fragments
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
The U-Boot environment is stored at offset 0x680000 (6.5MB)
While this is fine for AM62x SK EVM (because its mmc0boot0 partition is 31.5MB),
this does won't work on the Beagle Play, which only has 4MB.
Booting Beagle Play shows:
Loading Environment from MMC... MMC: block number 0x3500 exceeds max(0x2000)
*** Warning - !read failed, using default environment
Move the U-boot environment at lba 0x800 on mmc0boot0.
This reserves 1MB so that tiboot3 to be on mmc0boot0 as well, which is the
case for BeaglePlay.
Also add a raw_partition label so that we can erase it with:
fastboot erase bootenv
The boot0 partition now looks as:
blk
boot0 partition (31.5 MB)
0x0+----------------------------------+
| empty (1 MB) |
0x800+----------------------------------+
| environment (128 KB) |
| padding (384 KB) |
0xc00+----------------------------------+
| |
| Remaining space (30.0 MB) |
0xfc00+----------------------------------+
pick
Note:
CONFIG_ENV_OFFSET is in bytes and fastboot_raw_* is in lba number.
CONFIG_ENV_OFFSET=0x100000 -> lba 0x800
env size + padding = 512KB -> length of 0x400 lbas
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
When booting with a corrupt MMC environment, we can see:
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Loading Environment from nowhere... OK
After that, saving does not work:
=> env default -a -f
## Resetting to default environment
=> saveenv
Saving Environment to nowhere... not possible
This is because CONFIG_ENV_IS_NOWHERE=y is set in am62x in
am62x_evm_a53_defconfig and applying the am62x_android_53.config fragment does
not disable it.
Disable ENV_IS_NOWHERE explicitly so that => saveenv can repair broken environments.
Fixes: d5a7186e16a9 ("configs: am62x_android_a53.config: Store environment in MMC")
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Tested-by: Guillaume La Roque <glaroque@baylibre.com>
Reviewed-by: Guillaume La Roque <glaroque@baylibre.com>
|
|
Use envboot cmd before issuring distro_bootcmd as otherwise
environment variables from uEnv.txt are not getting imported.
The commands after distro_bootcmd have no impact since board starts
booting after distro_bootcmd, so it need to run last after all
environment variables are configured correctly.
Fixes: bde6ac54905 ("configs: am65x_evm: Switch envboot out for distro_bootcmd")
Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
|
|
commit 280f45d23977 ("configs: get rid of build warnings due to
SPL_USB_DWC3_GENERIC") missed enabling DWC3 glue layer for
usbmsc_defconfig and this broke boot from USB mass storage.
Fix this by enabling DWC3 glue layer.
Fixes: 280f45d23977 ("configs: get rid of build warnings due to SPL_USB_DWC3_GENERIC")
Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Reviewed-by: Roger Quadros <rogerq@kernel.org>
|
|
Add config fragments for am62xsip_sk_r5.config R5 configuration.
Signed-off-by: Nitin Yadav <n-yadav@ti.com>
|
|
RC Release 09.00.00.008
|
|
Enable the CONFIG_TI_SECURE_DEVICE by default.
Merge GP and HS configs.
Non-HS devices will continue to boot due to runtime device type detection.
TI's security enforcing SoCs will authenticate each binary it loads by
comparing it's signature with keys etched into the SoC during the boot
up process. The am65x family of SoCs by default will have some level of
security enforcement checking. To keep things as simple as possible,
enable the CONFIG_TI_SECURE_DEVICE options by default so all levels of
secure SoCs will work out of the box.
Signed-off-by: Judith Mendez <jm@ti.com>
Reviewed-by: Kamlesh Gurudasani <kamlesh@ti.com>
|
|
Add config fragments for j721e_beaglebone-ai64 A72 and R5 configuration.
This applies on to:
j721e_evm_a72_defconfig -> j721e_beagleboneai64_a72.config
j721e_evm_r5_defconfig -> j721e_beagleboneai64_r5.config
The usage model (with the fragment) would be:
make ARCH=arm j721e_evm_a72_defconfig j721e_beagleboneai64_a72.config
make ARCH=arm
OR
make ARCH=arm j721e_evm_r5_defconfig j721e_beagleboneai64_r5.config
make ARCH=arm
Signed-off-by: Nishanth Menon <nm@ti.com>
|
|
The android boot flow allows users to pick custom device tree overlays
to be applied for additional peripheral support.
This is done via an environment variable named "dtbo_index".
For example:
=> env set dtbo_index 2
=> saveenv
Allow users to save the environment so that the dtbos are applied on
each reboot.
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
The android boot flow is quite complex and adds a lot of new
environment variables a typical linux bootflow is not interested in.
Add a defconfig fragment to build bootloaders compatible with the
Android boot flow.
This applies on to:
am62x_evm_a53_defconfig / am62x_lpsk_a53_defconfig -> am62x_android_a53.config
The usage model (with the fragment) would be:
make ARCH=arm am62x_evm_a53_defconfig am62x_android_a53.config
make ARCH=arm
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
|
|
This reverts commit 7d9dbeafe637a25267f0902ead02f61843edb7f3.
commit 7988f626336a ("common: avb_verify: Add CONFIG_AVB_PUBKEY_FILE to specify the root avb public key")
was introduced to support AVB on am62x android.
But this broke am57x builds.
Android on am57xx is not validated currently hence reverting the patch
till a right fix is identified that scales to all supported platforms.
Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
Suggested-by: Andrew Davis <afd@ti.com>
|
|
Enable CONFIG_SET_DFU_ALT_INFO for all J7 platforms, to set the
dfu_alt_info environment variable dynamically from a platform
specific override. For now, this is performed by fetching the
partition information from the device tree, dynamic dfu_alt_info
override is now supported only for `sf` devices.
Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
|
|
Enable CONFIG_OF_SYSTEM_SETUP which does core number autodetection and
fixes the fdt.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Integrate downstream specifics.
Upstream-Status: Inappropriate
Those are really downstream specifics.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
