September 2007 - U-Boot

[U-Boot-Users] [PATCH] Fix do_bootm_linux() so that multi-file images with FDT blob boot.
by Bartlomiej Sieka 07 Sep '07

07 Sep '07

Fix the following issues in do_bootm_linux() that prevent booting the kernel from a mulit-file image (kernel + initrd + blob): - incorrect initrd address and length calculation - incorrect blob address calculation Also, make minor updates to the U-Boot's output and to the coding style. Signed-off-by: Bartlomiej Sieka <tur(a)semihalf.com> --- Tested on two MPC5200B-based boards, one using CONFIG_OF_FLAT_TREE (still), the other using CONFIG_OF_LIBFDT. On each board the mulit-file image was booted from an address in RAM, as well as in Flash. diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index bcb927f..4aca783 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -724,9 +724,8 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, if (tail) { data += 4 - tail; } - - len = ntohl(len_ptr[1]); - + len = ntohl (((image_header_t *)data)->ih_size); + data = data + sizeof(image_header_t); } else { /* * no initrd image @@ -817,27 +816,32 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, int i; /* skip kernel length, initrd length, and terminator */ - of_data = (ulong)(&len_ptr[3]); + of_flat_tree = (char *)(&len_ptr[3]); /* skip any additional image length fields */ for (i=2; len_ptr[i]; ++i) - of_data += 4; + of_flat_tree += 4; /* add kernel length, and align */ - of_data += ntohl(len_ptr[0]); + of_flat_tree += ntohl(len_ptr[0]); if (tail) { - of_data += 4 - tail; + of_flat_tree += 4 - tail; } /* add initrd length, and align */ tail = ntohl(len_ptr[1]) % 4; - of_data += ntohl(len_ptr[1]); + of_flat_tree += ntohl(len_ptr[1]); if (tail) { - of_data += 4 - tail; + of_flat_tree += 4 - tail; } + /* move the blob if it is in flash (set of_data to !null) */ + if (addr2info ((ulong)of_flat_tree) != NULL) + of_data = (ulong)of_flat_tree; + + #if defined(CONFIG_OF_FLAT_TREE) - if (*((ulong *)(of_flat_tree + sizeof(image_header_t))) != OF_DT_HEADER) { + if (*((ulong *)(of_flat_tree)) != OF_DT_HEADER) { #else - if (fdt_check_header(of_flat_tree + sizeof(image_header_t)) != 0) { + if (fdt_check_header (of_flat_tree) != 0) { #endif puts ("ERROR: image is not a fdt - " "must RESET the board to recover.\n"); @@ -845,9 +849,11 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, } #if defined(CONFIG_OF_FLAT_TREE) - if (((struct boot_param_header *)of_data)->totalsize != ntohl(len_ptr[2])) { + if (((struct boot_param_header *)of_flat_tree)->totalsize != + ntohl (len_ptr[2])) { #else - if (be32_to_cpu(fdt_totalsize(of_data)) != ntohl(len_ptr[2])) { + if (be32_to_cpu (fdt_totalsize (of_flat_tree)) != + ntohl(len_ptr[2])) { #endif puts ("ERROR: fdt size != image size - " "must RESET the board to recover.\n"); @@ -957,6 +963,7 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, "must RESET the board to recover.\n"); do_reset (cmdtp, flag, argc, argv); } + puts ("OK\n"); } /* * Add the chosen node if it doesn't exist, add the env and bd_t @@ -1011,6 +1018,7 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, printf (" Loading Device Tree to %08lx, end %08lx ... ", of_start, of_start + of_len - 1); memmove ((void *)of_start, (void *)of_data, of_len); + puts ("OK\n"); } /* * Create the /chosen node and modify the blob with board specific

3 6

[U-Boot-Users] Please pull u-boot-mpc5xxxx
by Grant Likely 07 Sep '07

07 Sep '07

The following changes since commit 60174746c668b309378a91488dded898e9553eae: Wolfgang Denk (1): Fix TFTP OACK code for short packets. are available in the git repository at: git://www.denx.de/git/u-boot-mpc5xxx master Grant Likely (3): libfdt: add convenience function fdt_find_and_setprop() Migrate 5xxx boards from CONFIG_OF_FLAT_TREE to CONFIG_OF_LIBFDT bootm/fdt: Only process the fdt if an fdt address was provided board/icecube/icecube.c | 7 +--- board/jupiter/jupiter.c | 8 +---- board/motionpro/motionpro.c | 8 ++--- board/tqm5200/tqm5200.c | 9 ++---- common/cmd_bootm.c | 36 ++++++++++++----------- cpu/mpc5xxx/cpu.c | 66 ++++++++++++++++++++++++++---------------- include/configs/IceCube.h | 2 +- include/configs/TQM5200.h | 2 +- include/configs/jupiter.h | 2 +- include/configs/motionpro.h | 2 +- include/libfdt.h | 2 + libfdt/fdt_rw.c | 26 +++++++++++++++++ 12 files changed, 102 insertions(+), 68 deletions(-) -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely(a)secretlab.ca (403) 399-0195

2 1

Re: [U-Boot-Users] MIPS port
by max y 06 Sep '07

06 Sep '07

In fact, that's what confused me. There about 9 families (74k , 24k etc) under 32 core. Each one has its own manual and programming guide. It would be nice there, there is one can summerize the difference in programming perpective. Which one is the volume you refer to? Max Andrew Dyer <amdyer(a)gmail.com> wrote: the 24K is a specific implementation of MIPS32 architecture. There are a few different main architectures (MIPS I, II, III, IV, MIPS32, and MIPS64), and some extensions (sort of like SSE in the x86 world). If you go on the MIPS website, you will find a 3 volume reference manual telling you all about MIPS32 from a programming perspective. You should get this. -- Hardware, n.: The parts of a computer system that can be kicked. --------------------------------- Yahoo! oneSearch: Finally, mobile search that gives answers, not web links.

1 0

[U-Boot-Users] fdt command: can't set a value-less property
by Bartlomiej Sieka 06 Sep '07

06 Sep '07

Hello, I'm playing with the fdt command in recent (60174746) U-Boot and I can't set a property that does not have a value. Documentation/powerpc/booting-without-of.txt" says "A property can have a value or not.", and fdt help suggests the same: fdt set <path> <prop> [<val>] - Set <property> [to <val>] However, I am getting: => fdt mknode / testnode => fdt list /testnode testnode { }; => fdt set /testnode testprop Usage: fdt - flattened device tree utility commands => fdt list /testnode testnode { }; Setting a property with value works: => fdt set /testnode testprop "testvalue" => fdt list /testnode testnode { testprop=""testvalue""; }; Am I doing something wrong, or is it a bug? Regards, Bartlomiej

2 3

[U-Boot-Users] port u-boot to my custom mpc7410+gt64260 board
by 张磊 06 Sep '07

06 Sep '07

Hi all. I want to port u-boot to my mpc7410 board.My board is very like Dy4-181 board,there are mpc7410 processor,Gt64260B bridge,512MB SDRAM,48MB flash and rtc uart so on. I have seen every board config file about gt64260+mpc74xx,but haven't found similar board like mine.Anyone can suggest one reference board suitable for me? My board memory map below: SCS0 00000000-1FFFFFFFF PCI_0 I/O E0000000-E0FFFFFF PCI_0 M0 E0000000-DFFFFFFF PCI_0 M1 40000000-41FFFFFF PCI_0 M2 90000000-91FFFFFF PCI_0 M3 RESERVE PCI_1 I/O E8000000-EFFFFFFF PCI_1 M0 B0000000-BFFFFFFF PCI_1 M1 C0000000-CFFFFFFF PCI_1 M2 RESERVE PCI_1 M3 RESERVE Gt registers F1000000-F100FFFF CS0 FD000000-FDFFFFFF flash CS1 FE000000-FEFFFFFF flash CS2 F4000000-F4000FFF uart rtc CS3 F5000000-F5007FFF nvram BOOTCS FF000000-FFFFFFFF flash And I don't understand some definition in /include/config/evb64260: #define CFG_DFL_GT_REGS 0x14000000 /* boot time GT_REGS */ #define CFG_MISC_REGION_BASE 0xf0000000 /* What to put in the bats. */ what's difference between CFG_DFL_GT_REGS and CFG_GT_REGS? what is CFG_MISC_REGION_BASE? I am new to u-boot.Hope for any advice.Thank you advance. ___________________________________________________________ 雅虎邮箱，以安全著称，是值得信赖的邮箱专家！ http://mail.yahoo.com.cn/

