September 2007 - U-Boot

[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