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

[U-Boot-Users] [PATCH-V4 1/2] libfdt: add convenience function fdt_find_and_setprop()
by Grant Likely 06 Sep '07

06 Sep '07

From: Grant Likely <grant.likely(a)secretlab.ca> Given the path to a node, fdt_find_and_setprop() allows a property value to be set directly. Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> --- include/libfdt.h | 2 ++ libfdt/fdt_rw.c | 26 ++++++++++++++++++++++++++ 2 files changed, 28 insertions(+), 0 deletions(-) diff --git a/include/libfdt.h b/include/libfdt.h index 340e89d..38c65a9 100644 --- a/include/libfdt.h +++ b/include/libfdt.h @@ -140,6 +140,8 @@ int fdt_setprop(void *fdt, int nodeoffset, const char *name, }) #define fdt_setprop_string(fdt, nodeoffset, name, str) \ fdt_setprop((fdt), (nodeoffset), (name), (str), strlen(str)+1) +int fdt_find_and_setprop(void *fdt, const char *node, const char *prop, + const void *val, int len, int create); int fdt_delprop(void *fdt, int nodeoffset, const char *name); int fdt_add_subnode_namelen(void *fdt, int parentoffset, const char *name, int namelen); diff --git a/libfdt/fdt_rw.c b/libfdt/fdt_rw.c index 693bfe4..55fcc41 100644 --- a/libfdt/fdt_rw.c +++ b/libfdt/fdt_rw.c @@ -188,6 +188,32 @@ int fdt_setprop(void *fdt, int nodeoffset, const char *name, return 0; } +/** + * fdt_find_and_setprop: Find a node and set it's property + * + * @fdt: ptr to device tree + * @node: path of node + * @prop: property name + * @val: ptr to new value + * @len: length of new property value + * @create: flag to create the property if it doesn't exist + * + * Convenience function to directly set a property given the path to the node. + */ +int fdt_find_and_setprop(void *fdt, const char *node, const char *prop, + const void *val, int len, int create) +{ + int nodeoff = fdt_find_node_by_path(fdt, node); + + if (nodeoff < 0) + return nodeoff; + + if ((!create) && (fdt_get_property(fdt, nodeoff, prop, 0) == NULL)) + return 0; /* create flag not set; so exit quietly */ + + return fdt_setprop(fdt, nodeoff, prop, val, len); +} + int fdt_delprop(void *fdt, int nodeoffset, const char *name) { struct fdt_property *prop;

1 1

[U-Boot-Users] ls on a JFFS2 partition results in multiple copies of a single filename
by Dan Batryn 06 Sep '07

06 Sep '07

