December 2010 - U-Boot

[U-Boot] [u-boot-atmel] Undefined Symbols with AT91RM9200DK_CONFIG
by James Kosin 09 Dec '10

09 Dec '10

With the latest from the u-boot-atmel area, the symbols below don't seem to be defined. Thanks, James --- error arm-eabi-gcc -g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DCONF IG_SYS_TEXT_BASE=0x21f00000 -I/home/jkosin/git/u-boot-atmel/include -fno-builtin -ffreestanding -nostdinc -isystem /home/jkosin/opt/armThumb-4.5.0/lib/gcc/arm-e abi/4.5.1/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux -mno-th umb-interwork -march=armv4 -Wall -Wstrict-prototypes -fno-stack-protector \ -o board.o board.c -c board.c: In function `__dram_init_banksize': board.c:233:29: error: `CONFIG_SYS_SDRAM_BASE' undeclared (first use in this fun ction) board.c:233:29: note: each undeclared identifier is reported only once for each function it appears in board.c: In function `board_init_f': board.c:279:17: error: `CONFIG_SYS_INIT_SP_ADDR' undeclared (first use in this f unction) board.c:312:9: error: `CONFIG_SYS_SDRAM_BASE' undeclared (first use in this func tion) make[1]: *** [board.o] Error 1 make[1]: Leaving directory `/home/jkosin/git/u-boot-atmel/arch/arm/lib' make: *** [arch/arm/lib/libarm.o] Error 2 --- end -- James Kosin Senior Software Engineer International Communications Group, Inc. 230 Pickett's Line Newport News, Virginia 23603 Phone: +1 (757) 947-1030 x 122 Fax: +1 (757) 947-1035

2 2

Re: [U-Boot] [STATUS] v2010.12-rc2 released
by Carlo Caione 09 Dec '10

09 Dec '10

> Some of the times, the boot hung after printing DRAM: 128 MiB, > but never did it hang without printing anything. The same here. Beagleboard xM rev.A hangs after DRAM: 256 MiB Regards, -- Carlo Caione

4 7

[U-Boot] [PATCH] fsl_upm: Add MxMR/MDR synchronization
by Peter Tyser 09 Dec '10

09 Dec '10

From: John Schmoller <jschmoller(a)xes-inc.com> According to Freescale reference manuals (eg section "13.4.4.2 Programming the UPMs" of the P4080 Reference Manual): "Since the result of any update to the MxMR/MDR register must be in effect before the dummy read or write to the UPM region, a write to MxMR/MDR should be followed immediately by a read of MxMR/MDR." The UPM on a custom P4080-based board did not work without performing a read of MxMR/MDR after a write. Signed-off-by: John Schmoller <jschmoller(a)xes-inc.com> Signed-off-by: Peter Tyser <ptyser(a)xes-inc.com> --- drivers/mtd/nand/fsl_upm.c | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/mtd/nand/fsl_upm.c b/drivers/mtd/nand/fsl_upm.c index b76c673..be00555 100644 --- a/drivers/mtd/nand/fsl_upm.c +++ b/drivers/mtd/nand/fsl_upm.c @@ -21,6 +21,7 @@ static void fsl_upm_start_pattern(struct fsl_upm *upm, u32 pat_offset) { clrsetbits_be32(upm->mxmr, MxMR_MAD_MSK, MxMR_OP_RUNP | pat_offset); + (void)in_be32(upm->mxmr); } static void fsl_upm_end_pattern(struct fsl_upm *upm) @@ -35,6 +36,7 @@ static void fsl_upm_run_pattern(struct fsl_upm *upm, int width, void __iomem *io_addr, u32 mar) { out_be32(upm->mar, mar); + (void)in_be32(upm->mar); switch (width) { case 8: out_8(io_addr, 0x0); -- 1.7.0.4

3 3

[U-Boot] [STATUS] next rebased / ARM help needed / release delayed
by Wolfgang Denk 09 Dec '10

09 Dec '10

Hello, here is some news. Not exactly good news it seems: 1) I had to rebase the "next" branch to remove a commit which incorrectly changed behaviour of some commands. 2) By some stupid accident I lost track of some / most / all ARM related patches that are supposed to go into the current release and/or next; unfortunately I also maked these as "applied' in patchwork. If you have any outstanding ARM patches that should go in, please drop me a note (ideally including the respective link into patchwork). Thanks, and sorry again. 3) We will have a delay in the release. I will try to get a -rc3 out by the weekend; new target for 2010.12 is December 20 (but don't hold your breath). Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de "If that makes any sense to you, you have a big problem." -- C. Durance, Computer Science 234

