January 2003 - U-Boot

[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] Loading from a CF card on the PCMCIA interface A P atch
by Rod Boyce 20 May '03

20 May '03

All, I have figured out my problem and have created a patch file to patch the file part_doc.c. This patch allows the command diskboot command to read from a partition inside an extended partition. <<part_dos.tar.gz>> Regards, Rod Boyce.

2 1

Re: [U-Boot-Users] How To Use gdb w/ u-boot source tree
by Wolfgang Denk 29 Apr '03

29 Apr '03

In message <EGEGIJHKDKJGAJMGIDPNOEKACDAA.jwalden(a)digitalatlantic.com> Jerry Walden wrote: > > Sorry - I did not make myself clear - > Instead of using gdb as a command line debugger, I was hoping to > use an IDE style debugger that can show source (comments etc), so > I can do source level debugging. That does not make any difference, or does it? fro example, use DDD as GUI frontend with GDB - but it's still GDB that will actually perform the debugging, so why shoud it behave differently? [Please, keep the list Cc:ed for the benefit of other readers...] Best regards, and a Happy New Year! 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 Time is fluid ... like a river with currents, eddies, backwash. -- Spock, "The City on the Edge of Forever", stardate 3134.0

5 43

[U-Boot-Users] Problems with objcopy -O binary
by Bogdan Woldert-Jokisz 10 Apr '03

10 Apr '03