I am using a JFFS2 file system on a NAND flash based memory system. I have a file in a partition that has been updated several times from the Linux that is running. What I notice when I perform an ls from the UBOOT prompt is that there are multiple instances of that file each with a different file length. I have tried turning on the define CFG_JFFS2_SORT_FRAGMENTS for the UBOOT build but this only results in reordering the ls results. I was looking at the code in file jffs2_1pass.c: /* list inodes with the given pino */ static u32 jffs2_1pass_list_inodes(struct b_lists * pL, u32 pino) { struct b_node *b; struct jffs2_raw_dirent *jDir; for (b = pL->dir.listHead; b; b = b->next) { jDir = (struct jffs2_raw_dirent *) get_node_mem(b->offset); if ((pino == jDir->pino) && (jDir->ino)) { /* ino=0 -> unlink */ u32 i_version = 0; struct jffs2_raw_inode ojNode; struct jffs2_raw_inode *jNode, *i = NULL; struct b_node *b2 = pL->frag.listHead; while (b2) { jNode = (struct jffs2_raw_inode *) get_fl_mem(b2->offset, sizeof(ojNode), &ojNode); if (jNode->ino == jDir->ino && jNode->version >= i_version) { if (i) put_fl_mem(i); if (jDir->type == DT_LNK) i = get_node_mem(b2->offset); else i = get_fl_mem(b2->offset, sizeof(*i), NULL); } b2 = b2->next; } dump_inode(pL, jDir, i); put_fl_mem(i); } put_fl_mem(jDir); } return pino; } So I have several questions: 1. In briefly looking at this code I see that the variable i_version is set to 0 and never updated during the scan of nodes. I am not familiar with the JFFS2 internals but this seems incorrect. Can someone please confirm i_version compares? 2. I also noticed that there is an alternate file in the same directory named jffs2_nand_1pass.c. It appears that this file is not used in the normal build of the fs/jffs2 object. When I tried using this file as an alternative for jff2_1pass.c, I found that the alternate file would not even compile if either DEBUG, DEBUG_DIRENTS or DEBUG_FRAGMENTS defines set. Could someone please comment on the state of this file and if it ready for general usage? 3. I also notice that neither of these files has support for the nodetype == JFFS2_NODETYPE_SUMMARY. So during the scan there are annoying messages that complain about the unknown node types. Is there a pending patch to take care of the additional node types? Thank you in advance for any information. Daniel Batryn Shoretel Inc. 960 Stewart Sunnyvale, CA 94085 Phone: (408) 331-3575 Fax: (408) 331-3333 CONFIDENTIALITY NOTICE: This e-mail and any attachments are confidential and may be protected by legal privilege and/or are otherwise exempt from disclosure. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please notify us immediately by returning it to the sender and delete this copy from your system.

1 0

[U-Boot-Users] booting kernel image from jffs2 partition
by Fabio Ubaldi 06 Sep '07

06 Sep '07

Hi all, I have a Spansion S29GL512N NOR flash. Specifically, I have two banks of 64 MB mapped in the following way: 0xf4000000- 0xf7ffffff First bank 0xfc000000-0xffffff Second Bank (boot bank) In the Linux kernel we have partitioned the flash in five parts: 0xf4000000 - 0xf43fffff Linux kernel image 0xf4400000 - 0xf4fffffff Rootfs Image 0xf5000000 - 0xf7ffffff Data1 0xfc000000 - 0xfff7ffff Data2 0xfff80000 - 0xffffffff U-boot image 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. A first question is: Is it possible to boot (bootm command) the images stored in partitions formatted using jffs2? i.e. after the images are replaced and the machine is rebooted, can the u-boot be configured to read the new image from these jffs2 partitions? If so, how is it possible to perform it? Because from Internet and manual, I reckon out that u-boot works using binary or file-system images stored in raw way and I don't understand if the image can be read andloaded from a not-raw partitions. Thanks in advance for the reply. Fabio Ubaldi

3 2

[U-Boot-Users] CFI code is writing over "protected" flash - help
by Scott Mann 05 Sep '07

05 Sep '07

