October 2003 - U-Boot

[U-Boot-Users] PQ2VADS (8270) & BDI2000 - III
by Matias Sundman (AL/EAB) 21 Oct '03

21 Oct '03

Hi, I tried to flash the u-boot.bin file to 0xff900000 and 0xff800000 but I cant get anything on the console ... am I missing some steps? I made the following steps: 1. Edited the MPC8260ADS.h file in order to set CFG_PQ2FADS as the target board ... 2. make MPC8260ADS_config 3. make clean 4. make all 5. Flashed area 0xff900000 and restarted the board No output on the console ... 6. Flashed area 0xff800000 and restarted the board No output on the console ... Any ideas? Cheers // Matias =========================================================================== -----Original Message----- From: Matias Sundman (AL/EAB) Sent: den 21 oktober 2003 10:24 To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] PQ2VADS (8270) & BDI2000 - II Hello again, I have now received a BDI2000 from Abatron. There is a configuration file included with the package for my target board, which is - PQ2FADS. U-boot is compiled with the CFG_PQ2FADS define in the MPC8260ADS.h file. Can I use the configuration file as is and burn u-boot.bin to the flash, and after a restart of the board I get a working u-boot automagically? Regards // Matias ------------------------------------------------------------------------- -----Original Message----- From: Chris Simmonds [mailto:chris@2net.co.uk] Sent: den 6 oktober 2003 10:45 To: Matias Sundman (TB/EAB) Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] PQ2VADS (8270) & BDI2000 Hi, I am using BDI2000 with an 8270 right now and it works fine. Its just the standard package for ppc 6xx/7xx/82xx/7400/7410. I used the configuration file for the vads8260 and fixed it up for my board (a custom unit). I don't have a config for the pq2vads board I'm afraid. Chris. Matias Sundman (TB/EAB) wrote: >Comrades, >I have compiled uboot for the PQ2VADS Motorola >evaluation board and tried to flash it with a >JTAG probe from GreenHills. Unfortunately their >probe does not support the 8270 architecture today. > >Does BDI2000 support the ppc8270 JTAG chain architecture? > >If so , does someone have a configuration file for the >PQ2VADS Motorola evaluation board? > >Best Regards // Matias > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >U-Boot-Users mailing list >U-Boot-Users(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/u-boot-users > -- Chris Simmonds 2net Limited chris(a)2net.co.uk http://www.2net.co.uk/ Tel: +44 (0)1962 869003 Fax: +44 (0)870 056 7556 "If it's not connected, it's not effective"(tm) ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] I have a mistake on making u-boot-0.4.0
by Dannel_Zhang 21 Oct '03

21 Oct '03

