January 2007 - U-Boot

[U-Boot-Users] Backwards compatibility of "arch/powerpc" model in 2.6 kernel
by Johns Daniel 08 Jan '07

08 Jan '07

I understand that u-boot now has the facility of booting PPC-Linux kernels based on the "arch/powerpc" model -- at least for some processors/platforms. Once u-boot is set up to boot an "arch/powerpc"-based kernel, can the same bootloader image also boot an older "arch/ppc"-based kernel? Is the infrastructure available to boot older and newer 2.6 kernels from the same u-boot image? -- Johns

2 1

[U-Boot-Users] with a further concentration in IT.
by clarinet 05 Jan '07

05 Jan '07

1 0

[U-Boot-Users] do_bootm_linux OF_FLAT_TREE
by David Updegraff 05 Jan '07

05 Jan '07

Hi. in common/cmd_boot, around line 624: Looks like there is a small hole in the logic here if you happen to want to boot with a MULTI image with a ptr. and flat_tree. Since "boot multi_img_addr - of_tree_addr" ends up falling into the 'Skipping initrd category'. Which is annoying, as it looses the initrd that is inside the MULTI img. An obvious solution does not pop out at me. Maybe special-case check for MULTI within that special-case of FLAT_TREE and argv=='-' ? Please suggest better way. Thnx. -dbu.

3 4

[U-Boot-Users] Request to subscribe
by Nithya C 05 Jan '07

05 Jan '07

Hi, Please subscribe me. Thanks, Nithya. *********************** Aricent-Unclassified *********************** "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

1 0

[U-Boot-Users] Ethernet Initialization at boot
by galvatron12＠mac.com 04 Jan '07

04 Jan '07

Hello, I upgraded u-boot that was running on a mpc5200 board and noticed that in newer versions of u-boot (upgraded to 1.1.5) ethernet is initialized at boot time. In the previous version (u-boot 1.1.1) that was being used ethernet was initialized when a network command was called. The issue is that ethernet is not always used and boot time has increased 1-3 sec depending if a network cable is plugged in. Is there a setting that will force u-boot NOT to initialize ethernet at boot? I did some digging and sorry if I missed something obvious. Thanks Dave

1 0

[U-Boot-Users] Exposure to softwaredevelopment methodologies.
by Wilkinson 04 Jan '07

04 Jan '07

1 0

Re: [U-Boot-Users] your criticiz
by Laurena Crayton 04 Jan '07

04 Jan '07

Hi VALJUUM $ 1. 25 VJAAGRA $ 3. 30 AMBJEEN $ 2. 90 CJAALJS $ 3. 75 XAANXAX $1. 50 http://www.panfriedcookie.info _____ He and Ron set off along one of the winding paths through the rosebushes, but they had gone only a short way when they heard an unpleasantly familiar voice.

1 0

[U-Boot-Users] reg ISP 1561 integration with u-boot1.1.6
by mahendra varman 04 Jan '07

04 Jan '07

Hi, Iam Using Philips PCI based ISP 1561 OHCI usb controller in a PPC7410 processor board. For integrating the ISP 1561 into U-boot 1.1.6 wht config commands i have to add... (I need to make cmd_usb.c in u boot 1.1.6 working for my device ) ? Please Guide me.. Thanks and regards R.Mahendran

2 1

Re: [U-Boot-Users] Question about U-Boot in general and the AT91RM9200 in particular
by Sascha Erlacher 04 Jan '07

04 Jan '07

>thus in any way you must use a small (<12Kb) initial bootloader, which >in turn loads u-boot from dataflash or NOR flash in SDRAM. Hello Ivan, this is not correct. As Wolfgang points out you can boot directly from NOR flash. It depends on the BootModeSelect (BMS) pin state of the AT91RM9200. The datasheet states: "Depending on the BMS pin state at reset and as a function of the remap command, the memory mapped at address 0x0 is different. Before execution of the remap command the on-chip ROM (BMS = 1) or the 16-bit non-volatile memory connected to external chip select zero (BMS = 0) is mapped into Internal Memory Area 0." When setting BMS=0 the AT91RM9200 internal boot rom code is not executed. If the external (NOR) flash contains a valid U-Boot image it will be executed directly, and, in case it properly initializes an external SDRAM, will be able to relocate itself to SDRAM without going through internal SRAM. Best regards, Sascha

3 2

Re: [U-Boot-Users] 1.1.6 at91 based board dataflash copy panic.
by Ivan Kuten 04 Jan '07

04 Jan '07

Hello, > When CFG_NO_FLASH is defined the content of either flash.h or flash.c is > not included in the code, but dataflash support depends on that so I get > a compilation error. I have been playing around and it seems that it is > not possible to do a exclusive dataflash binary for u-boot, am I right? Yes, now there is quite a mess with dataflash only setup. I was able to do "exclusive dataflash binary for u-boot" by adding necessary defines from flash.h to dataflash.h (these changes where included in patch I sent): ------------------------------------------------ #define ERR_OK 0 #define ERR_TIMOUT 1 #define ERR_NOT_ERASED 2 #define ERR_PROTECTED 4 #define ERR_INVAL 8 #define ERR_ALIGN 16 #define ERR_UNKNOWN_FLASH_VENDOR 32 #define ERR_UNKNOWN_FLASH_TYPE 64 #define ERR_PROG_ERROR 128 /* * Protection Flags for flash_protect(): */ #define FLAG_PROTECT_SET 0x01 #define FLAG_PROTECT_CLEAR 0x02 ------------------------------------------------ and removing flash related commands such as CFG_CMD_FLASH CFG_CMD_IMLS from board config. It was just quick workaround. ------------------------------------ Best regards, Ivan Embedded Linux Engineer Promwad - www.promwad.com ------------------------------------ > Hi. > > I have applied that patch and the problem is solved. Anyway I have > needed to do some additional changes. I will try to explain. > > When CFG_NO_FLASH is defined the content of either flash.h or flash.c is > not included in the code, but dataflash support depends on that so I get > a compilation error. I have been playing around and it seems that it is > not possible to do a exclusive dataflash binary for u-boot, am I right? > > As code is written CFG_NO_FLASH means that there isn't _any kind_ of > flash. So I guess the define in your patch should be CFG_DATAFLASH_ONLY > or similar. > > Thanks for your help, > > Regards. > > -- > Gerardo Martínez Bernat > tlf: 91 351 11 20 > Barracuda Systems SL > C/ Luxemburgo nº4 > 28224 Madrid > > > > >

1 0