Hello, I'm working on the port of u-boot to a custom board based on the MPC8250. I'm using a snapshot from the git repository (last date in the changelog is 7/14/07). I started with the Rattler configuration and have slowly progressed to this point (see output below). I've been stuck here for a couple days and so I thought that I would ask for advice now - hopefully, I am not missing the obvious! I have DEBUG enabled. Boot flash starts at 0xFE000000 (this is also the value of TEXT_BASE) and even though I've set CFG_FLASH_PROTECTION, the CFI code is erasing the flash over the "protected" range - that is, it starts writing at 0xFE000000. Any help would be greatly appreciated! Anyway, here is a (hopefully) pertinent snippet from my config file: <snip> #define CFG_FLASH_PROTECTION 1 /* Real (hardware) sectors protection */ #define CFG_FLASH_BASE 0xFE000000 #define CFG_FLASH_CFI #define CFG_FLASH_CFI_DRIVER #define CFG_MAX_FLASH_BANKS 1 /* max num of flash banks */ #define CFG_MAX_FLASH_SECT 32 /* max num of sects on one chip */ #define CFG_DIRECT_FLASH_TFTP <snip> #define CFG_MONITOR_BASE TEXT_BASE #if (CFG_MONITOR_BASE < CFG_FLASH_BASE) #define CFG_RAMBOOT #endif #define CFG_MONITOR_LEN (256 * 1024) /* Reserve 256 kB for Monitor */ #define CFG_ENV_IS_IN_FLASH #ifdef CFG_ENV_IS_IN_FLASH #define CFG_ENV_SECT_SIZE 0x10000 #define CFG_ENV_ADDR (CFG_MONITOR_BASE + CFG_MONITOR_LEN) #endif /* CFG_ENV_IS_IN_FLASH */ <snip> ********************** And the output to the console: MPC8250 Clock Configuration - Bus-to-Core Mult 2x, VCO Div 2, 60x Bus Freq 50-150, Core Freq 100-300 - dfbrg 1, corecnf 0x04, busdf 3, cpmdf 1, plldf 0, pllmf 1, pcidf 3 - vco_out 264000000, scc_clk 66000000, brg_clk 16500000 - cpu_clk 132000000, cpm_clk 132000000, bus_clk 66000000 CPU: MPC8250 (HiP4 Rev 14, Mask C.0 5K25A) at 132 MHz Board: Aztek CTA MPC8250. DRAM: 64 MB Top of RAM usable for U-Boot at: 04000000 Reserving 224k for U-Boot at: 03fc7000 Reserving 4160k for malloc() at: 03bb7000 Reserving 76 Bytes for Board Info at: 03bb6fb4 Reserving 72 Bytes for Global Data at: 03bb6f6c Stack Pointer at: 03bb6f48 New Stack Pointer is: 03bb6f48 Now running in RAM - U-Boot at: 03fc7000 FLASH: flash detect cfi fwc addr fe000000 cmd 0 0 8bit x 8 bit fwc addr fe000055 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr fe000010 is= 83 51 fwc addr fe000555 cmd 98 98 8bit x 8 bit is= cmd 51(Q) addr fe000010 is= 83 51 fwc addr fe000000 cmd 0 0000 16bit x 8 bit fwc addr fe0000aa cmd 98 9898 16bit x 8 bit is= cmd 51(Q) addr fe000020 is= 0051 5151 fwc addr fe000aaa cmd 98 9898 16bit x 8 bit is= cmd 51(Q) addr fe000020 is= 0051 5151 fwc addr fe000000 cmd 0 0000 16bit x 16 bit fwc addr fe0000aa cmd 98 0098 16bit x 16 bit is= cmd 51(Q) addr fe000020 is= 0051 0051 is= cmd 52(R) addr fe000022 is= 0052 0052 is= cmd 59(Y) addr fe000024 is= 0059 0059 ushort addr is at fe000050 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x2 addr[2] = 0x0 addr[3] = 0x0 retval = 0x2 device interface is 2 found port 2 chip 2 port 16 bits chip 16 bits ushort addr is at fe000026 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x2 addr[2] = 0x0 addr[3] = 0x0 retval = 0x2 fwc addr fe000000 cmd f0 00f0 16bit x 16 bit fwc addr fe000aaa cmd aa 00aa 16bit x 16 bit fwc addr fe000554 cmd 55 0055 16bit x 16 bit fwc addr fe000aaa cmd 90 0090 16bit x 16 bit fwc addr fe000000 cmd f0 00f0 16bit x 16 bit fwc addr fe0000aa cmd 98 0098 16bit x 16 bit ushort addr is at fe00002a info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x40 addr[2] = 0x0 addr[3] = 0x0 retval = 0x40 fe000020 : 00 51 00 52 00 59 00 02 00 00 00 40 00 00 00 00 .Q.R.Y.....@.... fe000030 : 00 00 00 00 00 00 00 27 00 36 00 00 00 00 00 04 .......'.6...... fe000040 : 00 00 00 0a 00 00 00 05 00 00 00 04 00 00 00 15 ................ fe000050 : 00 02 00 00 00 00 00 00 00 04 00 00 00 00 00 40 ...............@ fe000060 : 00 00 00 01 00 00 00 20 00 00 00 00 00 00 00 80 ....... ........ fe000070 : 00 00 00 1e 00 00 00 00 00 01 00 00 00 00 00 00 ................ fe000080 : 00 50 00 52 00 49 00 31 00 30 00 00 00 02 00 01 .P.R.I.1.0...... fe000090 : 00 01 00 04 00 00 00 00 00 00 00 00 00 00 00 00 ................ manufacturer is 2 manufacturer id is 0x1 device id is 0x49 device id2 is 0x0 cfi version is 0x3130 size_ratio 1 port 16 bits chip 16 bits found 4 erase regions long addr is at fe00005a info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x0 addr[2] = 0x0 addr[3] = 0x0 addr[4] = 0x0 addr[5] = 0x40 addr[6] = 0x0 addr[7] = 0x0 erase_region_count = 1 erase_region_size = 16384 long addr is at fe000062 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x1 addr[2] = 0x0 addr[3] = 0x0 addr[4] = 0x0 addr[5] = 0x20 addr[6] = 0x0 addr[7] = 0x0 erase_region_count = 2 erase_region_size = 8192 long addr is at fe00006a info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x0 addr[2] = 0x0 addr[3] = 0x0 addr[4] = 0x0 addr[5] = 0x80 addr[6] = 0x0 addr[7] = 0x0 erase_region_count = 1 erase_region_size = 32768 long addr is at fe000072 info->portwidth = 2 addr[0] = 0x0 addr[1] = 0x1e addr[2] = 0x0 addr[3] = 0x0 addr[4] = 0x0 addr[5] = 0x0 addr[6] = 0x0 addr[7] = 0x1 erase_region_count = 31 erase_region_size = 65536 ****** Thanks, Scott

