February 2007 - U-Boot

[U-Boot-Users] [patch] drop special case for ppc hosts
by Mike Frysinger 06 Mar '07

06 Mar '07

for some reason there's a special case for ppc HOSTARCH's when setting up the default CROSS_COMPILE value ... this messes up my default env builds when going between my x86/amd64/ppc dev hosts ;) attached patch simply drops this special case handling -mike

2 6

[U-Boot-Users] [GIT PULL] AVR32 relocation
by Haavard Skinnemoen 02 Mar '07

02 Mar '07

Hi Wolfgang, Please pull from the 'for-upstream' branch of git://www.atmel.no/~hskinnemoen/u-boot/avr32 for-upstream to receive the following updates: Haavard Skinnemoen (6): AVR32: Split start_u_boot into board_init_f and board_init_r AVR32: Use avr32-linux- cross-compilation prefix by default AVR32: Build position-independent u-boot AVR32: Clean up memory-map.h for at32ap7000 AVR32: Resource management rewrite AVR32: Relocate u-boot to SDRAM Makefile | 2 +- avr32_config.mk | 2 +- board/atmel/atstk1000/atstk1000.c | 13 + board/atmel/atstk1000/flash.c | 2 +- board/atmel/atstk1000/u-boot.lds | 21 +- cpu/at32ap/Makefile | 2 +- cpu/at32ap/at32ap7000/Makefile | 2 +- cpu/at32ap/at32ap7000/devices.c | 448 ------------------------ cpu/at32ap/at32ap7000/gpio.c | 77 ++++ cpu/at32ap/at32ap7000/hebi.c | 38 -- cpu/at32ap/cpu.c | 64 +++- cpu/at32ap/device.c | 126 ------- cpu/at32ap/entry.S | 3 +- cpu/at32ap/exception.c | 7 +- cpu/at32ap/hsdramc.c | 43 +-- cpu/at32ap/hsdramc1.h | 8 +- cpu/at32ap/hsmc3.h | 8 +- cpu/at32ap/interrupts.c | 14 +- cpu/at32ap/pio.c | 90 ++---- cpu/at32ap/pio2.h | 8 +- cpu/at32ap/pm.c | 127 +------- cpu/at32ap/sm.h | 8 +- cpu/at32ap/start.S | 113 +++++-- drivers/atmel_usart.c | 48 ++- drivers/atmel_usart.h | 8 +- include/asm-avr32/arch-at32ap7000/clk.h | 58 +++ include/asm-avr32/arch-at32ap7000/gpio.h | 210 +++++++++++ include/asm-avr32/arch-at32ap7000/hmatrix2.h | 8 +- include/asm-avr32/arch-at32ap7000/memory-map.h | 81 +++-- include/asm-avr32/arch-at32ap7000/platform.h | 146 -------- include/asm-avr32/global_data.h | 3 +- include/configs/atstk1002.h | 17 +- lib_avr32/avr32_linux.c | 4 +- lib_avr32/board.c | 139 +++++++- 34 files changed, 796 insertions(+), 1152 deletions(-) delete mode 100644 cpu/at32ap/at32ap7000/devices.c create mode 100644 cpu/at32ap/at32ap7000/gpio.c delete mode 100644 cpu/at32ap/at32ap7000/hebi.c delete mode 100644 cpu/at32ap/device.c create mode 100644 include/asm-avr32/arch-at32ap7000/clk.h create mode 100644 include/asm-avr32/arch-at32ap7000/gpio.h delete mode 100644 include/asm-avr32/arch-at32ap7000/platform.h After this, the avr32 port will relocate itself to the end of DRAM like the ppc port does. Attached is a combined diff with all the changes, for your reference (too big to include inline.) Quite a large number of files were touched. This is mostly early init code which assumed the .data and .bss sections were available. Now, I would like to use the cfi driver with the AT49BV6416 chip on atstk1000 instead of the custom driver, but unfortunately, it doesn't work. I'll have a closer look at it later (I think it's a combination of the geometry reversal issue and a special non-intel unlocking algorithm.) Thanks, Haavard

4 4

[U-Boot-Users] Uncompression of image takes time.
by Adarsh Babu 01 Mar '07

01 Mar '07

Hi, I have an image which is 1.5MB in size after compression, thats is done for MCF5271. When i try to load this on a MCF5271 eval board using u-boot 1.2.0 it takes about 25 secs to just uncompress. I loaded a MCF5272 eval board with U- Boot 1.2.0 and then tried to start the same image(which was done for MCF5271). It was very fast. The checksum verification finish off in a second and uncompression in 10 seconds ! The clock configurations for both are provided below: M5272C3.h define CFG_HZ 1000 #define CFG_CLK 66000000 M5271EVB.h: define CFG_HZ 1000000 #define CFG_CLK 100000000 What should I do to get the image to uncompress faster in the MCF5271 EVB? Regards, Adarsh.

2 4

[U-Boot-Users] [PATCH] Support for csb535fs / i.MX21 LiteKit.
by Txema Lopez 01 Mar '07

01 Mar '07

