July 2007 - U-Boot

[U-Boot-Users] The early console issue
by Sascha Hauer 06 Jul '07

06 Jul '07

Hi all, I see that having a configurable early console is of major importance for many people. I'm in the middle of reworking the console layer so that it features - completely position independent code, so can be called with runtime address != link address - runtime configurable in port and baudrate - printf if desired So wait for more to come ;) Btw some excavator has hacked our internet connection, but the repository is still available at git clone http://iocaste.penguin.de/git/U-Boot-NG-git (outdated) git clone http://iocaste.penguin.de/git/U-Boot-NG-wdimport.git (outdated soon when the custodian page is up) Regards, Sascha

1 0

[U-Boot-Users] [PATCH 0/3]Patchset for Ati bios emulator and Ati frambuffer driver
by Jason Jin 06 Jul '07

06 Jul '07

Hi, Stefan This patchset add Ati bios emulator and Ati video card framebuffer driver to u-boot. The bios emulator and the framebuffer driver work for Ati PCI and PCIE video card. We tested the patchset on 9200 PCI card, X300, X700 and X800 PCIE card in u-boot on MPC8641HPCN board. After the video card bios finish runnig in the bios emulator, We can use the Ati framebuffer driver in u-boot, we can also use the radeon base driver in kernel directly for those Ati video card. Thanks, Jason

3 6

[U-Boot-Users] CONFIG_CMD_* transition and other config changes
by Matthias Fuchs 06 Jul '07

06 Jul '07

Hi, how should I handle this situation: 1) I plan to update our board configs to the new CONFIG_CMD_* style. 2) I have a couple of patches that update our boards to use the new NAND subsystem instead of the legacy NAND stuff. Do I have to post the CONFIG_CMD series of patches against u-boot-testing and the NAND patches against the main repository? Or should I post the NAND related patches aginast main repository first and COFNIG_CMD patches that also contain the NAND stuff? So both patches for each board have the NAND stuff in common? Thanks for advice Matthias -- ----------------------------------------------------------------------- Dipl.-Ing. Matthias Fuchs esd electronic system design gmbh http://www.esd-electronics.com Vahrenwalder Str. 207 phone: +49-511-37298-0, fax: -68 30165 Hannover, Germany -----------------------------------------------------------------------

2 1

[U-Boot-Users] [PATCH 6/17] Reorganize and fix problems (returns) in the bootm command.
by Jerry Van Baren 06 Jul '07

06 Jul '07

