Eric Lee / smarc-uboot

23 Jan, 2020

1 commit

09 Dec, 2019

1 commit

06 Dec, 2019

1 commit

  • 1fae23899   warp7: Fix U-Boot corruption after saving the environment ... Browse Code »

    U-Boot binary has grown in such a way that it goes beyond the reserved
    area for the environment variables.

    Running "saveenv" followed by a "reset" causes U-Boot to hang because
    of this overlap.

    Fix this problem by increasing the CONFIG_ENV_OFFSET size.

    Also, in order to prevent this same problem in the future, use
    CONFIG_BOARD_SIZE_LIMIT, which will detect the overlap in build-time.

    CONFIG_BOARD_SIZE_LIMIT does not accept math expressions, so declare
    CONFIG_ENV_OFFSET with its direct value instead.

    Signed-off-by: Fabio Estevam
    Acked-by: Pierre-Jean Texier
    Tested-by: Pierre-Jean Texier
    Acked-by: Joris Offouga
    Tested-by: Joris Offouga

    Fabio Estevam
     

04 Dec, 2019

1 commit

21 Nov, 2019

2 commits

  • a09fea1d2   env: Finish migration of common ENV options ... Browse Code »
    1

    - In ARMv8 NXP Layerscape platforms we also need to make use of
    CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
    - On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
    to 0.
    - Add Kconfig entry for ENV_ADDR.
    - Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
    - Add ENV_xxx_REDUND options that depend on their primary option and
    SYS_REDUNDAND_ENVIRONMENT
    - On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
    for the pre-main-U-Boot environment location.
    - On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
    rather it being non-zero, as it will now be zero by default.
    - Rework the env_offset absolute in env/embedded.o to not use
    CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
    ENV_IS_IN_FLASH.
    - Migrate all platforms.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Cc: Patrick Delaunay
    Cc: uboot-stm32@st-md-mailman.stormreply.com
    Signed-off-by: Tom Rini
    Acked-by: Joe Hershberger
    Reviewed-by: Simon Goldschmidt

    Tom Rini
     
  • 8d8ee47e0   env: Add CONFIG_SYS_RELOC_GD_ENV_ADDR symbol ... Browse Code »
    24

    Today in initr_reloc_global_data() we use some non-obvious tests to
    determine if we need to relocate the env_addr within gd or not. In
    order to facilitate migration of other symbols to Kconfig we need to
    introduce a new symbol for this particular use case.

    Cc: Wolfgang Denk
    Cc: Joe Hershberger
    Signed-off-by: Tom Rini

    Tom Rini
     

08 Nov, 2019

1 commit

08 Oct, 2019

1 commit

24 Aug, 2019

1 commit

23 Jun, 2019

1 commit

05 May, 2019

1 commit

  • 623de3f08   Convert CONFIG_SUPPORT_EMMC_BOOT to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_SUPPORT_EMMC_BOOT

    As requested by Michal Simek , these boards
    have no eMMC so CONFIG_SUPPORT_EMMC_BOOT has not been migrated:

    xilinx_zynqmp_zc1275_revB
    xilinx_zynqmp_zc1751_xm018_dc4
    xilinx_zynqmp_zc1751_xm019_dc5
    xilinx_zynqmp_zcu100_revC
    xilinx_zynqmp_zcu102_rev1_0
    xilinx_zynqmp_zcu102_revA
    xilinx_zynqmp_zcu102_revB
    xilinx_zynqmp_zcu104_revA
    xilinx_zynqmp_zcu104_revC
    xilinx_zynqmp_zcu106_revA
    xilinx_zynqmp_zcu111_revA

    Signed-off-by: Alex Kiernan
    Acked-by: Lukasz Majewski
    Acked-by: Patrick Delaunay
    Acked-by: Ramon Fried
    Reviewed-by: Andy Shevchenko
    Tested-by: Sébastien Szymanski

    Alex Kiernan
     

01 May, 2019

1 commit

30 Apr, 2019

1 commit

26 Apr, 2019

2 commits

08 Feb, 2019

1 commit

29 Jan, 2019

5 commits

19 Jan, 2019

1 commit

  • 2acc24fc2   Kconfig: Migrate BOUNCE_BUFFER ... Browse Code »

    The bounce buffer is used by a few drivers (most of the MMC drivers)
    to overcome limitations in their respective DMA implementation.

    This moves the configuration to Kconfig and makes it user-selectable
    (even though it will be a required feature to make those drivers
    work): the expected usage is for drivers depending on this to 'select'
    it unconditionally from their respective Kconfig (see follow-up
    patches).

    This commit includes a full migration using moveconfig.py to ensure
    that each commit compiles. To ensure bisectability we update
    dependencies of various drivers to now select BOUNCE_BUFFER when needed.

    [trini: Squash all patches to ensure bisectability]
    Signed-off-by: Tom Rini
    Signed-off-by: Philipp Tomsich
    Reviewed-by: Otavio Salvador [dw_mmc portion]
    Reviewed-by: Fabio Estevam [mxsmmc portion]
    Reviewed-by: Simon Glass [tegra portion]

    Philipp Tomsich
     

