- 09 4月, 2017 21 次提交
-
-
由 Andrew F. Davis 提交于
TI K2G secure devices have to be built with TI_SECURE_DEVICE, FIT, and FIT_IMAGE_POST_PROCESS enabled. Add a dedicated defconfig for this. Signed-off-by: NAndrew F. Davis <afd@ti.com>
-
由 Andrew F. Davis 提交于
TI K2HK secure devices have to be built with TI_SECURE_DEVICE, FIT, and FIT_IMAGE_POST_PROCESS enabled. Add a dedicated defconfig for this. Signed-off-by: NAndrew F. Davis <afd@ti.com>
-
由 Vitaly Andrianov 提交于
TI K2E secure devices have to be built with TI_SECURE_DEVICE, FIT, and FIT_IMAGE_POST_PROCESS enabled. Add a dedicated defconfig for this. Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Madan Srinivas 提交于
This patch makes SYS_TEXT_BASE a config option for Keystone2 so that it can be used to load u-boot at different addresses on secure and non-secure Keystone2 devices. Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Madan Srinivas 提交于
Add a section describing the secure boot image used on Keystone2 secure devices. Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Madan Srinivas 提交于
Adds an additional image type needed for supporting secure keystone devices. The build generates u-boot_HS_MLO which can be used to boot from all media on secure keystone devices. Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Madan Srinivas 提交于
As K2 can directly boot U-Boot, add u-boot_HS_MLO as the secure image name for secure K2 devices, for all boot modes other than SPI flash. Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
Like the OMAP54xx, AM43xx, & AM33xx family SoCs, the keystone family of SoCs also have high security enabled models. Allow K2E devices to be built with HS Device Type Support. Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vitaly Andrianov 提交于
This commit implements the board_fit_image_post_process() function for the keystone architecture. This function calls into the secure boot monitor for secure authentication/decryption of the image. All needed work is handled by the boot monitor and, depending on the keystone platform, the security functions may be offloaded to other secure processing elements in the SoC. The boot monitor acts as the gateway to these secure functions and the boot monitor for secure devices is available as part of the SECDEV package for KS2. For more details refer doc/README.ti-secure Signed-off-by: NVitaly Andrianov <vitalya@ti.com> Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Madan Srinivas 提交于
The function 'board_fit_image_post_process' is defined only when the config option CONFIG_FIT_IMAGE_POST_PROCESS is enabled. For secure systems that do not use SPL but do use FIT kernel images, only CONFIG_FIT_IMAGE_POST_PROCESS will be defined, which will result in an implicit declaration of function 'board_fit_image_post_process' warning while building u-boot. Fix this warning. Signed-off-by: NMadan Srinivas <madans@ti.com> Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andrew F. Davis 提交于
The most common name for a FIT image containing a bootable kernel is "fitImage", as our builds now use this name also, change this to the default in our U-Boot environment. Signed-off-by: NAndrew F. Davis <afd@ti.com>
-
由 Cooper Jr., Franklin 提交于
Various commands to NAND flash results in the NAND flash becoming busy. For those commands the SoC should wait until the NAND indicates it is no longer busy before sending further commands. However, there is a delay between the time the SoC sends its last command and when the NAND flash sets its Ready/Busy Pin. This delay (tWB) must be respected or the SoC may falsely assume the flash is ready when in reality it just hasn't had enough time to indicate that it is busy. Properly delaying by tWB is already done for nand_command/nand_command_lp in nand_base.c including the version of it in the Linux kernel. Therefore, this patch brings the handling of tWB delay inline to nand_base.c Signed-off-by: NFranklin S Cooper Jr <fcooper@ti.com> [trini: Reformat comments slightly] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Sekhar Nori 提交于
Now that we have common MMC/SD boot environment variables that can be used across TI platforms, switch OMAP-L138 LCDK to use them. As a nice side-effect, we get support for using uEnv.txt on this platform. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Sekhar Nori 提交于
Introduce include/environment/ti/mmc.h that consolidates environment variable definitions for various TI boards that support MMC/SD. This allows reuse of same environment variables on non-ARMv7 TI platforms like OMAP-L138 for example. While at it, move DFU-related environment variable includes to only non-SPL builds for AM335x and AM437x since they are not really used for SPL today. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Sekhar Nori 提交于
Use environment variables for various memory addresses used on OMAP-L138 LCDK board. This makes it easy to customize the boot process. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Sekhar Nori 提交于
Enable some generic filesystem commands as well as disk partition related commands for OMAP-L138 LCDK board. These help in booting Linux from MMC/SD, for example. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Sekhar Nori 提交于
OMAP-L138 LCDK board does not have a SPI flash. Remove spiboot related environment variable definitions. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Lukasz Majewski 提交于
Up till this commit passing NULL as input parameter was allowed, but not handled properly. When one passed NULL to one of this function parameters, the code was executed causing data abort. However, what is more interesting, the abort was not caught because of code execution in HYP mode with masked CPSR A bit ("Imprecise Data Abort mask bit). The TI's AM57xx SoC switch to HYP mode with A bit masked in lowlevel_init.S due to SMC call. Such operation (by default) is performed in SoC ROM code. The problem would pop up when one: - Switch back to SVC mode after disabling LPAE support - Somebody enables A bit (by executing cpsie a asm instruction) and then the previously described exception would be caught. Signed-off-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Lukasz Majewski 提交于
The OMAP WDT IP block requires to be stopped before any write to its registers is performed. This problem has been thoroughly described in Linux kernel: "watchdog: omap: assert the counter being stopped before reprogramming: SHA1: 530c11d432727c697629ad5f9d00ee8e2864d453 Signed-off-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Lukasz Majewski 提交于
Signed-off-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Lukasz Majewski 提交于
Signed-off-by: NLukasz Majewski <lukma@denx.de> Reviewed-by: NTom Rini <trini@konsulko.com>
-
- 08 4月, 2017 19 次提交
-
-
-
-
由 Alexandru Gagniuc 提交于
Under the plethora of #ifdefs, the xyzModem code hid this pearl: static char *zm_out = (char *) 0x00380000; This was only enabled when DEBUG is defined, so it's probably why it went unnoticed for so long. No idea what platform had memory at that exact location, but the this approach is extremely hacky. Use a static buffer instead. Signed-off-by: NAlexandru Gagniuc <alex.g@adaptrum.com>
-
由 Alexandru Gagniuc 提交于
Signed-off-by: NAlexandru Gagniuc <alex.g@adaptrum.com>
-
由 Alexandru Gagniuc 提交于
spl_mmc.c calls mmc_initialize(). This symbol is provided in drivers/mmc/mmc.c when CONFIG_GENERIC_MMC is enabled. The sunxi Kconfig case is an oddball because it redefines SPL_MMC_SUPPORT. Signed-off-by: NAlexandru Gagniuc <alex.g@adaptrum.com> [trini: Update arch/arm/cpu/armv8/zynqmp/Kconfig] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Nobuhiro Iwamatsu 提交于
This removes CONFIG_BOOTSTAGE_USER_COUNT, CONFIG_BOOTSTAGE_STASH_ADDR and CONFIG_BOOTSTAGE_STASH_SIZE from defconfig following boards: - Alt - Gose - Koelsh - Lager - Porter - Silk - Stout - Blanche - Salvator-x Signed-off-by: NNobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Nobuhiro Iwamatsu 提交于
The default value of BOOTSTAGE_STASH_SIZE should be set to hexadecimal, but an integer value is set. This fixes the BOOTSTAGE_STASH_SIZE number from hexadecimal to integer. Signed-off-by: NNobuhiro Iwamatsu <iwamatsu@nigauri.org>
-
由 Vikas Manocha 提交于
On ARM v7M, the processor will return to ARM mode when executing blx instruction with bit 0 of the address == 0. Always set it to 1 to stay in thumb mode. Similar commit: f99993c1 Author: Matt Porter <mporter@konsulko.com> Date: Tue May 5 15:00:23 2015 -0400 common/cmd_boot: keep ARM v7M in thumb mode during do_go_exec() Signed-off-by: NVikas Manocha <vikas.manocha@st.com>
-
由 robertcnelson@gmail.com 提交于
BeagleBone Blue is next grenation of boards from BeagleBoard.org, focusing on robotics with a TI wl1835 wireless module for connectivity. This board can be indentified by the BLAx value after A335BNLT (BBB) in the at24 eeprom: BLAx: [aa 55 33 ee 41 33 33 35 42 4e 4c 54 42 4c 41 30 |.U3.A335BNLTBLA2|] http://beagleboard.org/blue https://github.com/beagleboard/beaglebone-blue firmware: https://github.com/beagleboard/beaglebone-black-wireless/tree/master/firmware wl18xx mac address: /proc/device-tree/ocp/ethernet@4a100000/slave@4a100200/mac-address Signed-off-by: NRobert Nelson <robertcnelson@gmail.com> CC: Tom Rini <trini@konsulko.com> CC: Jason Kridner <jkridner@beagleboard.org> CC: Will Newton <willn@resin.io> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 robertcnelson@gmail.com 提交于
SeeedStudio BeagleBone Green Wireless (BBGW) is an expansion of the SeeedStudio Green (BBG) with the Ethernet replaced by a TI wl1835 wireless module. This board can be indentified by the GW1x value after A335BNLT (BBB) in the at24 eeprom: GW1x [aa 55 33 ee 41 33 33 35 42 4e 4c 54 47 57 31 41 |.U3.A335BNLTGW1A|] http://beagleboard.org/green-wireless http://wiki.seeed.cc/BeagleBone_Green_Wireless/ firmware: https://github.com/beagleboard/beaglebone-black-wireless/tree/master/firmware wl18xx mac address: Stored in at24 eeprom at address 5-16: hexdump -e '8/1 "%c"' /sys/bus/i2c/devices/0-0050/eeprom | cut -b 5-16 Signed-off-by: NRobert Nelson <robertcnelson@gmail.com> CC: Tom Rini <trini@konsulko.com> CC: Jason Kridner <jkridner@beagleboard.org> CC: Will Newton <willn@resin.io> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 robertcnelson@gmail.com 提交于
BeagleBone Black Wireless is clone of the BeagleBone Black (BBB) with the Ethernet replaced by a TI wl1835 wireless module. This board can be indentified by the BWAx value after A335BNLT (BBB) in the at24 eeprom: BWAx [aa 55 33 ee 41 33 33 35 42 4e 4c 54 42 57 41 35 |.U3.A335BNLTBWA5|] http://beagleboard.org/black-wireless https://github.com/beagleboard/beaglebone-black-wireless firmware: https://github.com/beagleboard/beaglebone-black-wireless/tree/master/firmware wl18xx mac address: /proc/device-tree/ocp/ethernet@4a100000/slave@4a100200/mac-address Signed-off-by: NRobert Nelson <robertcnelson@gmail.com> CC: Tom Rini <trini@konsulko.com> CC: Jason Kridner <jkridner@beagleboard.org> CC: Will Newton <willn@resin.io> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Vikas Manocha 提交于
It also enables commands for cache enable/disable/status. Signed-off-by: NVikas Manocha <vikas.manocha@st.com> cc: Christophe KERELLO <christophe.kerello@st.com>
-
由 Vikas Manocha 提交于
This patch adds armv7m instruction & data cache support. Signed-off-by: NVikas Manocha <vikas.manocha@st.com> cc: Christophe KERELLO <christophe.kerello@st.com>
-
由 Joakim Tjernlund 提交于
ft_cpu_setup() already calls fdt_fixup_ethernet(), calling it in image_setup_libfdt() is both redundant and breaks any modifications done by ft_board_setup(). Restore the old behavior by removing the call in image_setup_libfdt() Fixes: 13d06981 ("image: Add device tree setup to image library") Signed-off-by: NJoakim Tjernlund <joakim.tjernlund@infinera.com>
-
由 Patrice Chotard 提交于
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
-
由 Andrew F. Davis 提交于
The env command 'args_fit' does not define a root path, this forces us to embed the rootfs into the FIT image. FIT images do not need to contain a rootfs, when they do not the kernel will fall-back to the kernel argument 'root', if this is not defined the kernel will not boot. It is safe to add this as when we do have the rootfs in FIT this argument is ignored. As 'loadfit' is only called from the MMC boot path, use 'args_mmc' to correctly populate 'bootargs'. Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 fuz@fuz.su 提交于
Good evening, I am trying to port FreeBSD to the ASUS Tinker Board, a computer based on the Rockchip 3288 SoC. FreeBSD's boot loader (named loader(8)) needs CONFIG_API to be enabled, but trying to build an U-Boot from trunk with both CONFIG_API and CONFIG_BLK (as required for Rockchip SoC's?) leads to the following build failure: $ CROSS_COMPILE=arm-none-eabi- gmake tinker-rk3288_defconfig all ... CC api/api_storage.o api/api_storage.c: In function 'dev_read_stor': api/api_storage.c:334:9: error: 'struct blk_desc' has no member named 'block_read' if ((dd->block_read) == NULL) { ^~ api/api_storage.c:339:11: error: 'struct blk_desc' has no member named 'block_read' return dd->block_read(dd, start, len, buf); ^~ api/api_storage.c:340:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ gmake[2]: *** [scripts/Makefile.build:281: api/api_storage.o] Fehler 1 gmake[1]: *** [Makefile:1229: api] Fehler 2 gmake: *** [Makefile:460: __build_one_by_one] Error 2 I applied the following fix, but the product doesn't boot. Perhaps that's not a property of the fix though: Yours, Robert Clausecker
-
由 Sekhar Nori 提交于
As per the latest pinmux data available for AM572x EVM, rev A3, input should be enabled on MMC clock lines for MMC2/2/3 for stable operation. Further, AM572x TRM, SPRUHZ6, Revised June 2016, in section 18.4.6.1.1 "Pad Configuration Registers" states that input should be enabled for MMC 2/3/4 clock lines. Enable input on MMC1 and MMC3 clock to match the latest pinmux data. Input is already enabled on MMC2 clock for BeagleBoard x15. Further, input is already enabled on all MMCx clocks for other AM57xx boards (AM572x and AM571x IDK). Tested with HS and UHS SD card on AM572x EVM Rev A3. Signed-off-by: NSekhar Nori <nsekhar@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vignesh R 提交于
SPI U-Boot image for K2 boards have now exceeded 512K partition allocated to it and no longer fit the partitions defined in kernel DTS file. Therefore, pass an updated MTD partition table from U-Boot as kernel command line arguments to avoid kernel from accidentally modifying boot loader image that has overflowed to next user partition. To do is, introduce a common environment file for declaring SPI partition so that each individual boards need not repeat the same. Choose appropriate SPI bus from board config file and pass it as command line argument to kernel. Signed-off-by: NVignesh R <vigneshr@ti.com>
-