April 2013 - U-Boot

[U-Boot] Interrupt handling ARM cortex A9 ( Armv7) in u-boot
by s_arm_uboot 05 Apr '13

05 Apr '13

Hi all. I am working on registering a gpio interrupt in the u-boot. I am using the a Armv7 ( Arm cortex A9) platform. My question is about registering a IRQ handler for the interrupt. I tried writing the function pointer of my IRQ directly to Interrupt vector table ( which is at 0xFFFF0000 in my case and my interrupt id is 56 and i calculated the address accordingly). What does thie CONFIG_USE_IRQ do and what is the purpose of the do_irq function and in short how can i register a IRQ for this particular HW interrupt. I am used to the higher level api's in the linux kernel and the lack of those api's in u-boot is giving a hard time for me ;). So kindly help me with this question Cheers, S -- View this message in context: http://u-boot.10912.n7.nabble.com/Interrupt-handling-ARM-cortex-A9-Armv7-in… Sent from the U-Boot mailing list archive at Nabble.com.

1 0

[U-Boot] [PATCH v2 0/3] Make tzpc initialization common for exynos4 and exynos5
by Inderpal Singh 05 Apr '13

05 Apr '13

The first patch moves the tzpc_init file from smdk5250 to armv7/exynos. The second makes tzpc_init common for exynos4 and exynos5. And the third makes necessary changes to exynos4 based origen and smdkv310 boards. The patchset has been tested on exynos4 based origen and exynos5 based Arndale board. Changes in v2: - removed uninitialised warning for start and end variables - corrected the SPL_TEXT_BASE for origen and smdkv310 - Added Chander's Acked-by Inderpal Singh (3): exynos: move tzpc_init to armv7/exynos exynos: update tzpc_init to make it common for exynos4 and exynos5 exynos: Update origen and smdkv310 to use common tzpc_init arch/arm/cpu/armv7/exynos/Makefile | 2 +- arch/arm/cpu/armv7/exynos/tzpc_init.c | 57 +++++++++++++++++++++++++++++ arch/arm/cpu/armv7/s5p-common/Makefile | 2 ++ arch/arm/include/asm/arch-exynos/tzpc.h | 28 +++++++++++++++ board/samsung/origen/lowlevel_init.S | 44 ++--------------------- board/samsung/origen/origen_setup.h | 25 ------------- board/samsung/smdk5250/Makefile | 1 - board/samsung/smdk5250/lowlevel_init.S | 2 ++ board/samsung/smdk5250/setup.h | 25 ------------- board/samsung/smdk5250/tzpc_init.c | 48 ------------------------- board/samsung/smdkv310/lowlevel_init.S | 60 ++----------------------------- include/configs/exynos5250-dt.h | 2 -- include/configs/origen.h | 2 ++ include/configs/smdkv310.h | 2 ++ spl/Makefile | 4 +++ 15 files changed, 102 insertions(+), 202 deletions(-) create mode 100644 arch/arm/cpu/armv7/exynos/tzpc_init.c delete mode 100644 board/samsung/smdk5250/tzpc_init.c -- 1.7.9.5

2 7

[U-Boot] Require guidance
by Rajdeep Vaghasia 05 Apr '13

05 Apr '13

hello, I have read about U - boot from Emebedded Linux Primer 2nd Edition. I want more in depth knowledge of U - boot. Can you please suggest me or give me the references through which I get more in depth knowledge about U - boot? Regards Rajdeep Vaghasia

3 2

[U-Boot] CAN support in u-boot
by Puneet Sharma 05 Apr '13

05 Apr '13

Hello, I have got a CAN controller (*Atmel SAM9263 Board*) which i want to test in u-boot to make sure it covers all the basic test required for its functionalities( like sending CAN frame, receving CAN frame etc). For the time being i cannot test it in kernel as it increases to much abstraction which is not desirable for me. Can you guide me to write some basic test cases in u-boot which can test the Controller on a basic level or give me some links which are doing similar things which i intened. regards -Puneet The information contained in this email and any attachments is confidential and may be subject to copyright or other intellectual property protection. If you are not the intended recipient, you are not authorized to use or disclose this information, and we request that you notify us by reply mail or telephone and delete the original message from your mail system.

1 0

[U-Boot] [Patch alt] common/cmd_test: Avoid macro expansion
by York Sun 05 Apr '13

05 Apr '13

