Secure boot improvements and test on Beaglebone Black
Subsystems (2)
cover Secure boot improvements and test on Beaglebone Black
This series adds a few improvements to the image signing feature to make it easier to use on the Beaglebone Black.
- Add a DEV_TREE_BIN option to make it easier to include the correct FDT (with embedded public keys) into the U-Boot image
- Enable cache for more TI boards (to speed things up)
- Increase malloc size
- Enable CONFIG_OF_CONTROL, FIT and secure boot on am33xx/omap (RFC only, not sure we want this, although we could create a separate config for it)
I also have a change to adjust mkimage to automatically make space in the FDT when adding hashes and signatures. Included here is the ENOSPC patch, but the fit_image.c patch will wait until the dumpimage tool is merged, since I am changing the same code.
With this, secure boot was tested successfully on Beaglebone Black.
Simon Glass (8):
am33xx/omap: Allow cache enable for all Sitara/OMAP
hash: Export functions to find and show hash
fdt: Add DEV_TREE_BIN option to specify a device tree binary file
fdt: Update functions which write to an FDT to return -ENOSPC
arm: ti: Increase malloc size to 16MB for armv7 boards
RFC: am33xx/omap: Enable CONFIG_OF_CONTROL
RFC: am33xx/omap: Enable FIT support
RFC: am33xx/omap: Enable secure boot with CONFIG_FIT_SIGNATURE
Makefile | 8 +- arch/arm/cpu/armv7/omap-common/Makefile | 4 + arch/arm/cpu/armv7/omap-common/hwinit-common.c | 41 -- arch/arm/cpu/armv7/omap-common/omap-cache.c | 56 +++ arch/arm/cpu/armv7/omap3/board.c | 8 - arch/arm/dts/am33xx.dtsi | 649 +++++++++++++++++++++++++ arch/arm/dts/dt-bindings/gpio/gpio.h | 15 + arch/arm/dts/dt-bindings/pinctrl/am33xx.h | 41 ++ arch/arm/dts/dt-bindings/pinctrl/omap.h | 54 ++ board/siemens/common/board.c | 9 - board/ti/dts/am335x-bone-common.dtsi | 262 ++++++++++ board/ti/dts/am335x-boneblack.dts | 17 + board/ti/dts/tps65217.dtsi | 56 +++ common/hash.c | 13 +- common/image-fit.c | 4 +- doc/README.fdt-control | 16 +- include/configs/am335x_evm.h | 9 + include/configs/ti_armv7_common.h | 2 +- include/hash.h | 22 + include/rsa.h | 3 +- lib/rsa/rsa-sign.c | 28 +- 21 files changed, 1236 insertions(+), 81 deletions(-) create mode 100644 arch/arm/cpu/armv7/omap-common/omap-cache.c create mode 100644 arch/arm/dts/am33xx.dtsi create mode 100644 arch/arm/dts/dt-bindings/gpio/gpio.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/am33xx.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/omap.h create mode 100644 board/ti/dts/am335x-bone-common.dtsi create mode 100644 board/ti/dts/am335x-boneblack.dts create mode 100644 board/ti/dts/tps65217.dtsi
Signature · 1 line
1.8.4
PATCH 1/8 am33xx/omap: Allow cache enable for all Sitara/OMAP
Enable the cache for all devices, unless CONFIG_SYS_DCACHE_OFF is defined. This speeds up the Beaglebone Black boot considerable.
(Tested only on Beaglebone Black with SD card boot)
--- arch/arm/cpu/armv7/omap-common/Makefile | 4 ++ arch/arm/cpu/armv7/omap-common/hwinit-common.c | 41 ------------------- arch/arm/cpu/armv7/omap-common/omap-cache.c | 56 ++++++++++++++++++++++++++ arch/arm/cpu/armv7/omap3/board.c | 8 ---- board/siemens/common/board.c | 9 ----- 5 files changed, 60 insertions(+), 58 deletions(-) create mode 100644 arch/arm/cpu/armv7/omap-common/omap-cache.c
arch/arm/cpu/armv7/omap-common/Makefile +4 -0
@@ -21,6 +21,10 @@ COBJS += vc.o COBJS += abb.o endif +ifeq ($(CONFIG_SYS_DCACHE_OFF),) +COBJS += omap-cache.o +endif + ifeq ($(CONFIG_OMAP34XX),) COBJS += boot-common.o SOBJS += lowlevel_init.o
arch/arm/cpu/armv7/omap-common/hwinit-common.c +0 -41
52 lines not on this page · raw message
arch/arm/cpu/armv7/omap-common/omap-cache.c new file +56 -0
56 lines not on this page · raw message
arch/arm/cpu/armv7/omap3/board.c +0 -8
@@ -478,11 +478,3 @@ void omap3_outer_cache_disable(void) omap3_update_aux_cr(0, 0x2); }#endif /* !CONFIG_SYS_L2CACHE_OFF */ - -#ifndef CONFIG_SYS_DCACHE_OFF -void enable_caches (void ) -{ -/* Enable D-cache. I-cache is already enabled in start.S */ -dcache_enable (); -} -#endif /* !CONFIG_SYS_DCACHE_OFF */
board/siemens/common/board.c +0 -9
@@ -159,13 +159,4 @@ U_BOOT_CMD("Sends U-Boot into infinite loop" ,"" ); - -#ifndef CONFIG_SYS_DCACHE_OFF -void enable_caches (void ) -{ -printf ("Enable d-cache\n" ); -/* Enable D-cache. I-cache is already enabled in start.S */ -dcache_enable (); -} -#endif /* CONFIG_SYS_DCACHE_OFF */ #endif /* !CONFIG_SPL_BUILD */
Signature · 1 line
1.8.4
PATCH 2/8 hash: Export functions to find and show hash
In reply to Simon GlassThese functions are generally useful for displaying a hash value and finding available algorithms, so export them.
--- common/hash.c | 13 ++++++------- include/hash.h | 22 ++++++++++++++++++++++ 2 files changed, 28 insertions(+), 7 deletions(-)
common/hash.c +6 -7
@@ -204,7 +204,7 @@ static int parse_verify_sum(struct hash_algo *algo, char *verify_str, u8 *vsum,return 0 ; } -static struct hash_algo *find_hash_algo (const char *name) +struct hash_algo *hash_find_algo (const char *name) {int i;
@@ -216,8 +216,7 @@ static struct hash_algo *find_hash_algo(const char *name)return NULL ; } -static void show_hash (struct hash_algo *algo,ulong addr,ulong len, -u8 *output) +void hash_show (struct hash_algo *algo,ulong addr,ulong len,u8 *output) {int i;
@@ -231,7 +230,7 @@ int hash_block(const char *algo_name, const void *data, unsigned int len, {struct hash_algo *algo; - algo =find_hash_algo (algo_name); + algo =hash_find_algo (algo_name);if (!algo) {debug ("Unknown hash algorithm '%s'\n" , algo_name);return -EPROTONOSUPPORT ;
@@ -265,7 +264,7 @@ int hash_command(const char *algo_name, int flags, cmd_tbl_t *cmdtp, int flag,u8 vsum[HASH_MAX_DIGEST_SIZE ];void *buf; - algo =find_hash_algo (algo_name); + algo =hash_find_algo (algo_name);if (!algo) {printf ("Unknown hash algorithm '%s'\n" , algo_name);return CMD_RET_USAGE ;
@@ -298,7 +297,7 @@ int hash_command(const char *algo_name, int flags, cmd_tbl_t *cmdtp, int flag,if (memcmp (output, vsum, algo->digest_size) !=0 ) {int i; -show_hash (algo, addr, len, output); +hash_show (algo, addr, len, output);printf (" != " );for (i =0 ; i < algo->digest_size; i++)printf ("%02x" , vsum[i]);
@@ -306,7 +305,7 @@ int hash_command(const char *algo_name, int flags, cmd_tbl_t *cmdtp, int flag,return 1 ; } }else { -show_hash (algo, addr, len, output); +hash_show (algo, addr, len, output);printf ("\n" );if (argc) {
include/hash.h +22 -0
@@ -77,4 +77,26 @@ int hash_command(const char *algo_name, int flags, cmd_tbl_t *cmdtp, int flag,int hash_block (const char *algo_name,const void *data,unsigned int len,uint8_t *output,int *output_size); +/** +* hash_find_algo() - Find an algorithm by name +* +* @name: Name of algorithm to search for +* @return pointer to algorithm structure, or NULL if not found +*/ +struct hash_algo *hash_find_algo (const char *name); + +/** +* hash_show() - Print out a hash algorithm and value +* +* You will get a message like this (without a newline at the end): +* +* "sha1 for 9eb3337c ... 9eb3338f ==> 7942ef1df479fd3130f716eb9613d107dab7e257" +* +* @algo: Algorithm used for hash +* @addr: Address of data that was hashed +* @len: Length of data that was hashed +* @output: Hash value to display +*/ +void hash_show (struct hash_algo *algo,ulong addr,ulong len,u8 *output); +#endif
Signature · 1 line
1.8.4
PATCH 3/8 fdt: Add DEV_TREE_BIN option to specify a device tree binary file
In reply to Simon GlassIn some cases, an externally-built device tree binary is required to be attached to U-Boot. An example is when using image signing, since in that case the .dtb file must include the public keys.
Add a DEV_TREE_BIN option to the Makefile, and update the documentation.
Usage is something like:
make DEV_TREE_BIN=boot/am335x-boneblack-pubkey.dtb
--- Makefile | 8 +++++++- doc/README.fdt-control | 16 ++++++++++++++-- 2 files changed, 21 insertions(+), 3 deletions(-)
Makefile +7 -1
@@ -416,9 +416,15 @@ endif all: $(ALL-y) $(SUBDIR_EXAMPLES) +# Allow a device tree binary to be given as a make argument +ifneq ($(DEV_TREE_BIN),) +$(obj)u-boot.dtb: + cp $(DEV_TREE_BIN) $@ +else $(obj)u-boot.dtb: checkdtc $(obj)u-boot $(MAKE) -C dts binary mv $(obj)dts/dt.dtb $@ +endif $(obj)u-boot-dtb.bin: $(obj)u-boot.bin $(obj)u-boot.dtb cat $^ >$@
@@ -452,7 +458,7 @@ ifndef CONFIG_SYS_UBOOT_START CONFIG_SYS_UBOOT_START := 0 endif -$(obj)u-boot.img: $(obj)u-boot.bin +$(obj)u-boot.img: $(obj)u-boot$(if $(CONFIG_OF_SEPARATE),-dtb,).bin $(obj)tools/mkimage -A $(ARCH) -T firmware -C none \ -O u-boot -a $(CONFIG_SYS_TEXT_BASE) \ -e $(CONFIG_SYS_UBOOT_START) \
doc/README.fdt-control +14 -2
@@ -122,7 +122,8 @@ This should include your CPU or SOC's device tree file, placed in arch/<arch>/dts, and then make any adjustments required. If CONFIG_OF_EMBED is defined, then it will be picked up and built into -the U-Boot image (including u-boot.bin). +the U-Boot image (including u-boot.bin). This is suitable for debugging +and development only and is not recommended for production devices. If CONFIG_OF_SEPARATE is defined, then it will be built and placed in a u-boot.dtb file alongside u-boot.bin. A common approach is then to
@@ -130,7 +131,10 @@ join the two: cat u-boot.bin u-boot.dtb >image.bin -and then flash image.bin onto your board. +and then flash image.bin onto your board. Note that U-Boot creates +u-boot-dtb.bin which does the above step for you also. If you are using +CONFIG_SPL_FRAMEWORK, then u-boot.img will be built to include the device +tree binary. If CONFIG_OF_HOSTFILE is defined, then it will be read from a file on startup. This is only useful for sandbox. Use the -d flag to U-Boot to
@@ -138,6 +142,14 @@ specify the file to read. You cannot use more than one of these options at the same time. +To use a device tree file that you have compiled yourself, pass +DEV_TREE_BIN=<filename> to 'make', as in: + + make DEV_TREE_BIN=boot/am335x-boneblack-pubkey.dtb + +Then U-Boot will copy that file to u-boot.dtb, put it in the .img file +if used, and u-boot-dtb.bin. + If you wish to put the fdt at a different address in memory, you can define the "fdtcontroladdr" environment variable. This is the hex address of the fdt binary blob, and will override either of the options.
Signature · 1 line
1.8.4
PATCH 4/8 fdt: Update functions which write to an FDT to return -ENOSPC
In reply to Simon GlassWhen writing values into an FDT it is possible that there will be insufficient space. If the caller gets a useful error in the then it can potentially deal with the situation.
Adjust these functions to return -ENOSPC when the FDT is full.
--- common/image-fit.c | 4 ++-- include/rsa.h | 3 ++- lib/rsa/rsa-sign.c | 28 +++++++++++++++++++--------- 3 files changed, 23 insertions(+), 12 deletions(-)
common/image-fit.c +2 -2
@@ -832,7 +832,7 @@ static int fit_image_hash_get_ignore(const void *fit, int noffset, int *ignore)* * returns: * 0, on success -* -1, on property read failure +* -ENOSPC if no space in device tree, -1 for other error */ int fit_set_timestamp (void *fit,int noffset,time_t timestamp) {
@@ -846,7 +846,7 @@ int fit_set_timestamp(void *fit, int noffset, time_t timestamp)printf ("Can't set '%s' property for '%s' node (%s)\n" ,FIT_TIMESTAMP_PROP ,fit_get_name (fit, noffset,NULL ),fdt_strerror (ret)); -return -1 ; +return ret == -FDT_ERR_NOSPACE ? -ENOSPC :-1 ; }return 0 ;
include/rsa.h +2 -1
@@ -46,7 +46,8 @@ int rsa_sign(struct image_sign_info *info,* * @info: Specifies key and FIT information * @keydest: Destination FDT blob for public key data -* @return: 0, on success, -ve on error +* @return: 0, on success, -ENOSPC if the keydest FDT blob ran out of space, +other -ve value on error */ int rsa_add_verify_data (struct image_sign_info *info,void *keydest);#else
lib/rsa/rsa-sign.c +19 -9
@@ -427,20 +427,30 @@ int rsa_add_verify_data(struct image_sign_info *info, void *keydest) ret =fdt_setprop_string (keydest, node,"key-name-hint" , info->keyname); - ret |=fdt_setprop_u32 (keydest, node,"rsa,num-bits" , bits); - ret |=fdt_setprop_u32 (keydest, node,"rsa,n0-inverse" , n0_inv); - ret |=fdt_add_bignum (keydest, node,"rsa,modulus" , modulus, bits); - ret |=fdt_add_bignum (keydest, node,"rsa,r-squared" , r_squared, bits); - ret |=fdt_setprop_string (keydest, node,FIT_ALGO_PROP , - info->algo->name); +if (!ret) + ret =fdt_setprop_u32 (keydest, node,"rsa,num-bits" , bits); +if (!ret) + ret =fdt_setprop_u32 (keydest, node,"rsa,n0-inverse" , n0_inv); +if (!ret) { + ret =fdt_add_bignum (keydest, node,"rsa,modulus" , modulus, + bits); + } +if (!ret) { + ret =fdt_add_bignum (keydest, node,"rsa,r-squared" , r_squared, + bits); + } +if (!ret) { + ret =fdt_setprop_string (keydest, node,FIT_ALGO_PROP , + info->algo->name); + }if (info->require_keys) { -fdt_setprop_string (keydest, node,"required" , - info->require_keys); + ret =fdt_setprop_string (keydest, node,"required" , + info->require_keys); }BN_free (modulus);BN_free (r_squared);if (ret) -return -EIO ; +return ret ==FDT_ERR_NOSPACE ? -ENOSPC : -EIO ;return 0 ; }
Signature · 1 line
1.8.4
PATCH 5/8 arm: ti: Increase malloc size to 16MB for armv7 boards
In reply to Simon GlassThe current size of 1MB is not enough use to use DFU. Increase it for ARMv7 boards, all of which should have 32MB or more SDRAM.
With this change it is possible to do 'dfu mmc 0' on a Beaglebone Black.
--- include/configs/ti_armv7_common.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/configs/ti_armv7_common.h +1 -1
@@ -102,7 +102,7 @@* we are on so we do not need to rely on the command prompt. We set a * console baudrate of 115200 and use the default baud rate table. */ -#define CONFIG_SYS_MALLOC_LEN (1024 << 10) +#define CONFIG_SYS_MALLOC_LEN (16 << 20)#define CONFIG_SYS_HUSH_PARSER #define CONFIG_SYS_PROMPT "U-Boot# "#define CONFIG_SYS_CONSOLE_INFO_QUIET
Signature · 1 line
1.8.4
PATCH 6/8 RFC: am33xx/omap: Enable CONFIG_OF_CONTROL
In reply to Simon GlassAdd support for device tree control and add device tree files for the beaglebone black initially.
--- arch/arm/dts/am33xx.dtsi | 649 ++++++++++++++++++++++++++++++ arch/arm/dts/dt-bindings/gpio/gpio.h | 15 + arch/arm/dts/dt-bindings/pinctrl/am33xx.h | 41 ++ arch/arm/dts/dt-bindings/pinctrl/omap.h | 54 +++ board/ti/dts/am335x-bone-common.dtsi | 262 ++++++++++++ board/ti/dts/am335x-boneblack.dts | 17 + board/ti/dts/tps65217.dtsi | 56 +++ include/configs/am335x_evm.h | 6 + 8 files changed, 1100 insertions(+) create mode 100644 arch/arm/dts/am33xx.dtsi create mode 100644 arch/arm/dts/dt-bindings/gpio/gpio.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/am33xx.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/omap.h create mode 100644 board/ti/dts/am335x-bone-common.dtsi create mode 100644 board/ti/dts/am335x-boneblack.dts create mode 100644 board/ti/dts/tps65217.dtsi
arch/arm/dts/am33xx.dtsi new file +649 -0
@@ -0,0 +1,649 @@ +/* + * Device Tree Source for AM33XX SoC + * + * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ + * + * This file is licensed under the terms of the GNU General Public License + * version 2. This program is licensed "as is" without any warranty of any + * kind, whether express or implied. + */ + +#include <dt-bindings/gpio/gpio.h> +#include <dt-bindings/pinctrl/am33xx.h> + +#include "skeleton.dtsi" + +/ { + compatible = "ti,am33xx"; + interrupt-parent = <&intc>; + + aliases { + serial0 = &uart0; + serial1 = &uart1; + serial2 = &uart2; + serial3 = &uart3; + serial4 = &uart4; + serial5 = &uart5; + d_can0 = &dcan0; + d_can1 = &dcan1; + usb0 = &usb0; + usb1 = &usb1; + phy0 = &usb0_phy; + phy1 = &usb1_phy; + }; + + cpus { + #address-cells = <1>; + #size-cells = <0>; + cpu at 0 { + compatible = "arm,cortex-a8"; + device_type = "cpu"; + reg = <0>; + + /* + * To consider voltage drop between PMIC and SoC, + * tolerance value is reduced to 2% from 4% and + * voltage value is increased as a precaution. + */ + operating-points = < + /* kHz uV */ + 720000 1285000 + 600000 1225000 + 500000 1125000 + 275000 1125000 + >; + voltage-tolerance = <2>; /* 2 percentage */ + clock-latency = <300000>; /* From omap-cpufreq driver */ + }; + }; + + /* + * The soc node represents the soc top level view. It is uses for IPs + * that are not memory mapped in the MPU view or for the MPU itself. + */ + soc { + compatible = "ti,omap-infra"; + mpu { + compatible = "ti,omap3-mpu"; + ti,hwmods = "mpu"; + }; + }; + + am33xx_pinmux: pinmux at 44e10800 { + compatible = "pinctrl-single"; + reg = <0x44e10800 0x0238>; + #address-cells = <1>; + #size-cells = <0>; + pinctrl-single,register-width = <32>; + pinctrl-single,function-mask = <0x7f>; + }; + + /* + * XXX: Use a flat representation of the AM33XX interconnect. + * The real AM33XX interconnect network is quite complex.Since + * that will not bring real advantage to represent that in DT + * for the moment, just use a fake OCP bus entry to represent + * the whole bus hierarchy. + */ + ocp { + compatible = "simple-bus"; + #address-cells = <1>; + #size-cells = <1>; + ranges; + ti,hwmods = "l3_main"; + + intc: interrupt-controller at 48200000 { + compatible = "ti,omap2-intc"; + interrupt-controller; + #interrupt-cells = <1>; + ti,intc-size = <128>; + reg = <0x48200000 0x1000>; + }; + + gpio0: gpio at 44e07000 { + compatible = "ti,omap4-gpio"; + ti,hwmods = "gpio1"; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x44e07000 0x1000>; + interrupts = <96>; + }; + + gpio1: gpio at 4804c000 { + compatible = "ti,omap4-gpio"; + ti,hwmods = "gpio2"; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x4804c000 0x1000>; + interrupts = <98>; + }; + + gpio2: gpio at 481ac000 { + compatible = "ti,omap4-gpio"; + ti,hwmods = "gpio3"; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x481ac000 0x1000>; + interrupts = <32>; + }; + + gpio3: gpio at 481ae000 { + compatible = "ti,omap4-gpio"; + ti,hwmods = "gpio4"; + gpio-controller; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <1>; + reg = <0x481ae000 0x1000>; + interrupts = <62>; + }; + + uart0: serial at 44e09000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart1"; + clock-frequency = <48000000>; + reg = <0x44e09000 0x2000>; + interrupts = <72>; + status = "disabled"; + }; + + uart1: serial at 48022000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart2"; + clock-frequency = <48000000>; + reg = <0x48022000 0x2000>; + interrupts = <73>; + status = "disabled"; + }; + + uart2: serial at 48024000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart3"; + clock-frequency = <48000000>; + reg = <0x48024000 0x2000>; + interrupts = <74>; + status = "disabled"; + }; + + uart3: serial at 481a6000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart4"; + clock-frequency = <48000000>; + reg = <0x481a6000 0x2000>; + interrupts = <44>; + status = "disabled"; + }; + + uart4: serial at 481a8000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart5"; + clock-frequency = <48000000>; + reg = <0x481a8000 0x2000>; + interrupts = <45>; + status = "disabled"; + }; + + uart5: serial at 481aa000 { + compatible = "ti,omap3-uart"; + ti,hwmods = "uart6"; + clock-frequency = <48000000>; + reg = <0x481aa000 0x2000>; + interrupts = <46>; + status = "disabled"; + }; + + i2c0: i2c at 44e0b000 { + compatible = "ti,omap4-i2c"; + #address-cells = <1>; + #size-cells = <0>; + ti,hwmods = "i2c1"; + reg = <0x44e0b000 0x1000>; + interrupts = <70>; + status = "disabled"; + }; + + i2c1: i2c at 4802a000 { + compatible = "ti,omap4-i2c"; + #address-cells = <1>; + #size-cells = <0>; + ti,hwmods = "i2c2"; + reg = <0x4802a000 0x1000>; + interrupts = <71>; + status = "disabled"; + }; + + i2c2: i2c at 4819c000 { + compatible = "ti,omap4-i2c"; + #address-cells = <1>; + #size-cells = <0>; + ti,hwmods = "i2c3"; + reg = <0x4819c000 0x1000>; + interrupts = <30>; + status = "disabled"; + }; + + wdt2: wdt at 44e35000 { + compatible = "ti,omap3-wdt"; + ti,hwmods = "wd_timer2"; + reg = <0x44e35000 0x1000>; + interrupts = <91>; + }; + + dcan0: d_can at 481cc000 { + compatible = "bosch,d_can"; + ti,hwmods = "d_can0"; + reg = <0x481cc000 0x2000 + 0x44e10644 0x4>; + interrupts = <52>; + status = "disabled"; + }; + + dcan1: d_can at 481d0000 { + compatible = "bosch,d_can"; + ti,hwmods = "d_can1"; + reg = <0x481d0000 0x2000 + 0x44e10644 0x4>; + interrupts = <55>; + status = "disabled"; + }; + + timer1: timer at 44e31000 { + compatible = "ti,am335x-timer-1ms"; + reg = <0x44e31000 0x400>; + interrupts = <67>; + ti,hwmods = "timer1"; + ti,timer-alwon; + }; + + timer2: timer at 48040000 { + compatible = "ti,am335x-timer"; + reg = <0x48040000 0x400>; + interrupts = <68>; + ti,hwmods = "timer2"; + }; + + timer3: timer at 48042000 { + compatible = "ti,am335x-timer"; + reg = <0x48042000 0x400>; + interrupts = <69>; + ti,hwmods = "timer3"; + }; + + timer4: timer at 48044000 { + compatible = "ti,am335x-timer"; + reg = <0x48044000 0x400>; + interrupts = <92>; + ti,hwmods = "timer4"; + ti,timer-pwm; + }; + + timer5: timer at 48046000 { + compatible = "ti,am335x-timer"; + reg = <0x48046000 0x400>; + interrupts = <93>; + ti,hwmods = "timer5"; + ti,timer-pwm; + }; + + timer6: timer at 48048000 { + compatible = "ti,am335x-timer"; + reg = <0x48048000 0x400>; + interrupts = <94>; + ti,hwmods = "timer6"; + ti,timer-pwm; + }; + + timer7: timer at 4804a000 { + compatible = "ti,am335x-timer"; + reg = <0x4804a000 0x400>; + interrupts = <95>; + ti,hwmods = "timer7"; + ti,timer-pwm; + }; + + rtc at 44e3e000 { + compatible = "ti,da830-rtc"; + reg = <0x44e3e000 0x1000>; + interrupts = <75 + 76>; + ti,hwmods = "rtc"; + }; + + spi0: spi at 48030000 { + compatible = "ti,omap4-mcspi"; + #address-cells = <1>; + #size-cells = <0>; + reg = <0x48030000 0x400>; + interrupts = <65>; + ti,spi-num-cs = <2>; + ti,hwmods = "spi0"; + status = "disabled"; + }; + + spi1: spi at 481a0000 { + compatible = "ti,omap4-mcspi"; + #address-cells = <1>; + #size-cells = <0>; + reg = <0x481a0000 0x400>; + interrupts = <125>; + ti,spi-num-cs = <2>; + ti,hwmods = "spi1"; + status = "disabled"; + }; + + usb: usb at 47400000 { + compatible = "ti,am33xx-usb"; + reg = <0x47400000 0x1000>; + ranges; + #address-cells = <1>; + #size-cells = <1>; + ti,hwmods = "usb_otg_hs"; + status = "disabled"; + + ctrl_mod: control at 44e10000 { + compatible = "ti,am335x-usb-ctrl-module"; + reg = <0x44e10620 0x10 + 0x44e10648 0x4>; + reg-names = "phy_ctrl", "wakeup"; + status = "disabled"; + }; + + usb0_phy: usb-phy at 47401300 { + compatible = "ti,am335x-usb-phy"; + reg = <0x47401300 0x100>; + reg-names = "phy"; + status = "disabled"; + ti,ctrl_mod = <&ctrl_mod>; + }; + + usb0: usb at 47401000 { + compatible = "ti,musb-am33xx"; + status = "disabled"; + reg = <0x47401400 0x400 + 0x47401000 0x200>; + reg-names = "mc", "control"; + + interrupts = <18>; + interrupt-names = "mc"; + dr_mode = "otg"; + mentor,multipoint = <1>; + mentor,num-eps = <16>; + mentor,ram-bits = <12>; + mentor,power = <500>; + phys = <&usb0_phy>; + + dmas = <&cppi41dma 0 0 &cppi41dma 1 0 + &cppi41dma 2 0 &cppi41dma 3 0 + &cppi41dma 4 0 &cppi41dma 5 0 + &cppi41dma 6 0 &cppi41dma 7 0 + &cppi41dma 8 0 &cppi41dma 9 0 + &cppi41dma 10 0 &cppi41dma 11 0 + &cppi41dma 12 0 &cppi41dma 13 0 + &cppi41dma 14 0 &cppi41dma 0 1 + &cppi41dma 1 1 &cppi41dma 2 1 + &cppi41dma 3 1 &cppi41dma 4 1 + &cppi41dma 5 1 &cppi41dma 6 1 + &cppi41dma 7 1 &cppi41dma 8 1 + &cppi41dma 9 1 &cppi41dma 10 1 + &cppi41dma 11 1 &cppi41dma 12 1 + &cppi41dma 13 1 &cppi41dma 14 1>; + dma-names = + "rx1", "rx2", "rx3", "rx4", "rx5", "rx6", "rx7", + "rx8", "rx9", "rx10", "rx11", "rx12", "rx13", + "rx14", "rx15", + "tx1", "tx2", "tx3", "tx4", "tx5", "tx6", "tx7", + "tx8", "tx9", "tx10", "tx11", "tx12", "tx13", + "tx14", "tx15"; + }; + + usb1_phy: usb-phy at 47401b00 { + compatible = "ti,am335x-usb-phy"; + reg = <0x47401b00 0x100>; + reg-names = "phy"; + status = "disabled"; + ti,ctrl_mod = <&ctrl_mod>; + }; + + usb1: usb at 47401800 { + compatible = "ti,musb-am33xx"; + status = "disabled"; + reg = <0x47401c00 0x400 + 0x47401800 0x200>; + reg-names = "mc", "control"; + interrupts = <19>; + interrupt-names = "mc"; + dr_mode = "otg"; + mentor,multipoint = <1>; + mentor,num-eps = <16>; + mentor,ram-bits = <12>; + mentor,power = <500>; + phys = <&usb1_phy>; + + dmas = <&cppi41dma 15 0 &cppi41dma 16 0 + &cppi41dma 17 0 &cppi41dma 18 0 + &cppi41dma 19 0 &cppi41dma 20 0 + &cppi41dma 21 0 &cppi41dma 22 0 + &cppi41dma 23 0 &cppi41dma 24 0 + &cppi41dma 25 0 &cppi41dma 26 0 + &cppi41dma 27 0 &cppi41dma 28 0 + &cppi41dma 29 0 &cppi41dma 15 1 + &cppi41dma 16 1 &cppi41dma 17 1 + &cppi41dma 18 1 &cppi41dma 19 1 + &cppi41dma 20 1 &cppi41dma 21 1 + &cppi41dma 22 1 &cppi41dma 23 1 + &cppi41dma 24 1 &cppi41dma 25 1 + &cppi41dma 26 1 &cppi41dma 27 1 + &cppi41dma 28 1 &cppi41dma 29 1>; + dma-names = + "rx1", "rx2", "rx3", "rx4", "rx5", "rx6", "rx7", + "rx8", "rx9", "rx10", "rx11", "rx12", "rx13", + "rx14", "rx15", + "tx1", "tx2", "tx3", "tx4", "tx5", "tx6", "tx7", + "tx8", "tx9", "tx10", "tx11", "tx12", "tx13", + "tx14", "tx15"; + }; + + cppi41dma: dma-controller at 07402000 { + compatible = "ti,am3359-cppi41"; + reg = <0x47400000 0x1000 + 0x47402000 0x1000 + 0x47403000 0x1000 + 0x47404000 0x4000>; + reg-names = "glue", "controller", "scheduler", "queuemgr"; + interrupts = <17>; + interrupt-names = "glue"; + #dma-cells = <2>; + #dma-channels = <30>; + #dma-requests = <256>; + status = "disabled"; + }; + }; + + epwmss0: epwmss at 48300000 { + compatible = "ti,am33xx-pwmss"; + reg = <0x48300000 0x10>; + ti,hwmods = "epwmss0"; + #address-cells = <1>; + #size-cells = <1>; + status = "disabled"; + ranges = <0x48300100 0x48300100 0x80 /* ECAP */ + 0x48300180 0x48300180 0x80 /* EQEP */ + 0x48300200 0x48300200 0x80>; /* EHRPWM */ + + ecap0: ecap at 48300100 { + compatible = "ti,am33xx-ecap"; + #pwm-cells = <3>; + reg = <0x48300100 0x80>; + ti,hwmods = "ecap0"; + status = "disabled"; + }; + + ehrpwm0: ehrpwm at 48300200 { + compatible = "ti,am33xx-ehrpwm"; + #pwm-cells = <3>; + reg = <0x48300200 0x80>; + ti,hwmods = "ehrpwm0"; + status = "disabled"; + }; + }; + + epwmss1: epwmss at 48302000 { + compatible = "ti,am33xx-pwmss"; + reg = <0x48302000 0x10>; + ti,hwmods = "epwmss1"; + #address-cells = <1>; + #size-cells = <1>; + status = "disabled"; + ranges = <0x48302100 0x48302100 0x80 /* ECAP */ + 0x48302180 0x48302180 0x80 /* EQEP */ + 0x48302200 0x48302200 0x80>; /* EHRPWM */ + + ecap1: ecap at 48302100 { + compatible = "ti,am33xx-ecap"; + #pwm-cells = <3>; + reg = <0x48302100 0x80>; + ti,hwmods = "ecap1"; + status = "disabled"; + }; + + ehrpwm1: ehrpwm at 48302200 { + compatible = "ti,am33xx-ehrpwm"; + #pwm-cells = <3>; + reg = <0x48302200 0x80>; + ti,hwmods = "ehrpwm1"; + status = "disabled"; + }; + }; + + epwmss2: epwmss at 48304000 { + compatible = "ti,am33xx-pwmss"; + reg = <0x48304000 0x10>; + ti,hwmods = "epwmss2"; + #address-cells = <1>; + #size-cells = <1>; + status = "disabled"; + ranges = <0x48304100 0x48304100 0x80 /* ECAP */ + 0x48304180 0x48304180 0x80 /* EQEP */ + 0x48304200 0x48304200 0x80>; /* EHRPWM */ + + ecap2: ecap at 48304100 { + compatible = "ti,am33xx-ecap"; + #pwm-cells = <3>; + reg = <0x48304100 0x80>; + ti,hwmods = "ecap2"; + status = "disabled"; + }; + + ehrpwm2: ehrpwm at 48304200 { + compatible = "ti,am33xx-ehrpwm"; + #pwm-cells = <3>; + reg = <0x48304200 0x80>; + ti,hwmods = "ehrpwm2"; + status = "disabled"; + }; + }; + + mac: ethernet at 4a100000 { + compatible = "ti,cpsw"; + ti,hwmods = "cpgmac0"; + cpdma_channels = <8>; + ale_entries = <1024>; + bd_ram_size = <0x2000>; + no_bd_ram = <0>; + rx_descs = <64>; + mac_control = <0x20>; + slaves = <2>; + active_slave = <0>; + cpts_clock_mult = <0x80000000>; + cpts_clock_shift = <29>; + reg = <0x4a100000 0x800 + 0x4a101200 0x100>; + #address-cells = <1>; + #size-cells = <1>; + interrupt-parent = <&intc>; + /* + * c0_rx_thresh_pend + * c0_rx_pend + * c0_tx_pend + * c0_misc_pend + */ + interrupts = <40 41 42 43>; + ranges; + + davinci_mdio: mdio at 4a101000 { + compatible = "ti,davinci_mdio"; + #address-cells = <1>; + #size-cells = <0>; + ti,hwmods = "davinci_mdio"; + bus_freq = <1000000>; + reg = <0x4a101000 0x100>; + }; + + cpsw_emac0: slave at 4a100200 { + /* Filled in by U-Boot */ + mac-address = [ 00 00 00 00 00 00 ]; + }; + + cpsw_emac1: slave at 4a100300 { + /* Filled in by U-Boot */ + mac-address = [ 00 00 00 00 00 00 ]; + }; + }; + + ocmcram: ocmcram at 40300000 { + compatible = "ti,am3352-ocmcram"; + reg = <0x40300000 0x10000>; + ti,hwmods = "ocmcram"; + }; + + wkup_m3: wkup_m3 at 44d00000 { + compatible = "ti,am3353-wkup-m3"; + reg = <0x44d00000 0x4000 /* M3 UMEM */ + 0x44d80000 0x2000>; /* M3 DMEM */ + ti,hwmods = "wkup_m3"; + }; + + elm: elm at 48080000 { + compatible = "ti,am3352-elm"; + reg = <0x48080000 0x2000>; + interrupts = <4>; + ti,hwmods = "elm"; + status = "disabled"; + }; + + tscadc: tscadc at 44e0d000 { + compatible = "ti,am3359-tscadc"; + reg = <0x44e0d000 0x1000>; + interrupt-parent = <&intc>; + interrupts = <16>; + ti,hwmods = "adc_tsc"; + status = "disabled"; + + tsc { + compatible = "ti,am3359-tsc"; + }; + am335x_adc: adc { + #io-channel-cells = <1>; + compatible = "ti,am3359-adc"; + }; + }; + + gpmc: gpmc at 50000000 { + compatible = "ti,am3352-gpmc"; + ti,hwmods = "gpmc"; + reg = <0x50000000 0x2000>; + interrupts = <100>; + gpmc,num-cs = <7>; + gpmc,num-waitpins = <2>; + #address-cells = <2>; + #size-cells = <1>; + status = "disabled"; + }; + }; +};
arch/arm/dts/dt-bindings/gpio/gpio.h new file +15 -0
@@ -0,0 +1,15 @@ +/* +* This header provides constants for most GPIO bindings. +* +* Most GPIO bindings include a flags cell as part of the GPIO specifier. +* In most cases, the format of the flags cell uses the standard values +* defined in this header. +*/ + +#ifndef _DT_BINDINGS_GPIO_GPIO_H +#define _DT_BINDINGS_GPIO_GPIO_H + +#define GPIO_ACTIVE_HIGH 0 +#define GPIO_ACTIVE_LOW 1 + +#endif
arch/arm/dts/dt-bindings/pinctrl/am33xx.h new file +41 -0
41 lines not on this page · raw message
arch/arm/dts/dt-bindings/pinctrl/omap.h new file +54 -0
54 lines not on this page · raw message
board/ti/dts/am335x-bone-common.dtsi new file +262 -0
262 lines not on this page · raw message
board/ti/dts/am335x-boneblack.dts new file +17 -0
@@ -0,0 +1,17 @@ +/* + * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License version 2 as + * published by the Free Software Foundation. + */ +/dts-v1/; + +#include "am33xx.dtsi" +#include "am335x-bone-common.dtsi" + +&ldo3_reg { + regulator-min-microvolt = <1800000>; + regulator-max-microvolt = <1800000>; + regulator-always-on; +};
board/ti/dts/tps65217.dtsi new file +56 -0
56 lines not on this page · raw message
include/configs/am335x_evm.h +6 -0
@@ -18,6 +18,12 @@#include <configs/ti_am335x_common.h> +#ifndef CONFIG_SPL_BUILD +# define CONFIG_OF_CONTROL +# define CONFIG_OF_SEPARATE +# define CONFIG_DEFAULT_DEVICE_TREE am335x-boneblack +#endif +#define MACH_TYPE_TIAM335EVM 3589/* Until the next sync */ #define CONFIG_MACH_TYPE MACH_TYPE_TIAM335EVM
Signature · 1 line
1.8.4
PATCH 7/8 RFC: am33xx/omap: Enable FIT support
In reply to Simon GlassEnable booting a FIT containing a kernel/device tree.
--- include/configs/am335x_evm.h | 1 + 1 file changed, 1 insertion(+)
include/configs/am335x_evm.h +1 -0
@@ -19,6 +19,7 @@#include <configs/ti_am335x_common.h> #ifndef CONFIG_SPL_BUILD +# define CONFIG_FIT # define CONFIG_OF_CONTROL # define CONFIG_OF_SEPARATE # define CONFIG_DEFAULT_DEVICE_TREE am335x-boneblack
Signature · 1 line
1.8.4
PATCH 8/8 RFC: am33xx/omap: Enable secure boot with CONFIG_FIT_SIGNATURE
In reply to Simon GlassEnable secure boot functionality.
--- include/configs/am335x_evm.h | 2 ++ 1 file changed, 2 insertions(+)
include/configs/am335x_evm.h +2 -0
@@ -20,6 +20,8 @@#ifndef CONFIG_SPL_BUILD # define CONFIG_FIT +# define CONFIG_FIT_SIGNATURE +# define CONFIG_RSA # define CONFIG_OF_CONTROL # define CONFIG_OF_SEPARATE # define CONFIG_DEFAULT_DEVICE_TREE am335x-boneblack
Signature · 1 line
1.8.4
cover Secure boot improvements and test on Beaglebone Black
In reply to Simon GlassHi Tom,
Quoted 11 lines · Simon Glass
This series adds a few improvements to the image signing feature to make it easier to use on the Beaglebone Black.
- Add a
DEV_TREE_BINoption to make it easier to include the correct FDT (with embedded public keys) into the U-Boot image
- Enable cache for more TI boards (to speed things up)
- Increase malloc size
- EnableCONFIG_OF_CONTROL, FIT and secure boot on am33xx/omap (RFC only, not sure we want this, although we could create a separate config for it)
Quoted 6 lines
I also have a change to adjust mkimage to automatically make space in the FDT when adding hashes and signatures. Included here is the ENOSPC patch, but the
fit_image.cpatch will wait until the dumpimage tool is merged, since I am changing the same code.With this, secure boot was tested successfully on Beaglebone Black.
Do you think any of these patches should be applied?
Regards,
Simon
Quoted 46 lines
Simon Glass (8):
am33xx/omap: Allow cache enable for all Sitara/OMAP
hash: Export functions to find and show hash
fdt: AddDEV_TREE_BINoption to specify a device tree binary file
fdt: Update functions which write to an FDT to return-ENOSPC
arm: ti: Increase malloc size to 16MB for armv7 boards
RFC: am33xx/omap: EnableCONFIG_OF_CONTROL
RFC: am33xx/omap: Enable FIT support
RFC: am33xx/omap: Enable secure boot withCONFIG_FIT_SIGNATUREMakefile | 8 +- arch/arm/cpu/armv7/omap-common/Makefile | 4 + arch/arm/cpu/armv7/omap-common/hwinit-common.c | 41 -- arch/arm/cpu/armv7/omap-common/omap-cache.c | 56 +++ arch/arm/cpu/armv7/omap3/board.c | 8 - arch/arm/dts/am33xx.dtsi | 649 +++++++++++++++++++++++++ arch/arm/dts/dt-bindings/gpio/gpio.h | 15 + arch/arm/dts/dt-bindings/pinctrl/am33xx.h | 41 ++ arch/arm/dts/dt-bindings/pinctrl/omap.h | 54 ++ board/siemens/common/board.c | 9 - board/ti/dts/am335x-bone-common.dtsi | 262 ++++++++++ board/ti/dts/am335x-boneblack.dts | 17 + board/ti/dts/tps65217.dtsi | 56 +++ common/hash.c | 13 +- common/image-fit.c | 4 +- doc/README.fdt-control | 16 +- include/configs/am335x_evm.h | 9 + include/configs/ti_armv7_common.h | 2 +- include/hash.h | 22 + include/rsa.h | 3 +- lib/rsa/rsa-sign.c | 28 +- 21 files changed, 1236 insertions(+), 81 deletions(-) create mode 100644 arch/arm/cpu/armv7/omap-common/omap-cache.c create mode 100644 arch/arm/dts/am33xx.dtsi create mode 100644 arch/arm/dts/dt-bindings/gpio/gpio.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/am33xx.h create mode 100644 arch/arm/dts/dt-bindings/pinctrl/omap.h create mode 100644 board/ti/dts/am335x-bone-common.dtsi create mode 100644 board/ti/dts/am335x-boneblack.dts create mode 100644 board/ti/dts/tps65217.dtsi--
1.8.4
cover Secure boot improvements and test on Beaglebone Black
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 14 lines · Simon Glass
Hi Tom,
Quoted 11 lines · Simon Glass
This series adds a few improvements to the image signing feature to make it easier to use on the Beaglebone Black.
- Add a
DEV_TREE_BINoption to make it easier to include the correct FDT (with embedded public keys) into the U-Boot image
- Enable cache for more TI boards (to speed things up)
- Increase malloc size
- EnableCONFIG_OF_CONTROL, FIT and secure boot on am33xx/omap (RFC only, not sure we want this, although we could create a separate config for it)
Quoted 8 lines
Quoted 6 lines
I also have a change to adjust mkimage to automatically make space in the FDT when adding hashes and signatures. Included here is the ENOSPC patch, but the
fit_image.cpatch will wait until the dumpimage tool is merged, since I am changing the same code.With this, secure boot was tested successfully on Beaglebone Black.
Do you think any of these patches should be applied?
Sorry I've taken so long to cycle back on this. At the high level, I'm OK with it. But we need to make sure we can do these features optionally, perhaps with a separate build?
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJStJOnAAoJENk4IS6UOR1WpGcP/0CljP92ImQWtwcNcyCsjOqU Nkm2hJ1eI3e4XGEVkO9zWAxrcTtCOgdWdOnMeLjtpWTrWZ/CKmEXcbU6rxR7Q/vu /8r0FrUaYNHxsuTs0P5aBWhs3G+C83wKbbFViseHaKx2GMQ8+SZg72YBgDdI1t+B rEaA9t4/ZEFKY5HgJ47NZ/cJvs/2EFpbGTZgmgiqT/1P0aayN6YOAvmbkkkuxn8g HIJ8Jt1bGZ6CqTkDMt/qCeunCinSU76C19Bj+6cMTtoam9rltzdWaPoc4adi3QPw WfEZnUia5KxuGDLV/itO2LUrO58r8N5eOJN3iISAGkgzmRumhaxjlOrytq97p//D ZHlbwp2aQKLTRLh7B9T7HRs3AW3j+ltlQ11iF0GXtZ4WGeqy2IfMrhY708CwG/p5 Nu12cDW7hk5QJs/Dy55VsnxQ8t4yp/Y6v1K9g49BWKp/KZVa8qEab8VIV2N9iO38 czHfs4tlY3LgdP2y7fx15gANMM82eK6z9PkDtP+tvlkBGCh/FQ1wLUiq3pBR0VKu vhmM33RzkI9l2nIFzDybwU5iLfjGOm4ILuLNsQpTU1wWCjoyCi6t3fkqNQfHrguS Kun0UHf7M104q0SxwR03hv/RZw9sM5vFFq/2rWQI+vZ2neMMCd+LtOiIQUPTWUp+ NEYG+D/UfhT3WGlvzMdT
=wxou
-----END PGP SIGNATURE-----
cover Secure boot improvements and test on Beaglebone Black
Hi Tom,
Quoted 26 lines · Tom Rini
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 12 lines · Simon Glass
Hi Tom,
Quoted 9 lines · Simon Glass
This series adds a few improvements to the image signing feature to make it easier to use on the Beaglebone Black.
- Add a
DEV_TREE_BINoption to make it easier to include the correct FDT (with embedded public keys) into the U-Boot image
- Enable cache for more TI boards (to speed things up)
- Increase malloc size
- EnableCONFIG_OF_CONTROL, FIT and secure boot on am33xx/omap (RFC only, not sure we want this, although we could create aseparate
Quoted 3 lines
Quoted 3 lines
config for it)
I also have a change to adjust mkimage to automatically make space in
the
Quoted 1 line
Quoted 1 line
FDT when adding hashes and signatures. Included here is the ENOSPC
patch,
Quoted 3 lines
Quoted 3 lines
but the
fit_image.cpatch will wait until the dumpimage tool is merged, since I am changing the same code.
Quoted 8 lines
Quoted 3 lines
Quoted 1 line
With this, secure boot was tested successfully on Beaglebone Black.
Do you think any of these patches should be applied?
Sorry I've taken so long to cycle back on this. At the high level, I'm OK with it. But we need to make sure we can do these features optionally, perhaps with a separate build?
Do you think we should apply the ones except for the secure boot stuff (marked RFC)?
Regards,
Simon
[U-Boot] sandbox question
In reply to Simon GlassHi, Simon:
Sandbox concept is a very good idea to test uboot's non-platform part code.
I have a question about compiling uboot sandbox branch:
1. It seems sandbox branch could be compiled by gcc compiler on a x86 platform.
Not need to set cross compiler tool chains.
And after finished compiling, it could be run on a x86 environment. So, my question is:
Arm cross compiler tool chains could produce different obj file for a
same .C file.
The obj file for a same .C file by arm cross compiler tool chain is
not different with the obj file produced by a x86 gcc tool.
(On my x86 platform, defaut gcc is a x86 version)
So, for more precise test for non-platform code:
User should compile sandbox branch with an arm cross compiler tool
chain.
And should run it on an arm linux environment?
Best wishes,
[U-Boot] sandbox question
Hi, Simon:
Sorry for some typo.
I re-wrote this mail:
---------------------------------------
I have a question about compiling uboot sandbox branch:
1. It seems sandbox branch could be compiled by gcc compiler on a x86 platform.
Not need to set cross compiler tool chains.
And after finished compiling, it could be run on a x86 environment. So, my question is:
The obj file for a same .C file by arm cross compiler tool chain is
different with the obj file produced by a x86 gcc tool.
(On my x86 platform, defaut gcc is a x86 version)
So, for more precise test for non-platform code:
User should compile sandbox branch with an arm cross compiler tool
chain.
And should run it on an arm linux environment?
Best wishes,
[U-Boot] sandbox question
Hi Tiger,
Quoted 4 lines · On 30 December 2013 17:42, <[email protected]> wrote:
Hi, Simon:
Sorry for some typo.
I re-wrote this mail:
I've been away, sorry for the delay.
Quoted 11 lines
---------------------------------------
I have a question about compiling uboot sandbox branch:
1. It seems sandbox branch could be compiled by gcc compiler on a x86 platform.
Not need to set cross compiler tool chains.
And after finished compiling, it could be run on a x86 environment. So, my question is:
The obj file for a same .C file by arm cross compiler tool chain is
different with the obj file produced by a x86 gcc tool.
(On my x86 platform, defaut gcc is a x86 version)
Quoted 5 lines
So, for more precise test for non-platform code:
User should compile sandbox branch with an arm cross compiler tool
chain.
And should run it on an arm linux environment?
Well you could, but what benefit would that provide? It would not use any code from arch/arm if that is what you are thinking. Sandbox is its own 'architecture'?
Regards,
Simon
Quoted 3 lines
Best wishes,
[U-Boot] sandbox question
Hi, Simon:
Thanks for your reply!
Quoted 1 line
Well you could, but what benefit would that provide? It would not use
any code from arch/arm if that is what you are thinking. Sandbox is its own >'architecture'?
For example:
1. i want to test fs/ext4 driver.
They are architecture independent code.
I means:
(1) the obj files produced by arm gcc compiler are different with obj files produced by x86 gcc compiler.
Maybe arm gcc compiler would introduce some arm architecture
related optimizations for fs/ext4 drivers.
Maybe x86 gcc compiler would introduce some x86 architecture
related optimizations for fs/ext4 drivers.
So, if sandbox's fs/ext4 drivers' test passed on an x86
platform,but these architecture related optimizations would cause
some potential bugs on ARM platform.
Is it a problem?
Best wishes,
[U-Boot] sandbox question
Hello Tiger,
Quoted 7 lines · On Wed, Jan 8, 2014 at 6:22 AM, <[email protected]> wrote:
Hi, Simon:
Thanks for your reply!
Quoted 1 line
Well you could, but what benefit would that provide? It would not use
any code from
arch/armif that is what you are thinking. Sandbox is its own >'architecture'?
Your question seems a bit odd to me. My understanding of the sandbox feature, is to let someone play around with u-boot from an architecture independent perspective. Theoretically, this means that you should be able to cross-compile the sandbox application as an ARM executable and run it anywhere ... like on the Raspberry Pi (ARMv7, I think). Or you could just compile it and run on a standard x86 system.
Obviously, the binary images produced for both architectures will be different, but the code should work the same. And naturally, running the application on an x86 system working at 2Ghz will be different from running it on an ARM system working at 700Mhz. The whole point of calling the code "architecture independent" is that it will work across all systems.
Quoted 5 lines
So, if sandbox's fs/ext4 drivers' test passed on an x86
platform,but these architecture related optimizations would causesome potential bugs on ARM platform.
If you really do find an odd bug where it does not work as expected (it can happen), then that's an exceptional case which should be investigated further. I'm not sure if investigating it in sandbox mode will help.
-Abraham V.
[U-Boot] sandbox question
Hi, Albrahm:
Thanks a lot!
Best wishes,