Hi all, This patch, for the 1.2.0 version, adds support for the csb535fs board embedded in a csb935fs breakout board. The set is known as i.MX21 Litekit. The main features of the board are: csb535fs. - MC9328MX21 processor with an ARM926EJS core. - 8 Mbytes of NOR FLASH. - 64 MBytes of SDRAM. csb935fs - CS8900 10 MBit Ethernet controller. - RS232. - USB. - SD/MMC. - Compact Flash. - 3,5'' 240*320 QVGA TFT LCD. This patch only adds support for: - MC9328MX21 processor with an ARM926EJS core. - 8 Mbytes of NOR FLASH. - 64 MBytes of SDRAM. - CS8900 10 MBit Ethernet controller. - RS232. Signed-off-by: Jose Maria Lopez <tlopez(a)fagorautomation.es> CHANGELOG * Add support for the csb535fs board: Patch by Jose Maria Lopez, 27 February 2007

3 7

[U-Boot-Users] How to Port U-Boot to New Hardware Platform?
by Haifeng.Wu＠infineon.com 01 Mar '07

01 Mar '07

Dear All, I'm fairly new to U-Boot and not familiar with the architecture of U-Boot. But I think the directory hierarchy can tell me that U-Boot divides all the codes into board-related, CPU-related and common. I'm interested in porting U-Boot to our hardware platform, yet I don't know which code should be modified or added. Have some one done U-Boot porting for new hardware platform before? Would you like to share how to do it with me? I'm looking forward to hearing from you. B.R Wu Haifeng

3 4

[U-Boot-Users] JS28F256P33 intel flash. Can we use u-boot as bootloader?
by melinda develey 28 Feb '07

28 Feb '07

Hi all, we are developing a board with MPC875 and JS28F256P33 as flash. I wonder if it is possible to use u-boot-1.2.0 or if we have to resort to another boot loader. This is a CFI flash and thus no modification should be needed on u-boot. Is it true? Bye, Melinda. --------------------------------- Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates.

2 3

Re: [U-Boot-Users] mpc8641d and CONFIG_VERY_BIG_RAM (Chris Fester)
by Sebastien Douheret 28 Feb '07

28 Feb '07

Hi Chris, if you don't defined CONFIG_VERY_BIG_RAM with a big RAM size like 1GB, you may have another bug when you attempt to boot a Linux with a ramdisk. When you have big RAM, you must generally enable HIGHMEM support in Linux. If you try to boot an U-Boot image-multi (Kernel + ramdisk) without setting CONFIG_VERY_BIG_RAM, the ramdisk will be placed at the end of the memory (upper than 512MB). The issue is that ramdisk must not be in HIGHMEM area (Low Memory 0 to 512MB, High Memory 512MB to 1GB in my example) because of HIGHMEM is not functional when Kernel attempts to un-compress ramdisk during init phase. If you want to keep CONFIG_VERY_BIG_RAM un-define in U-Boot, you have another tip that force U-Boot to set ramdisk in Low Memory area. Set "initrd_high" environemental U-Boot parameter to no or to a valid Low memory address (see code of do_bootm_linux function in cmd_bootm.c file) Best regards, Sebastien D. Envoyez vos cartes de voeux depuis www.laposte.net Elles seront ensuite distribuées par le facteur : pratique et malin !

2 1

[U-Boot-Users] RFC: extended image formats
by Wolfgang Denk 28 Feb '07

28 Feb '07

Hello, I'm trying to figure out what could be done to add (at least in some cases) more information to U-Boot images. In this case, the existing CRC32 checksum is not sufficient; therequirement is to use some stronger hashes (md5 or sha1) to verify the correctness of the kernel and file system images. A similar thing happened not so long ago when we discussed how to add the OFT blob. Here some thoughts: * The original 64 byte header is tabu and cannot be changed to provide compatibility to existing versions. * A quick & dirty hack could use a multi-file image to add - for example - the SHA1 checksum as separate image in addition to the kernel (and eventually file system) image(s). Add an OFT blob, and the confusion is perfect. Seems we need a more structured approach. I would like to use this opportunity to collect ideas and suggestions for a more generalized solution that is flexible and extensible enough to handle not only the current , but also future requirements. At least some of them ;-) All input welcome... Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, HRB 165235 Munich, CEO: Wolfgang Denk Office: Kirchenstr. 5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de Don't have a battle of wits with an unarmed opponent.

4 4

[U-Boot-Users] [PATCH] Fix AT9RM9200 timer to avoid erroneous timeouts
by Anders Larsen 28 Feb '07

28 Feb '07

Hi, the timeout handling in e.g. drivers/cfi_flash.c assumes that get_timer() increments to 0xffffffff, then starts from 0 again. The implementation in cpu/arm920t/at91rm9200/interrupts.c acts differently - it only increments to 0xffffffff/TIMER_LOAD_VAL, thereby wrapping too early (every couple of minutes). Now and again this causes e.g. flash_status_check() to erroneously report a timeout. The patch below fixes this. Cheers Anders

2 1

[U-Boot-Users] mkimage for windows
by Koen De Clercq (TELETASK) 28 Feb '07

28 Feb '07

Hi, Does anyone know how to make mkimage for native windows (or for dos)? Or has someone a compiled version ready for use? (I want to use "mkimage.exe" in our production system to automatically generate images from scripts with the serial number.) Thanks, Koen

2 1