Hi all, I am working intel xscale pxa255 based board. I have a mistake on makeing u-boot-0.4.0,The erro information message as follow. who would please give me some ideas please? pt/u-boot/tools' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/tools' make[1]: Entering directory `/opt/u-boot/lib_generic' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/lib_generic' make[1]: Entering directory `/opt/u-boot/lib_arm' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/lib_arm' make[1]: Entering directory `/opt/u-boot/cpu/pxa' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/cpu/pxa' make[1]: Entering directory `/opt/u-boot/board/lubbock' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/board/lubbock' make[1]: Entering directory `/opt/u-boot/common' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/common' make[1]: Entering directory `/opt/u-boot/disk' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/disk' make[1]: Entering directory `/opt/u-boot/fs' make[2]: Entering directory `/opt/u-boot/fs/jffs2' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/jffs2' make[2]: Entering directory `/opt/u-boot/fs/fdos' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/fdos' make[2]: Entering directory `/opt/u-boot/fs/fat' make[2]: `.depend' is up to date. make[2]: Leaving directory `/opt/u-boot/fs/fat' make[1]: Leaving directory `/opt/u-boot/fs' make[1]: Entering directory `/opt/u-boot/net' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/net' make[1]: Entering directory `/opt/u-boot/rtc' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/rtc' make[1]: Entering directory `/opt/u-boot/dtt' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/dtt' make[1]: Entering directory `/opt/u-boot/drivers' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/drivers' make[1]: Entering directory `/opt/u-boot/post' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/post' make[1]: Entering directory `/opt/u-boot/post/cpu' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/post/cpu' make[1]: Entering directory `/opt/u-boot/examples' make[1]: `.depend' is up to date. make[1]: Leaving directory `/opt/u-boot/examples' make[1]: Entering directory `/opt/u-boot/tools' gcc -g -Wall -pedantic -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -O -c envcrc.c gcc -g -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -c environment.c gcc -Wall -pedantic -I../include -I.. -DTEXT_BASE=0xa3000000 -DUSE_HOSTCC -O -o envcrc envcrc.o crc32.o environment.o make[2]: Entering directory `/opt/u-boot/tools/gdb' make[2]: Nothing to be done for `all'. make[2]: Leaving directory `/opt/u-boot/tools/gdb' make[1]: Leaving directory `/opt/u-boot/tools' make[1]: Entering directory `/opt/u-boot/lib_generic' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o crc32.o crc32.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o display_options.o display_options.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o vsprintf.o vsprintf.c arm-linux-ar crv libgeneric.a crc32.o ctype.o display_options.o ldiv.o string.o vsprintf.o zlib.o r - crc32.o r - ctype.o r - display_options.o r - ldiv.o r - string.o r - vsprintf.o r - zlib.o make[1]: Leaving directory `/opt/u-boot/lib_generic' make[1]: Entering directory `/opt/u-boot/lib_arm' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o armlinux.o armlinux.c arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-loa d-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000000 -I/opt/u-boot/include - fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib/gcc-lib/arm-linux/3.2.1/in clude -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o board.o board.c arm-linux-ar crv libarm.a _udivsi3.o _umodsi3.o armlinux.o board.o cache.o div0. o r - _udivsi3.o r - _umodsi3.o r - armlinux.o r - board.o r - cache.o r - div0.o make[1]: Leaving directory `/opt/u-boot/lib_arm' make[1]: Entering directory `/opt/u-boot/cpu/pxa' arm-linux-gcc -Wa,-gstabs -D__ASSEMBLY__ -g -Os -fno-strict-aliasing -fno-co mmon -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa3000 000 -I/opt/u-boot/include -fno-builtin -nostdinc -isystem /opt/xscale/bin/../lib /gcc-lib/arm-linux/3.2.1/include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march= armv4 -mtune=strongarm1100 -c -o start.o /opt/u-boot/cpu/pxa/start.S /opt/u-boot/cpu/pxa/start.S: Assembler messages: /opt/u-boot/cpu/pxa/start.S:145: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:146: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:160: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:167: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:169: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:381: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:382: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:387: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:388: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:393: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:394: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:399: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:400: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:405: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:406: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:429: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:430: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:435: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up /opt/u-boot/cpu/pxa/start.S:436: Error: internal_relocation (type: OFFSET_IMM) n ot fixed up make[1]: *** [start.o] Error 1 make[1]: Leaving directory `/opt/u-boot/cpu/pxa' make: *** [subdirs] Error 1 Thanks & Regards, Dannel Zhang

1 0

[U-Boot-Users] Maintainer of AT91RM9200DK???
by Steven Scholz 21 Oct '03

21 Oct '03

Hi there, who considers himself as the U-Boot maintainer of the AT91RM9200 cpu and the AT91RM9200DK eval board? Rick, is that you? I just porting U-Boot to our AT91RM9200 based board and it migth be necessary to change some code in the AT91RM9200 relevant stuff. So I am looking for people to talk to before that. Thanks a million. Steven

4 6

[U-Boot-Users] PQ2VADS (8270) & BDI2000 - II
by Matias Sundman (AL/EAB) 21 Oct '03

21 Oct '03

Hello again, I have now received a BDI2000 from Abatron. There is a configuration file included with the package for my target board, which is - PQ2FADS. U-boot is compiled with the CFG_PQ2FADS define in the MPC8260ADS.h file. Can I use the configuration file as is and burn u-boot.bin to the flash, and after a restart of the board I get a working u-boot automagically? Regards // Matias ------------------------------------------------------------------------- -----Original Message----- From: Chris Simmonds [mailto:chris@2net.co.uk] Sent: den 6 oktober 2003 10:45 To: Matias Sundman (TB/EAB) Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] PQ2VADS (8270) & BDI2000 Hi, I am using BDI2000 with an 8270 right now and it works fine. Its just the standard package for ppc 6xx/7xx/82xx/7400/7410. I used the configuration file for the vads8260 and fixed it up for my board (a custom unit). I don't have a config for the pq2vads board I'm afraid. Chris. Matias Sundman (TB/EAB) wrote: >Comrades, >I have compiled uboot for the PQ2VADS Motorola >evaluation board and tried to flash it with a >JTAG probe from GreenHills. Unfortunately their >probe does not support the 8270 architecture today. > >Does BDI2000 support the ppc8270 JTAG chain architecture? > >If so , does someone have a configuration file for the >PQ2VADS Motorola evaluation board? > >Best Regards // Matias > > >------------------------------------------------------- >This sf.net email is sponsored by:ThinkGeek >Welcome to geek heaven. >http://thinkgeek.com/sf >_______________________________________________ >U-Boot-Users mailing list >U-Boot-Users(a)lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/u-boot-users > -- Chris Simmonds 2net Limited chris(a)2net.co.uk http://www.2net.co.uk/ Tel: +44 (0)1962 869003 Fax: +44 (0)870 056 7556 "If it's not connected, it's not effective"(tm)

1 0

[U-Boot-Users] not booting
by Rakesh jagota 21 Oct '03

21 Oct '03

Hi all, I am working on mpc8245 based board. I have compiled the ppcboot with 64MB ram and its working fine and linux is ported successfully. But when I have configured the RAM to 128MB in ppcboot, I am getting the boot prompt and while loading linux its crashing . What can be the reason? Thanks & Regards, rakesh

2 1

[U-Boot-Users] Enhanced SDRAM tests with u-boot
by Thomas Schäfer 21 Oct '03

21 Oct '03

Hi all, I have problems with the Bringup of a custom MPC8280 board and I assume that SDRAM could be the reason. When performing memory tests on the complete SDRAM with the test routines included with u-boot 0.4.5, everything is working fine. Also, u-boot is running without problems. But when booting a (known to work) linux kernel (2.4.18, MontaVista 3.0), I get exceptions after decompressing the kernel (alignment, 0x600) and when executing the initial scripts (program, 0x700). So I would like to perform more sophisticated SDRAM tests with u-boot, including burst tests. Is there anybody who has done this before? Any hints are appreciated. Best regards Thomas Schäfer ____________________________________ GIGA STREAM GmbH Konrad-Zuse-Str. 7 66115 Saarbrücken Tel.: + 49 (0)681 / 95916 - 203 Fax: + 49 (0)681 / 95916 - 100 E-mail: tschaefer(a)giga-stream.de

2 1

RE: [U-Boot-Users] Any *urgent* bug fixes pending?
by Woodruff, Richard 21 Oct '03

21 Oct '03

Wolfgang, Should I wait before sending in device chaining again? There are several other patches, but I haven't had the time to clean them enough to get beyond the entrance threshold. -- the effect useful -- omap_toto # coninfo List of available devices: lcd 00000002 ..O stdout stderr keypad 00000001 .I. stdin touch 00000001 .I. stdin serial 80000003 SIO stdin stdout stderr 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 Wolfgang Denk Sent: Monday, October 20, 2003 8:07 AM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Any *urgent* bug fixes pending? Hi everybody, getting closer to a 1.0.0 release I would like to verify that there are no _urgent_ bug fixes left. Can you please verify that I checked in all _urgent_ patches / bug fixes sent to me, or that I acknowledged that I will postpone the modifications until after 1.0.0? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "The first rule of magic is simple. Don't waste your time waving your hands and hoping when a rock or a club will do." - McCloctnik the Lucid ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

2 1

[U-Boot-Users] MPC8270 Custom Board: Stack Pointer Corruption
by mss59＠att.net 20 Oct '03

20 Oct '03

I am working on an MPC8270 based custom board. u-boot is ported from EP8260 board version. RAM is 128M, flash is 16M. After u-boot relocates code in the ram, sometimes, stack pointer gets corrupted. And sometimes, I get bus fault which overwirtes all u-boot area in the RAM with some pattern like this bus fault 07f6bcd0 : 02001111 07f6be18 07f6bc68 11111111 ...........h.... 07f6bce0 : 42757320 4661756c 74204020 30782020 Bus Fault @ 0x 07f6bcf0 : 20202020 20202020 20202020 20202020 07f6bd00 : 20202020 20202020 20202020 20202020 07f6bd10 : 20202020 20202020 20202020 20202020 07f6bd20 : 20202020 20202020 20202020 20202020 07f6bd30 : 20202020 20202020 20202020 20202020 07f6bd40 : 20202020 20202020 20202020 20202020 07f6bd50 : 20202020 20202020 20202020 20202020 07f6bd60 : 20202020 20202020 20202020 20202020 07f6bd70 : 20202020 20202020 20202020 20202020 07f6bd80 : 20202020 20202020 20202020 20202020 07f6bd90 : 20202020 20202020 20202020 20202020 07f6bda0 : 20202020 20202020 20202020 20202020 07f6bdb0 : 20202020 20202020 20202020 20202020 07f6bdc0 : 20202020 20202020 20202020 20202020 ---> This patters is written till the end of ram. BDImn8270>rd GPR00: 00000000 07f6bbd0 ffdfffff 08000004 GPR04: 00000000 00000010 07f58a9d 00000007 GPR08: 00000001 00000000 00000000 00000007 GPR12: 00000020 00400000 07ffd000 080cc000 GPR16: fffdffff bffdffff ff7fffff fff7ef5f GPR20: 48000002 07f6bad0 00000000 07fcf098 GPR24: 07f6bce0 00000001 07fecdbc 07f6bfb4 GPR28: 07f6bcee 07f6bf70 07ffdcb8 07ff2ed8 CR : 48000002 MSR: 00000000 Any ideas..... Thanks Ravi.

2 1

[U-Boot-Users] 859/866 clock issues
by Nye Liu 20 Oct '03

20 Oct '03

two minor things on the 859/866 1) measure_gclk() is very inaccurate. Better to use the plprcr and CFG_8XX_XIN (which MUST BE 10MHz for that cpu) to derive the "real" bus clock. 2) the 859/866 does NOT support external speeds higher than 66MHz, so if cpu_clk is greater, EBDF01 MUST BE USED IN CFG_SCCR I have a patch for 1, but i no longer have my 859/866 eval board I have no patch for 2, but eventually we should come up with some sort of solution; the 859/866 is almost always configured to run faster than 66MHz. -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

3 3

[U-Boot-Users] Stack Pointer Problem: MPC8270 Custom Board
by mss59＠att.net 20 Oct '03

20 Oct '03

I am working on an MPC8270 based custom board. u-boot is ported from EP8260 board version. RAM is 128M, flash is 16M. After u-boot relocates code in the ram, sometimes, stack pointer gets corrupted. And sometimes, I get bus fault which overwirtes all u-boot area in the RAM with some pattern like this bus fault 07f6bcd0 : 02001111 07f6be18 07f6bc68 11111111 ...........h.... 07f6bce0 : 42757320 4661756c 74204020 30782020 Bus Fault @ 0x 07f6bcf0 : 20202020 20202020 20202020 20202020 07f6bd00 : 20202020 20202020 20202020 20202020 07f6bd10 : 20202020 20202020 20202020 20202020 07f6bd20 : 20202020 20202020 20202020 20202020 07f6bd30 : 20202020 20202020 20202020 20202020 07f6bd40 : 20202020 20202020 20202020 20202020 07f6bd50 : 20202020 20202020 20202020 20202020 07f6bd60 : 20202020 20202020 20202020 20202020 07f6bd70 : 20202020 20202020 20202020 20202020 07f6bd80 : 20202020 20202020 20202020 20202020 07f6bd90 : 20202020 20202020 20202020 20202020 07f6bda0 : 20202020 20202020 20202020 20202020 07f6bdb0 : 20202020 20202020 20202020 20202020 07f6bdc0 : 20202020 20202020 20202020 20202020 ---> This patters is written till the end of ram. BDImn8270>rd GPR00: 00000000 07f6bbd0 ffdfffff 08000004 GPR04: 00000000 00000010 07f58a9d 00000007 GPR08: 00000001 00000000 00000000 00000007 GPR12: 00000020 00400000 07ffd000 080cc000 GPR16: fffdffff bffdffff ff7fffff fff7ef5f GPR20: 48000002 07f6bad0 00000000 07fcf098 GPR24: 07f6bce0 00000001 07fecdbc 07f6bfb4 GPR28: 07f6bcee 07f6bf70 07ffdcb8 07ff2ed8 CR : 48000002 MSR: 00000000 Any ideas..... Thanks Ravi.

2 1

[U-Boot-Users] Any *urgent* bug fixes pending?
by Wolfgang Denk 20 Oct '03

20 Oct '03

Hi everybody, getting closer to a 1.0.0 release I would like to verify that there are no _urgent_ bug fixes left. Can you please verify that I checked in all _urgent_ patches / bug fixes sent to me, or that I acknowledged that I will postpone the modifications until after 1.0.0? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "The first rule of magic is simple. Don't waste your time waving your hands and hoping when a rock or a club will do." - McCloctnik the Lucid

2 2

[U-Boot-Users] Bug in at91rm9200_ether.c
by Steven Scholz 20 Oct '03

20 Oct '03

Hi there, I think there's terrible bug in the U-Boot ethernet driver for AT91RM9200 cpus. The function at91rm9200_EmacWritePhy() does not write the correct data. Attached patch fixes that. Thanks, -- Steven Scholz imc Measurement & Control imc Meßsysteme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin 13355 Berlin Germany Deutschland fon: +49 30 467090-0 Tel: 030 / 467090-0 fax: +49 30 4631576 fax: 030 / 4631576 + diff -u ./cpu/at91rm9200/at91rm9200_ether.c.orig ./cpu/at91rm9200/at91rm9200_ether.c --- ./cpu/at91rm9200/at91rm9200_ether.c.orig Sat Oct 18 18:14:46 2003 +++ ./cpu/at91rm9200/at91rm9200_ether.c Sat Oct 18 18:15:33 2003 @@ -341,7 +341,8 @@ { p_mac->EMAC_MAN = (AT91C_EMAC_HIGH & ~AT91C_EMAC_LOW) | AT91C_EMAC_CODE_802_3 | AT91C_EMAC_RW_W | - (RegisterAddress << 18); + (RegisterAddress << 18) | + (*pOutput); udelay (10000);

2 1

[U-Boot-Users] PATCH, mpc8xx - typo in mpc8xx.h
by Nye Liu 20 Oct '03

20 Oct '03

Wolfgang, there is a minor typo in mpc8xx.h Index: mpc8xx.h =================================================================== RCS file: /home/cvs/u-boot-mrv/include/mpc8xx.h,v retrieving revision 1.1.1.4 retrieving revision 1.5 diff -u -r1.1.1.4 -r1.5 --- mpc8xx.h 19 Sep 2003 23:43:28 -0000 1.1.1.4 +++ mpc8xx.h 18 Oct 2003 00:16:44 -0000 1.5 @@ -138,7 +138,7 @@ #define PLPRCR_MF_MSK 0xffff001e /* Multiplication factor + PDF bits */ #define PLPRCR_MFN_MSK 0xf8000000 /* Multiplication factor numerator bits */ #define PLPRCR_MFN_SHIFT 0x0000001b /* Multiplication factor numerator shift*/ -#define PLPRCR_MFD_MSK 0x03c00000 /* Multiplication factor denominator bits */ +#define PLPRCR_MFD_MSK 0x07c00000 /* Multiplication factor denominator bits */ #define PLPRCR_MFD_SHIFT 0x00000017 /* Multiplication factor denominator shift*/ #define PLPRCR_S_MSK 0x00300000 /* Multiplication factor integer bits */ #define PLPRCR_S_SHIFT 0x00000014 /* Multiplication factor integer shift */ -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

2 1

[U-Boot-Users] cpu/arm925 timer fixes.
by Woodruff, Richard 20 Oct '03

20 Oct '03

Hello, This patch fixes a few bugs which made udelay() not work properly on 925 based systems. A while back when I increased my boards clock speed I ran into quite a few problems which resulted in these fixes. I think the Innovator should be switched over to use a real udelay code instead of its busy spins. They do not scale at all with clock speed, and do not keep the useful timestamp properly updating. Regards, Richard W.

2 1

[U-Boot-Users] Patch: Nios dk1c20 network support
by Scott McNutt 20 Oct '03

20 Oct '03

This patch adds networking support for the Altera Nios Development Kit, Cyclone Edition (DK-1C20). Regards, --Scott McNutt <<nios-net.diff>> begin 600 nios-net.diff M9&EF9B`M3F%U<F(@=2UB;V]T+3(P,#,M3V-T+3$U+6]R:6<O9&]C+U)%041- M12YD:S%C,C`@=2UB;V]T+3(P,#,M3V-T+3$U+6YE=R]D;V,O4D5!1$U%+F1K M,6,R,`HM+2T@=2UB;V]T+3(P,#,M3V-T+3$U+6]R:6<O9&]C+U)%041-12YD M:S%C,C`),C`P,RTQ,"TQ-2`R,CHR,SHS-2XP,#`P,#`P,#`@+3`T,#`**RLK M('4M8F]O="TR,#`S+4]C="TQ-2UN97<O9&]C+U)%041-12YD:S%C,C`),C`P M,RTQ,"TQ-2`R,CHU-SHT,"XP,#`P,#`P,#`@+3`T,#`*0$`@+3(L-R`K,BPW M($!`"B`)"0D@3FEO<R!$979E;&]P;65N="!+:70*(`D)"2`@($-Y8VQO;F4@ M161I=&EO;G,*(`HM"0D@("`@3&%S="!5<&1A=&4Z($]C=&]B97(@-"P@,C`P M,PHK"0D@("`@3&%S="!5<&1A=&4Z($]C=&]B97(@,34L(#(P,#,*(#T]/3T] M/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T] M/3T]/3T]/3T]/3T]/3T]/3T]"B`*(%1H:7,@9FEL92!C;VYT86EN<R!I;F9O M<FUA=&EO;B!R96=A<F1I;F<@52U";V]T(&%N9"!T:&4@06QT97)A"D!`("TS M-"PW("LS-"PQ,"!`0`H@4')O9W)A;6UI;F<@52U";V]T(&EN=&\@1DQ!4T@@ M=VET:"!'15)-4PH@+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM+2T*(%1H92!C=7)R96YT('9E<G-I;VX@;V8@=&AE($1++3%#,C`@ M<&]R="!O8V-U<&EE<R!L97-S('1H86X*+38P($M">71E+B!3;R!E=F5R>71H M:6YG('=I;&P@9FET(&EN=&\@82!S:6YG;&4@1FQA<V@@<V5C=&]R+@HK-C`@ M2T)Y=&4@=VET:"!N971W;W)K('-U<'!O<G0@9&ES86)L960N(%-O(&5V97)Y M=&AI;F<@=VEL;"!F:70**VEN=&\@82!S:6YG;&4@9FQA<V@@<V5C=&]R+B!7 M:71H(&YE='=O<FL@<W5P<&]R="`H92YG+B!B;V]T<"P**W1F='!B;V]T+"!P M:6YG+"!E=&,I('1H92!F;&%S:"!F;V]T<')I;G0@:7,@86)O=70@-S=++@HK M"B!4;R!P<F]G<F%M(%4M0F]O="!I;G1O('1H92!$2RTQ0S(P(&9L87-H('5S M:6YG($=%4DU3(&1O('1H90H@9F]L;&]W:6YG.@H@"F1I9F8@+4YA=7)B('4M M8F]O="TR,#`S+4]C="TQ-2UO<FEG+V1O8R]214%$344N;FEO<R!U+6)O;W0M M,C`P,RU/8W0M,34M;F5W+V1O8R]214%$344N;FEO<PHM+2T@=2UB;V]T+3(P M,#,M3V-T+3$U+6]R:6<O9&]C+U)%041-12YN:6]S"3(P,#,M,3`M,34@,C(Z M,C,Z,S4N,#`P,#`P,#`P("TP-#`P"BLK*R!U+6)O;W0M,C`P,RU/8W0M,34M M;F5W+V1O8R]214%$344N;FEO<PDR,#`S+3$P+3$U(#(R.C4Y.C,U+C`P,#`P M,#`P,"`M,#0P,`I`0"`M,2PW("LQ+#<@0$`*(`H@"0D)("`@52U";V]T(&9O M<B!.:6]S+3,R"B`*+0D)("`@($QA<W0(a)57!D871E.B!/8W1O8F5R(#0L(#(P M,#,**PD)("`@($QA<W0(a)57!D871E.B!/8W1O8F5R(#$U+"`R,#`S"B`]/3T] M/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T] M/3T]/3T]/3T]/3T]/3T]/3T]/0H@"B!4:&ES(&9I;&4@8V]N=&%I;G,@:6YF M;W)M871I;VX@<F5G87)D:6YG(%4M0F]O="!A;F0@=&AE($%L=&5R80I`0"`M M,3<T+#@@*S$W-"PV($!`"B!4:&5R92!A<F4@<&QE;G1Y(&]F(&%R96%S('=H M97)E(&AE;'`@:7,@;F5E9&5D+B!(97)E)W,@87)E('-O;64@:61E87,*(&9O M<B!T:&]S92!I;G1E<F5S=&5D(&EN(&-O;G1R:6)U=&EN9SH*(`HM+5--0R`Y M,4,Q,3$@<W5P<&]R="X@12YG+B!A9&0@:6X@=&9T<&)O;W0L(&5T8RX*+0H@ M+4-O;7!A8W1&;&%S:"X@4&]R="`F('1E<W0@0T8O1D%4+@H@"B`M05--22!S M=7!P;W)T+B!5<V4@05--22!F;W(@96YV:7)O;FUE;G0L(&5T8RX*9&EF9B`M M3F%U<F(@=2UB;V]T+3(P,#,M3V-T+3$U+6]R:6<O9')I=F5R<R]S;6,Y,3$Q M,2YH('4M8F]O="TR,#`S+4]C="TQ-2UN97<O9')I=F5R<R]S;6,Y,3$Q,2YH M"BTM+2!U+6)O;W0M,C`P,RU/8W0M,34M;W)I9R]D<FEV97)S+W-M8SDQ,3$Q M+F@),C`P,RTQ,"TQ-2`R,CHR,SHS-RXP,#`P,#`P,#`@+3`T,#`**RLK('4M M8F]O="TR,#`S+4]C="TQ-2UN97<O9')I=F5R<R]S;6,Y,3$Q,2YH"3(P,#,M M,3`M,34@,C(Z-3`Z,C8N,#`P,#`P,#`P("TP-#`P"D!`("TQ-S@L-B`K,3<X M+#,Q($!`"B`)"0D)?2D*("-E;F1I9@H@"BLC:68@9&5F:6YE9"A#3TY&24=? M4TU#7U5315\S,E]"250I"BL**R-D969I;F4)4TU#7VEN;"AR*2`)*"HH*'9O M;&%T:6QE(&1W;W)D("HI*%--0U]"05-%7T%$1%)%4U,K*'(I*2DI"BL**R-D M969I;F4@4TU#7VEN<VPH<BQB+&PI(`DH>PEI;G0@7U]I(#L@(%P**PD)"0D) M9'=O<F0@*E]?8C([("!<"BL)"0D@("`@"0E?7V(R(#T@*&1W;W)D("HI(&([ M("!<"BL)"0D@("`@"0EF;W(@*%]?:2`](#`[(%]?:2`\(&P[(%]?:2LK*2![ M("!<"BL)"0D)"2`@*BA?7V(R("L@7U]I*2`](%--0U]I;FPH<BD[("!<"BL) M"0D)"2`@4TU#7VEN;"@P*3L@(%P**PD)"0D)?3L@(%P**PD)"0E]*0HK"BLC M9&5F:6YE"5--0U]O=71L*&0L<BD)*"HH*'9O;&%T:6QE(&1W;W)D("HI*%-- M0U]"05-%7T%$1%)%4U,K*'(I*2D@/2!D*0HK"BLC9&5F:6YE(%--0U]O=71S M;"AR+&(L;"D)*'L):6YT(%]?:3L@7`HK"0D)"0ED=V]R9"`J7U]B,CL@7`HK M"0D)"0E?7V(R(#T@*&1W;W)D("HI(&([(%P**PD)"0D)9F]R("A?7VD@/2`P M.R!?7VD@/"!L.R!?7VDK*RD@>R!<"BL)"0D)"2`@("!334-?;W5T;"@@*BA? M7V(R("L@7U]I*2P@<BD[(%P**PD)"0D)?2!<"BL)"0D)?2D**PHK(V5N9&EF M("\J($-/3D9)1U]334-?55-%7S,R7T))5"`J+PHK"B`C96YD:68*(`H@+RHM M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM+2TM+2TM+2TM+2T*9&EF9B`M3F%U<F(@=2UB;V]T+3(P,#,M3V-T M+3$U+6]R:6<O:6YC;'5D92]C;VYF:6=S+T1+,4,R,"YH('4M8F]O="TR,#`S M+4]C="TQ-2UN97<O:6YC;'5D92]C;VYF:6=S+T1+,4,R,"YH"BTM+2!U+6)O M;W0M,C`P,RU/8W0M,34M;W)I9R]I;F-L=61E+V-O;F9I9W,O1$LQ0S(P+F@) M,C`P,RTQ,"TQ-2`R,CHR,SHT,BXP,#`P,#`P,#`@+3`T,#`**RLK('4M8F]O M="TR,#`S+4]C="TQ-2UN97<O:6YC;'5D92]C;VYF:6=S+T1+,4,R,"YH"3(P M,#,M,3`M,34@,C(Z-3,Z-#@N,#`P,#`P,#`P("TP-#`P"D!`("TY-BPQ,B`K M.38L,3`@0$`*("\J+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM"B`@*B!% M=&AE<FYE="`M+2!N965D<R!W;W)K(0H@("HM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM+2TM M+2TM+2TM*B\*+2-I9B`P"B`C9&5F:6YE($-/3D9)1U]$4DE615)?4TU#.3$Q M,3$)"0DO*B!5<VEN9R!334,Y,6,Q,3$)*B\*+2-D969I;F4(a)0T].1DE'7U-- M0SDQ,3$Q7T)!4T4),'@P,#DQ,#`P,`DO*B!"87-E(&%D9')E<W,)"2HO"BTC M=6YD968@($-/3D9)1U]334,Y,3$Q,5]%6%1?4$A9"0D)+RH@3F\@97AT97)N M86P@4$A9"2HO"BTC9&5F:6YE($-/3D9)1U]334-?55-%7S,R7T))5`DQ"0DO M*B`S,BUB:70@:2]F"0DJ+PHM(V5N9&EF"BLC9&5F:6YE($-/3D9)1U]334,Y M,3$Q,5]"05-%"3!X,#`Y,3`S,#`)+RH@0F%S92!A9&1R97-S"0DJ+PHK(W5N M9&5F("!#3TY&24=?4TU#.3$Q,3%?15A47U!(60D)"2\J($EN=&5R;F%L(%!( M60D)*B\**R-D969I;F4(a)0T].1DE'7U--0U]54T5?,S)?0DE4"0D)+RH@,S(M M8FET(&1A=&$@<F0O=W()*B\*(`H@(V1E9FEN92!#3TY&24=?151(041$4@D) M,#@Z,#`Z,V4Z,C8Z,&$Z-6(*("-D969I;F4(a)0T].1DE'7TY%5$U!4TL)"3(U M-2XR-34N,C4U+C`*0$`@+3$S,2PW("LQ,CDL-B!`0`H@"0D)"2!#1D=?0TU$ M7TI&1E,R"7P@7`H@"0D)"2!#1D=?0TU$7TM'1$()?"!<"B`)"0D)($-&1U]# M341?3D%.1`E\(%P*+0D)"0D@0T9'7T--1%].150)?"!<"B`)"0D)($-&1U]# M341?34U#"7P@7`H@"0D)"2!#1D=?0TU$7TU)20E\(%P*(`D)"0D@0T9'7T-- M1%]00TD)?"!<"F1I9F8@+4YA=7)B('4M8F]O="TR,#`S+4]C="TQ-2UO<FEG M+VQI8E]N:6]S+V)O87)D+F,@=2UB;V]T+3(P,#,M3V-T+3$U+6YE=R]L:6)? M;FEO<R]B;V%R9"YC"BTM+2!U+6)O;W0M,C`P,RU/8W0M,34M;W)I9R]L:6)? M;FEO<R]B;V%R9"YC"3(P,#,M,3`M,34@,C(Z,C,Z-#4N,#`P,#`P,#`P("TP M-#`P"BLK*R!U+6)O;W0M,C`P,RU/8W0M,34M;F5W+VQI8E]N:6]S+V)O87)D M+F,),C`P,RTQ,"TQ-2`R,CHS-3HQ,"XP,#`P,#`P,#`@+3`T,#`*0$`@+3(W M+#8@*S(W+#<@0$`*("-I;F-L=61E(#QC;VUM;VXN:#X*("-I;F-L=61E(#QD M979I8V5S+F@^"B`C:6YC;'5D92`\=V%T8VAD;V<N:#X**R-I;F-L=61E(#QN M970N:#X*(`H@"B`O*@I`0"`M,3`W+#8@*S$P."PX($!`"B`*(`EB9%]T("IB M9#L*(`EI;FET7V9N8U]T("HJ:6YI=%]F;F-?<'1R.PHK"6-H87(@*G,L("IE M.PHK"6EN="!I.PH@"B`)+RH@4&]I;G1E<B!I<R!W<FET86)L92!S:6YC92!W M92!A;&QO8V%T960@82!R96=I<W1E<B!F;W(@:70N"B`)("H@3FEO<R!T<F5A M=',@0T9'7T="3%]$051!7T]&1E-%5"!A<R!A;B!A9&1R97-S+@I`0"`M,3(Y M+#8@*S$S,BPQ,B!`0`H@"6)D+3YB:5]S<F%M<W1A<G0]($-&1U]34D%-7T)! M4T4["B`)8F0M/F)I7W-R86US:7IE"3T@0T9'7U-204U?4TE:13L*(`EB9"T^ M8FE?8F%U9')A=&4)/2!#3TY&24=?0D%51%)!5$4["BL)8F0M/F)I7VEP7V%D M9'(@/2!G971E;G9?25!A9&1R("@B:7!A9&1R(BD["BL)<R`](&=E=&5N=B`H M(F5T:&%D9'(B*3L**PEF;W(@*&D@/2`P.R!I(#P@-CL@*RMI*2!["BL)"6)D M+3YB:5]E;F5T861D<EMI72`](',@/R!S:6UP;&5?<W1R=&]U;"`H<RP@)F4L M(#$V*2`Z(#`["BL)"6EF("AS*2!S(#T@*"IE*2`_(&4@*R`Q(#H@93L**PE] M"B`*(`EF;W(@*&EN:71?9FYC7W!T<B`](&EN:71?<V5Q=65N8V4[("II;FET M7V9N8U]P='([("LK:6YI=%]F;F-?<'1R*2!["B`)"6EF("@H*FEN:71?9FYC M7W!T<BD@*"D@(3T@,"D@>PI`0"`M,38T+#,@*S$W,RPT($!`"B`)<'5T<R@B M(R,C($524D]2(",C(R!0;&5A<V4@<F5S970@8F]A<F0@(R,C7&XB*3L*(`EF .;W(@*#L[*3L*('T**PH= ` end

2 1

[U-Boot-Users] Re: Revised patch: is_console_quiet(), and user feedback control during a TFTP operation
by Wolfgang Denk 20 Oct '03

20 Oct '03

Dear Jon, in message <1066216586.8112.17.camel(a)smoke.cideas.com> you wrote: > > I did some QA on my two latest patches, and found some minors problems > with the patch generation. I have regenerated these two patches. I > have verified that each patch by itself applies cleanly and doesn't > cause code bloat. > > I should of done this for the first iteration, but I thought it wasn't > needed. Sorry :< > > The two revised patches are attached. ... > CVS Comments: > > - Adding the CFG_CONSOLE_IS_QUIET option to support runtime changes in > console output. The is_console_quiet() function is used to > determine the status of quiet mode. Quiet mode is based on the > value of the "quiet" environment variable. Non-zero values indicate > that quiet mode is active. Please explain why we need yet another environment variable to control the output of console messages. I know that you are aware of the "silent" stuff. Why do we need something new like "quiet" now? I don't like to have 20 different implementations of more or less the same feature. Also, please consider the use of "setenv stdout nulldev". Put on hold with a strong tendency to reject it. > CHANGELOG: > > - Adding a number of options to control the user feedback during a > TFTP operation: > CFG_TFTP_BLINK_STATUS_ON_DATA_IN > CFG_TFTP_BLOCKS_PER_HASH > CFG_TFTP_HASHES_PER_FLASH > CFG_TFTP_HASHES_PER_LINE > CFG_TFTP_PROGESS_QUIET > CFG_TFTP_TIMEOUT_COUNT Come on - this is complete overkill, isn't it? > - Toggle the Status LED on TFTP activity - gives nice visual > indication of booting / network activity Conflicts with existing status LED driver, which has a pre-defined function on many boards. > - Change Status LED back to blinking on TFTP timeout Breaks function of status LED driver on many boards. > - Provide control over the maximum TFTP timeout Please note that code has been added to enable the TFTP client code to specify to the server the desired timeout value (see RFC-2349). This should be used. Sorry, but this is IMHO creaping featurism that does not add any value but renders the code unreadable. Can you please explain why you think I should add this? Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de If I had to live my life again, I'd make the same mistakes, only sooner. -- Tallulah Bankhead

1 0

[U-Boot-Users] README patch to add hint about CONFIG_SILENT_CONSOLE
by Jon Diekema 20 Oct '03

20 Oct '03

--- README 2003-10-14 07:12:06.000000000 -0400 +++ README 2003-10-14 20:08:20.000000000 -0400 @@ -479,6 +479,10 @@ When CONFIG_CFB_CONSOLE is defined, video console is default i/o. Serial console can be forced with environment 'console=serial'. + + When CONFIG_SILENT_CONSOLE is defined, console + messages can be silenced with the "silent" environment + variable. See doc/README.silent for more information. -- ------------------\\----------------------\\---------------------------- Jon Diekema | | Smiths Aerospace (616) 241-8310 | | 3290 Patterson Avenue, SE jon.diekema(a)smiths-aerospace.com \\ Grand Rapids, MI 49512 ****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************

2 1

[U-Boot-Users] Stack Size for MPC8xx???
by Steven Scholz 18 Oct '03

18 Oct '03

Hi there, does someone know how big the stack is for an MPC8xx based boards? I had this problem: I started porting U-Boot to my new AT91RM9200 based board. After doing the flash code I tried "saveenv". Simple reading, writing and erasing was working. But the board crashed when doing "saveenv". I found these lines in common/env_flash.c: int saveenv(void) { ... #if defined(CFG_ENV_SECT_SIZE) && (CFG_ENV_SECT_SIZE > CFG_ENV_SIZE) ulong flash_offset; uchar env_buffer[CFG_ENV_SECT_SIZE]; #else ... /* copy old contents to temporary buffer */ memcpy (env_buffer, (void *)flash_sect_addr, CFG_ENV_SECT_SIZE); I have CFG_ENV_SECT_SIZE = 64K and CFG_ENV_SIZE=4K and realized that my stack was far to small to save an 64KB flash sector. The funny thing is that I never worried about that issue. And it never seems to be a problem on our MPC8xx based boards... Thanks. -- Steven Scholz imc Measurement & Control imc Meßsysteme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin 13355 Berlin Germany Deutschland fon: +49 30 467090-0 Tel: 030 / 467090-0 fax: +49 30 4631576 fax: 030 / 4631576

2 1

[U-Boot-Users] problems about flash setting
by wang cheng 18 Oct '03

18 Oct '03

dear all! sorry ,but i really don't understand. 1.What's the meaning of flash memory banks,is the number of flash chips? ie:if i have 2 chips of 29f040s on my board,then the CFG_MAX_FLASH_BANKS should be 2,right? 2.What's the meaning of FLASH_BASE0_PRELIM and FLASH_BASE1_PRELIM, Is the FLASH_BASE0_PRELIM should be set to the flash_base_addr that defined by cs0? Then what about flash_base1_prelim? 3.What's the difference between br/or_prelim and br/or_remap and their respective function ??Is the br/or_remap must be set or optional depended on my board? Thanks very much for any help!

2 1

[U-Boot-Users] u-boot on cerfboard
by rik rm 17 Oct '03

17 Oct '03

Hi list, Has anybdy ported the u-boot on cerf board 250 (intrinsyc pxa250) ?? I am interested in doing the same but i do not have the BDI debugger and flashing a non working /non tested u-boot is a bit of a risk !!! Any pointers will be of great help. regards rik --------------------------------- Do you Yahoo!? The New Yahoo! Shopping - with improved product search

2 1

[U-Boot-Users] AT91RM9200 and -mtune=arm7dtmi ???
by Steven Scholz 17 Oct '03

17 Oct '03

Hi there, the file cpu/at91rm9200/config.mk contains an option "-mtune=arm7tdmi". I am new to ARM processors so please bear my stupid question: The Atmel AT91RM9200 is and ARM9 / ATM920T. So shouldn't this option be different? Like "-mtune=atm920" or something? What is it good for anyway? Thanks a million! -- Steven Scholz imc Measurement & Control imc Meßsysteme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin 13355 Berlin Germany Deutschland fon: +49 30 467090-0 Tel: 030 / 467090-0 fax: +49 30 4631576 fax: 030 / 4631576

1 0

[U-Boot-Users] linux 2.6 kernel support for u-boot
by Holger Schurig 17 Oct '03

17 Oct '03

Hi ! I just saw that u-boot has now official support in the Linux 2.6 kernel. In Linus' current Bitkeeper tree was a checkin of a change that allows one to execute "make uImage": $ make -n V=1 uImage ... echo ' Kernel: arch/arm/boot/zImage is ready' ... /bin/sh /usr/src/ramses/linux-2.6/scripts/mkuboot.sh -A arm \ -O linux -T kernel -C none -a 0xa0008000 -e 0xa0008000 \ -n 'Linux-2.6.0-test7-bkpxa' -d arch/arm/boot/zImage \ arch/arm/boot/uImage ... echo ' Image arch/arm/boot/uImage is ready' -- Try Linux 2.6 from BitKeeper for PXA2x0 CPUs at http://www.mn-logistik.de/unsupported/linux-2.6/

1 0

[U-Boot-Users] u/zImage and 64360
by Ronen Shitrit 16 Oct '03

16 Oct '03

Hi 1. As specified in the U-Boot README: " Building a Linux Image: ----------------------- With U-Boot, "normal" build targets like "zImage" or "bzImage" are not used. If you use recent kernel source, a new build target "uImage" will exist which .... " Does it means I can't load a zImage of the kernel by using the tftp??? 2. Does anyone knows if there is already a u-boot version for the Marvell 64360 boards?? Thanks -- Ronen Shitrit M.S.I.L D.N. Misgav 20184 Tel: +972-4-9951000 Fax: +972-4-9951001 Email: mailto: ronen.shitrit(a)il.marvell.com _____________________________________________________________ This message may contain confidential, proprietary or legally privileged information. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone, or by e-mail and delete the message from your computer.

3 3

[U-Boot-Users] Starting with Lite5200 Eval Board
by Aquin Remi 16 Oct '03

16 Oct '03

Hello, How to configure U-Boot + Linux with : - Video Card on PCI, - HD, - CD Reader, - CAN Driver.

2 1

[U-Boot-Users] MIPS support
by Ronen Shitrit 16 Oct '03

16 Oct '03

Hi I'm a little confused, in the web page http://sourceforge.net/projects/u-boot/ it says: "CPU architectures are supported: PowerPC(MPC5xx, MPC8xx, MPC82xx, MPC7xx, MPC74xx, 4xx), ARM(ARM7, ARM9, StrongARM, Xscale), MIPS(4Kc,5Kc)," but when I loaded the u-boot-0.4.0 version , I read the README file and there it says: "* Target CPU Architecture (Provisions for Alpha, ARM, Intel x86, IA64, MIPS, MIPS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; Currently supported: PowerPC)." So I wanted to know if someone has a clue whether the README file isn't update or the web site, and if someone tried to run it on a MIPS. (I saw under the lib cpu that there is a dir for the MIPS) Thanks alot -- Ronen Shitrit M.S.I.L D.N. Misgav 20184 Tel: +972-4-9951000 Fax: +972-4-9951001 Email: mailto: ronen.shitrit(a)il.marvell.com _____________________________________________________________ This message may contain confidential, proprietary or legally privileged information. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by telephone, or by e-mail and delete the message from your computer.

2 1

[U-Boot-Users] How to compute TEXT_BASE address in my new board?
by Jacob Chan 16 Oct '03

16 Oct '03

Dear all, I have an Intel Xscale PXA263 based board. I want to put u-boot on this board instead. Could someone tell me how to compute TEXT_BASE address in my board? Best regards, Jacob

3 2

RE: [U-Boot-Users] Porting to a new board
by Cedric Aubert 16 Oct '03

16 Oct '03

They are a little description of the manner to port u-boot to a new board in the readme file. Look at this first. Hope that's help Cedric > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Curt Brune > Sent: Thursday, October 16, 2003 8:03 AM > To: u-boot-users(a)lists.sourceforge.net > Subject: [U-Boot-Users] Porting to a new board > > > Hi, > > I have an ARM7TDMI based board that is not currently supported by > u-boot and I would like to have a go at it -- the board is described > here: > > http://www.cucy.net/evb4510.pdf > > The boot loader that comes with the board is lame. It requires one to > connect with a windows program to program the flash and to do other > u-boot type things. I want to put u-boot on this board instead. > > Is there a "new board porting guide" or other porting related docs? > > Cheers, > Curt > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

[U-Boot-Users] Porting to a new board
by Curt Brune 16 Oct '03

16 Oct '03

Hi, I have an ARM7TDMI based board that is not currently supported by u-boot and I would like to have a go at it -- the board is described here: http://www.cucy.net/evb4510.pdf The boot loader that comes with the board is lame. It requires one to connect with a windows program to program the flash and to do other u-boot type things. I want to put u-boot on this board instead. Is there a "new board porting guide" or other porting related docs? Cheers, Curt

1 0

[U-Boot-Users] Does the driver of SMSC 91C111 can apply to SMSC91C113?
by 李法龙 16 Oct '03

16 Oct '03

Thanks a lot!

1 0

[U-Boot-Users] U-boot Memory Map
by Raghu 15 Oct '03

15 Oct '03

Hi, Looking for a document for u-boot memory map. Enabling DEBUG at board.c I got few of them, Is there any addition to this ? *************************************************** CPU: unknown MPC860 (0x08000003) at 50 MHz: 4 kB I-Cache 4 kB D-Cache FEC pres ent Board: Force ( MPC852T ) DRAM: 64 MB Top of RAM usable for U-Boot at: 04000000 Reserving 256k for U-Boot at: 03fc0000 Reserving 448k for malloc() at: 03f50000 Reserving 60 Bytes for Board Info at: 03f4ffc4 Reserving 44 Bytes for Global Data at: 03f4ff98 Stack Pointer at: 03f4ff78 New Stack Pointer is: 03f4ff78 Now running in RAM - U-Boot at: 03fc0000 FLASH: 1 MB AM29LV008BB (8 Mbit, bottom boot sect) ****************************************************** Warm Regards, Raghu. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

2 3

[U-Boot-Users] Adding a number of options to control the user feedback during a TFTP operation
by Jon Diekema 15 Oct '03

15 Oct '03

Product: - u-boot Version: - 1.0.0-pre CHANGELOG: - Adding a number of options to control the user feedback during a TFTP operation: CFG_TFTP_BLINK_STATUS_ON_DATA_IN CFG_TFTP_BLOCKS_PER_HASH CFG_TFTP_HASHES_PER_FLASH CFG_TFTP_HASHES_PER_LINE CFG_TFTP_PROGESS_QUIET CFG_TFTP_TIMEOUT_COUNT Patched files: - README - net/tftp.c ------------------\\----------------------\\---------------------------- Jon Diekema | | Smiths Aerospace (616) 241-8310 | | 3290 Patterson Avenue, SE jon.diekema(a)smiths-aerospace.com \\ Grand Rapids, MI 49512 ****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************

1 0

[U-Boot-Users] Adding is_console_quiet() to support runtime changes in console output
by Jon Diekema 15 Oct '03

15 Oct '03

Product: - u-boot Version: - 1.0.0-pre CHANGELOG: - Adding is_console_quiet() to support runtime changes in console output CVS Comments: - Adding the CFG_CONSOLE_IS_QUIET option to support runtime changes in console output. The is_console_quiet() function is used to determine the status of quiet mode. Quiet mode is based on the value of the "quiet" environment variable. Non-zero values indicate that quiet mode is active. Patched files: - README - include/console.h - common/console.c - common/cmd_nvedit.c -- ------------------\\----------------------\\---------------------------- Jon Diekema | | Smiths Aerospace (616) 241-8310 | | 3290 Patterson Avenue, SE jon.diekema(a)smiths-aerospace.com \\ Grand Rapids, MI 49512 ****************************************** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ******************************************

1 0

[U-Boot-Users] walnut 405gp bridge setting
by Xiaoshan Zuo 15 Oct '03

15 Oct '03

I have a customized walnut 405 gp board. While using u-boot the bridge was not set correclty. The problem was that the bridge didn't respond to requst. The problem was traced down to PCIC0_CMD[MA]=0 on the bridge. The bit is set correclty in pci_405gp_init, later it is got changed in pci_hose_scan_bus. It is not supposed to be changed, as suggested by the comment below in the code. But this comment contradict with function pci_hose_scan_bus which intentionly doesn't skip the bridge. Removing #ifndef in pci_hose_scan_bus makes the bridge work. My question is: is this a typo? Where can I search for u-boot mailing list archive? linuxppc is very easy to serach useful information. Sorry for the newbie question. Thanks, Xiaoshan /* * drivers/pci.c skips every host bridge but the 405GP since it could * be set as an Adapter. * * I (Andrew May) don't know what we should do here, but I don't want * the auto setup of a PCI device disabling what is done pci_405gp_init * as has happened before. */ void pci_405gp_setup_bridge(struct pci_controller *hose, pci_dev_t dev, struct pci_config_table *entry) { #ifdef DEBUG printf("405gp_setup_bridge\n"); #endif } In drivers/pci.c: int pci_hose_scan_bus(struct pci_controller *hose, int bus) { #ifndef CONFIG_405GP /* don't skip host bridge on ppc405gp */ /* Skip our host bridge */ if ( dev == PCI_BDF(hose->first_busno,0,0) ) continue; #endif

1 0

[U-Boot-Users] Where does u-boot start when booting Linux?
by Allen Curtis 14 Oct '03

14 Oct '03

I was hoping that someone could give me a quick answer. When u-boot starts Linux, does is start from the beginning for does it jump in somewhere past decompress()? I have been looking at the Linux code and it doesn't appear that the bdinfo structure is being handled correctly for u-boot. There is an CONFIG_EMBEDDEDBOOT option but even this only passes the boot parameter in a few instances. Does u-boot fix this somehow? Another thing is embed_config() for the ADS8260 board, forces the baud-rate to 9600 but 2_4_devel is quite happy at 115200 as in u-boot. This is interesting since I am trying to fix a serial baud-rate problem. TIA!

2 5

[U-Boot-Users] SCC Ethernet with PHY BCM522
by Raghu 14 Oct '03

14 Oct '03

Hello All, I have a MPC852T based board. I have configured SCC4 ETHERNET register and I have a PHY ( Broadcom 5222 ) chip as a PHY support. I am able to do a SCC loopback, but the data is not going out from the PHY when I diable the loopback. How do I access the PHY from SCC "scc.c" driver ?? do I have to do this anyway ? The PHY is getting accessed from "MII" i.e I am able to do "mii read/write" The Dual BCM Phy registers are located at 0x10 and 0x11 offset. of PHY. Warm Regards Raghu. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

2 3

[U-Boot-Users] Enabling the data size parameter for memory commands like "md"?
by Pasi Huhtiniemi 14 Oct '03

14 Oct '03

Hello, I'm playing around with a day-old cvs snapshot of U-Boot, using it with "make at91rm9200dk_config". My problem is the same with 0.4.0. >From the source (and from the usage help) I understand that at least the memory commands like "md" should accept (optional) data size parameter (.b/.w/.l) as the first parameter. How do you enable this? In my environment they don't work: 1) argv[0] is the command itself (like "md"), not the data size parameter from where the source tries to read it and 2) if I give the data size parameter, the upper framework counts the amount of parameters to be illegal and therefore certain commands give me an error message (the short usage). I suppose there is a #define missing? What is it? I could not quickly find it grepping the source, googling the net / mailing list archives. Best Regards, Pasi Huhtiniemi