hi When I compile u-boot-0.3.0 then I have the following problem: ppc_405-ld -g -Ttext 0x40000 -o sched -e sched sched.o libsyscall.a ppc_405-objcopy -O srec sched sched.srec ppc_405-objcopy -O binary hello_world.srec hello_world.bin 2>/dev/null make[1]: *** [hello_world.bin] Error 1 make[1]: Leaving directory `/home/bwoldert/bootloader/u-boot-0.3.0/examples' make: *** [subdirs] Error 1 I found out: ppc_405-objcopy -O binary hello_world.srec hello_world.bin ppc_405-objcopy: Warning: Output file cannot represent architecture UNKNOWN! ppc_405-objcopy: hello_world.srec: Bad value When I delete hello_world from the Makefile, then I have the same problem with examples/sched.c. I compile on a i386. What's wrong? regards Bogdan

2 1

[U-Boot-Users] [PATCH]: tools/envcrc.c
by Laudney Ren 02 Mar '03

02 Mar '03

Hi, all: In u-boot-0.2.0, the file "tools/envcrc.c" failed to consider the difference between "normal env" and "redundand env". It is a very obvious error. Here is the patch: ====================================================================== --- old/u-boot-0.2.0/tools/envcrc.c Tue Dec 24 18:52:15 2002 +++ new/u-boot-0.2.0/tools/envcrc.c Wed Jan 15 15:56:48 2003 @@ -36,15 +36,32 @@ # ifndef CFG_ENV_OFFSET # define CFG_ENV_OFFSET (CFG_ENV_ADDR - CFG_FLASH_BASE) # endif +# if !defined(CFG_ENV_ADDR_REDUND) && defined(CFG_ENV_OFFSET_REDUND) +# define CFG_ENV_ADDR_REDUND (CFG_FLASH_BASE + CFG_ENV_OFFSET_REDUND) +# endif # ifndef CFG_ENV_SIZE # define CFG_ENV_SIZE CFG_ENV_SECT_SIZE # endif -# if ((CFG_ENV_ADDR >= CFG_MONITOR_BASE) && \ - ((CFG_ENV_ADDR+CFG_ENV_SIZE) <= (CFG_MONITOR_BASE + CFG_MONITOR_LEN))) -# define ENV_IS_EMBEDDED +# if defined(CFG_ENV_ADDR_REDUND) && !defined(CFG_ENV_SIZE_REDUND) +# define CFG_ENV_SIZE_REDUND CFG_ENV_SIZE +# endif +# if (CFG_ENV_ADDR >= CFG_MONITOR_BASE) && \ + (CFG_ENV_ADDR+CFG_ENV_SIZE) <= (CFG_MONITOR_BASE + CFG_MONITOR_LEN) +# define ENV_IS_EMBEDDED 1 +# endif +# if defined(CFG_ENV_ADDR_REDUND) || defined(CFG_ENV_OFFSET_REDUND) +# define CFG_REDUNDAND_ENVIRONMENT 1 # endif #endif /* CFG_ENV_IS_IN_FLASH */ +#ifdef CFG_REDUNDAND_ENVIRONMENT +# define ENV_HEADER_SIZE (sizeof(unsigned long) + 1) +#else +# define ENV_HEADER_SIZE (sizeof(unsigned long)) +#endif + +#define ENV_SIZE (CFG_ENV_SIZE - ENV_HEADER_SIZE) + extern unsigned long crc32 (unsigned long, const unsigned char *, unsigned int); #ifdef ENV_IS_EMBEDDED @@ -57,8 +74,8 @@ #ifdef ENV_IS_EMBEDDED int crc ; unsigned char *envptr = &environment, - *dataptr = envptr + sizeof(unsigned int) + 1; - unsigned int datasize = env_size - (dataptr - envptr) ; + *dataptr = envptr + ENV_HEADER_SIZE; + unsigned int datasize = ENV_SIZE ; crc = crc32(0, dataptr, datasize) ; -- An expert is one who knows more and more about less and less until he knows absolutely everything about nothing.

2 1

[U-Boot-Users] 8260 flash programming with BDI2000
by Donald White 02 Feb '03

02 Feb '03

Hi Group, About a year ago I ported ppcboot 1.0.5 and HHL 2.0 to a custom 860T board. I used a wiggler to support that work and to migrate the ppcboot to U-Boot. Today I was given a custom 8260 board and a BDI2000 with bdiGDB to use in porting U-Boot and HHL 2.0. I have installed the hardware and can talk to the board. Now here is my question. How do I use the BDI2000 to program flash? Do I just use the telnet interface and do: BDI>erase 0xfe000000 <step> <count> ;what is step? BDI>prog 0 u-boot.srec SREC ;assuming u-boot is based at 0xfe000000 I am having trouble understanding the meaning of the telnet commands. Should I just say I need bdiPro? Thanks, Don

3 3

RE: [U-Boot-Users] FW: Trying to program u-boot into flash using BDI2000
by brian.auld＠adic.com 01 Feb '03

01 Feb '03

I just switched to our second ebony and it worked. I was holding off using that box as we already had a functional VxWorks bootrom on it. Given that they appeared to be no clear answers, I figured it was worth swapping to see what would happen. ... and it passed. Woohoo. Sorry for red herring. --Brian -----Original Message----- From: brian.auld(a)adic.com [mailto:brian.auld@adic.com] Sent: Friday, January 31, 2003 6:06 PM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] FW: Trying to program u-boot into flash using BDI2000 For those who don't follow linuxppc-embedded, any ideas. I realized this list might be in a better position to answer this thread. Thanks, -- Brian -----Original Message----- From: brian.auld(a)adic.com [mailto:brian.auld@adic.com] Sent: Friday, January 31, 2003 6:01 PM To: linuxppc-embedded(a)lists.linuxppc.org Subject: RE: Trying to program u-boot into flash using BDI2000 Yep, I have these (peripheral bus setups) set as per the BDI config file. I'll go ahead and attach the whole thing instead of just [HOST] and [FLASH]. The default boot setup on Ebony is to use a 0.5MB chunk of flash at the very top of the memory map (0xfff80000 --> 0xffffffff). I also just realized that the u-boot.bin that I'm trying to load is 524788bytes. Given that 0.5MB is not exactly 500000bytes and is right around the 524788 number, is it that: (a) 0.5MB is not enough to hold the u-boot binary?? (b) u-boot is designed to fit like a glove into 0.5MB of flash. It sounds like too much of a coincidence to be right around the 524K number. Others that have installed u-boot/ppcboot into ebony/walnut flash, have the used the default top 0.5MB chunk or RAM, or did they have to change dip switches to achieve a configuration that provided a larger boot flash area?? -- Brian == ATTACHMENT OF FULL CONFIG FILE (WITH COMMENTS REMOVE FOR EASY READING == [INIT] ; Setup TLB WTLB 0xF0000095 0x1F00003F WTLB 0x00000098 0x0000003F ; Setup Peripheral Bus WDCR 0x12 0x00000010 WDCR 0x13 0x9B015480 WDCR 0x12 0x00000000 WDCR 0x13 0xFFF18000 ; Setup SDRAM Controller (DDR SDRAM) ; single-sided,non-buffered, 12x10(4), 128MB DIMM WDCR 0x10 0x00000082 WDCR 0x11 0x40000000 WDCR 0x10 0x00000080 WDCR 0x11 0x410A4012 WDCR 0x10 0x00000081 WDCR 0x11 0x8080082B WDCR 0x10 0x00000040 WDCR 0x11 0x000A4001 WDCR 0x10 0x00000030 WDCR 0x11 0x08200000 WDCR 0x10 0x00000020 WDCR 0x11 0x06000000 WDCR 0x11 0x86000000 [TARGET] JTAGCLOCK 1 CPUTYPE 440 BDIMODE AGENT BREAKMODE SOFT STEPMODE JTAG [HOST] IP 172.16.77.151 FILE u-boot.bin FORMAT BIN START 0xfff80000 LOAD MANUAL DEBUGPORT 2001 [FLASH] CHIPTYPE AM29F CHIPSIZE 0x80000 BUSWIDTH 8 WORKSPACE 0x000040000 FILE u-boot.bin FORMAT BIN 0x00000000 ERASE 0xFFF80000 ERASE 0xFFF90000 ERASE 0xFFFA0000 ERASE 0xFFFB0000 ERASE 0xFFFC0000 ERASE 0xFFFD0000 ERASE 0xFFFE0000 ERASE 0xFFFF0000 [REGS] IDCR1 0x010 0x011 IDCR2 0x012 0x013 IDCR3 0x014 0x015 IDCR4 0x016 0x017 FILE reg440gp.def ============================= END OF ATTACHMENT =========================== -----Original Message----- From: Chris Zimman [mailto:chris@cryptoapps.com] Sent: Friday, January 31, 2003 5:28 PM To: brian.auld(a)adic.com Subject: Re: Trying to program u-boot into flash using BDI2000 On Fri, Jan 31, 2003 at 01:18:32PM -0800, brian.auld(a)adic.com wrote: > > J39 is confirmed open (i.e. write enabled). Are the peripheral bus setups correct? These are what I was using ; Setup Peripheral Bus WDCR 0x12 0x00000010 ;Select EBC0_B0AP WDCR 0x13 0x9B015480 ;B0AP: Flash and SRAM WDCR 0x12 0x00000000 ;Select EBC0_B0CR WDCR 0x13 0xFFF18000 ;B0CR: 1MB at 0xFFF00000, r/w, 8bit --Chris > > -----Original Message----- > From: Chris Zimman [mailto:chris@cryptoapps.com] > Sent: Friday, January 31, 2003 3:05 PM > To: brian.auld(a)adic.com > Subject: Re: Trying to program u-boot into flash using BDI2000 > > On Fri, Jan 31, 2003 at 11:40:36AM -0800, brian.auld(a)adic.com wrote: > > Just as a first -- did you check the flash write protect jumper (J39)? > Should be open. > > --Chris > > > > > The embedded linux on ebony(440GP) saga continues: > > > > - ELDK in place (check) > > - kernel compiled (check) > > - u-boot compiled (check) > > - ebony in place (check ... dip switch settings confirmed) > > - BDI2000 in hand (arrived this morning) > > > > OK, I'm trying to program flash with u-boot (I'm using u-boot.bin). I am > > using the 440GP config file provided by abatron, plus the [FLASH] > parameters > > from the example in the bdiGDB users manual for programming flash on the > > 405. It looks like the memory map as it pertains to flash as well as the > > part (AMD29F040) was consistent from the 405 --> 440, so it seemed logical > > to use these FLASH values. The 440GP config file provided does not have > any > > FLASH parameters set, which is why I made this change. > > > > Well, I successfully erased the flash from 0xfff8000 - 0xffffffff and > > checked the locations after the erase ... they were all 'F's. I then tried > > to program the flash with my u-boot.bin and got the following: > > > > ===== start of bdi clip ===== > > BDI>prog 0xfff80000 u-boot.bin bin= > > Programming u-boot.bin , please wait .... > > # Programming flash memory failed at 0xfff80000 > > BDI>prog 0xfff80000 u-boot.bin bin > > Programming u-boot.bin , please wait .... > > # Programming flash memory failed at 0xfff80000 > > BDI> > > ===== end of bdi clip ===== > > > > Any ideas why this failed. Attached is my config file. I'll just attach > the > > [HOST] and [FLASH] sections to make it a little easier on the eyes. For > > anyone familiar with BDI sample 440GP confile file, you will see that it > is > > this file with the [FLASH] additions I mentioned above. Actually, after > > looking at the file, I remembered that I also trimmed information in the > > [HOST] section ... specifically stuff that was presuming path to Windows > > information. My host is Linux. > > > > ===== start of config file ([HOST] and [FLASH] sections) ===== > > ;bdiGDB configuration file for IBM 440GP Reference Board > > > > -- cut -- > > > > [HOST] > > IP 172.16.77.151 ;Linux host > > ;FILE u-boot.bin > > ;FORMAT BIN > > ;START 0x200000 > > LOAD MANUAL ;load code MANUAL or AUTO after reset > > DEBUGPORT 2001 > > DUMP dump.bin ;Linux: dump.bin must already exist and > > public writable > > > > [FLASH] > > CHIPTYPE AM29F ; flash part = AMD29F040B > > CHIPSIZE 0x80000 ;The size of one flash chip in bytes (0.5MB) > > BUSWIDTH 8 ;The width of the flash memory bus in bits (8 > | > > 16 | 32) > > WORKSPACE 0x000040000 ; RAM buffer for fast flash programming > > FILE u-boot.bin ;The file to program > > FORMAT BIN 0x00000000 > > ERASE 0xFFF80000 > > ERASE 0xFFF90000 > > ERASE 0xFFFA0000 > > ERASE 0xFFFB0000 > > ERASE 0xFFFC0000 > > ERASE 0xFFFD0000 > > ERASE 0xFFFE0000 > > ERASE 0xFFFF0000 > > > > -- cut -- > > > > ===== end of config file ( with cuts) ===== > > > > -- Brian > > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] FW: Trying to program u-boot into flash using BDI2000
by brian.auld＠adic.com 01 Feb '03

01 Feb '03

For those who don't follow linuxppc-embedded, any ideas. I realized this list might be in a better position to answer this thread. Thanks, -- Brian -----Original Message----- From: brian.auld(a)adic.com [mailto:brian.auld@adic.com] Sent: Friday, January 31, 2003 6:01 PM To: linuxppc-embedded(a)lists.linuxppc.org Subject: RE: Trying to program u-boot into flash using BDI2000 Yep, I have these (peripheral bus setups) set as per the BDI config file. I'll go ahead and attach the whole thing instead of just [HOST] and [FLASH]. The default boot setup on Ebony is to use a 0.5MB chunk of flash at the very top of the memory map (0xfff80000 --> 0xffffffff). I also just realized that the u-boot.bin that I'm trying to load is 524788bytes. Given that 0.5MB is not exactly 500000bytes and is right around the 524788 number, is it that: (a) 0.5MB is not enough to hold the u-boot binary?? (b) u-boot is designed to fit like a glove into 0.5MB of flash. It sounds like too much of a coincidence to be right around the 524K number. Others that have installed u-boot/ppcboot into ebony/walnut flash, have the used the default top 0.5MB chunk or RAM, or did they have to change dip switches to achieve a configuration that provided a larger boot flash area?? -- Brian == ATTACHMENT OF FULL CONFIG FILE (WITH COMMENTS REMOVE FOR EASY READING == [INIT] ; Setup TLB WTLB 0xF0000095 0x1F00003F WTLB 0x00000098 0x0000003F ; Setup Peripheral Bus WDCR 0x12 0x00000010 WDCR 0x13 0x9B015480 WDCR 0x12 0x00000000 WDCR 0x13 0xFFF18000 ; Setup SDRAM Controller (DDR SDRAM) ; single-sided,non-buffered, 12x10(4), 128MB DIMM WDCR 0x10 0x00000082 WDCR 0x11 0x40000000 WDCR 0x10 0x00000080 WDCR 0x11 0x410A4012 WDCR 0x10 0x00000081 WDCR 0x11 0x8080082B WDCR 0x10 0x00000040 WDCR 0x11 0x000A4001 WDCR 0x10 0x00000030 WDCR 0x11 0x08200000 WDCR 0x10 0x00000020 WDCR 0x11 0x06000000 WDCR 0x11 0x86000000 [TARGET] JTAGCLOCK 1 CPUTYPE 440 BDIMODE AGENT BREAKMODE SOFT STEPMODE JTAG [HOST] IP 172.16.77.151 FILE u-boot.bin FORMAT BIN START 0xfff80000 LOAD MANUAL DEBUGPORT 2001 [FLASH] CHIPTYPE AM29F CHIPSIZE 0x80000 BUSWIDTH 8 WORKSPACE 0x000040000 FILE u-boot.bin FORMAT BIN 0x00000000 ERASE 0xFFF80000 ERASE 0xFFF90000 ERASE 0xFFFA0000 ERASE 0xFFFB0000 ERASE 0xFFFC0000 ERASE 0xFFFD0000 ERASE 0xFFFE0000 ERASE 0xFFFF0000 [REGS] IDCR1 0x010 0x011 IDCR2 0x012 0x013 IDCR3 0x014 0x015 IDCR4 0x016 0x017 FILE reg440gp.def ============================= END OF ATTACHMENT =========================== -----Original Message----- From: Chris Zimman [mailto:chris@cryptoapps.com] Sent: Friday, January 31, 2003 5:28 PM To: brian.auld(a)adic.com Subject: Re: Trying to program u-boot into flash using BDI2000 On Fri, Jan 31, 2003 at 01:18:32PM -0800, brian.auld(a)adic.com wrote: > > J39 is confirmed open (i.e. write enabled). Are the peripheral bus setups correct? These are what I was using ; Setup Peripheral Bus WDCR 0x12 0x00000010 ;Select EBC0_B0AP WDCR 0x13 0x9B015480 ;B0AP: Flash and SRAM WDCR 0x12 0x00000000 ;Select EBC0_B0CR WDCR 0x13 0xFFF18000 ;B0CR: 1MB at 0xFFF00000, r/w, 8bit --Chris > > -----Original Message----- > From: Chris Zimman [mailto:chris@cryptoapps.com] > Sent: Friday, January 31, 2003 3:05 PM > To: brian.auld(a)adic.com > Subject: Re: Trying to program u-boot into flash using BDI2000 > > On Fri, Jan 31, 2003 at 11:40:36AM -0800, brian.auld(a)adic.com wrote: > > Just as a first -- did you check the flash write protect jumper (J39)? > Should be open. > > --Chris > > > > > The embedded linux on ebony(440GP) saga continues: > > > > - ELDK in place (check) > > - kernel compiled (check) > > - u-boot compiled (check) > > - ebony in place (check ... dip switch settings confirmed) > > - BDI2000 in hand (arrived this morning) > > > > OK, I'm trying to program flash with u-boot (I'm using u-boot.bin). I am > > using the 440GP config file provided by abatron, plus the [FLASH] > parameters > > from the example in the bdiGDB users manual for programming flash on the > > 405. It looks like the memory map as it pertains to flash as well as the > > part (AMD29F040) was consistent from the 405 --> 440, so it seemed logical > > to use these FLASH values. The 440GP config file provided does not have > any > > FLASH parameters set, which is why I made this change. > > > > Well, I successfully erased the flash from 0xfff8000 - 0xffffffff and > > checked the locations after the erase ... they were all 'F's. I then tried > > to program the flash with my u-boot.bin and got the following: > > > > ===== start of bdi clip ===== > > BDI>prog 0xfff80000 u-boot.bin bin= > > Programming u-boot.bin , please wait .... > > # Programming flash memory failed at 0xfff80000 > > BDI>prog 0xfff80000 u-boot.bin bin > > Programming u-boot.bin , please wait .... > > # Programming flash memory failed at 0xfff80000 > > BDI> > > ===== end of bdi clip ===== > > > > Any ideas why this failed. Attached is my config file. I'll just attach > the > > [HOST] and [FLASH] sections to make it a little easier on the eyes. For > > anyone familiar with BDI sample 440GP confile file, you will see that it > is > > this file with the [FLASH] additions I mentioned above. Actually, after > > looking at the file, I remembered that I also trimmed information in the > > [HOST] section ... specifically stuff that was presuming path to Windows > > information. My host is Linux. > > > > ===== start of config file ([HOST] and [FLASH] sections) ===== > > ;bdiGDB configuration file for IBM 440GP Reference Board > > > > -- cut -- > > > > [HOST] > > IP 172.16.77.151 ;Linux host > > ;FILE u-boot.bin > > ;FORMAT BIN > > ;START 0x200000 > > LOAD MANUAL ;load code MANUAL or AUTO after reset > > DEBUGPORT 2001 > > DUMP dump.bin ;Linux: dump.bin must already exist and > > public writable > > > > [FLASH] > > CHIPTYPE AM29F ; flash part = AMD29F040B > > CHIPSIZE 0x80000 ;The size of one flash chip in bytes (0.5MB) > > BUSWIDTH 8 ;The width of the flash memory bus in bits (8 > | > > 16 | 32) > > WORKSPACE 0x000040000 ; RAM buffer for fast flash programming > > FILE u-boot.bin ;The file to program > > FORMAT BIN 0x00000000 > > ERASE 0xFFF80000 > > ERASE 0xFFF90000 > > ERASE 0xFFFA0000 > > ERASE 0xFFFB0000 > > ERASE 0xFFFC0000 > > ERASE 0xFFFD0000 > > ERASE 0xFFFE0000 > > ERASE 0xFFFF0000 > > > > -- cut -- > > > > ===== end of config file ( with cuts) ===== > > > > -- Brian > > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

1 0

RE: [U-Boot-Users] Download of kernel Image through Serial Line.
by leeyang 30 Jan '03

30 Jan '03

> >- Minimum Flash Size if I don't use NFS ( full embeded application ) > > 4MB. For a resonable 'standard' Embedded Linux runtime > environment for PowerPC including basic network support > you need approx. the following space in Flash: > > U-Boot : 120 KB > Linux kernel : 600 KB > RAMDisk image : 1 MB > Root file-system on JFFS2: 2.5 MB My embedded fs are ppcboot+kernel+ramdisk(rootfs),However ramdisk will take 4.5M ram. I am going to switch to jffs2, but could you tell me the function of your 1M ramdisk? Would you please check http://lists.infradead.org/pipermail/linux-mtd/2003-January/006836.html and I state my situation there. Thank you! leeyang

2 1