1 0

[U-Boot-Users] Day trader watch list
by uaemero＠southernperu.com.pe 05 Sep '07

05 Sep '07

Brokers Push Volume High As Market Watchers Alert Investors. Vega Promotional Sys, Inc V G P M $0.07 Brokers move huge volumes as investors are reading up the latest news on VGPM. The time to get in is now. Set your buy for Thursday opening bell.

1 0

[U-Boot-Users] Multicast TFTP problems
by Rafal Jaworowski 05 Sep '07

05 Sep '07

Dave, I'm having problems with tftp transfer with current U-Boot running on MPC5121 (FEC controller); since your mcast tftp implementation we first attempt to transfer using some bigger blocksize: #define TFTP_MTU_BLOCKSIZE 1468, and it seems my problems are related to this size. When running current code (ET_DEBUG enabled) it fails like the following: => run load Using FEC ETHERNET device TFTP from server 192.168.1.1; our IP address is 192.168.160.77 Filename '/tftpboot/ads5121/u-boot.bin'. Load address: 0x100000 Loading: send option "timeout 5" Got OACK: timeout 5 Blocksize ack: 1468, 1468 T T T T T T T T T T Retry count exceeded; starting again Using FEC ETHERNET device TFTP from server 192.168.1.1; our IP address is 192.168.160.77 Filename '/tftpboot/ads5121/u-boot.bin'. Load address: 0x100000 Loading: send option "timeout 5" Got OACK: timeout 5 Blocksize ack: 1468, 1468 Abort => It fails with TFTP_MTU_BLOCKSIZE values above 1454, but it's ok with anything up to this (including 1454): => run load Using FEC ETHERNET device TFTP from server 192.168.1.1; our IP address is 192.168.160.77 Filename '/tftpboot/ads5121/u-boot.bin'. Load address: 0x100000 Loading: send option "timeout 5" Got OACK: timeout 5 Blocksize ack: 1454, 1454 ########### done Bytes transferred = 157720 (26818 hex) => Any hints on these observations? What might be going wrong here? kind regards, Rafal

3 6

[U-Boot-Users] [PATCH] Add .gitignore files
by Grant Likely 05 Sep '07