2 4

[U-Boot] [PATCH 0/4] ARM relocation fixes
by Andreas Bießmann 09 Dec '10

09 Dec '10

As discussed in http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/89864/focus=89905 here are the changes for r8 usage in all arm relocate_code() implementations. Additionally there is a change to armv7 code which is persumably broken (at least when CONFIG_PRELADER is _not_ defined). Please comment on that patch, the rest should go in v2010.12. Andreas Bießmann (4): arm: copy_loop(): use scratch register arm: relocate_code(): do not set register useless arm: fixloop(): do not use r8 for relocation armv7: fix relocation skip arch/arm/cpu/arm1136/start.S | 20 ++++++++++---------- arch/arm/cpu/arm1176/start.S | 20 ++++++++++---------- arch/arm/cpu/arm720t/start.S | 20 ++++++++++---------- arch/arm/cpu/arm920t/start.S | 20 ++++++++++---------- arch/arm/cpu/arm925t/start.S | 20 ++++++++++---------- arch/arm/cpu/arm926ejs/start.S | 20 ++++++++++---------- arch/arm/cpu/arm946es/start.S | 20 ++++++++++---------- arch/arm/cpu/arm_intcm/start.S | 20 ++++++++++---------- arch/arm/cpu/armv7/start.S | 24 ++++++++++++------------ arch/arm/cpu/ixp/start.S | 20 ++++++++++---------- arch/arm/cpu/lh7a40x/start.S | 20 ++++++++++---------- arch/arm/cpu/pxa/start.S | 20 ++++++++++---------- arch/arm/cpu/s3c44b0/start.S | 20 ++++++++++---------- arch/arm/cpu/sa1100/start.S | 20 ++++++++++---------- 14 files changed, 142 insertions(+), 142 deletions(-) -- 1.7.3.2

3 14

[U-Boot] Full Arm emulator to run under x86
by Toan Pham 09 Dec '10

09 Dec '10

Hi I am new to uboot and I would like to learn it under an emulator instead of a remote target. For instance, I'd like to experiment it with the Android operating system. So far, I have tried qemu (utility qemu-system-arm) to boot the kernel or an arm+uboot bootable sd flash image on x86 architecture and the result was unsuccessful. My purpose is not to run for example Android on an x86 architecture, because i know that there's Android for i386. However, more of a full Arm system emulator that should be able to boot U-boot bootloader and then the Linux kernel, and also a bootable block device or image. thank you, -toan

1 0

[U-Boot] can't build u-boot-2010.12-rc2 for at91rm9200ek
by zzs213 09 Dec '10

09 Dec '10

