September 2007 - U-Boot

[U-Boot-Users] U-boot not compiling--may be bug..
by Bhagwat 04 Sep '07

04 Sep '07

HI all I have taken u-boot code from u-boot-1.1.6 ( http://www.denx.de/wiki/UBoot ) I tried to compile for omap1510inn(which is having arm926ejs core), I want to compile it for arm926ejs. I have done, $make omap1510inn_config $make It is throwing me errors, board.c: In function `start_armboot': board.c:331: error: incompatible types in assignment board.c:373: warning: passing arg 1 of `smc_set_mac_addr' from incompatible pointer type make[1]: *** [board.o] Error 1 make[1]: Leaving directory `/home/bhagwat/u-boot/u-boot-1.1.6/lib_arm' seems some bug.. please help me; I am not able to proceed. Regards, __Bhagwat

2 1

[U-Boot-Users] [PATCH/RFC] mpc5200: switch to CONFIG_OF_LIBFDT
by Grant Likely 04 Sep '07

04 Sep '07

From: Grant Likely <grant.likely(a)secretlab.ca> Here is a patch which converts the icecube* and tqm5200 boards from using OF_FLAT_TREE to OF_LIBFDT. It also fixes the compile of cm5200. It's been tested on the lite5200. Still to be resolved: is there a better place to put the helper functions. Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> --- board/icecube/icecube.c | 10 ++++--- board/tqm5200/tqm5200.c | 12 +++++--- cpu/mpc5xxx/cpu.c | 67 ++++++++++++++++++++++++++++----------------- include/configs/IceCube.h | 2 + include/configs/TQM5200.h | 2 + 5 files changed, 57 insertions(+), 36 deletions(-) diff --git a/board/icecube/icecube.c b/board/icecube/icecube.c index c027f6f..6a2a77a 100644 --- a/board/icecube/icecube.c +++ b/board/icecube/icecube.c @@ -29,9 +29,11 @@ #include <pci.h> #include <asm/processor.h> -#if defined(CONFIG_OF_FLAT_TREE) -#include <ft_build.h> -#endif +#ifdef CONFIG_OF_LIBFDT +#include <libfdt.h> +#include <libfdt_env.h> +#include <fdt_support.h> +#endif /* CONFIG_OF_LIBFDT */ #if defined(CONFIG_LITE5200B) #include "mt46v32m16.h" @@ -386,7 +388,7 @@ void ide_set_reset (int idereset) } #endif -#if defined(CONFIG_OF_FLAT_TREE) && defined(CONFIG_OF_BOARD_SETUP) +#if defined(CONFIG_OF_LIBFDT) && defined(CONFIG_OF_BOARD_SETUP) void ft_board_setup(void *blob, bd_t *bd) { diff --git a/board/tqm5200/tqm5200.c b/board/tqm5200/tqm5200.c index 51f4aeb..09f1709 100644 --- a/board/tqm5200/tqm5200.c +++ b/board/tqm5200/tqm5200.c @@ -32,9 +32,11 @@ #include <pci.h> #include <asm/processor.h> -#if defined(CONFIG_OF_FLAT_TREE) -#include <ft_build.h> -#endif +#ifdef CONFIG_OF_LIBFDT +#include <libfdt.h> +#include <libfdt_env.h> +#include <fdt_support.h> +#endif /* CONFIG_OF_LIBFDT */ #ifdef CONFIG_VIDEO_SM501 #include <sm501.h> @@ -780,9 +782,9 @@ int board_get_height (void) #endif /* CONFIG_VIDEO_SM501 */ -#if defined(CONFIG_OF_FLAT_TREE) && defined(CONFIG_OF_BOARD_SETUP) +#if defined(CONFIG_OF_LIBFDT) && defined(CONFIG_OF_BOARD_SETUP) void ft_board_setup(void *blob, bd_t *bd) { ft_cpu_setup(blob, bd); } -#endif /* defined(CONFIG_OF_FLAT_TREE) && defined(CONFIG_OF_BOARD_SETUP) */ +#endif /* defined(CONFIG_OF_LIBFDT) && defined(CONFIG_OF_BOARD_SETUP) */ diff --git a/cpu/mpc5xxx/cpu.c b/cpu/mpc5xxx/cpu.c index 1eac2bb..bb3ad49 100644 --- a/cpu/mpc5xxx/cpu.c +++ b/cpu/mpc5xxx/cpu.c @@ -31,8 +31,9 @@ #include <mpc5xxx.h> #include <asm/processor.h> -#if defined(CONFIG_OF_FLAT_TREE) -#include <ft_build.h> +#if defined(CONFIG_OF_LIBFDT) +#include <libfdt.h> +#include <libfdt_env.h> #endif DECLARE_GLOBAL_DATA_PTR; @@ -111,29 +112,45 @@ unsigned long get_tbclk (void) /* ------------------------------------------------------------------------- */ -#ifdef CONFIG_OF_FLAT_TREE -void -ft_cpu_setup(void *blob, bd_t *bd) +#ifdef CONFIG_OF_LIBFDT +static void fixup_prop(void *fdt, char *node, char *prop, void *val, int size, + int create) { - u32 *p; - int len; - - /* Core XLB bus frequency */ - p = ft_get_prop(blob, "/cpus/" OF_CPU "/bus-frequency", &len); - if (p != NULL) - *p = cpu_to_be32(bd->bi_busfreq); - - /* SOC peripherals use the IPB bus frequency */ - p = ft_get_prop(blob, "/" OF_SOC "/bus-frequency", &len); - if (p != NULL) - *p = cpu_to_be32(bd->bi_ipbfreq); - - p = ft_get_prop(blob, "/" OF_SOC "/ethernet@3000/mac-address", &len); - if (p != NULL) - memcpy(p, bd->bi_enetaddr, 6); - - p = ft_get_prop(blob, "/" OF_SOC "/ethernet@3000/local-mac-address", &len); - if (p != NULL) - memcpy(p, bd->bi_enetaddr, 6); + int nodeoff; + int rc; + + nodeoff = fdt_find_node_by_path(fdt, node); + if (nodeoff < 0) { + printf("Couldn't find %s:%s\n", node, fdt_strerror(nodeoff)); + return; + } + + if ((!create) && (fdt_get_property(fdt, nodeoff, prop, 0) == NULL)) + return; + + rc = fdt_setprop(fdt, nodeoff, prop, val, size); + if (rc) + printf("Problem setting %s = %s: %s\n", + node, prop, fdt_strerror(rc)); +} + +static void fixup_int_prop(void *fdt, char *node, char *prop, u32 val, + int create) +{ + val = cpu_to_be32(val); + fixup_prop(fdt, node, prop, &val, sizeof(val), create); +} + +void ft_cpu_setup(void *blob, bd_t *bd) +{ + char * cpu_path = "/cpus/" OF_CPU; + char * eth_path = "/" OF_SOC "/ethernet@3000"; + + fixup_int_prop(blob, cpu_path, "timebase-frequency", OF_TBCLK, 1); + fixup_int_prop(blob, cpu_path, "bus-frequency", bd->bi_busfreq, 1); + fixup_int_prop(blob, cpu_path, "clock-frequency", bd->bi_intfreq, 1); + fixup_int_prop(blob, "/" OF_SOC, "bus-frequency", bd->bi_ipbfreq, 1); + fixup_prop(blob, eth_path, "mac-address", bd->bi_enetaddr, 6, 0); + fixup_prop(blob, eth_path, "local-mac-address", bd->bi_enetaddr, 6, 0); } #endif diff --git a/include/configs/IceCube.h b/include/configs/IceCube.h index bdd92ba..4c16d22 100644 --- a/include/configs/IceCube.h +++ b/include/configs/IceCube.h @@ -178,7 +178,7 @@ #endif /* CONFIG_MPC5200 */ /* pass open firmware flat tree */ -#define CONFIG_OF_FLAT_TREE 1 +#define CONFIG_OF_LIBFDT 1 #define CONFIG_OF_BOARD_SETUP 1 #define OF_CPU "PowerPC,5200@0" diff --git a/include/configs/TQM5200.h b/include/configs/TQM5200.h index c08173b..e0c9d81 100644 --- a/include/configs/TQM5200.h +++ b/include/configs/TQM5200.h @@ -701,7 +701,7 @@ * Open firmware flat tree support *----------------------------------------------------------------------- */ -#define CONFIG_OF_FLAT_TREE 1 +#define CONFIG_OF_LIBFDT 1 #define CONFIG_OF_BOARD_SETUP 1 #define OF_CPU "PowerPC,5200@0"

6 18

[U-Boot-Users] ARM cleanup - was: [GIT PULL] [ARM] Please pull fromgit://denx.de/git/u-boot-arm.git
by Peter Pearse 04 Sep '07

04 Sep '07

Wolfgang I've got a bit lost here - can you explain a bit more. please excuse me if the following seems a bit basic - I just want to understand what I need to clean up. You said: --- snip --- > > I'm afraid I don't understand. We are not talking about any startup > > code, but about the code of the "reset" function, i. e. what > > casues the board to reset. --- snip --- I can't find a reference to the reset function. There is do_reset() and set_cpu(), which the arm code supplies. The only use of reset I can see is as a label in the ARM start.S. The standard arm entry point to the U-Boot image is something like:- .globl _start _start: b reset ldr pc, _undefined_instruction ldr pc, _software_interrupt ldr pc, _prefetch_abort ldr pc, _data_abort ldr pc, _not_used ldr pc, _irq ldr pc, _fiq which is a (never currently used) imitation of the ARM architecture vector table. So when U-Boot runs it jumps to code of the form reset: Code to set the cpu to SVC32 mode #ifndef CONFIG_SKIP_LOWLEVEL_INIT Code to e.g. remap RAM #endif #ifndef CONFIG_SKIP_RELOCATE_UBOOT Copy U-Boot code to RAM #endif /* CONFIG_SKIP_RELOCATE_UBOOT */ Code to set up the stack clear BSS Jump to board.c::start_armboot() --- snip --- >> The writers (and cut & pasters) of ARM code seem to have assumed that >> reset: >> is the entry to the code which runs immediately after the processor is >> reset, rather than the code which makes the processor reset. > Well, if that was the assumption, that all this code has obviously never been tested on any real hardware. >> Could we accept Ulf's code whilst I give this more consideration? > It's so utterly wrong that I think we have to clean this up before the next release. > If nobody submits a better patch, we will have to remove the bogus code. --- snip --- Is there anything that needs changing about the process I have described above? I could add ifdeffed code to really install the vector table at the ARM reset point(s), but it seems to me that the code will work OK as it is. I do need to work with Ulf to put his code down into cpu_init_crit. Both he & I missed the fact that CONFIG_BOOTBINFUNC got split & changed into the two CONFIG_SKIP defines. Regards Peter

3 9

[U-Boot-Users] openmoko patch of uboot for s3c2443
by paopaoer maillist 04 Sep '07

04 Sep '07

i down the patch http://svn.openmoko.org/trunk/src/target/u-boot/patches/uboot-s3c2443.patch patch to the u-boot-1.2.0 but compile error does anybody has the patch port uboot to s3c2443 best wishes paopaoer

1 0

Re: [U-Boot-Users] newbies to u-boot
by Bhagwat 04 Sep '07

04 Sep '07

HI all, I got the U-boot code and I am trying to compile it for my SOC. I am using ARM926EJS core. I have done follwing steps 1. In makefile I have added below lines moschip_config : unconfig @./mkconfig $(@:_config=) arm arm926ejs moschip 2. I have copied header file in include dir $ cp include/configs/armadillo.h include/configs/moschip.h 3. Then I have copied dir $cp board/armadillo/ board/moschip/ after doing $make moschip_config $make I am getting follwoing errs.. armadillo.c: In function `dram_init': armadillo.c:58: error: `PHYS_SDRAM_1' undeclared (first use in this function) armadillo.c:58: error: (Each undeclared identifier is reported only once armadillo.c:58: error: for each function it appears in.) armadillo.c:59: error: `PHYS_SDRAM_1_SIZE' undeclared (first use in this function) make[1]: *** [armadillo.o] Error 1 Can anyone tell me, If i am missing any steps for compilation. Regards, __Bhagwat

3 4

[U-Boot-Users] please issue u-boot1.2.0 with ppc405EZ cpu
by longyitan 03 Sep '07

03 Sep '07

i want to use u-boot1.2.0 on ppc405ez's board ,

2 1

Re: [U-Boot-Users] ACCESS TIME
by Sondra Jean 03 Sep '07

03 Sep '07

Have you ever hoped to have a high dollar Watch? We have the problem solved for you! We carry all the expensive brands for a low fraction of the expense. www.oellwkjj.com

1 0

[U-Boot-Users] Can't access FPGA in my BDI2000 telnet console.
by jxnuxdy 03 Sep '07

03 Sep '07

Hi, I add the CS1 initialzation for my FPGA in the config file "evkit440epx.cfg", but I can't access the FPGA space, I measured the CS1 for the FPGA is always HIGH, so seems I didn't init the CS1 successfully in the config file "evkit440epx.cfg". Is this issue due to my config file "evkit440epx.cfg" or the BDI2000 itself ? (attachment is my config file) ,Thanks.- Denny

1 0

[U-Boot-Users] Maximum male enhancement
by Grant Evans 03 Sep '07

03 Sep '07

We've been supplying hundreds of thousands of men with generic brand-name goods for more than 4 years already - and have never received a single complaint! That should definitely mean something: http://awrowxg.wholestrange.cn/?537903072178

1 0

[U-Boot-Users] TI DaVinci Initial Bootloader, tar.gz
by ksi＠koi8.net 03 Sep '07

03 Sep '07

Here it is... I'm not sure it belongs here but I think it would be right thing to include initial bootloaders for platforms that require them into U-Boot tree. It might be subtrees under board directories, a separate boot/ or something off the main tree or anything else. The reason is simple -- U-Boot is supposed to be the first program that runs on a system, kinda like pee-see BIOS or something, but some platforms require even lower level program, bootloader, to either load U-Boot upon startup or to write it in system ROM. If we had those in the U-Boot tree we would've had everything required to bringup a virgin board in one place. I personally don't see any other place for those small programs to go. We do have U-Boot for a lot of absolutely different platforms in the same tree so one doesn't have to search for a particular port at obscure places and I feel that adding initial bootloaders would make it even better. What do you think guys? As for the actual DaVinci bootloader, it is in attached tar.gz. It is not polished, ugly at places but it works and it doesn't require any Windoze, sorry for an expression, "servers" or proprietary tools. It works with both small and large page NAND. There is a rather brief readme inside the archive that explains what it is, how to run it and documents formats. Any comments are welcome. --- ****************************************************************** * KSI@home KOI8 Net < > The impossible we do immediately. * * Las Vegas NV, USA < > Miracles require 24-hour notice. * ******************************************************************

1 0