Do *NOT* return after the "point of no return" has been passed. If something goes wrong, the board must be reset after that point. Move the "Transferring control to Linux" debug message back to where it belongs: just before transferring control to linux. Signed-off-by: Gerald Van Baren <vanbaren(a)cideas.com> --- common/cmd_bootm.c | 130 +++++++++++++++++++++++++-------------------------- 1 files changed, 64 insertions(+), 66 deletions(-) diff --git a/common/cmd_bootm.c b/common/cmd_bootm.c index 25a55bd..25b9d74 100644 --- a/common/cmd_bootm.c +++ b/common/cmd_bootm.c @@ -45,8 +45,8 @@ DECLARE_GLOBAL_DATA_PTR; - /*cmd_boot.c*/ - extern int do_reset (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]); +/*cmd_boot.c*/ +extern int do_reset (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]); #if (CONFIG_COMMANDS & CFG_CMD_DATE) || defined(CONFIG_TIMESTAMP) #include <rtc.h> @@ -763,8 +763,8 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, if ((ntohl(hdr->ih_load) < ((unsigned long)hdr + ntohl(hdr->ih_size) + sizeof(hdr))) && ((ntohl(hdr->ih_load) + ntohl(hdr->ih_size)) > (unsigned long)hdr)) { - printf ("ERROR: Load address overwrites Flat Device Tree uImage\n"); - return; + puts ("ERROR: Load address overwrites Flat Device Tree uImage\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } printf(" Verifying Checksum ... "); @@ -773,34 +773,34 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, header.ih_hcrc = 0; if(checksum != crc32(0, (uchar *)&header, sizeof(image_header_t))) { - printf("ERROR: Flat Device Tree header checksum is invalid\n"); - return; + puts ("ERROR: Flat Device Tree header checksum is invalid\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } checksum = ntohl(hdr->ih_dcrc); addr = (ulong)((uchar *)(hdr) + sizeof(image_header_t)); if(checksum != crc32(0, (uchar *)addr, ntohl(hdr->ih_size))) { - printf("ERROR: Flat Device Tree checksum is invalid\n"); - return; + puts ("ERROR: Flat Device Tree checksum is invalid\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } printf("OK\n"); if (ntohl(hdr->ih_type) != IH_TYPE_FLATDT) { - printf ("ERROR: uImage not Flat Device Tree type\n"); - return; + puts ("ERROR: uImage not Flat Device Tree type\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } if (ntohl(hdr->ih_comp) != IH_COMP_NONE) { - printf("ERROR: uImage is not uncompressed\n"); - return; + puts ("ERROR: uImage is not uncompressed\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #if defined(CONFIG_OF_LIBFDT) if (fdt_check_header(of_flat_tree + sizeof(image_header_t)) != 0) { #else if (*((ulong *)(of_flat_tree + sizeof(image_header_t))) != OF_DT_HEADER) { #endif - printf ("ERROR: uImage data is not a flat device tree\n"); - return; + puts ("ERROR: uImage data is not a flat device tree\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } memmove((void *)ntohl(hdr->ih_load), @@ -808,8 +808,8 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, ntohl(hdr->ih_size)); of_flat_tree = (char *)ntohl(hdr->ih_load); } else { - printf ("Did not find a flat flat device tree at address %08lX\n", of_flat_tree); - return; + puts ("Did not find a flat flat device tree\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } printf (" Booting using flat device tree at 0x%x\n", of_flat_tree); @@ -840,8 +840,8 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, #else if (((struct boot_param_header *)of_data)->magic != OF_DT_HEADER) { #endif - printf ("ERROR: image is not a flat device tree\n"); - return; + puts ("ERROR: image is not a flat device tree\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #if defined(CONFIG_OF_LIBFDT) @@ -849,8 +849,8 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, #else if (((struct boot_param_header *)of_data)->totalsize != ntohl(len_ptr[2])) { #endif - printf ("ERROR: flat device tree size does not agree with image\n"); - return; + puts ("ERROR: flat device tree size does not agree with image\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } } #endif @@ -923,15 +923,6 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, initrd_end = 0; } - debug ("## Transferring control to Linux (at address %08lx) ...\n", - (ulong)kernel); - - SHOW_BOOT_PROGRESS (15); - -#if defined(CFG_INIT_RAM_LOCK) && !defined(CONFIG_E500) - unlock_ram_in_cache(); -#endif - #if defined(CONFIG_OF_LIBFDT) /* move of_flat_tree if needed */ if (of_data) { @@ -960,19 +951,19 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, * if the user wants it (the logic is in the subroutines). */ if (fdt_chosen(of_flat_tree, initrd_start, initrd_end, 0) < 0) { - printf("Failed creating the /chosen node (0x%08X), aborting.\n", of_flat_tree); - return; + puts ("ERROR: Failed creating the /chosen node, aborting.\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #ifdef CONFIG_OF_HAS_UBOOT_ENV if (fdt_env(of_flat_tree) < 0) { - printf("Failed creating the /u-boot-env node, aborting.\n"); - return; + puts ("ERROR: Failed creating the /u-boot-env node, aborting.\nMust RESET 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) { - printf("Failed creating the /bd_t node, aborting.\n"); - return; + puts ("ERROR: Failed creating the /bd_t node, aborting.\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #endif } @@ -997,55 +988,62 @@ do_bootm_linux (cmd_tbl_t *cmdtp, int flag, memmove ((void *)of_start, (void *)of_data, of_len); } #endif - - /* - * Linux Kernel Parameters (passing board info data): - * r3: ptr to board info data - * r4: initrd_start or 0 if no initrd - * r5: initrd_end - unused if r4 is 0 - * r6: Start of command line string - * r7: End of command line string - */ -#if defined(CONFIG_OF_FLAT_TREE) || defined(CONFIG_OF_LIBFDT) - if (!of_flat_tree) /* no device tree; boot old style */ -#endif - (*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end); - /* does not return */ - -#if defined(CONFIG_OF_FLAT_TREE) || defined(CONFIG_OF_LIBFDT) - /* - * Linux Kernel Parameters (passing device tree): - * r3: ptr to OF flat tree, followed by the board info data - * r4: physical pointer to the kernel itself - * r5: NULL - * r6: NULL - * r7: NULL - */ #if defined(CONFIG_OF_FLAT_TREE) ft_setup(of_flat_tree, kbd, initrd_start, initrd_end); /* ft_dump_blob(of_flat_tree); */ #endif #if defined(CONFIG_OF_LIBFDT) if (fdt_chosen(of_flat_tree, initrd_start, initrd_end, 0) < 0) { - printf("Failed creating the /chosen node (0x%08X), aborting.\n", of_flat_tree); - return; + puts ("ERROR: Failed to create the /chosen node, aborting.\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #ifdef CONFIG_OF_HAS_UBOOT_ENV if (fdt_env(of_flat_tree) < 0) { - printf("Failed creating the /u-boot-env node, aborting.\n"); - return; + puts ("ERROR: Failed to create the /u-boot-env node, aborting.\nMust RESET 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) { - printf("Failed creating the /bd_t node, aborting.\n"); - return; + puts ("ERROR: Failed to create the /bd_t node, aborting.\nMust RESET board to recover\n"); + do_reset (cmdtp, flag, argc, argv); } #endif #endif /* if defined(CONFIG_OF_LIBFDT) */ - (*kernel) ((bd_t *)of_flat_tree, (ulong)kernel, 0, 0, 0); + debug ("## Transferring control to Linux (at address %08lx) ...\n", + (ulong)kernel); + + SHOW_BOOT_PROGRESS (15); + +#if defined(CFG_INIT_RAM_LOCK) && !defined(CONFIG_E500) + unlock_ram_in_cache(); #endif + +#if defined(CONFIG_OF_FLAT_TREE) || defined(CONFIG_OF_LIBFDT) + if (of_flat_tree) { /* device tree; boot new style */ + /* + * Linux Kernel Parameters (passing device tree): + * r3: ptr to flattened device tree, followed by the board info data + * r4: physical pointer to the kernel itself + * r5: NULL + * r6: NULL + * r7: NULL + */ + (*kernel) ((bd_t *)of_flat_tree, (ulong)kernel, 0, 0, 0); + /* does not return */ + } +#endif + /* + * Linux Kernel Parameters (passing board info data): + * r3: ptr to board info data + * r4: initrd_start or 0 if no initrd + * r5: initrd_end - unused if r4 is 0 + * r6: Start of command line string + * r7: End of command line string + */ + (*kernel) (kbd, initrd_start, initrd_end, cmd_start, cmd_end); + /* does not return */ } #endif /* CONFIG_PPC */ -- 1.4.4.4

