May 2009 - U-Boot

Re: [U-Boot] [PATCH 1/1] SMC911x driver fixed for NFS boot
by Josh Karabin 19 May '09

19 May '09

Manikandan Pillai wrote: > eth_halt() function in the smc911x drivers used to call the > smc911x_reset() function. eth_halt() used to be called after > tftp transfers. This used to put the ethernet chip in reset > while the linux boots up resulting in the ethernet driver > not coming up. NFS boot used to fail as a result. > > This patch calls smc911x_shutdown() instead of smc911x_reset(). > Some comments received has also been fixed. This patch fixes NFS boot in the case where the kernel is first loaded with tftpboot, as described. If the kernel is loaded using some other mechanism, like flash, the smc device is never initialized. At least in the case where there is no valid EEPROM connected to the smc device, NFS boot will fail. I'm not sure whether or not a loaded MAC address has anything to do with it, or if the kernel is expecting the smc device to be in a different state. Relying on tftpboot leaving the ethernet device in the right state doesn't seem right. Is there an existing clean way to deal with this, short of adding an initramfs to fix it up? I'll work on a patch if someone can suggest an approach that makes sense. Regards, - Josh

2 1

[U-Boot] how to use a function provided by u-boot in linux driver
by Kartheek N S 19 May '09

19 May '09

Hi All, I would like to use miiphy_read and miiphy_write functions provided by u-boot in the linux kernel driver. This is required for reading the link status of each of the phys associated with a switch. I added miiphy_read and miiphy_write to the exports.h and tried to use it in the kernel. But we get lots of multiple reference errors as some libraries will be there both in u-boot and linux kernel. Could I do something like a dll or lib for these functions and use them in the linux kernel driver ? Please guide me on this. Thanks, Kartheek N S -- View this message in context: http://www.nabble.com/how-to-use-a-function-provided-by-u-boot-in-linux-dri… Sent from the Uboot - Users mailing list archive at Nabble.com.

3 2

[U-Boot] Nand driver acts different in two different settings
by John Tobias 19 May '09

19 May '09

Hello all, I have tested two scenarios for writing/reading a data on my nand flash and it act's differently the nand driver on DM6446. 1st scenario: I booted my board with NFS, mounted my nand flash partition manually mount -t jffs2 /dev/mtdblock11 /mnt Then, I put data on nand partition by copying the following directories (/bin /lib): cp -daR /bin /lib /mnt I unmounted and remounted it and I didn't get any errors/warnings, even I try many times. 2nd scenario: I erased the said partition using flash_eraseall -j /dev/mtdblock11, write the .jffs2 image on flash using nandwrite. Then, I reboot my board to boot on nand. The first boot, I didn't get any errors/warnings. But, after the 2nd reboot, I got the following errors: mtd->read(0x7b74 bytes from 0x2a9848c) returned ECC error Empty flash at 0x02a9cea4 ends at 0x02a9d000 jffs2_scan_dirent_node(): Name CRC failed on node at 0x02a9d4b8: Read 0x87ca3075, calculated 0x9a7d2011 jffs2_scan_dirent_node(): Name CRC failed on node at 0x02a9e198: Read 0x1c93832c, calculated 0x1947e8af jffs2_scan_dirent_node(): Name CRC failed on node at 0x02a9e660: Read 0xb08c7dea, calculated 0x7855f7e2 jffs2_scan_dirent_node(): Name CRC failed on node at 0x02a9eb2c: Read 0x06400c2b, calculated 0x06400c29 jffs2_scan_dirent_node(): Name CRC failed on node at 0x02a9faec: Read 0xa532c097, calculated 0x6e6e1332 Why it acts so differently the two scenarios, since I'm using same driver?. Does booting on nand, the driver should behave differently?. Am I missing something or is there any special cases that I need to do on nand? Any help would be appreciated. Thanks, John

1 0

[U-Boot] [PATCH 0/3] TQM834x: configuration update
by Wolfgang Denk 19 May '09

19 May '09

The following 3 patches update the configuration for the TQM834x board: Wolfgang Denk (3): TQM834x: fix environment size; add redundant env. TQM834x: add FDT support TQM834x: use buffered writes to accelerate writing to flash Signed-off-by: Wolfgang Denk <wd(a)denx.de>

3 7

[U-Boot] uboot-2009.06-rc1: git: seeing extra files in git status report.
by Richard Retanubun 19 May '09

19 May '09

Hi Guys, I rebased to uboot-2009.06-rc1 some time ago and did a 'git status' today, in addition to the files I know I modified, I'm seeing some extra files: # On branch master # Untracked files: # (use "git add <file>..." to include in what will be committed) # tools/crc32.c # tools/env_embedded.c # tools/fdt.c # tools/fdt_ro.c # tools/fdt_rw.c # tools/fdt_strerror.c # tools/fdt_wip.c # tools/image.c # tools/libfdt_internal.h # tools/md5.c # tools/sha1.c # tools/zlib.h I'm wondering if other people are seeing this. If it is fixed for 2009.06-rc2, then sorry for arriving late to the party :) - Richard

2 1