05 Sep '07

From: Grant Likely <grant.likely(a)secretlab.ca> Signed-off-by: Grant Likely <grant.likely(a)secretlab.ca> --- .gitignore | 14 ++++++++++++++ examples/.gitignore | 5 +++++ include/.gitignore | 6 ++++++ tools/.gitignore | 9 +++++++++ 4 files changed, 34 insertions(+), 0 deletions(-) diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..9d9f7aa --- /dev/null +++ b/.gitignore @@ -0,0 +1,14 @@ +*.rej +*.orig +*.a +*.o +*.depend +System.map +/u-boot +/u-boot.map +/u-boot.bin +/u-boot.srec +/LOG +/errlog +/reloc_off + diff --git a/examples/.gitignore b/examples/.gitignore new file mode 100644 index 0000000..f547024 --- /dev/null +++ b/examples/.gitignore @@ -0,0 +1,5 @@ +/hello_world +/interrupt +/sched +*.bin +*.srec diff --git a/include/.gitignore b/include/.gitignore new file mode 100644 index 0000000..d8fda80 --- /dev/null +++ b/include/.gitignore @@ -0,0 +1,6 @@ +/asm +/asm-ppc/arch +/bmp_logo.h +/config.h +/config.mk +/version_autogenerated.h diff --git a/tools/.gitignore b/tools/.gitignore new file mode 100644 index 0000000..c33679a --- /dev/null +++ b/tools/.gitignore @@ -0,0 +1,9 @@ +/bmp_logo +/crc32.c +/envcrc +/environment.c +/gen_eth_addr +/img2srec +/mkimage +/sha1.c +/ubsha1

1 0

[U-Boot-Users] iic1 can't work on 440EPx
by Dong Yuan Xiao (CW) 05 Sep '07

05 Sep '07

Hi all, Is there anyone working on the 440EPx? I found the code in u-boot 1.2.0 only support iic0, so iic1 didn't work. However I tried many ways to enable the iic1 bus, bus all failed. I even tried the simple way as changing the 'I2C_BASE_ADDR' in file ../include/440_i2c.h to (CFG_PERIPHERAL_BASE + 0x00000800), still can't make the iic1 work, why? can anyone give me the answer that why the u-boot always skip the iic1 bus, is there some bug in the iic1 bus itself? ,Thanks - Denny

3 2

[U-Boot-Users] Enabling Cache in MPC5200
by santoshguru＠yahoo.com 05 Sep '07

05 Sep '07

