June 2004 - U-Boot

[U-Boot-Users] MPC8272ADS & U-Boot 1.1.1 (Second Try)
by Juergen Selent 23 Jun '04

23 Jun '04

Hi, its the second try without base64, sorry for that (I hate Outlook grrr). Currently I am using U-Boot 1.0.0/Linux 2.4.22 with an MPC8272ADS-Board without any problems. Now I wanna upgrade to U-Boot Version 1.1.1 and I run into the following problem: U-Boot starts up without any problems, it loads the linux kernel image (uImage) via TFTP. The checksum of the imgae is correct, uncompressing works fine, but than the kernel does not start up. All I get is a immediate reboot into U-Boot. Cause is a CHECKSTOP EXCEPTION. Its the same kernel image which works great under U-Boot 1.0.0. Any ideas? Here is the log: U-Boot 1.1.1 (Jun 23 2004 - 13:24:00) MPC8272 Reset Status: External Soft, External Hard MPC8272 Clock Configuration - Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq 25-75 , Core Freq 100-300 - dfbrg 1, corecnf 0x0a, busdf 3, cpmdf 1, plldf 0, pllmf 3 - vco_out 400000000, scc_clk 100000000, brg_clk 25000000 - cpu_clk 400000000, cpm_clk 200000000, bus_clk 100000000 - pci_clk 66666666 CPU: MPC8272 (HiP7 Rev 13, Mask 0.0 0K50M) at 400 MHz Board: Motorola MPC8272ADS DRAM: 64 MB FLASH: 8 MB In: serial Out: serial Err: serial Net: FCC1 ETHERNET Hit any key to stop autoboot: 3-2-1-0 Using FCC1 ETHERNET device TFTP from server 10.0.0.136; our IP address is 10.0.0.201 Filename 'uImage'. Load address: 0x400000 Loading: ################################################################# ################################################################# ######### done Bytes transferred = 709133 (ad20d hex) ## Booting image at 00400000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 709069 Bytes = 692.5 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK --- NOW A RESET OCCURS --- U-Boot 1.1.1 (Jun 23 2004 - 13:24:00) MPC8272 Reset Status: Check Stop, External Soft, External Hard Thanx -- Juergen Selent Elmeg Communcation Systems GmbH Development Office Berlin Alt-Moabit 96c 10559 Berlin

1 0

[U-Boot-Users] MPC8272ADS & U-Boot 1.1.1
by "Selent, Jürgen" 23 Jun '04

23 Jun '04

Hi, until today I am using U-Boot 1.0.0/Linux 2.4.22 with an MPC8272ADS-Board without problems. Today I thought its time to update to U-Boot 1.1.1. Now I have a problem: U-Boot starts up without any problems, it loads the linux kernel image (pImage) via TFTP. The checksum of the imgae is correct, uncompressing works fine, but the kernel does not start up. All I get is a immediate reboot into U-Boot. Its the same kernel image which works great under U-Boot 1.0.0. Any ideas? Regards -- Juergen Selent Elmeg Communcation Systems GmbH Entwicklungsbüro Berlin Alt-Moabit 96c 10559 Berlin Email j.se??nt[at]el?eg.de

1 0

[U-Boot-Users] How can I port u-boot to a custom PPC board?
by Yusuf Ibrahim Özkök 23 Jun '04

23 Jun '04

Hi, I want to use u-boot on a custom designed ppc (MPC8245) board. Is it possible(by means of GPL license of u-boot)? if so, is there any detailed documentation telling about how to port u-boot to new boards. Or can you direct me to any other sources to achieve this work. Regards, yusuf. ################################################################################################ Dikkat: Bu elektronik posta mesaji kisisel ve ozeldir. Eger size gonderilmediyse lutfen gondericiyi bilgilendirip mesaji siliniz. Firmamiza gelen ve giden mesajlar virus taramasindan gecirilmekte, guvenlik nedeni ile kontrol edilerek saklanmaktadir. Mesajdaki gorusler ve bakis acisi gondericiye ait olup Aselsan A.S. resmi gorusu olmak zorunda degildir. ################################################################################################ Attention: This e-mail message is privileged and confidential. If you are not the intended recipient please delete the message and notify the sender. E-mails to and from the company are monitored for operational reasons and in accordance with lawful business practices. Any views or opinions presented are solely those of the author and do not necessarily represent the views of the company. ################################################################################################

2 1

[U-Boot-Users] [PATCH] Motorola i.MX support (1/2)
by Sascha Hauer 23 Jun '04

23 Jun '04