[U-Boot] [PATCH v2] OMAP3: Introduce CONFIG option for power code
by Dirk Behme 19 May '09

19 May '09

Some OMAP3 boards need control for external power companion chips. Introduce a CONFIG option for this, to avoid Makefile changes for each board. Signed-off-by: Dirk Behme <dirk.behme(a)googlemail.com> --- Compile tested with ./MAKEALL ARM_CORTEX_A8, boot tested on OMAP3 based BeagleBoard. Note: This patch trys to fix the first comment of http://lists.denx.de/pipermail/u-boot/2009-April/051383.html Changes in v2: - Mention about which power companion chips we talk here This version v2 replaces all previous patches board/omap3/common/Makefile | 5 +---- doc/README.omap3 | 11 +++++++++++ include/configs/omap3_beagle.h | 1 + include/configs/omap3_overo.h | 1 + include/configs/omap3_pandora.h | 1 + include/configs/omap3_zoom1.h | 1 + 6 files changed, 16 insertions(+), 4 deletions(-) Index: u-boot-main/doc/README.omap3 =================================================================== --- u-boot-main.orig/doc/README.omap3 +++ u-boot-main/doc/README.omap3 @@ -77,6 +77,17 @@ For all other commands see help +Custom configs +============== + +CONFIG_OMAP3_POWER + +Some OMAP3 boards use external power companion chips to be configured. Enable +this CONFIG option in your board specific configuration file if your board +uses such a companion chip. E.g. TWL4030 or compatible TPS65950. + +This enables compilation of board/omap3/common/power.c. + Acknowledgements ================ Index: u-boot-main/board/omap3/common/Makefile =================================================================== --- u-boot-main.orig/board/omap3/common/Makefile +++ u-boot-main/board/omap3/common/Makefile @@ -29,10 +29,7 @@ endif LIB = $(obj)lib$(VENDOR).a -COBJS-$(CONFIG_OMAP3_BEAGLE) += power.o -COBJS-$(CONFIG_OMAP3_OVERO) += power.o -COBJS-$(CONFIG_OMAP3_PANDORA) += power.o -COBJS-$(CONFIG_OMAP3_ZOOM1) += power.o +COBJS-$(CONFIG_OMAP3_POWER) += power.o COBJS := $(COBJS-y) SRCS := $(COBJS:.o=.c) Index: u-boot-main/include/configs/omap3_beagle.h =================================================================== --- u-boot-main.orig/include/configs/omap3_beagle.h +++ u-boot-main/include/configs/omap3_beagle.h @@ -37,6 +37,7 @@ #define CONFIG_OMAP34XX 1 /* which is a 34XX */ #define CONFIG_OMAP3430 1 /* which is in a 3430 */ #define CONFIG_OMAP3_BEAGLE 1 /* working with BEAGLE */ +#define CONFIG_OMAP3_POWER 1 /* use power code, see README.omap3 */ #include <asm/arch/cpu.h> /* get chip and board defs */ #include <asm/arch/omap3.h> Index: u-boot-main/include/configs/omap3_overo.h =================================================================== --- u-boot-main.orig/include/configs/omap3_overo.h +++ u-boot-main/include/configs/omap3_overo.h @@ -29,6 +29,7 @@ #define CONFIG_OMAP34XX 1 /* which is a 34XX */ #define CONFIG_OMAP3430 1 /* which is in a 3430 */ #define CONFIG_OMAP3_OVERO 1 /* working with overo */ +#define CONFIG_OMAP3_POWER 1 /* use power code, see README.omap3 */ #include <asm/arch/cpu.h> /* get chip and board defs */ #include <asm/arch/omap3.h> Index: u-boot-main/include/configs/omap3_pandora.h =================================================================== --- u-boot-main.orig/include/configs/omap3_pandora.h +++ u-boot-main/include/configs/omap3_pandora.h @@ -32,6 +32,7 @@ #define CONFIG_OMAP34XX 1 /* which is a 34XX */ #define CONFIG_OMAP3430 1 /* which is in a 3430 */ #define CONFIG_OMAP3_PANDORA 1 /* working with pandora */ +#define CONFIG_OMAP3_POWER 1 /* use power code, see README.omap3 */ #include <asm/arch/cpu.h> /* get chip and board defs */ #include <asm/arch/omap3.h> Index: u-boot-main/include/configs/omap3_zoom1.h =================================================================== --- u-boot-main.orig/include/configs/omap3_zoom1.h +++ u-boot-main/include/configs/omap3_zoom1.h @@ -38,6 +38,7 @@ #define CONFIG_OMAP34XX 1 /* which is a 34XX */ #define CONFIG_OMAP3430 1 /* which is in a 3430 */ #define CONFIG_OMAP3_ZOOM1 1 /* working with Zoom MDK Rev1 */ +#define CONFIG_OMAP3_POWER 1 /* use power code, see README.omap3 */ #include <asm/arch/cpu.h> /* get chip and board defs */ #include <asm/arch/omap3.h>

2 2

[U-Boot] Not getting the Uboot prompt for sbc2410x using u-boot1.1.6
by vishal dahiwal 19 May '09