5 10

Re: [U-Boot-Users] U-boot ColdFire development
by Liew Tsi Chung-r5aahp 06 Jul '07

06 Jul '07

Stefan, Here is the test version for 5329 u-boot source at Freescale. http://opensource.freescale.com/git?p=u-boot-coldfire.git;a=summary Added: board/freescale/M5329EVB/Makefile config.mk flash.c m5329evb.c and u-boot.lds cpu/mcf532x/Makefile config.mk cpu.c cpu_init.c speed.c start.S drivers/net/mcffec.c drivers/serial/mcfserial.c include/asm-m68k/immap_5329.h m5329.h mcfrtc.h include/configs/M5329EVB.h lib_m68k/interrupts.c rtc/rtc.c Modified: Makefile MAKEALL README common/cmd_bdinfo.c cmd_mii.c include/asm-m68k/byteorder.h fec.h io.h mcftimer.h mcfuart.h ptrace.h u-boot.h lib_m68k/board.c time.c I had placed the mcfserial.c under drivers/serial and mcffec.c under drivers/net. The rtc.c is under rtc/. 1. I do have one more doubt about placing the following defines as we discussed early. > /* Timer */ > #define CONFIG_MCFTMR > #ifdef CONFIG_MCFTMR > # define CFG_UDELAY_BASE (0xFC070000) > # define CFG_TMR_BASE (0xFC074000) > # define CFG_INTR_BASE (0xFC048000) > # define CFG_TMRINTR_NO (32) > # define CFG_TMRINTR_MASK (1) > #endif If I place the #ifdef CONFIG_MCFTMR ... #endif in say immap_5329.h, isn't that in time.c must include <asm/immap_5329.h>. Time.c #ifdef CONFIG_5329 #include <asm/immap_5329.h> #endif #ifdef CONFIG_5272 #include <asm/immap_5272.h> #endif ... Is there a way not to include <asm/immap_5xxx.h> in time.c each time a new processor is added? 2. I seperated the MII feature from fec.c and placed in under board/freescale/mxxxevb.c. Since the mii phy is board dependent not cpu dependent, do you agree? 3. EHCI/OTG driver development. Do I need to modify the current cmd_usb.c to include EHCI or create a new file cmd_hsusb.c? Regards, TsiChung