I download u-boot-2010.12-rc2 and make at91rm9200ek use the flowwing command make O=../build at91rm9200ek and get error message like this arm-linux-gcc -D__ASSEMBLY__ -g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__ -DCONFIG_SYS_TEXT_BASE=0x10000000 -I/home/zzs/DownLoad/uboot/xx/build/include2 -I/home/zzs/DownLoad/uboot/xx/build/include -I/home/zzs/DownLoad/uboot/xx/u-boot-2010.12-rc2/include -fno-builtin -ffreestanding -nostdinc -isystem /home/zzs/work/tools/eldk4.1/usr/bin/../lib/gcc/arm-linux/4.0.0/include -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=apcs-gnu -mno-thumb-interwork -march=armv4 \ -o /home/zzs/DownLoad/uboot/xx/build/arch/arm/cpu/arm920t/start.o start.S -c start.S: Assembler messages: start.S:251: Error: bad arguments to instruction -- `add r1,r9' It looks a illegal instruction in start.S my toolchain is eldk4.1 anybody help me!!

5 12

[U-Boot] [PATCH 1/2] AT91: fix TOP9000 built issues
by Reinhard Meyer 09 Dec '10

09 Dec '10

Since I originally made and checked the TOP9000 support patch some changes to mainline broke the built. This small patch fixes this. Signed-off-by: Reinhard Meyer <u-boot(a)emk-elektronik.de> --- board/emk/top9000/Makefile | 6 +++--- board/emk/top9000/top9000.c | 2 +- include/configs/top9000.h | 8 ++++++-- 3 files changed, 10 insertions(+), 6 deletions(-) diff --git a/board/emk/top9000/Makefile b/board/emk/top9000/Makefile index 9b28048..3ac6f14 100644 --- a/board/emk/top9000/Makefile +++ b/board/emk/top9000/Makefile @@ -26,9 +26,9 @@ include $(TOPDIR)/config.mk -LIB = $(obj)lib$(BOARD).a +LIB = $(obj)lib$(BOARD).o -COBJS-y += top9000.o +COBJS-y += $(BOARD).o COBJS-$(CONFIG_ATMEL_SPI) += spi.o SRCS := $(SOBJS:.o=.S) $(COBJS-y:.o=.c) @@ -36,7 +36,7 @@ OBJS := $(addprefix $(obj),$(COBJS-y)) SOBJS := $(addprefix $(obj),$(SOBJS)) $(LIB): $(obj).depend $(OBJS) $(SOBJS) - $(AR) $(ARFLAGS) $@ $(OBJS) $(SOBJS) + $(call cmd_link_o_target, $(OBJS) $(SOBJS)) clean: rm -f $(SOBJS) $(OBJS) diff --git a/board/emk/top9000/top9000.c b/board/emk/top9000/top9000.c index b0fe2d6..73dd706 100644 --- a/board/emk/top9000/top9000.c +++ b/board/emk/top9000/top9000.c @@ -120,7 +120,7 @@ int board_mmc_getcd(u8 *cd, struct mmc *mmc) int board_early_init_f(void) { - at91_shdwn_t *shdwn = (at91_shdwn_t *)AT91_SHDWN_BASE; + struct at91_shdwn *shdwn = (struct at91_shdwn *)AT91_SHDWN_BASE; /* * make sure the board can be powered on by diff --git a/include/configs/top9000.h b/include/configs/top9000.h index ff3933b..814fb6c 100644 --- a/include/configs/top9000.h +++ b/include/configs/top9000.h @@ -40,9 +40,13 @@ /* * Warning: changing CONFIG_SYS_TEXT_BASE requires - * adapting the initial boot program + * adapting the initial boot program. + * Guard it since the definition finds its way to the command-line and + * causes warnings when this file is included */ -#define CONFIG_SYS_TEXT_BASE 0x21f00000 /* 31 MB into RAM */ +#ifndef CONFIG_SYS_TEXT_BASE +# define CONFIG_SYS_TEXT_BASE 0x21f00000 /* 31 MB into RAM */ +#endif /* Command line configuration */ #include <config_cmd_default.h> -- 1.7.3.3.398.g0b0cd

1 1

[U-Boot] hwmon init
by Heiko Schocher 09 Dec '10

09 Dec '10

Hello, Is there a reason why the dtt sensors are initialized and accessed on u-boot startup? The U-Boot Design Principles[1] clearly say: Initialize devices only when they are needed within U-Boot, i.e. don't initialize the Ethernet interface(s) unless U-Boot performs a download over Ethernet; don't initialize any IDE or USB devices unless U-Boot actually tries to load files from these, etc. (and don't forget to shut down these devices after using them - otherwise nasty things may happen when you try to boot your OS). Should that be changed? bye, Heiko [1] http://www.denx.de/wiki/U-Boot/DesignPrinciples -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

3 3

[U-Boot] [PATCH 0/4] get at91rm9200ek working with ARM relocation
by Andreas Bießmann 09 Dec '10

09 Dec '10

This patch series enables at91rm9200ek board to work with new ARM relocation. Unfortunately the board does _not_ fully work, there is one issue left I can't figure out currently. When booting from pre-initialised clock and RAM (e.g. by JTAG dongle or preloader) the relocation works. But when booting from NOR flash the board hangs just after 'relocation Offset is: 11f7f000'. I think it is the same issue with using bss before relocation but couldn't find the loacation til now. I don't know if I get it done til release of v2010.12 but like to have the current changes in. The series includes two patches already in Reinhard's u-boot-atmel/at91-next branch but the base of at91-next is outdated and they will not apply cleanly. So feel free to include them or not. Reinhard, any comments? The mentioned patches are: at91rm9200ek: add configure target for RAM boot MAKEALL: fix AT91 Beside that the 'add configure target for RAM boot' is needed for working configuration as ram-boot since nor-boot is currently broken ;) Andreas Bießmann (4): at91rm9200ek: add configure target for RAM boot MAKEALL: fix AT91 arm920t: fix linker skript for -pie linking arm920t/at91/timer: replace bss variables by gd MAKEALL | 18 +++--------------- arch/arm/cpu/arm920t/at91/timer.c | 29 ++++++++++++++--------------- arch/arm/cpu/arm920t/u-boot.lds | 3 +++ board/atmel/at91rm9200ek/config.mk | 2 -- boards.cfg | 3 ++- include/configs/at91rm9200ek.h | 16 ++++++++++++++++ 6 files changed, 38 insertions(+), 33 deletions(-) delete mode 100644 board/atmel/at91rm9200ek/config.mk -- 1.7.3.2

5 19