cmd_test.c adds "true" and "false" as new commands. We need to avoid macro expansion for U_BOOT_CMD. Signed-off-by: York Sun <yorksun(a)freescale.com> --- This is alternative patch to fix macro expansion issue for cmd_test.c common/cmd_test.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/common/cmd_test.c b/common/cmd_test.c index d4ec186..26a84af 100644 --- a/common/cmd_test.c +++ b/common/cmd_test.c @@ -144,6 +144,14 @@ static int do_test(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) return expr; } +#ifdef true +#undef true +#endif + +#ifdef false +#undef false +#endif + U_BOOT_CMD( test, CONFIG_SYS_MAXARGS, 1, do_test, "minimal test like /bin/sh", -- 1.7.9.5

2 1

[U-Boot] [PATCH] CRITICAL error in v2013.04-rc2 (true and false not working)
by Pali Rohár 04 Apr '13

04 Apr '13

Hello, with this version of gcc which is default in ubuntu 12.10: $ arm-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=arm-linux-gnueabi-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabi/4.7/lto-wrapper Target: arm-linux-gnueabi Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.7.2-1ubuntu1' --with- bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program- suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --with-gxx-include-dir=/usr/arm-linux-gnueabi/include/c++/4.7.2 --libdir=/usr/lib --enable-nls --enable- clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --enable-plugin --enable-objc-gc --enable-multilib --disable-sjlj-exceptions --with-arch=armv5t --with-float=soft --disable-werror --enable- checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=arm-linux-gnueabi --program-prefix=arm-linux- gnueabi- --includedir=/usr/arm-linux-gnueabi/include --with-headers=/usr/arm-linux-gnueabi/include --with-libs=/usr/arm-linux- gnueabi/lib Thread model: posix gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-1ubuntu1) u-boot "true" and "false" hush commands are copiled incorrectly in uboot v2013.04-rc2 (c8142633e169665b246352918df5b76fd243bb71) when I run help in u-boot it show: # help 0 - do nothing, unsuccessfully 1 - do nothing, successfully ? - alias for 'help' base - print or set address offset ... Instead "0" and "1" there should be "false" and "true" command. This happen when stdbool.h from C99 compiler is included in cmd_test.c and then true and false macros are expanded to 1 and 0. Quick fix for this is adding #undef before U_BOOT_CMD: diff --git a/common/cmd_test.c b/common/cmd_test.c index d4ec186..a7ec8ac 100644 --- a/common/cmd_test.c +++ b/common/cmd_test.c @@ -155,6 +155,7 @@ static int do_false(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) return 1; } +#undef false U_BOOT_CMD( false, CONFIG_SYS_MAXARGS, 1, do_false, "do nothing, unsuccessfully", @@ -166,6 +167,7 @@ static int do_true(cmd_tbl_t *cmdtp, int flag, int argc, char * const argv[]) return 0; } +#undef true U_BOOT_CMD( true, CONFIG_SYS_MAXARGS, 1, do_true, "do nothing, successfully", Without above patch and with gcc 4.7.2 it is not possible to use u-boot on Nokia RX-51, becuase it has true and false commands in preboot env. Please fix this problem in u-boot v2013.04. -- Pali Rohár pali.rohar(a)gmail.com

4 12

[U-Boot] [PATCH] common/cmd_test: Avoid macro expansion
by York Sun 04 Apr '13

04 Apr '13

cmd_test.c adds "true" and "false" as new commands. We need to avoid macro expansion for U_BOOT_CMD. Signed-off-by: York Sun <yorksun(a)freescale.com> --- common/cmd_test.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/common/cmd_test.c b/common/cmd_test.c index d4ec186..cb22f8b 100644 --- a/common/cmd_test.c +++ b/common/cmd_test.c @@ -21,6 +21,15 @@ * MA 02111-1307 USA */ +/* + * Define _STDBOOL_H here to avoid macro expansion of true and false. + * If the future code requres macro true or false, remove this define + * and undef true and false before U_BOOT_CMD. This define and comment + * shall be removed if changes to U_BOOT_CMD is made to take string + * instead of stringifying it. + */ +#define _STDBOOL_H + #include <common.h> #include <command.h> -- 1.7.9.5

1 0

[U-Boot] [PATCH 0/2] Add initial support for AQUILA-CYGNUS
by Enric Balletbo i Serra 04 Apr '13

04 Apr '13