Hi, I am using a LITE5200 evaluation board, and am not able to enable the cache. The execution hangs in these calls. void EnableInstCache(void) { __asm(" mfspr r5,1008"); __asm(" ori r5,r5,0x00008800");// # Set the ICE and ICFI bit __asm(" andi. r6,r5,0x0000F7FF");// # clear the ICFI bit for the final store __asm(" mtspr 1008,r5"); __asm(" isync"); __asm(" isync"); __asm(" isync"); __asm(" isync"); __asm(" sync"); __asm(" mtspr 1008,r6");// # Do the final store __asm(" isync"); __asm(" sync"); } void EnableDataCache(void) { __asm(" mfspr r5,1008"); __asm(" ori r5,r5,0x00004400");// # Set the ICE and ICFI bit __asm(" andi. r6,r5,0x0000FBFF");// # clear the ICFI bit for the final store __asm(" mtspr 1008,r5"); __asm(" isync"); __asm(" isync"); __asm(" isync"); __asm(" isync"); __asm(" sync"); __asm(" mtspr 1008,r6");// # Do the final store __asm(" isync"); __asm(" sync"); } What could be the problem? Thanks -San

3 2

[U-Boot-Users] uImage starting problem on Virtex-4 (PPC405)
by Miroslaw Dach 05 Sep '07

05 Sep '07

Hi All, I have successfully built u-boot 1.2.0 on my Avnet evaluation board (ml403 like) which uses virtex-4 xilinx FPGA with built-in ppc405 processor. The u-boot was configured to deal with UART lite. I have build also zImage.elf which runs very well on my board. I have however difficulties to run kernel image via u-boot. My board has 32 MB of RAM memory (address range 0x000000 - 0x1ffffff) The steps which I have done are as following: 1. I have build u-boot and loaded it via jtag to my board XMD% dow u-boot1a.elf section, .text: 0x01a00000-0x01a0d838 section, .resetvec: 0x01a122f0-0x01a122f4 section, .rodata: 0x01a0d838-0x01a0fc5b section, .reloc: 0x01a0fd00-0x01a102a8 section, .data: 0x01a102a8-0x01a10740 section, .data.rel: 0x01a10740-0x01a1076c section, .data.rel.local: 0x01a1076c-0x01a10ba4 section, .u_boot_cmd: 0x01a10ba4-0x01a10db4 section, .bss: 0x01a10e00-0x01a122f0 Downloaded Program u-boot1a.elf 2. I have loaded the uImage via jtag to the memory location 0x600000 3. I have started u-boot: U-Boot 1.2.0 (Aug 31 2007 - 10:49:57) ### No HW ID - assuming ML403 DRAM: 32 MB Using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 4. I have started uImage => bootm 0x600000 ## Booting image at 00600000 ... Image Name: Linux-2.6.21-rc6 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 981837 Bytes = 958.8 kB Load Address: 00a00000 Entry Point: 00a00000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x01FCC668 => set upper limit to 0x00800000 No initrd ## Transferring control to Linux (at address 00a00000) ... 5. After that the system just hangs 6. I have tried as well to run zImage.elf from u-boot (zImage.elf runs well when started straight from jtag): => bootelf 0x600000 Loading .text @ 0x00400000 (14140 bytes) Loading .data @ 0x00404000 (987136 bytes) Clearing .bss @ 0x004f5000 (8504 bytes) ## Starting application at 0x00400000 ... loaded at: 00400000 004F7138 board data at: 004F5120 004F5138 relocated to: 004040B4 004040CC zimage at: 00404EA9 004F49F5 avail ram: 004F8000 01FFFFFF Linux/PPC load: console=ttyUL0,9600 root=/dev/nfs rw nfsroot=129.117.144.113:/opt/eldk41/ppc_4xx,tcp ip=::::virtex4-mirek:eth0:dhcp panic=1 Uncompressing Linux... 7. After that system just hangs My observation is that: - when launching zImage from u-boot, the system blocks during zImage uncompressing - when launching uImage from u-boot the system blocks after u-boot uncompresses the uImage I do not know what I do wrong. Maybe the processor is not set to the correct mode of the apportion or the memory locations are not correct. I do not also know what should be the proper: Load Address and Entry Point for uImage. The zImage refers to the location 0x400000 (as listed above). I attache to this post my Avnet board u-boot configuration. Any suggestion is welcome Best Regards Mirek -- ============================================================================= Miroslaw Dach (Miroslaw.Dach(a)psi.ch) - SLS/Controls Group PSI - Paul Scherrer Institut CH-5232 Villigen =============================================================================

3 7

[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

[U-Boot-Users] etkedebn
by Cheri Hei 02 Sep '07

02 Sep '07

Hello Hei Say hello to my little friend, well big friend now konb Howk http://www.arratx.com/

1 0

[U-Boot-Users] where did you hide that camera?
by a.a.de.groot＠porte-oceane.com 01 Sep '07

01 Sep '07

1 0

[U-Boot-Users] Report to Recipient(s)
by SEC01NOT＠staubli.com 01 Sep '07

01 Sep '07

Incident Information:- Originator: u-boot-users-bounces(a)lists.sourceforge.net Recipients: <u-boot-users(a)lists.sourceforge.net> Subject: [U-Boot-Users] where did you hide that camera? WARNING=The file / html you received infected with the W32/Zhelatin.gen!eml virus. The file attachment was not successfully cleaned.

1 0