Hello List, These patches add Motorola MM1 support for U-boot. The patches are against U-boot-1.1.1 and add support for two custom boards and the Davicom dm9000 ethernet chip. All comments and feedback welcome, Sascha Hauer patch-u-boot-1.1.1-imx.bz2 - Motorola MX1 support patch-u-boot-1.1.1-mx1fs2.bz2 - mx1fs2 board support patch-u-boot-1.1.1-scb9328.bz2 - scb9328 board support patch-u-boot-1.1.1-dm9000.bz2 - dm9000 network driver support (used in scb9328)

6 17

[U-Boot-Users] about the include/linux directory
by gold ares 23 Jun '04

23 Jun '04

hello everyone who can tell me what's the role of the `include/linux' directory and why we need the directory?? why don't we put those files in `linux' dir into other directory like its parent dir -- 'include'. thanks a lot -- _____________________________________________________________ Web-based SMS services available at http://www.operamail.com. >From your mailbox to local or overseas cell phones. Powered by Outblaze

2 1

[U-Boot-Users] A strange problem in lib_ppc/board.c
by Frank Young 23 Jun '04

23 Jun '04

Hi, I am trying to install u-boot on my Walnut with PPC405. After I load the program, the u-boot hangs without any output on the serial console. I located that the program is stopped at the point of where board_init_f() is called. More specifically, the u-boot stop at for (init_fnc_ptr = init_sequence; *init_fnc_ptr; ++init_fnc_ptr) { if ((*init_fnc_ptr) () != 0) { hang (); } } None of the function init_fnc_ptr pointing to has been called successfully. For test purpose, I wrote the following codes and put them in board_init_f(): 409 char s[10] = {'h','e','l','l','o'}; 410 if (s[0] == 'h') { 411 s_putc('y'); 412 } else { 413 s_putc('n'); 414 } s_putc() is a function I created to send one char to UART. It has been tested working fine. But the u-boot hangs at line 410. Then I changed the test code to the following: 409 // char s[10] = {'h','e','l','l','o'}; 410 char s[10]; 411 s[0] = 'h'; 412 s[1] = 'e'; 413 s[2] = 'l'; 414 s[3] = 'l'; 415 s[4] = 'o'; 416 if (s[0] == 'h') { 417 s_putc('y'); 418 } else { 419 s_putc('n'); 420 } Then the UART showed a 'y' on the screen, which is what I expected. So from the tests I did above, seems some thing wrong with the pointer. It also explains the reason why init_fnc_ptr didn't work well. But I couldn't figure out what is wrong. I would appreciate if any one can give me some clues. Thanks! Frank _________________________________________________________________ Get fast, reliable Internet access with MSN 9 Dial-up now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/

1 0

[U-Boot-Users] Problem compiling examples
by Andy Hawkins 22 Jun '04

22 Jun '04