From: Enric Balletbo i Serra <eballetbo(a)iseebcn.com> IGEP COM AQUILA and CYGNUS are two computer-on-module based on AM3354 and AM3352 processors. Both use SODIMM from factor and are designed for industrial range purpose. Enric Balletbo i Serra (2): Add DDR3 support for IGEP COM AQUILA/CYGNUS. ARM: Add support for IGEP COM AQUILA/CYGNUS MAINTAINERS | 1 + arch/arm/include/asm/arch-am33xx/ddr_defs.h | 17 ++ board/isee/igep0033/Makefile | 46 ++++ board/isee/igep0033/board.c | 232 +++++++++++++++++++++ board/isee/igep0033/board.h | 27 +++ board/isee/igep0033/mux.c | 89 ++++++++ boards.cfg | 1 + include/configs/igep0033.h | 300 +++++++++++++++++++++++++++ 8 files changed, 713 insertions(+) create mode 100644 board/isee/igep0033/Makefile create mode 100644 board/isee/igep0033/board.c create mode 100644 board/isee/igep0033/board.h create mode 100644 board/isee/igep0033/mux.c create mode 100644 include/configs/igep0033.h -- 1.7.10.4

3 7

[U-Boot] [PATCH] biosemu: include <asm/io.h> header
by Linus Walleij 04 Apr '13

04 Apr '13

This makes sure we have inline functions such as inb/outb that are used in these two files by including the arch-specific <asm/io.h> header. However the ARM version does not provide the accessors unless the config symbol __io is also defined so add that in front of the include. After this the bios emulator will compile on ARM systems. Signed-off-by: Linus Walleij <linus.walleij(a)linaro.org> --- drivers/bios_emulator/besys.c | 2 ++ drivers/bios_emulator/bios.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/drivers/bios_emulator/besys.c b/drivers/bios_emulator/besys.c index 84724b7..ad88a53 100644 --- a/drivers/bios_emulator/besys.c +++ b/drivers/bios_emulator/besys.c @@ -47,6 +47,8 @@ * ****************************************************************************/ +#define __io +#include <asm/io.h> #include <common.h> #include "biosemui.h" diff --git a/drivers/bios_emulator/bios.c b/drivers/bios_emulator/bios.c index 7cf4879..bcc192f 100644 --- a/drivers/bios_emulator/bios.c +++ b/drivers/bios_emulator/bios.c @@ -41,6 +41,8 @@ * ****************************************************************************/ +#define __io +#include <asm/io.h> #include <common.h> #include "biosemui.h" -- 1.8.1.4

3 9

Re: [U-Boot] [PATCH v3 3/7] Add fuse API and commands
by Benoît Thébaudeau 04 Apr '13

04 Apr '13

On Tuesday, March 26, 2013 10:28:39 PM, Benoît Thébaudeau wrote: > On Tuesday, March 26, 2013 10:24:52 PM, Benoît Thébaudeau wrote: > > This can be useful for fuse-like hardware, OTP SoC options, etc. > > > > Signed-off-by: Benoît Thébaudeau <benoit.thebaudeau(a)advansee.com> > > --- > > Changes in v3: > > - Rebase against latest u-boot-imx/master. > > - Update copyright years. > > - Rename the "ovride" command to "override" as it is nicer to read. > > - For obvious safety reasons, ask the user to confirm each fuse > > programming > > operation, unless the '-y' command line option was given, which can be > > used > > in scripts. > > - Rename "row" to "word" since it is less confusing and it is vocabulary > > common > > to iim and ocotp in the reference manuals. > > - Add doc/README.fuse. > > > > Changes in v2: > > - Rebase against latest master. > > > > README | 1 + > > common/Makefile | 1 + > > common/cmd_fuse.c | 214 > > ++++++++++++++++++++++++++++++++++++++++++++++ > > doc/README.fuse | 73 ++++++++++++++++ > > include/config_cmd_all.h | 1 + > > include/fuse.h | 49 +++++++++++ > > 6 files changed, 339 insertions(+) > > create mode 100644 common/cmd_fuse.c > > create mode 100644 doc/README.fuse > > create mode 100644 include/fuse.h > > FYI, I have started to work on the OCOTP stuff too with this API. I attach > the > corresponding README that I made. > > I will resume my work on this subject in about two weeks. This will be either > a > v4 or a new series, depending on what the v3 became in the meantime. Forget this v3. I will drop the bit interface in v4. It is redundant and not very useful, except to reduce the human error factor when playing with a single fuse, and people are supposed to know what they're doing, so... Best regards, Benoît

1 0