1 0

Re: [U-Boot-Users] MIPS port
by max y 06 Sep '07

06 Sep '07

I am confused by all these MIPS families. I went to MIPS web site. 24K is part of 32 core. What do you eman MIPS32 compilant exactly? Max Andrew Dyer <amdyer(a)gmail.com> wrote: > I am going to use u-boot for MIPS 24k. Any one know which current port I > can start with as reference. you'll probably be a bit on your own. I don't think any of the current mips ports are really close to a 24K. Watch the cache handling/locking code in particular, as it is not very generic. We use Au1550 which is MIPS32 compliant, so the db1550 port might be a place to start. One other common gotcha is u-boot requires the toolchain to use the denx naming conventions - somewhere in the scripts and makefiles (I forget the file) they use the name of the toolchain to check for endianness, so mips_4KCel-gcc would work right, but mipsel-linux-gcc would fail with an error that is not very clear :-(. -- Hardware, n.: The parts of a computer system that can be kicked. --------------------------------- Pinpoint customers who are looking for what you sell.

1 0

[U-Boot-Users] PPC 405 walnut
by raj reddy 06 Sep '07

06 Sep '07

My board is close to PPC405 Walnut board. But there is slight modification in the FLASH chip and SDRAM. -> FLASH chip on my custom board is AT49BV320C (flash interface 16Bits). How do I add this ATMEL chip driver to the u-boot. -> SDRAM controller not read from EEPROM , i want to hardcode the values of the SDRAM using the sdram_init (i.e sdram.c) function instead of the spd_sdram.c file. Do i need to change the function implimentation init_func_ram() in the board.c file. plz throw the light to resolve..... Regards, Entry. --------------------------------- Unlimited freedom, unlimited storage. Get it now

2 3

[U-Boot-Users] [PATCH] bootm/fdt: Only process the fdt if an fdt address was provided
by Grant Likely 06 Sep '07

06 Sep '07

From: Grant Likely <grant.likely(a)secretlab.ca> Boards with CONFIG_OF_LIBFDT enabled are not able to boot old-style kernels using the board info structure (instead of passing a device tree) This change allows the old style booting to be used if the fdt argument was not passed to 'bootm'. Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> --- common/cmd_bootm.c | 36 +++++++++++++++++++----------------- 1 files changed, 19 insertions(+), 17 deletions(-) diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index bcb927f..919188f 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -962,29 +962,31 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, * Add the chosen node if it doesn't exist, add the env and bd_t * if the user wants it (the logic is in the subroutines). */ - if (fdt_chosen(of_flat_tree, initrd_start, initrd_end, 0) < 0) { - puts ("ERROR: /chosen node create failed - " - "must RESET the board to recover.\n"); - do_reset (cmdtp, flag, argc, argv); - } + if (of_flat_tree) { + if (fdt_chosen(of_flat_tree, initrd_start, initrd_end, 0) < 0) { + puts ("ERROR: /chosen node create failed - " + "must RESET the board to recover.\n"); + do_reset (cmdtp, flag, argc, argv); + } #ifdef CONFIG_OF_HAS_UBOOT_ENV - if (fdt_env(of_flat_tree) < 0) { - puts ("ERROR: /u-boot-env node create failed - " - "must RESET the board to recover.\n"); - do_reset (cmdtp, flag, argc, argv); - } + if (fdt_env(of_flat_tree) < 0) { + puts ("ERROR: /u-boot-env node create failed - " + "must RESET the board to recover.\n"); + do_reset (cmdtp, flag, argc, argv); + } #endif #ifdef CONFIG_OF_HAS_BD_T - if (fdt_bd_t(of_flat_tree) < 0) { - puts ("ERROR: /bd_t node create failed - " - "must RESET the board to recover.\n"); - do_reset (cmdtp, flag, argc, argv); - } + if (fdt_bd_t(of_flat_tree) < 0) { + puts ("ERROR: /bd_t node create failed - " + "must RESET the board to recover.\n"); + do_reset (cmdtp, flag, argc, argv); + } #endif #ifdef CONFIG_OF_BOARD_SETUP - /* Call the board-specific fixup routine */ - ft_board_setup(of_flat_tree, gd->bd); + /* Call the board-specific fixup routine */ + ft_board_setup(of_flat_tree, gd->bd); #endif + } #endif /* CONFIG_OF_LIBFDT */ #if defined(CONFIG_OF_FLAT_TREE) #ifdef CFG_BOOTMAPSZ

3 3

Re: [U-Boot-Users] booting kernel image from jffs2 partition
by Marco Stornelli 06 Sep '07

06 Sep '07

Stefano babic wrote: >Fabio Ubaldi wrote: >> We'd like to format linux kernel and rootfs image partitions (and the >> others) with jffs2, because the two images may be replaced with newer >> ones while Linux is running. >It is not a problem to replace the linux image while it is running, >because Linux runs from RAM. You can always replace the Linux image. >> A first question is: >> Is it possible to boot (bootm command) the images stored in partitions >> formatted using jffs2? >U-boot can read JFFS2 partitions, but as I said, this should not be >necessary if your goal is only to replace the kernel images. And u-boot >does not need to understand the rootfs, too. >Regards, >stefano babic Hi all, I work with Fabio Ubaldi. The problem is this: the new linux kernel image is send to system from a remote site and the system has to update the image automatically. Our ideas was this: after the system had mounted the jffs2 linux kernel partition, it copy the new image in /mnt/kernel (jffs2 linux kernel partition) and after that the system is rebooted. To perform this U-Boot must be able to boot a linux kernel image from a jffs2 partition. I hope that the problem is now more clear. Thanks. Marco Stornelli

2 1

[U-Boot-Users] MIPS port
by max y 06 Sep '07

06 Sep '07

Hi, I am going to use u-boot for MIPS 24k. Any one know which current port I can start with as reference. Thanks in advance, Max --------------------------------- Got a little couch potato? Check out fun summer activities for kids.

1 0