December 2003 - U-Boot

[U-Boot-Users] mkimage for DOS
by Dave Westwood 10 Jun '05

10 Jun '05

long shot really, but does anyone have a working executable mkimage for DOS or a dos window in windows (don't flame me for using windows !!)

2 1

[U-Boot-Users] Binary file cat
by Adam Bezanson 03 Aug '04

03 Aug '04

Hi, I have ported u-boot to my arm920t based system. I have a unique situation in that my processor requires a binary header to be placed In front of u-boot.bin before it is burnt into flash. If the processor doesn't find this header in flash it will not boot out of flash. Currently I have the header file as a separate file in the root directory and when I finish a new compile I have a shell script which Simply does a 'cat header.bin u-boot.bin > out.bin'. I'd like to get away from this and add it to the Makefiles so for my board I don't have to run this script every time. Before I go editing a top-level Makefile, I wanted to ask for advice on how I should go About doing this? Anything I can do in my board-specific directory would make me feel better. Suggestions? Thanks, Adam

3 6

[U-Boot-Users] loading linux in FADS860T board through u-boot-1.0.0
by RamanaYV 17 Mar '04

17 Mar '04

I was trying to load linux-2.4.4 in FADS860T board using u-boot-1.0.0. I have settted environment variables like ipaddr,serverip,ethaddr,bootargs bootfile and saved the environment. Then,i typed tftpboot to download image from server. Then,i typed bootm to start the booting process. System is stucked by showing "Uncompressing Kernel Image ... OK" sequence of these events r given below.can u please suggest, what i need to do to come out from this. Thank you. U-Boot 1.0.0 (Mar 17 2004 - 14:06:16) CPU: XPC86xxxZPnnD4 at 40 MHz: 4 kB I-Cache 4 kB D-Cache FEC present Board: FADS with db MPC821, MPC860 / MPC860SAR / MPC860T rev PILOT DRAM: (4 MB SDRAM) 4M 60ns DRAM: 8 MB FLASH: 2 MB In: serial Out: serial Err: serial Net: FEC ETHERNET =>printenv stdin=serial stdout=serial stderr=serial Environment size: 41/16380 bytes =>setenv ipaddr 192.168.1.115 =>setenv serverip 192.168.1.87 =>setenv ip 192.168.1.115 =>setenv ethaddr 00:30:bf:01:02:d0 =>setenv bootargs "root=/dev/nfs rw nfsroot=192.168.1.87:/opt/eldk/ppc8xx ip=192 .168.1.115:192.168.1.87:192.168.1.115:255.255.255.0:ppc::off" =>setenv bootfile "pImage_fads_fec" =>saveenv Saving Environment to Flash... Un-Protected 1 sectors Erasing Flash... . done Erased 1 sectors Writing to Flash... done Protected 1 sectors =>printenv stdin=serial stdout=serial stderr=serial ipaddr=192.168.1.115 serverip=192.168.1.87 ip=192.168.1.115 ethaddr=00:30:bf:01:02:d0 bootargs="root=/dev/nfs rw nfsroot=192.168.1.87:/opt/eldk/ppc8xx ip=192.168 1.11 5:192.168.1.87:192.168.1.115:255.255.255.0:ppc::off" bootfile="pImage_fads_fec" Environment size: 287/16380 bytes =>tftpboot TFTP from server 192.168.1.87; our IP address is 192.168.1.115 Filename 'pImage_fads_fec'. Load address: 0x100000 Loading: T invalid RARP header #####################################################TX timeout ############ ####################### done Bytes transferred = 448321 (6d741 hex) =>bootm ## Booting image at 00100000 . Image Name: Linux-2.4.4 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 448257 Bytes = 437.8 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK

3 2

[U-Boot-Users] FADS860T board
by RamanaYV 17 Mar '04

17 Mar '04

I was trying to load linux-2.4.4 in FADS860T board using u-boot-1.0.0. i am getting the followin symptom, can anyone suggest to come out from this problem.. U-Boot 1.0.0 (Mar 17 2004 - 14:06:16) CPU: XPC86xxxZPnnD4 at 40 MHz: 4 kB I-Cache 4 kB D-Cache FEC present Board: FADS with db MPC821, MPC860 / MPC860SAR / MPC860T rev PILOT DRAM: (4 MB SDRAM) 4M 60ns DRAM: 8 MB FLASH: 2 MB In: serial Out: serial Err: serial Net: FEC ETHERNET =>printenv stdin=serial stdout=serial stderr=serial Environment size: 41/16380 bytes =>setenv ipaddr 192.168.1.115 =>setenv serverip 192.168.1.87 =>setenv ip 192.168.1.115 =>setenv ethaddr 00:30:bf:01:02:d0 =>setenv bootargs "root=/dev/nfs rw nfsroot=192.168.1.87:/opt/eldk/ppc8xx ip=192 .168.1.115:192.168.1.87:192.168.1.115:255.255.255.0:ppc::off" =>setenv bootfile "pImage_fads_fec" =>saveenv Saving Environment to Flash... Un-Protected 1 sectors Erasing Flash... . done Erased 1 sectors Writing to Flash... done Protected 1 sectors =>printenv stdin=serial stdout=serial stderr=serial ipaddr=192.168.1.115 serverip=192.168.1.87 ip=192.168.1.115 ethaddr=00:30:bf:01:02:d0 bootargs="root=/dev/nfs rw nfsroot=192.168.1.87:/opt/eldk/ppc8xx ip=192.168.1.11 5:192.168.1.87:192.168.1.115:255.255.255.0:ppc::off" bootfile="pImage_fads_fec" Environment size: 287/16380 bytes =>tftpboot TFTP from server 192.168.1.87; our IP address is 192.168.1.115 Filename 'pImage_fads_fec'. Load address: 0x100000 Loading: T invalid RARP header #####################################################TX timeout ############ ####################### done Bytes transferred = 448321 (6d741 hex) =>bootm ## Booting image at 00100000 ... Image Name: Linux-2.4.4 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 448257 Bytes = 437.8 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Thanks to all.

2 1

[U-Boot-Users] [PATCH] PCMCIA card support for PXA/WEPEP250
by Leon KUKOVEC 02 Mar '04

02 Mar '04

Hi everybody, New Feature: * support for PCMCIA card on WEPEP250 board. Notice: The default configuration of WEPEP250 board does not include PCMCIA support. To include PCMCIA and IDE support the WEPEP250 configuration has to be adjusted. Note that I have changed TEXT_ADDRESS for WEPEP250 board to start at 0xA1000000. If my understanding is correct, Linux kernel will use the memory that was occupied by U-Boot code while running in RAM. Tweaking can be done later. In case of any issues, let me know. -- Best Regards, Leon.

3 4

[U-Boot-Users] [PATCH] fix the ARM memory layout
by Anders Larsen 08 Feb '04

08 Feb '04

Hi, here's a fresh version of my rather intrusive patch from the 17.th sept. to rearrange the ARM memory layout to bring it in line with the README. This has the positive side-effect of actually allow U-Boot to run on PXA- and IXP-based targets; the current implementation sets up the heap using bogus addresses causing u-boot to crash (this even applies to the recently added board "ixdp425"). This patch doesn't go all the way, though, since doing away with the board-specific setting of TEXT_BASE would require the code to be position-independent, which at least the cpu initialization code in cpu/*/start.S is _not_. CHANGELOG: Bring the ARM memory layout in line with the documentation. Cheers Anders

5 11

[U-Boot-Users] PATCH: include/linux/byteorder/swab.h
by Leon Kukovec 07 Feb '04

07 Feb '04

Fixes: o the optimization can now be disabled (config.mk: OPTFLAGS = -O0) (makes debugging easier) Change: o changed extern __inline__ into static __inline__ in include/linux/byteorder/swab.h COMPILER: ELDK x86 2.1.0 (RedHat 9.0) BUILD FOR: ppc mips arm BUILD STATUS: ERIC FAILED ixdp425 FAILED lubbock FAILED MPC8540ADS FAILED MPC8560ADS FAILED NOTE: the same builds fail for U-Boot HEAD branch. -- Best Regards, Leon.

2 3

[U-Boot-Users] [patch] CONFIG_SILENT_CONSOLE
by Wolter Kamphuis 06 Feb '04

06 Feb '04

Hi all, I've changed the implementation of the CONFIG_SILENT_CONSOLE flag a bit. Instead of checking for the CONFIG_SILENT_CONSOLE flag in lib_*/board.c I've moved the code to common/console.c. Now all (and future) architectures and boards can use the CONFIG_SILENT_CONSOLE flag. The patch is against the current CVS. Wolter Kamphuis MuLogic B.V. diff -purN u-boot/common/console.c u-boot.silent/common/console.c --- u-boot/common/console.c 2003-10-16 01:53:50.000000000 +0200 +++ u-boot.silent/common/console.c 2003-12-15 10:37:49.000000000 +0100 @@ -191,6 +191,11 @@ void putc (const char c) { DECLARE_GLOBAL_DATA_PTR; +#ifdef CONFIG_SILENT_CONSOLE + if (gd->flags & GD_FLG_SILENT) + return(0); +#endif + if (gd->flags & GD_FLG_DEVINIT) { /* Send to the standard output */ fputc (stdout, c); @@ -204,6 +209,11 @@ void puts (const char *s) { DECLARE_GLOBAL_DATA_PTR; +#ifdef CONFIG_SILENT_CONSOLE + if (gd->flags & GD_FLG_SILENT) + return; +#endif + if (gd->flags & GD_FLG_DEVINIT) { /* Send to the standard output */ fputs (stdout, s); diff -purN u-boot/doc/README.silent u-boot.silent/doc/README.silent --- u-boot/doc/README.silent 2003-10-10 12:05:42.000000000 +0200 +++ u-boot.silent/doc/README.silent 2003-12-15 10:54:52.000000000 +0100 @@ -9,8 +9,6 @@ The following actions are taken if "sile - Until the console devices have been initialized, output has to be suppressed by testing for the flag "GD_FLG_SILENT" in "gd->flags". - Currently only the messages for the TRAB board are handled in this - way. - When the console devices have been initialized, "stdout" and "stderr" are set to "nulldev", so subsequent messages are diff -purN u-boot/lib_arm/board.c u-boot.silent/lib_arm/board.c --- u-boot/lib_arm/board.c 2003-12-07 01:46:27.000000000 +0100 +++ u-boot.silent/lib_arm/board.c 2003-12-15 10:39:02.000000000 +0100 @@ -115,13 +115,6 @@ static int init_baudrate (void) static int display_banner (void) { -#ifdef CONFIG_SILENT_CONSOLE - DECLARE_GLOBAL_DATA_PTR; - - if (gd->flags & GD_FLG_SILENT) - return (0); -#endif - printf ("\n\n%s\n\n", version_string); printf ("U-Boot code: %08lX -> %08lX BSS: -> %08lX\n", _armboot_start, _armboot_end_data, _armboot_end); @@ -148,11 +141,6 @@ static int display_dram_config (void) DECLARE_GLOBAL_DATA_PTR; int i; -#ifdef CONFIG_SILENT_CONSOLE - if (gd->flags & GD_FLG_SILENT) - return (0); -#endif - puts ("RAM Configuration:\n"); for(i=0; i<CONFIG_NR_DRAM_BANKS; i++) { @@ -165,12 +153,6 @@ static int display_dram_config (void) static void display_flash_config (ulong size) { -#ifdef CONFIG_SILENT_CONSOLE - DECLARE_GLOBAL_DATA_PTR; - - if (gd->flags & GD_FLG_SILENT) - return; -#endif puts ("Flash: "); print_size (size, "\n"); }

2 1

[U-Boot-Users] Hang after relocating u-boot code...
by SAM SONG 09 Jan '04

09 Jan '04

Hi, The monitor port can work on my custom board but u-boot hang or crashes after relocation.I read the DULG FAQ about the answer.I,however,want to make sure about the fact why the same SDRAM init code does work on RPXlite but in vain on my custom board for the SDRAM hardware design are the same with these two boards. I am sure that my UPMA RAM WORD is OK because of successful relocation.When I traced the code using BDI2000 and found that the code often went wrong after start.S:574. /* * We are done. Do not return, instead branch to second part of board * initialization, now running from RAM. */ 572 addi r0, r10, in_ram - _start + EXC_OFF_SYS_RESET 573 mtlr r0 574 blr BDI>ci - TARGET: target has entered debug mode BDI>i Target state : debug mode Debug entry cause : entering check stop state Current PC : 0x00000200 Meanwhile,I checked the signal of SDRAM chip(MT48LC16M16)by WAVEFORM and noticed that A[20-29] & D[0-31] on RPXlite board have 1KHz plus whereas zero level on my board after reset. Is this realated with my hardware design or just software adjustment is enough? Any hints is welcome! Thanks in advance and Happy New Year!!! SAM SONG __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 7

RE: [U-Boot-Users] OMAP1510 Innovator kit booting questions
by Woodruff, Richard 06 Jan '04

06 Jan '04

In cpu/arm925/interrupts.c. Remove the hard coded delay loops which are wrapped with INNOVATOROMAP1510. This enables the code which will use ARM timers (which are driven by the 12MHz reference / by a factor in the header file). This should provide constant time irrespective to your cpu dpll speed. This is what I use in (though not with innovator). This will fix some problems, and it "might" fix your problem. It will probably make your boot speed correct, but it still sounds like some clock is not set properly. I have a bit more fixed up dpll setup code which I will get around to sending in sometime. Regards, Richard W. -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Grigory A. Sent: Friday, December 26, 2003 7:06 PM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] OMAP1510 Innovator kit booting questions 2. Next - I am using autoboot mode with 3-5 seconds of bootdelay. But 1 u-boot seconds is approximately 15-20 of real seconds. Yes - this is board specific - maybe some clock setup missed - (by me?) or PLL settings - so could someone help me with it? Only that I have changed - I've switched to use UART2 for serial communication - it is working well - I don't think that it has got any influence to board speed. Thanks for answers. -- Best regards, Grigory mailto:Ryhor@tut.by ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1