Hi all, Typical...I tried to recreate the problem with compiling the standalone examples and couldn't. However, as soon as I sent the previous e-mail, I realised I had other source trees around. I tried compiling one of those, and got this error (apologies for the horrible formatting, it's a very long compile command). ppc_405-gcc -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE=0xFFFC0000 -I/usr/src/u-boot-evo/u-boot-1.1.0-orig/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/montavista/pro/devkit/ppc/405/bin/../lib/gcc-lib/powerpc-hardhat-linux/3.3.1/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29 -mstring -Wa,-m405 -mcpu=405 -msoft-float -Wall -Wstrict-prototypes -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE=0xFFFC0000 -I/usr/src/u-boot-evo/u-boot-1.1.0-orig/include -fno-builtin -ffreestanding -nostdinc -isystem /opt/montavista/pro/devkit/ppc/405/bin/../lib/gcc-lib/powerpc-hardhat-linux/3.3.1/include -pipe -DCONFIG_PPC -D__powerpc__ -DCONFIG_4xx -ffixed-r2 -ffixed-r29 -mstring -Wa,-m405 -mcpu=405 -msoft-float -I.. -Bstatic -T /usr/src/u-boot-evo/u-boot-1.1.0-orig/board/dave/PPChameleonEVB/u-boot.lds -Ttext 0xFFFC0000 -n hello_world.c -o hello_world ppc_405-gcc: 0xFFFC0000: No such file or directory /opt/montavista/pro/devkit/ppc/405/bin/../lib/gcc-lib/powerpc-hardhat-linux/3.3.1/../../../../powerpc-hardhat-linux/bin/as: option `-n' is ambiguous make[1]: *** [hello_world] Error 2 This is compiling using MontaVista Pro 3.1, U-Boot 1.1.0, configured for a PPChameleonEVB board using make PPChameleonEVB_config Hope this helps in tracking down the problem...not sure the other tree (that I've modified to provide support for our custom hardware) compiles Ok... Andy

1 0

[U-Boot-Users] Uboot compiling problem...
by Stephan Magnier 22 Jun '04

22 Jun '04

Hello there, I have some problems with the generation of the U-boot I am using the following version : Uboot is 1.0.2 ELDK 3.0 >[root@linux-three u-boot]# make TQM823L_config >rm -f include/config.h include/config.mk >Configuring for TQM823L board... Seems to be OK "Make all" gives me this : >make[1]: Entering directory `/opt/u-boot/examples' >ppc_8xx-gcc -g -Os -fPIC -ffixed-r14 -meabi -D__KERNEL__ -DTEXT_BASE= -I / >opt/u-boot/include -fno-builtin -ffreestanding -nostdinc -isystem >/opt/ELDK/usr/bin/../lib/gcc-lib/ppc-linux/3.2.2/include -pipe -DCONFIG_PP C > -D__powerpc__ -DCONFIG_8xx -ffixed-r2 -ffixed-r29 -mstring -mcpu=860 -msof t >-float -Wall -Wstrict-prototypes -g -Os -fPIC -ffixed-r14 -meabi -D__KER N >EL__ -DTEXT_BASE= -I/opt/u-boot/include -fno-builtin -ffreestanding -nostdi n >c -isystem >opt/ELDK/usr/bin/../lib/gcc-lib/ppc-linux/3.2.2/include -pipe -DCONFIG_PPC >-D__powerpc__ -DCONFIG_8xx -ffixed-r2 -ffixed-r29 -mstring -mcpu=860 -msoft - >float -I.. -Bstatic -T /opt/u-boot/board/tqm8xx/u-boot.lds -Ttext -n >hello_world.c > -o hello_world >/opt/ELDK/usr/bin/../lib/gcc-lib/ppc-linux/3.2.2/../../../../ppc-linux/bin/ a >s: option `-n' is ambiguous >make[1]: *** [hello_world] Error 2 >make[1]: Leaving directory `/opt/u-boot/examples' >make: *** [examples] Error 2 >[root@linux-three u-boot]# I think this must be an older (much older) version of U-Boot. It cannot be compiled with the newer versions of the GNU toolchain as included with ELDK-3.0. [WD] Please make sure to use a more recent version of U-Boot, for example the one that is included with the ELDK (see for example directory /opt/eldk/ppc_8xx/usr/src/u-boot-1.0.2). My installation of U-boot-1.0.2 (downloaded separtely from the "Leo" website) is placed at the same level of the ELDK... but I don't think that could be a real problem.... isn't it ? (path seems to be also recognised? ) But could you please tell me why, the make file is referring to the Hello_world file ?? AFAIK, there is no "hello_world.c" file installed by default with the ELDK ??? regards, Stephane

3 4

[U-Boot-Users] u-boot's func -- `strcpy'
by gold ares 22 Jun '04

22 Jun '04

hello,everyone! I'am ares. I have read the u-boot's source codes for some days? I wonder why u-boot have implemented some codes like `strcpy' which have been included by the glibc. and please tell me if the u-boot write all codes that it needs and don't use any glibc's func. 2004-06-22 -- _____________________________________________________________ Web-based SMS services available at http://www.operamail.com. >From your mailbox to local or overseas cell phones. Powered by Outblaze

3 2

RE: [U-Boot-Users] u-boot on top of another bootloader
by Seingier François-Xavier 22 Jun '04

22 Jun '04

> Can u-boot run on top of another bootloader? The board I'm > working on has a > proprietary boot loader. I cannot totally abandon this > bootloader because > the vendor is unwilling to disclose some critical details of > the board. So > I'm thinking of putting u-boot on top of it. Is this idea feasible? reminds me something ;) (see post a few weeks ago...) > > The original boot loader is at 0xFFF00000. One thing I need > to do is to > move the u-boot location to somewhere else. AFAIK u-boot > usually locates at > 0xFFF00000. What feature of a board decides the address of the first > instruction? > I did the following: The manufacturer provided a srec version of its bootloader and a flash utility. Using a debugger, I made sure I could put back the original bootloader if anything went wrong with u-boot. After this I gathered as much information about the board as I could by: - using the debugger and writing down the values of initialized registers (done by the original bootloader) - using some "utilities" provided by the original bootloader Then I decided where to flash u-boot. On a ppc cpu, the processor first jumps at address 0xfffffffc. At this very address there is a branch instruction to a bootloader. For example, with the original bootloader this could be 0xfff00000. You could replace this value and the position of u-boot in flash by using the config.mk file in the board/$BOARD directory. This will place the .text section at the defined position and replace the branch address from the reset vector to the correct one. hope this helps, regards François-Xavier SEINGIER

2 1