March 2009 - U-Boot

[U-Boot] compile uboot1.3.4 problem
by John Smith 03 Mar '09

03 Mar '09

hi all, I got a problem that I cannot fix,when I am trying to compile uboot1.3.4 for my processer s3c2440. =============================================================== root@john-desktop:/home/john/u-boot-1.3.4 # /usr/local/arm/3.3.2/bin/arm-linux- ar: libyt2440.a File format not recognized -bash:/usr/local/arm/3.3.2/bin/arm-linux-ar:: No such file or directory =============================================================== libyt2440.a is a file under my board directory, I found nothing in it when I opened it. I have no idea about this problem,any idea you guys? any help is appreciated! regards john

1 0

[U-Boot] [PATCH] Can build with only jffs2 cmdline support
by Kyungmin Park 03 Mar '09

03 Mar '09

Some program such as UBI only used the mtdpart only. however current jffs2 cmdline has dependent with jffs2 cmd This patch make a build only jffs2 cmdline without jffs2 cmd dependency. Signed-off-by: Kyungmin Park <kyungmin.park(a)samsung.com> --- diff --git a/common/Makefile b/common/Makefile index f13cd11..18d76fa 100644 --- a/common/Makefile +++ b/common/Makefile @@ -98,6 +98,7 @@ COBJS-$(CONFIG_CMD_IMMAP) += cmd_immap.o COBJS-$(CONFIG_CMD_IRQ) += cmd_irq.o COBJS-$(CONFIG_CMD_ITEST) += cmd_itest.o COBJS-$(CONFIG_CMD_JFFS2) += cmd_jffs2.o +COBJS-$(CONFIG_JFFS2_CMDLINE) += cmd_jffs2.o COBJS-$(CONFIG_CMD_LICENSE) += cmd_license.o COBJS-y += cmd_load.o COBJS-$(CONFIG_LOGBUFFER) += cmd_log.o diff --git a/common/cmd_jffs2.c b/common/cmd_jffs2.c index d0a7cea..3af1bff 100644 --- a/common/cmd_jffs2.c +++ b/common/cmd_jffs2.c @@ -2005,6 +2005,7 @@ static struct part_info* jffs2_part_info(struct mtd_device *dev, unsigned int pa /* U-boot commands */ /***************************************************/ +#ifdef CONFIG_CMD_JFFS2 /** * Routine implementing fsload u-boot command. This routine tries to load * a requested file from jffs2/cramfs filesystem on a current partition. @@ -2144,6 +2145,7 @@ int do_jffs2_fsinfo(cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) } return 1; } +#endif /* CONFIG_CMD_JFFS2 */ /* command line only */ #ifdef CONFIG_JFFS2_CMDLINE @@ -2295,6 +2297,7 @@ int do_jffs2_mtdparts(cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) #endif /* #ifdef CONFIG_JFFS2_CMDLINE */ /***************************************************/ +#ifdef CONFIG_CMD_JFFS2 U_BOOT_CMD( fsload, 3, 0, do_jffs2_fsload, "load binary file from a filesystem image", @@ -2314,6 +2317,7 @@ U_BOOT_CMD( "print information about filesystems", " - print information about filesystems\n" ); +#endif #ifdef CONFIG_JFFS2_CMDLINE U_BOOT_CMD(

3 5

[U-Boot] Status open patches: NAND Flash
by Wolfgang Denk 02 Mar '09

02 Mar '09

Dear Scott, I have the following patches still marked as open in my list. Could you please have a look... NAND-FLASH: 11/04 John Rigby [U-Boot] [PATCH v3] Freescale NFC NAND driver 11/10 Kyungmin Park [U-Boot] [PATCH] [ONENAND] Reduce OneNAND IPL code size v2 02/09 Alessandro Rubini [U-Boot] [PATCH 2/3] Nand driver for Nomadik SoC 02/09 Alessandro Rubini Re: [U-Boot] [PATCH 2/3] Nand driver for Nomadik SoC Thanks in advance. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de Man did not weave the web of life; he is merely a strand in it. Whatever he does to the web, he does to himself. - Seattle [1854]

2 1

Re: [U-Boot] U-Boot hangs after loading device tree
by Pieter 02 Mar '09

02 Mar '09

Afzal Nadirshah wrote: > > Hi, > > I am trying to bring linux up on our custom board, by loading the kernel.img , canynlands.dtb and Ramdisk onto the RAM using the serial port. > > However the boot process is getting hung. The boot boot process stops after the following messages : > > > > > > => run flash_self > > ## Booting kernel from Legacy Image at 1c000000 ... > > Image Name: Linux-2.6.25.7-00002-geaaf8db > > Created: 2008-06-30 13:53:11 UTC > > Image Type: PowerPC Linux Kernel Image (gzip compressed) > > Data Size: 1547704 Bytes = 1.5 MB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > ## Loading init Ramdisk from Legacy Image at 1c200000 ... > > Image Name: Simple Embedded Linux Framework > > Created: 2002-10-24 9:30:38 UTC > > Image Type: PowerPC Linux RAMDisk Image (gzip compressed) > > Data Size: 1476478 Bytes = 1.4 MB > > Load Address: 00000000 > > Entry Point: 00000000 > > Verifying Checksum ... OK > > ## Flattened Device Tree blob at 1c1e0000 > > Booting using the fdt blob at 0x1c1e0000 > > Uncompressing Kernel Image ... OK > > Loading Ramdisk to 1fc78000, end 1fde077e ... OK > > Loading Device Tree to 007f9000, end 007ff0b4 ... OK > > > > > > I have changed the kernel_addr, fdt_addr and the ramdisk_addr to the RAM addresses. > > This is the output of the printenv command : > > > > > > => printenv > > bootdelay=5 > > baudrate=115200 > > loads_echo= > > preboot=echo;echo Type "run flash_nfs" to mount root filesystem over NFS;echo > > hostname=canyonlands > > netdev=eth0 > > nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} > > ramargs=setenv bootargs root=/dev/ram rw > > addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}1 > > addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} > > addmisc=setenv bootargs ${bootargs} > > initrd_high=30000000 > > kernel_addr_r=400000 > > fdt_addr_r=800000 > > ramdisk_addr_r=C00000 > > hostname=canyonlands > > bootfile=canyonlands/uImage > > ramdisk_file=canyonlands/uRamdisk > > rootpath=/opt/eldk/ppc_4xxFP > > flash_self=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > > flash_nfs=run nfsargs addip addtty addmisc;bootm ${kernel_addr} - ${fdt_addr} > > net_nfs=tftp ${kernel_addr_r} ${bootfile}; tftp ${fdt_addr_r} ${fdt_file}; run nfsargs addip a} > > net_self_load=tftp ${kernel_addr_r} ${bootfile};tftp ${fdt_addr_r} ${fdt_file};tftp ${ramdisk_; > > net_self=run net_self_load;run ramargs addip addtty addmisc;bootm ${kernel_addr_r} ${ramdisk_a} > > fdt_file=canyonlands/canyonlands.dtb > > load=tftp 200000 canyonlands/u-boot.bin > > update=protect off 0x01000000 FFFFFFFF;era 0x01000000 FFFFFFFF;cp.b ${fileaddr} 0x01000000 ${fv > > upd=run load update > > nload=tftp 200000 canyonlands/u-boot-nand.bin > > nupdate=nand erase 0 100000;nand write 200000 0 100000;setenv filesize;saveenv > > nupd=run nload nupdate > > pciconfighost=1 > > pcie_mode=RP:RP > > fdt_addr=1c1e0000 > > ramdisk_addr=1c200000 > > ram_root=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} > > ram_ws=1C000000 > > kernel_addr=1c000000 > > stdin=serial > > stdout=serial > > stderr=serial > > ver=U-Boot 2009.01 (Feb 25 2009 - 15:12:15) > > bootcmd=run flash_self > > bootargs=root=/dev/ram rw ip=::::canyonlands:eth0:off panic=1 console=ttyS0,115200 > > filesize=1687BE > > > > Have anybody faced a similar problem? > > > I recently had a similar problem - the solution was a combination of DTS tweaks and U-Boot defines for my board. have a look at the post mortem debugging and recheck all your defines. <http://www.denx.de/wiki/view/DULG/LinuxPostMortemAnalysis> or search the mailing list for my postings: [U-Boot] Custom MPC8548 boot using FDT problem cheers pieter

1 0

[U-Boot] U-Boot hangs after loading device tree
by Afzal Nadirshah 02 Mar '09

02 Mar '09

Hi, I am trying to bring linux up on our custom board, by loading the kernel.img , canynlands.dtb and Ramdisk onto the RAM using the serial port. However the boot process is getting hung. The boot boot process stops after the following messages : => run flash_self ## Booting kernel from Legacy Image at 1c000000 ... Image Name: Linux-2.6.25.7-00002-geaaf8db Created: 2008-06-30 13:53:11 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 1547704 Bytes = 1.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 1c200000 ... Image Name: Simple Embedded Linux Framework Created: 2002-10-24 9:30:38 UTC Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 1476478 Bytes = 1.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 1c1e0000 Booting using the fdt blob at 0x1c1e0000 Uncompressing Kernel Image ... OK Loading Ramdisk to 1fc78000, end 1fde077e ... OK Loading Device Tree to 007f9000, end 007ff0b4 ... OK I have changed the kernel_addr, fdt_addr and the ramdisk_addr to the RAM addresses. This is the output of the printenv command : => printenv bootdelay=5 baudrate=115200 loads_echo= preboot=echo;echo Type "run flash_nfs" to mount root filesystem over NFS;echo hostname=canyonlands netdev=eth0 nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ramargs=setenv bootargs root=/dev/ram rw addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}1 addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate} addmisc=setenv bootargs ${bootargs} initrd_high=30000000 kernel_addr_r=400000 fdt_addr_r=800000 ramdisk_addr_r=C00000 hostname=canyonlands bootfile=canyonlands/uImage ramdisk_file=canyonlands/uRamdisk rootpath=/opt/eldk/ppc_4xxFP flash_self=run ramargs addip addtty addmisc;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} flash_nfs=run nfsargs addip addtty addmisc;bootm ${kernel_addr} - ${fdt_addr} net_nfs=tftp ${kernel_addr_r} ${bootfile}; tftp ${fdt_addr_r} ${fdt_file}; run nfsargs addip a} net_self_load=tftp ${kernel_addr_r} ${bootfile};tftp ${fdt_addr_r} ${fdt_file};tftp ${ramdisk_; net_self=run net_self_load;run ramargs addip addtty addmisc;bootm ${kernel_addr_r} ${ramdisk_a} fdt_file=canyonlands/canyonlands.dtb load=tftp 200000 canyonlands/u-boot.bin update=protect off 0x01000000 FFFFFFFF;era 0x01000000 FFFFFFFF;cp.b ${fileaddr} 0x01000000 ${fv upd=run load update nload=tftp 200000 canyonlands/u-boot-nand.bin nupdate=nand erase 0 100000;nand write 200000 0 100000;setenv filesize;saveenv nupd=run nload nupdate pciconfighost=1 pcie_mode=RP:RP fdt_addr=1c1e0000 ramdisk_addr=1c200000 ram_root=run ramargs addip;bootm ${kernel_addr} ${ramdisk_addr} ${fdt_addr} ram_ws=1C000000 kernel_addr=1c000000 stdin=serial stdout=serial stderr=serial ver=U-Boot 2009.01 (Feb 25 2009 - 15:12:15) bootcmd=run flash_self bootargs=root=/dev/ram rw ip=::::canyonlands:eth0:off panic=1 console=ttyS0,115200 filesize=1687BE Have anybody faced a similar problem? Regards, Afzal Nadirshah http://www.mindtree.com/email/disclaimer.html

1 0

[U-Boot] [PATCH] i2c, dtt: move dtt_init () to board_init_r ()
by Heiko Schocher 02 Mar '09

02 Mar '09

it is not necessary to init the DTTs so early, so move this init to board_init_r (). Signed-off-by: Heiko Schocher <hs(a)denx.de> --- lib_ppc/board.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lib_ppc/board.c b/lib_ppc/board.c index f1b62f5..45c87d6 100644 --- a/lib_ppc/board.c +++ b/lib_ppc/board.c @@ -339,9 +339,6 @@ init_fnc_t *init_sequence[] = { #if defined(CONFIG_HARD_SPI) init_func_spi, #endif -#if defined(CONFIG_DTT) /* Digital Thermometers and Thermostats */ - dtt_init, -#endif #ifdef CONFIG_POST post_init_f, #endif @@ -993,6 +990,9 @@ void board_init_r (gd_t *id, ulong dest_addr) WATCHDOG_RESET (); +#if defined(CONFIG_DTT) /* Digital Thermometers and Thermostats */ + dtt_init (); +#endif #if defined(CONFIG_CMD_SCSI) WATCHDOG_RESET (); puts ("SCSI: "); -- 1.6.0.6 -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

1 1

Re: [U-Boot] ref:fail to include stdio.h
by Paul Wang 01 Mar '09

01 Mar '09

Hi, Jean, Thanks for the information. The signature I need is SHA1 + RSA. The existing SHA1 module on u-boot is OK, and I have checked it generates the correct Hash. Regards. Paul Wang -----Original Message----- From: Jean-Christophe PLAGNIOL-VILLARD [mailto:plagnioj@jcrosoft.com] Sent: Friday, February 27, 2009 2:52 PM To: Paul Wang Subject: Re: [U-Boot] ref:fail to include stdio.h On 12:27 Fri 27 Feb , Paul Wang wrote: > I am trying to port some code of xyssl to u-boot in order to do the > digital signature verification. I've already do this for a company but they never publish the code and they are not obliged (non-public product) but which signature do you need? SHA1, SHA256, RSA?? please keep it off list Best Regards, J. ---- This message contains confidential information and may contain information that is legally privileged. If you have received this message by mistake, please immediately notify us and delete the original message. Thank you. ----

1 0