17 Dec, 2018

1 commit

14 Nov, 2018

1 commit

22 Oct, 2018

1 commit

  • c7b3a7ee5   optee: adjust dependencies and default values for dram ... Browse Code »
    12

    We may have, the not yet considered, scenario where OPTEE is loaded before
    u-boot and *not* by u-boot, e.g, the boot flow using the ARM Trusted
    Firmware (ATF), where in the 32bit flow is:
    BootRom->ATF(BL2)->Optee(BL32)->u-boot(BL33)

    In this case we need still to reserve the memory used by optee, to avoid
    for example to realocate ourself to the same address at the end of DRAM.
    So, we change here the dependencies on the OPTEE lib and we set the default
    size and base of TZRAM to zero.

    Signed-off-by: Rui Miguel Silva
    Signed-off-by: Bryan O'Donoghue
    Cc: Fabio Estevam
    Cc: Ryan Harkin
    Cc: u-boot@lists.denx.de

    Rui Miguel Silva
     

17 Aug, 2018

1 commit

  • 86cf1c828   configs: Migrate CONFIG_NR_DRAM_BANKS ... Browse Code »
    13

    We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

08 Aug, 2018

1 commit

04 Jun, 2018

1 commit

26 Apr, 2018

7 commits

  • e426e1935   warp7: defconfig: Fix CAAM on boot with tip-of-tree ... Browse Code »

    Booting the following image with tip-of-tree we get a CAAM DECO error (and
    subsequent crash due to a kernel bug in 4.1).

    http://freescale.github.io/#download -> BoardsWaRPboard community - WaRP -
    Wearable Reference PlatformFSL Community BSP 2.3fsl-image-multimediawayland

    Image: fsl-image-multimedia-imx7s-warp-20180323-90.rootfs.sdcard

    Error:
    caam 30900000.caam: Entropy delay = 3200
    caam 30900000.caam: failed to acquire DECO 0

    caam 30900000.caam: failed to acquire DECO 0
    caam 30900000.caam: Entropy delay = 12400
    caam 30900000.caam: failed to acquire DECO 0
    caam 30900000.caam: failed to instantiate RNG
    ------------[ cut here ]------------
    WARNING: CPU: 0 PID: 1 at
    /home/jenkins/workspace/fsl-community-bsp-pyro_xwayland_2/build/tmp/work-shared/imx7s-warp/kernel-source/mm/vmalloc.c:1465
    caam_remove+0x6)
    Trying to vfree() nonexistent vm area (88047000)
    Modules linked in:
    CPU: 0 PID: 1 Comm: swapper/0 Not tainted
    4.1.36-4.1-1.0.x-imx-warp7+ga543d1b #1
    Hardware name: Freescale i.MX7 Dual (Device Tree)
    [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
    [] (show_stack) from [] (dump_stack+0x78/0x8c)
    [] (dump_stack) from []
    (warn_slowpath_common+0x80/0xb0)
    [] (warn_slowpath_common) from []
    (warn_slowpath_fmt+0x30/0x40)
    [] (warn_slowpath_fmt) from [] (caam_remove+0x6c/0x3f4)
    [] (caam_remove) from [] (caam_probe+0x874/0xfa8)
    [] (caam_probe) from [] (platform_drv_probe+0x48/0xa4)
    [] (platform_drv_probe) from []
    (driver_probe_device+0x174/0x2a8)
    [] (driver_probe_device) from []
    (__driver_attach+0x8c/0x90)
    [] (__driver_attach) from []
    (bus_for_each_dev+0x68/0x9c)
    [] (bus_for_each_dev) from []
    (bus_add_driver+0xf4/0x1e8)
    [] (bus_add_driver) from [] (driver_register+0x78/0xf4)
    [] (driver_register) from []
    (do_one_initcall+0x8c/0x1d0)
    [] (do_one_initcall) from []
    (kernel_init_freeable+0x140/0x1d0)
    [] (kernel_init_freeable) from []
    (kernel_init+0x8/0xe8)
    [] (kernel_init) from [] (ret_from_fork+0x14/0x2c)
    ---[ end trace d5f941204ed8cb28 ]---
    caam: probe of 30900000.caam failed with error -11
    Unable to handle kernel NULL pointer dereference at virtual address
    00000004
    pgd = 80004000
    [00000004] *pgd=00000000
    Internal error: Oops: 805 [#1] PREEMPT SMP ARM

    [] (caam_sm_startup) from [] (caam_sm_init+0x50/0x58)
    [] (caam_sm_init) from [] (do_one_initcall+0x8c/0x1d0)
    [] (do_one_initcall) from []
    (kernel_init_freeable+0x140/0x1d0)
    [] (kernel_init_freeable) from []
    (kernel_init+0x8/0xe8)
    [] (kernel_init) from [] (ret_from_fork+0x14/0x2c)
    Code: e59d300c e2832010 e5843008 e5834068 (e58a2004)
    ---[ end trace d5f941204ed8cb29 ]---
    Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

    Fix: Enable the CAAM correctly by setting CONFIG_ARMV7_BOOT_SEC_DEFAULT=y
    in the upstream defconfig.

    Signed-off-by: Bryan O'Donoghue
    Cc: Fabio Estevam
    Cc: Breno Lima
    Reviewed-by: Fabio Estevam
    Tested-by: Breno Lima

    Bryan O'Donoghue
     
  • baea5ecd2   warp7: defconfig: Enable CMD_SETEXPR ... Browse Code »

    setexpr allows us to do arithmetic for env variables - something that is
    both useful and required when doing HAB authentication without hard-coding
    HAB load addresses.

    This patch enables CMD_SETEXPR for the WaRP7 defconfig.

    Signed-off-by: Bryan O'Donoghue
    Tested-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Bryan O'Donoghue
     
  • 42fcabdb2   warp7: defconfig: Enable CONFIG_BOOTM_TEE ... Browse Code »

    This patch enables CONFIG_BOOTM_TEE. Once enabled its possible to
    chain-load Linux through OPTEE.

    Loading kernel to 0x80800000
    => run loadimage

    Load FDT to 0x83000000
    => run loadfdt

    Load OPTEE to 0x84000000
    => fatload mmc 0:5 0x84000000 /lib/firmware/uTee.optee

    Then chain-load to the kernel via OPTEE

    => bootm 0x84000000 - 0x83000000

    Image Name:
    Image Type: ARM Trusted Execution Environment Kernel Image (uncompressed)
    Data Size: 249844 Bytes = 244 KiB
    Load Address: 9dffffe4
    Entry Point: 9e000000
    Verifying Checksum ... OK
    Loading Kernel Image ... OK

    Signed-off-by: Bryan O'Donoghue
    Tested-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Bryan O'Donoghue
     
  • 9fb2c1faa   warp7: defconfig: Enable CONFIG_SECURE_BOOT ... Browse Code »

    Various function associated with booting the WaRP7 in High Assurance Boot
    (HAB) mode are enabled by switching on CONFIG_SECURE_BOOT.

    This patch enables CONFIG_SECURE_BOOT for the WaRP7 defconfig.

    Signed-off-by: Bryan O'Donoghue
    Tested-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Bryan O'Donoghue
     
  • 4bcbfcf45   warp7: Specify CONFIG_OPTEE_LOAD_ADDR ... Browse Code »

    In order to sign images with the IMX code-signing-tool (CST) we need to
    know the load address of a given image. The best way to derive this load
    address is to make it into a define - so that u-boot.cfg contains the
    address - which we can then parse when generating the IMX CST headers.

    This patch makes the OPTEE_LOAD_ADDR available via u-boot.cfg for further
    parsing by external tools.

    Signed-off-by: Bryan O'Donoghue
    Reviewed-by: Ryan Harkin
    Tested-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Bryan O'Donoghue
     
  • c727bba74   warp7: defconfig: Enable OPTEE for WaRP7 ... Browse Code »

    Requires setting CONFIG_OPTEE=y and setting an OPTEE TrustZone DRAM base in
    include/configs/warp7.h.

    Signed-off-by: Bryan O'Donoghue
    Tested-by: Breno Lima
    Reviewed-by: Fabio Estevam

    Bryan O'Donoghue
     
  • 0803bcf8a   warp7: configs: enable CONFIG_CMD_FS_GENERIC ... Browse Code »

    This enable generic file system commands (load, ls).

    Signed-off-by: Pierre-Jean TEXIER
    Reviewed-by: Fabio Estevam
    Acked-by: Bryan O'Donoghue

    Pierre-Jean TEXIER
     

09 Apr, 2018

1 commit

11 Feb, 2018

1 commit

  • 278b90ce7   configs: Migrate CONFIG_SYS_TEXT_BASE ... Browse Code »
    15

    On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

11 Oct, 2017

1 commit

  • ad12dc184   cmd: Toggle the default value of CONFIG_CMD_IMLS ... Browse Code »

    Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

04 Oct, 2017

2 commits