3 2

[U-Boot-Users] error appears when make u-boot
by boymanchen 14 Oct '03

14 Oct '03

Hi,all I have download a u-boot project, and want to build it into a bin file. But an error message appears during the process.The following is my step: 1. cd */u-boot 2. make csb266_config Error: no rule to make target 'csb266_config'. Stop. In the Makefile, I can see the rule for csb266 board, but why can't i build it? Anybody can help me? please, thank you very much! Regards Feng ______________________________________ =================================================================== ÔÚœñÌìÏíÊÜÃ÷Ìì£¬»ÝÆÕÕÐÐÐÍÆ³ö·ÖÆÚÃâÏ¢¹ºPC (http://ad4.sina.com.cn/shc/zhuiyu_hprefresh.html)

2 1

[U-Boot-Users] Support for ALTERA FPGAs
by Steven Scholz 13 Oct '03

13 Oct '03

Hi there, the patch attached adds support for ALTERA FPGAs. For now only the ACEX1K using the so called "passive serial" Interface. The code and idea is heavily stolen from the xilinx stuff. And just like there the board specific code has to provide some functions for handling the FPGA signals CONF_DONE, DATA, DCLK, nCONFIG, nSTATUS. I thought I release it quite early to avoid redundant work done by others and hope this could be a usefull starting point for people using Altera FPGAs. * Patch by Steven Scholz, 10 Oct 2003 - Add support for Altera FPGA ACEX1K Cheers, -- Steven Scholz imc Measurement & Control imc Meßsysteme GmbH Voltastr. 5 Voltastr. 5 13355 Berlin 13355 Berlin Germany Deutschland fon: +49 30 467090-0 Tel: 030 / 467090-0 fax: +49 30 4631576 fax: 030 / 4631576