19 May '09

Hi All, I am new to uBoot. I am using the sbc2410x board. I successfully compiled the uboot-1.1.6 for this board. But after downloading the uboot.bin to the flash, i am not getting the uboot prompt on serial terminal. I am using the NAND flash. Do i have to make the changes for NAND flash and recompile the uboot?

2 1

Re: [U-Boot] uboot kernel rejects filesystem
by Detlev Zundel 19 May '09

19 May '09

Hi Bharat, [re-adding the mailing list as others may also profit from the discussion] > Thank you for the prompt reply. > > Unfortunately in linux tree, my board specific MTD partition info is not > preset. > > Is there any quick way round. Yep - thinking some more, I see two possible (quick) solutions. > M/M Layout: > 0xBF000000 : U-BOOT > 0xBF040000 : u_boot_config_area > 0xBF060000: vm_linux_image (with u-boot header : created by mkimage and LZMA) > 0xBF260000: root_fs area... Here I have flashed squashfs (without u-boot hdr) > Should I? > 0xBFFC0000: root_fs_data .. JFFS RW filesystem Just as a sidenote - are you able to use the JFFS (really JFFS, not JFFS2?) image? If so, then you _do_ have an MTD partition in Linux which you only need to tweak. > I do following on u-boot prompt > > board>bootm 0xBF060000 0xBF260000 This command only makes sense, if the image at 0xbf260000 is wrapped with mkimage. This is exactly the first solution that you can try, i.e. use mkimage with -T ramdisk to wrap your image and use the it with the two argument bootm version like you tried. Maybe you will need to specify "rootfstype=squashfs" on the command line also, you will have to check this. Having said this, if you are on an ARM platform, the above will very likely not work, so you will have to turn to the other solution I have in mind: > NO SUCCESS > again I try: > with modification to > include/configs/my_board.h file as > > #define MTDIDS_DEFAULT "nor0=app" > #define MTDPARTS_DEFAULT \ > "mtdparts=app:64k(u-boot),64k(boot_config),64k(board_config),2048k > (kernel),13696(rootfs),256kb(roots_data)" > #define CONFIG_BOOTARGS "root=/dev/mtdblock4 rootfstype=squashfs console= > ttyS1,115200" > > board>bootm 0xbf060000 The "mtdparts" variable in U-Boot has no automagic connection to the Linux kernel. It was designed however with connecting in Linux by using the following Linux config: drivers/mtd/Kconfig:106 "Device Drivers" config MTD_CMDLINE_PARTS bool "Command line partition table parsing" depends on MTD_PARTITIONS = "y" && MTD = "y" ---help--- Allow generic configuration of the MTD partition tables via the kernel command line. Multiple flash resources are supported for hardware where different kinds of flash memory are available. So if you have this support in your Linux configuration, you can pass the whole "mtdpart=.." through the linux commandline. A nasty part here is the beginning (you chose "app") of the configuration - as you will need to find what your kernel thinks the name of the flash chip is. > I think in second case it does make sense to pass mtdblock4 since my kernel > (;;) does not recognize it. > > Is there any work around like adding mtd table in linux kernel from uboot via > bootargs. Yes, like I stated above. Please try either method - if you are trying via MTD, be sure to include the contents of /proc/mtd and the relevant section of the Linux bootlog where the MTD layer registers in your next mail. Thanks Detlev PS: And please stop quoting the full text of the whole e-mail thread as this is considered to be impolite on mailing lists. -- Each language has its purpose, however humble. Each language expresses the Yin and Yang of software. Each language has its place within the Tao. But do not program in COBOL if you can avoid it. -- The Tao of Programming -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu(a)denx.de

3 7

[U-Boot] [PATCH] UBI: fix return code in ubi_volume_read
by Stefan Roese 19 May '09

19 May '09

From: Andreas Huber <andreas.huber(a)keymile.com> Return -ENODEV instead of 0 when trying to read from a non existing volume. Signed-off-by: Andreas Huber <andreas.huber(a)keymile.com> Signed-off-by: Stefan Roese <sr(a)denx.de> --- common/cmd_ubi.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/common/cmd_ubi.c b/common/cmd_ubi.c index 02a2e55..64a7307 100644 --- a/common/cmd_ubi.c +++ b/common/cmd_ubi.c @@ -327,7 +327,7 @@ static int ubi_volume_read(char *volume, char *buf, size_t size) } if (i == ubi->vtbl_slots) { printf("%s volume not found\n", volume); - return 0; + return -ENODEV; } printf("read %i bytes from volume %d to %x(buf address)\n", -- 1.6.2.5

1 0

[U-Boot] [RFC] API Licence
by Jean-Christophe PLAGNIOL-VILLARD 19 May '09

19 May '09

Hi, I'd like to known if it's possible to update the COPYING NOTE! This copyright does *not* cover the so-called "standalone" applications that use U-Boot services by means of the jump table provided by U-Boot exactly for this purpose - this is merely considered normal use of U-Boot, and does *not* fall under the heading of "derived work". to also include the API as a non derived work as the standalone? Best Regards, J.

4 5