4 9

[U-Boot-Users] u-boot in Linux Journal Aug 2007 (Issue 160)
by Jerry Van Baren 06 Jul '07

06 Jul '07

Das U-Boot got a reference in "Building a Next-Generation Residential Gateway" starting on p. 58 (denx.de and sourceforge.net are listed in the "Resources" sidebar on p.61). gvb

1 0

[U-Boot-Users] does cramfs/JFFS2 employ checksums ?
by Iyer 06 Jul '07

06 Jul '07

Is there a cramfs based checksum on the data that is being stored on the MTD where the cramfs mounts ? Say, there is some data on MTD device 2 and the kernel mounts the cramfs image on MTD device 2 and is there any mechanism to verify that the data on the cramfs image hasn't been compromised? I guess JFFS2 also has it's own checksum, because it detects bad blocks. Correct me if I'm wrong. thanks iyer --------------------------------- Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out.

1 0

[U-Boot-Users] [PATCH 0/17] New-old set of patches for the u-boot-fdt repository
by Jerry Van Baren 06 Jul '07

06 Jul '07

Hi all, I have updated the "fdt" branch of the u-boot-fdt repository with a reworked set of previously published patches plus a small improvement (adding a "fdt boardsetup" command). I am republishing the full set of patches because (a) I did some reorganization, making it confusing to try to cherry-pick the unchanged old patches and (b) its been a while since the old set was published. Best regards, gvb

1 1

[U-Boot-Users] U-boot refactoring
by Grant Likely 06 Jul '07

06 Jul '07

Between Jon's CFG->CONFIG changes, Sascha's u2boot effort, and the duplicate file cleanup that I've been hacking on, there are a fair number of invasive changes going in to u-boot. Also, at OLS this year we talked a bit about formalizing the u-boot release procedure and maybe using a merge window and a stabilization period. So, my question is this; with all the changes being talked about on the list; what order/schedule should be used for bringing these changes into mainline? I think we should decide which pieces should go in first, and plan to stagger them so there is time to recover from each invasive change. Thoughts? I also think that Jon's CONFIG_ changes should probably be merged first, and as soon as possible. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely(a)secretlab.ca (403) 399-0195

6 13

[U-Boot-Users] Fwd: text_vvsjniz.pdf
by Harold Lugo 05 Jul '07

05 Jul '07

1 0