2 5

[U-Boot-Users] DiskOnChip problem on warm boot
by James Bates 13 Oct '03

13 Oct '03

Hi all, Have had my MPC8260ADS based system up and running for a while now but I have recently noticed a problem when I warm boot. When it comes to detecting the DOC chip I just get a series of 10 "Doc_WaitReady timeout" messages. This takes about a couple of minutes and then it carries on with the boot as normal. Any ideas of what is happening? This does not happen in a power on reset. Regards, James This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.

2 2

RE: [U-Boot-Users] gcc print-libgcc-file-name
by Scott McNutt 13 Oct '03

13 Oct '03

> This has already been addresses in a patch by > David Müller of 22 Sep which I checked in today. > > I think this solves the problem. Please correct > me if I'm wrong. This solves the problem ... if for some reason a problem remains in the Nios make files I will fix. Thanks, --Scott

1 0

[U-Boot-Users] I cann't initialize OR/BR registers in cpu_init.c?
by wang cheng 13 Oct '03

13 Oct '03

hello ! all I'm porting u-boot-0.4.0 to my WindRiver MDP PRO board now,some addressing specifications are listed below.I choose the fads823 as the model.I have vision ICE ii & vision CLICK to program flash and debug the code. I compile the code in the vmware linux environment.After "make myboard_config" and "make",I copy the u-boot(ELF) to the vision CLICK path in windows environment，then Convert to .BIN file, program to flash,run,use the hyperterminal as the console. Now in the cpu_init.c ,I masked all the OR/BR initialization clause,for when I released them there's nothing displayed on the hyperterminal ;but when masked them ,the program can run to the "=>"(after main_loop();)with the vision ICE II and to the relocate_code()(in the board_init_f();)without the visionICE II ,some register value are listed below in the vision CLICK BKM mode. **1.why I cann't initialize the OR/BR registers in the cpu_init.c **2.how to modify the dram initialization to pass the relocate_code() 3.can you tell me something details about the BCSR register in the FADS823 model. 4.are there any better model for WindRiver MDPRRO board ? Any suggests are very appreciated! specifications: Addressing: Total address range 4GB (on and off board) Flash Memory 1.0MB on board 16MB SIMM (4MB Std.) SRAM Memory 2MB (512K Std.) DRAM Memory 32MB SIMM (16MB Std.) EEPROM 8K >BKM>sc ****************** SIU ***************** IMMR xxxxxxxx FF000000 SIUMCR FF000000 00610000 SYPCR FF000004 FFFFFF88 SWSR FF00000E 0000 SIPEND FF000010 00000000 SIMASK FF000014 00400000 SIEL FF000018 00000000 SIVEC FF00001C 3C000000 TESR FF000020 00000000 SDCR FF000030 00004001 ****************** UPM_A ***************** UPMA_T0 FF00017C 0FF3FC00 UPMA_T1 FF00017C 1FF7FC07 UPMA_T2 FF00017C FFFFFFFF UPMA_T3 FF00017C FFFFFFFF ...... ****************** UPM_B ***************** UPMB_T0 FF00017C 0FF3CC24 UPMB_T1 FF00017C 0FF3CC04 UPMB_T2 FF00017C 0CF3CC04 UPMB_T3 FF00017C 00F3CC04 UPMB_T4 FF00017C 00F3CC00 UPMB_T5 FF00017C 37F7CC47 UPMB_T6 FF00017C FFFFFFFF UPMB_T7 FF00017C FFFFFFFF U ..... ****************** MEMC ***************** BR0 FF000100 FFF00801 OR0 FF000104 FFF00760 BR1 FF000108 00000000 OR1 FF00010C 00000000 BR2 FF000110 000000C1 OR2 FF000114 FF000800 BR3 FF000118 00000000 OR3 FF00011C 00000000 BR4 FF000120 03000081 OR4 FF000124 FBF80010 BR5 FF000128 10000401 OR5 FF00012C FFC00760 BR6 FF000130 00000000 OR6 FF000134 00000000 BR7 FF000138 00000000 OR7 FF00013C 00000000 MAR FF000164 00000000 MCR FF000168 0000001B MAMR FF000170 0C120111 MBMR FF000174 2FB20111 MSTAT FF000178 0000 MPTPR FF00017A 0800 MDR FF00017C FF0C0027 ****************** CLOCKS ***************** SCCRK FF000380 55CCAA33 SCCR FF000280 01800000 PLPRCRK FF000384 55CCAA33 PLPRCR FF000284 00400000 RSRK FF000388 55CCAA33 RSR FF000288 D0000000 ****************** SI ***************** SIMODE FF000AE0 00000000 SIGMR FF000AE4 00 SISTR FF000AE6 00 SICMR FF000AE7 00 SICR FF000AEC 00000000 SIRP FF000AF0 00000000

2 1

[U-Boot-Users] [PATCH] support for Intel IXP
by Kyle Harris 10 Oct '03

10 Oct '03

Wolfgang, Please find attached a patch for Intel CPU IXP425 and eval board IXDP425. This is applied against 0.4.0 (I tried several times to pull from CVS but failed, and finally gave up). Note: This patch does NOT include support for the PCI bridge :( Regards, Kyle.

3 8

Re: [U-Boot-Users] Ramdisk for MPC8xx
by Wolfgang Denk 10 Oct '03

10 Oct '03

Dear Raghu, in message <20031010132205.90468.qmail(a)web40406.mail.yahoo.com> you wrote: > > > Well, did you read the README ? > Yes, I did but I am not very clear about the mem map. There is some documentation around, including the HOWTO (now at http://www.denx.de/twiki/bin/view/PPCEmbedded/Introduction) and mailing list archives. > > AFAIK this code never made it into the public Linux > > kernel tres. > > I think this is the same on on the www.kernel.org site I mean: we added this to the DENX linux kernel trees, but I don't expect to find it in the public trees. > > This is why I recommended our SELF bassed ramdisk > > image. > > I tried your suggeted ramdisk image and also set the > initrd_high = ffffffff and IT WORKED !!! > Thank you so much. You're welcome. > I have a dubious distinction of never getting the > busybox built by me up and running :-) See the SELF (either from the ELDK RPM or from our FTP server). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "You shouldn't make my toaster angry." - Household security explained in "Johnny Quest"

1 0

[U-Boot-Users] Ramdisk for MPC8xx
by Raghu 10 Oct '03

10 Oct '03

Hello All, I am porting linux-2.4.22 to MPC852T based board. I have an issue with the Ramdisk. I have a total of 64MB SDRAM, and I am creating a ramdisk of 32MB. The compressed Ramdisk file is of 3.4MB size. Look like when I do the "bootm" command the Ramdisk is corrupting some important u-boot data. I have the console dump below. Is there a minimal Ramdisk that I can directly use ?? Warm Regards Raghu. ****************************************************** =>tftpload 1000000 uImage TFTP from server 10.208.1.90; our IP address is 10.208.1.247 Filename 'uImage'. Load address: 0x1000000 Loading: ####### done Bytes transferred = 649227 (9e80b hex) =>tftpload 2000000 ramdisk TFTP from server 10.208.1.90; our IP address is 10.208.1.247 Filename 'ramdisk'. Load address: 0x2000000 Loading:#### done Bytes transferred = 3685400 (383c18 hex) =>bootm 1000000 2000000 ## Booting image at 01000000 ... Image Name: Linux 2.4.22 Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 649163 Bytes = 633.9 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## cmdline at 0x007FFF00 ... 0x007FFF10 memstart = 0x00000000 memsize = 0x04000000 flashstart = 0xFE000000 flashsize = 0x00100000 flashoffset = 0x0001B000 sramstart = 0x00000000 sramsize = 0x00000000 immr_base = 0xFF000000 bootflags = 0x00000001 intfreq = 50 MHz busfreq = 50 MHz ethaddr = 00:00:00:00:00:02 IP addr = 10.208.1.247 baudrate = 38400 bps ## Loading RAMDisk Image at 02000000 ... Image Name: Linux Ramdisk Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 3685336 Bytes = 3.5 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Ramdisk to 03bcb000, end 03f4ebd8 ... ****************************************************** __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

2 3

[U-Boot-Users] Re: [PATCH] u-boot, support for dbau1x00 board
by Wolfgang Denk 09 Oct '03

09 Oct '03

In message <3F858A9D.5000002(a)corelatus.com> you wrote: > > here is the patch for dbau1x00 board. > > I left out the renaming of serial.* to asc_serial.* from > the main patch in case you want to do it yourself in > cvs. > I add a second patch for this in case you want it. Added both patches. > Comment: > I changed the mail address for Magnus Damm. He left Ericsson > some 5 years ago, so that address does not work anymore. Thanks. > dbau1x00 board will not compile unless 2 of the patches > for cmd_ide.c I mailed to list is added. > ( ATA read/write and CONFIG_IDE_8xx_DIRECT stuff. ) > > * Patch by Thomas Lange, 09 Oct 2003: > Support for new board dbau1x00 (mips32) added Added, thanks. Will show up on CVS soon. [You keep me pretty busy these days ;-) ] Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de Little known fact about Middle Earth: The Hobbits had a very sophi- sticated computer network! It was a Tolkien Ring...

1 0

[U-Boot-Users] [PATCH] memsize option
by Thomas Lange 09 Oct '03

09 Oct '03

Some versions of linux expect memsize in MB, other in bytes. This patch adds a new config option CONFIG_MEMSIZE_IN_BYTES that solves this. Also added a fix for mips that uses this new option. * Patch by Thomas Lange, 9 Oct 2003: New option CONFIG_MEMSIZE_IN_BYTES for passing memsize args to linux /Thomas diff -purN u-boot-cvs/README u-boot-new/README --- u-boot-cvs/README 2003-09-18 12:02:25.000000000 +0200 +++ u-boot-new/README 2003-10-09 12:37:08.000000000 +0200 @@ -405,7 +405,7 @@ The following options need to be configu CONFIG_8xx_GCLK_FREQ - if get_gclk_freq() can not work e.g. no 32KHz reference PIT/RTC clock -- Clock Interface: +- Linux Interface: CONFIG_CLOCKS_IN_MHZ U-Boot stores all clock information in Hz @@ -415,11 +415,16 @@ The following options need to be configu "clocks_in_mhz" can be defined so that U-Boot converts clock data to MHZ before passing it to the Linux kernel. - When CONFIG_CLOCKS_IN_MHZ is defined, a definition of "clocks_in_mhz=1" is automatically included in the default environment. + CONFIG_MEMSIZE_IN_BYTES + + When transfering memsize parameter to linux, some versions + expect it to be in bytes, others in MB. + Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. + - Console Interface: Depending on board, define exactly one serial port (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2, diff -purN u-boot-cvs/lib_mips/mips_linux.c u-boot-new/lib_mips/mips_linux.c --- u-boot-cvs/lib_mips/mips_linux.c 2003-06-27 23:32:47.000000000 +0200 +++ u-boot-new/lib_mips/mips_linux.c 2003-10-09 12:46:39.000000000 +0200 @@ -183,7 +183,18 @@ void do_bootm_linux(cmd_tbl_t *cmdtp, in linux_params_init (PHYSADDR(gd->bd->bi_boot_params), commandline); +#ifdef CONFIG_MEMSIZE_IN_BYTES + sprintf (env_buf, "%lu", gd->ram_size); +#ifdef DEBUG + printf ("## Giving linux memsize in bytes, %lu\n",gd->ram_size); +#endif +#else sprintf (env_buf, "%lu", gd->ram_size >> 20); +#ifdef DEBUG + printf ("## Giving linux memsize in MB, %lu\n",gd->ram_size >> 20); +#endif +#endif /* CONFIG_MEMSIZE_IN_BYTES */ + linux_env_set ("memsize", env_buf); sprintf (env_buf, "0x%08X", (uint)PHYSADDR(initrd_start));

2 1

[U-Boot-Users] [PATCH] ATA identity, Endian swap
by Thomas Lange 09 Oct '03

09 Oct '03

Reading of ATA drive id is broken in cmd_ide.c for big endian cpu:s that are not ppc. If I am not mistaken, the text strings should be endian swapped on big endian cpu:s, but not for little ones. * Patch by Thomas Lange, 10 Oct 2003: Endian swap ATA identity for all big endian cpu:s, not just ppc. /Thomas --- u-boot-0.4.8/common/cmd_ide.c 2003-07-01 23:07:07.000000000 +0200 +++ u-boot-0.4.8_new/common/cmd_ide.c 2003-10-08 23:56:06.000000000 +0200 @@ -164,9 +164,6 @@ static uchar ide_wait (int dev, ulong t static void __inline__ ide_outb(int dev, int port, unsigned char val); static unsigned char __inline__ ide_inb(int dev, int port); -#ifdef __PPC__ -static void input_swap_data(int dev, ulong *sect_buf, int words); -#endif static void input_data(int dev, ulong *sect_buf, int words); static void output_data(int dev, ulong *sect_buf, int words); static void ident_cpy (unsigned char *dest, unsigned char *src, unsigned int len); @@ -809,7 +806,13 @@ output_data_short(int dev, ulong *sect_b *pbuf = 0; } # endif /* CONFIG_AMIGAONEG3SE */ +#endif /* __PPC_ */ +/* We only need to swap data if we are running on a big endian cpu. */ +/* But Au1x00 cpu:s already swaps data in big endian mode! */ +#if defined(__LITTLE_ENDIAN) || defined(CONFIG_AU1X00) +#define input_swap_data(x,y,z) input_data(x,y,z) +#else static void input_swap_data(int dev, ulong *sect_buf, int words) { @@ -821,9 +824,7 @@ input_swap_data(int dev, ulong *sect_buf *dbuf++ = ld_le16(pbuf); } } -#else /* ! __PPC__ */ -#define input_swap_data(x,y,z) input_data(x,y,z) -#endif /* __PPC__ */ +#endif /* __LITTLE_ENDIAN || CONFIG_AU1X00 */ #ifdef __PPC__

2 1

[U-Boot-Users] [PATCH] cmd_ide.c, ifdef code only needed by 8xx_direct
by Thomas Lange 09 Oct '03

09 Oct '03

A big chunk of code in cmd_ide.c is only valid for boards that set CONFIG_IDE_8xx_DIRECT That makes it harder than neccesary to follow the flow since alot of calculations/variables are pointless. * Patch by Thomas Lange, 10 Oct 2003: code only needed by CONFIG_IDE_8xx_DIRECT ifdef:ed /Thomas --- u-boot-0.4.8/common/cmd_ide.c 2003-07-01 23:07:07.000000000 +0200 +++ u-boot-0.4.8_new/common/cmd_ide.c 2003-10-09 00:02:42.000000000 +0200 @@ -65,6 +65,7 @@ #if (CONFIG_COMMANDS & CFG_CMD_IDE) +#ifdef CONFIG_IDE_8xx_DIRECT /* Timings for IDE Interface * * SETUP / LENGTH / HOLD - cycles valid for 50 MHz clk @@ -101,6 +102,8 @@ static int pio_mode = CFG_PIO_MODE; #define PCMCIA_MK_CLKS( t, T ) (( (t) * (T) + 999U ) / 1000U ) +#endif /* CONFIG_IDE_8xx_DIRECT */ + /* ------------------------------------------------------------------------- */ /* Current I/O Device */ @@ -180,8 +183,6 @@ ulong atapi_read (int device, ulong blkn #ifdef CONFIG_IDE_8xx_DIRECT static void set_pcmcia_timing (int pmode); -#else -#define set_pcmcia_timing(a) /* dummy */ #endif /* ------------------------------------------------------------------------- */ @@ -472,9 +473,8 @@ int do_diskboot (cmd_tbl_t *cmdtp, int f void ide_init (void) { - DECLARE_GLOBAL_DATA_PTR; - #ifdef CONFIG_IDE_8xx_DIRECT + DECLARE_GLOBAL_DATA_PTR; volatile immap_t *immr = (immap_t *)CFG_IMMR; volatile pcmconf8xx_t *pcmp = &(immr->im_pcmcia); #endif @@ -502,6 +502,7 @@ void ide_init (void) WATCHDOG_RESET(); +#ifdef CONFIG_IDE_8xx_DIRECT /* Initialize PIO timing tables */ for (i=0; i <= IDE_MAX_PIO_MODE; ++i) { pio_config_clk[i].t_setup = PCMCIA_MK_CLKS(pio_config_ns[i].t_setup, @@ -518,6 +519,7 @@ void ide_init (void) pio_config_ns[i].t_length, pio_config_clk[i].t_length, pio_config_ns[i].t_hold, pio_config_clk[i].t_hold); } +#endif /* CONFIG_IDE_8xx_DIRECT */ /* Reset the IDE just to be sure. * Light LED's to show @@ -528,12 +530,12 @@ void ide_init (void) #ifdef CONFIG_IDE_8xx_DIRECT /* PCMCIA / IDE initialization for common mem space */ pcmp->pcmc_pgcrb = 0; -#endif /* start in PIO mode 0 - most relaxed timings */ pio_mode = 0; set_pcmcia_timing (pio_mode); +#endif /* * Wait for IDE to get ready. * According to spec, this can take up to 31 seconds!

2 1

[U-Boot-Users] [PATCH] fix ATA for non ppc
by Thomas Lange 09 Oct '03

09 Oct '03

AFAIK, cmd_ide.c is broken for non ppc boards. The read/write functions does not add ATA base address, which causes failure. This patch solves that. It also contains a patch for shannon board that will be broken with this change. * Patch by Thomas Lange, 10 Oct 2003: fixes for ide on non ppc boards /Thomas diff -purN u-boot-0.4.8/common/cmd_ide.c u-boot-0.4.8_new/common/cmd_ide.c --- u-boot-0.4.8/common/cmd_ide.c 2003-07-01 23:07:07.000000000 +0200 +++ u-boot-0.4.8_new/common/cmd_ide.c 2003-10-09 00:06:50.000000000 +0200 @@ -42,8 +42,12 @@ #ifdef CONFIG_STATUS_LED # include <status_led.h> #endif -#ifdef __I386__ +#ifndef __PPC__ #include <asm/io.h> +#ifdef __MIPS__ +/* Macros depend on this variable */ +static unsigned long mips_io_port_base = 0; +#endif #endif #ifdef CONFIG_SHOW_BOOT_PROGRESS @@ -116,9 +120,8 @@ ulong ide_bus_offset[CFG_IDE_MAXBUS] = { #endif }; -#ifdef __PPC__ + #define ATA_CURR_BASE(dev) (CFG_ATA_BASE_ADDR+ide_bus_offset[IDE_BUS(dev)]) -#endif #ifndef CONFIG_AMIGAONEG3SE static int ide_bus_ok[CFG_IDE_MAXBUS]; @@ -763,7 +766,7 @@ ide_outb(int dev, int port, unsigned cha static void __inline__ ide_outb(int dev, int port, unsigned char val) { - outb(val, port); + outb(val, ATA_CURR_BASE(dev)+port); } #endif /* __PPC__ */ @@ -785,7 +788,7 @@ ide_inb(int dev, int port) static unsigned char __inline__ ide_inb(int dev, int port) { - return inb(port); + return inb(ATA_CURR_BASE(dev)+port); } #endif /* __PPC__ */ @@ -846,7 +849,7 @@ output_data(int dev, ulong *sect_buf, in static void output_data(int dev, ulong *sect_buf, int words) { - outsw(ATA_DATA_REG, sect_buf, words<<1); + outsw(ATA_CURR_BASE(dev)+ATA_DATA_REG, sect_buf, words<<1); } #endif /* __PPC__ */ @@ -870,7 +873,7 @@ input_data(int dev, ulong *sect_buf, int static void input_data(int dev, ulong *sect_buf, int words) { - insw(ATA_DATA_REG, sect_buf, words << 1); + insw(ATA_CURR_BASE(dev)+ATA_DATA_REG, sect_buf, words << 1); } #endif /* __PPC__ */ @@ -1420,14 +1423,14 @@ input_data_shorts(int dev, ushort *sect_ static void output_data_shorts(int dev, ushort *sect_buf, int shorts) { - outsw(ATA_DATA_REG, sect_buf, shorts); + outsw(ATA_CURR_BASE(dev)+ATA_DATA_REG, sect_buf, shorts); } static void input_data_shorts(int dev, ushort *sect_buf, int shorts) { - insw(ATA_DATA_REG, sect_buf, shorts); + insw(ATA_CURR_BASE(dev)+ATA_DATA_REG, sect_buf, shorts); } #endif /* __PPC__ */ diff -purN u-boot-0.4.8/include/configs/shannon.h u-boot-0.4.8_new/include/configs/shannon.h --- u-boot-0.4.8/include/configs/shannon.h 2002-11-03 19:03:56.000000000 +0100 +++ u-boot-0.4.8_new/include/configs/shannon.h 2003-10-08 23:45:24.000000000 +0200 @@ -204,13 +204,13 @@ #define CFG_ATA_BASE_ADDR CFG_PCMCIA_ATTRB_ADDR /* Offset for data I/O */ -#define CFG_ATA_DATA_OFFSET (CFG_ATA_BASE_ADDR) +#define CFG_ATA_DATA_OFFSET 0 /* Offset for normal register accesses */ -#define CFG_ATA_REG_OFFSET (CFG_ATA_BASE_ADDR) +#define CFG_ATA_REG_OFFSET 0 /* Offset for alternate registers */ -#define CFG_ATA_ALT_OFFSET (CFG_ATA_BASE_ADDR) +#define CFG_ATA_ALT_OFFSET 0 /*----------------------------------------------------------------------- */

2 1

[U-Boot-Users] Re: minor patch for u-boot
by Wolfgang Denk 09 Oct '03

09 Oct '03

In message <3F83826E.4080605(a)corelatus.com> you wrote: > > Since it only affects some comments, maybe you dont need to add it > to CHANGELOG? Indeed. > ------ > * Corrected old file location comments in common.h > ------ Thanks, added. Will show up on CVS soon. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de Uncertain fortune is thoroughly mastered by the equity of the calcu- lation. - Blaise Pascal

1 0