June 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] Linux kernel crash in the early_init function
by llandre 28 Aug '03

28 Aug '03

I have a problem with U-Boot on the 405EP eval. board. Everything works fine until the kernel takes control and the system hangs: ------------------------------------------------------------------------------------ U-Boot 0.2.0 (May 6 2003 - 12:04:15) CPU: IBM PowerPC 405EP Rev. A at 266.666 MHz (PLB=133, OPB=66, EBC=66 MHz) PCI async ext clock used (sync mode not supported), internal PCI arbd 16 kB I-Cache 16 kB D-Cache Board: ### No HW ID - assuming WALNUT405 I2C: ready DRAM: 128 MB Top of RAM usable for U-Boot at: 08000000 Reserving 192k for U-Boot at: 07fd0000 Reserving 132k for malloc() at: 07faf000 Reserving 112 Bytes for Board Info at: 07faef90 Reserving 44 Bytes for Global Data at: 07faef64 Stack Pointer at: 07faef48 New Stack Pointer is: 07faef48 Now running in RAM - U-Boot at: 07fd0000 FLASH: 512 kB [board.c, 767] Calling env_relocate ... env_relocate[203] offset = 0x8050000 env_relocate[221] malloced ENV at 07faf008 In: serial Out: serial Err: serial KGDB: kgdb ready ready U-Boot relocated to 07fd0000 [board.c, 913] Calling interrupt_init ... ### main_loop entered: bootdelay=3 ### main_loop: bootcmd="tftpboot 0x400000 vmlinux.PPCBoot" Hit any key to stop autoboot: 0 ENET Speed is 10 Mbps - HALF duplex connection TX_BUFF 0 @ 0x07fb0228 RX_BUFF 0 @ 0x07ff3fc0 RX_BUFF 1 @ 0x07ff45c0 RX_BUFF 2 @ 0x07ff4bc0 RX_BUFF 3 @ 0x07ff51c0 Install interrupt for vector 9 ==> 07fd49c0 Install interrupt for vector 10 ==> 07fd49c0 Install interrupt for vector 11 ==> 07fd49c0 Install interrupt for vector 12 ==> 07fd49c0 Install interrupt for vector 13 ==> 07fd49c0 Install interrupt for vector 14 ==> 07fd49c0 Install interrupt for vector 15 ==> 07fd49c0 ARP broadcast 1 Got good ARP - start TFTP TFTP from server 192.168.10.6; our IP address is 192.168.10.203 Filename 'vmlinux.PPCBoot'. Load address: 0x400000 Loading: ################################################################# ######################################### done Bytes transferred = 539758 (83c6e hex) Automatic boot of image at addr 0x00400000 ... ## Booting image at 00400000 ... Image Name: Linux-2.4.21-pre5 Created: 2003-05-06 11:42:31 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 539694 Bytes = 527 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x07FAE5B8 => set upper limit to 0x00800000 ## cmdline at 0x007FFC00 ... 0x007FFC16 bd address = 0x07FAEF90 memstart = 0x00000000 memsize = 0x08000000 flashstart = 0xFFF80000 flashsize = 0x00080000 flashoffset = 0x00030000 sramstart = 0x00000000 sramsize = 0x00000000 bootflags = 0x6BBA3A55 procfreq = 266.666 MHz plb_busfreq = 133.333 MHz pci_busfreq = 33.333 MHz ethaddr = 00:50:C2:1E:AF:FE IP addr = 192.168.10.203 baudrate = 115200 bps No initrd ## Transferring control to Linux (at address 00000000) ... ------------------------------------------------------------------------------------ I found that the function memset_io, invoked by early_init, corrupts the memory region where the function identify_cpu is located. This is the disassembled produced by objdump: c0006774 <identify_cpu>: c0006774: 3d 03 c0 12 addis r8,r3,-16366 c0006778: 39 08 e1 40 addi r8,r8,-7872 c000677c: 7c ff 42 a6 mfpvr r7 c0006780: 80 a8 00 00 lwz r5,0(r8) c0006784: 7c a5 38 38 and r5,r5,r7 c0006788: 80 c8 00 04 lwz r6,4(r8) c000678c: 7c 06 28 40 cmplw r6,r5 c0006790: 41 82 00 0c beq- c000679c <identify_cpu+0x28> c0006794: 39 08 00 20 addi r8,r8,32 c0006798: 4b ff ff e8 b c0006780 <identify_cpu+0xc> c000679c: 3c c3 c0 14 addis r6,r3,-16364 c00067a0: 38 c6 f0 bc addi r6,r6,-3908 c00067a4: 54 84 10 3a rlwinm r4,r4,2,0,29 c00067a8: 7d 03 40 50 subf r8,r3,r8 c00067ac: 7d 04 31 2e stwx r8,r4,r6 c00067b0: 4e 80 00 20 blr This is what I see in memory before executing the memset_io: PPC405EP>go - TARGET: target has entered debug mode PPC405EP>md 0xc0006774 8 c0006774 : 0x3d03c012 1023655954 =... c0006778 : 0x3908e140 956883264 9..@ c000677c : 0x7cff42a6 2097103526 |.B. c0006780 : 0x80a80000 -2136473600 .... c0006784 : 0x7ca53838 2091202616 |.88 c0006788 : 0x80c80004 -2134376444 .... c000678c : 0x7c062840 2080778304 |.(@ c0006790 : 0x4182000c 1099038732 A... PPC405EP>go - TARGET: target has entered debug mode This is what I see in memory after executing the memset_io: PPC405EP>md 0xc0006774 8 c0006774 : 0xff03ffff - 16515073 .... c0006778 : 0xff08ffff - 16187393 .... c000677c : 0xff08ffff - 16187393 .... c0006780 : 0x80a80000 -2136473600 .... c0006784 : 0x7ca53838 2091202616 |.88 c0006788 : 0x80c80004 -2134376444 .... c000678c : 0x3c060840 1007028288 <..@ c0006790 : 0x7c062840 2080778304 |.(@ PPC405EP> Anybody have already seen something like that? Is it possible that this has to do with an erroneous cache initialization? Many thanks in advance. llandre

2 1

[U-Boot-Users] Booting MPC8266ads kernel
by Currie Reid 30 Jun '03

30 Jun '03

Hello, I am trying to find anyone who has had success in using u-boot to boot an MPC8266ads kernel to give me a pointer or 2 in the right direction. I have rsync'd the latest 2.4 development kernel from penguinppc.org as it contains the appropriate drivers etc. for the board and have u-boot running on the board now. However, when I tftp the kernel to the board and try to bootm, I get: Uncompressing Kernel Image ... OK and then no progress from there. Looking through the users list and the README file, I noticed that the the bd_info has to be the same between u-boot.h and the kernel's appropriate header file; there is also some recommendations with regards to the "clocks_in_mhz" option and the synchronization of IMAP_ADDR and CFG_IMMR. I have also built the kernel by hand using the system detailed in the u-boot README file, with the objcopy;gzip -9; mkimage, all to no avail. If anyone has any insight in this regard, I would very much appreciate it. Thanks in advance, Currie Reid ......................................................................... U-Boot 0.3.0 (Jun 15 2003 - 18:36:34) MPC8260 Reset Status: Check Stop, External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 3x, VCO Div 2, 60x Bus Freq 33-100, Core Freq 100-300 - dfbrg 0, corecnf 0x08, busdf 3, cpmdf 1, plldf 0, pllmf 1 - vco_out 266666664, scc_clk 66666666, brg_clk 66666666 - cpu_clk 199999998, cpm_clk 133333332, bus_clk 66666666 CPU: MPC8260 (Rev 14, Mask unknown [immr=0x0062,k=0x002d]) at 199.999 MHz Board: Motorola MPC8266ADS I2C: ready DRAM: SDRAM configuration read from SPD Size per side = 16MB Organization: 1 sides, 2 banks, 9 Columns, 11 Rows, Data width = 64 bits Refresh rate = 16, CAS latency = 3 Total size: 16 MB FLASH: 8 MB In: serial Out: serial Err: serial Net: FCC2 ETHERNET => tftp ARP broadcast 1 TFTP from server 47.129.82.27; our IP address is 47.129.82.129 Filename '/tftpboot/uImage.MPC8266'. Load address: 0x100000 Loading: ################################################################# ################################################ done Bytes transferred = 575660 (8c8ac hex) => printenv bootdelay=5 serial#=MCP8266ADS-PCI 0210 ethaddr=4A:DC:16:9D:37:D8 baudrate=57600 hostname=pcary3h5 bootfile=/tftpboot/uImage.MPC8266 rootpath=/export/47.129.82.129 filesize=8c8b0 gatewayip=47.129.82.1 netmask=255.255.255.0 ipaddr=47.129.82.129 serverip=47.129.82.27 bootargs=root=/dev/nfs rw nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off stdin=serial stdout=serial stderr=serial clocks_in_mhz=1 => bootm ## Booting image at 00100000 ... Image Name: Linux 2.4.21 - MPC8266ads Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 575596 Bytes = 562.1 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK

1 0

[U-Boot-Users] soft_i2c and ds1307 with tqm823l
by Seb James 30 Jun '03

30 Jun '03

Hi, I'm working on getting a ds1307 realtime clock working with a tqm823l as a new user to u-boot (I've never compiled u-boot or ppcboot before). I'd like to make some improvements to the README which is already excellent but seems to have a couple of omissions, particularly regarding the configuration of u-boot to work with i2c. Firstly, the ds1307 code compiles fine, but of course it needs the i2c code to be compiled alongside it. Although this is obvious, the newcomer to u-boot doesn't (i.e. I didn't) know that calling for ds1307.c to be compiled doesn't in itself cause the i2c code to be compiled, so a note to this effect in the realtime clock section of the README would be a helpful addition. Now, in trying to get I2C properly compiled, I find quite a lot of information about I2C setup in the README. Here's a line from the README (starting at line 907): "If this is selected, either CONFIG_HARD_I2C or CONFIG_SOFT_I2C must be defined to include the appropriate I2C driver." No mention is made of what values the 'appropriate driver' might have or where to look for them. I assume you might define something like this: #define CONFIG_HARD_I2C mpc8xx But I can't see what you'd write for CONFIG_SOFT_I2C. A bit more clarification here would be useful. There are a number of extra defines related to CONFIG_SOFT_I2C, such as I2C_INIT, I2C_PORT, etc. It's not too clear what these should be set to. The diff between my TQM823L.h and the original TQM823L.h is (also attached as changes.diff): Some investigation has shown that I need to set I2C_SDA and I2C_SCL to the name of the correct functions. What are the possibilities for these? The same seems to be true of I2C_READ. What are the units for I2C_DELAY? I'm assuming seconds. Why is there both I2C_DELAY and CFG_I2C_SPEED to configure? These seem to configure the same thing - the speed of the I2C clock line. Ok, I think that should be enough for now, best regards, Seb James.

2 9

Re : [U-Boot-Users] SPI + SCC problem
by Yigit Can 30 Jun '03

30 Jun '03

Yes, I have enabled it, but it makes no difference. Is this a bug ? > ----- Original Message ----- > From: "Wolfgang Denk" <wd(a)denx.de> > To: "Yigit Can" <yigit.can(a)karel.com.tr> > Cc: <u-boot-users(a)lists.sourceforge.net> > Sent: Friday, June 27, 2003 5:26 PM > Subject: Re: [U-Boot-Users] SPI + SCC problem > > > > In message <008c01c33cb2$613a6cd0$3002a8c0@yigitcan> you wrote: > > > > > > but when I use the SPI driver with Tqm850L (configured as SCC2 by > > > default ) it does not receive any byte. The problem i found is the SCC > > > controllers > > > when i select SCC1 from make menu screen my driver works but ethernet > > > fails. > > > I must use ethernet for my applications. > > > > Did you enable the uCode patch? > > > > > > 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 > > Q: How do you spell "onomatopoeia"? > > A: The way it sounds. > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: INetU > > Attention Web Developers & Consultants: Become An INetU Hosting Partner. > > Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! > > INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php > > _______________________________________________ > > U-Boot-Users mailing list > > U-Boot-Users(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/u-boot-users > > >

3 12

[U-Boot-Users] Global Data area
by Robin Gilks 30 Jun '03

30 Jun '03

Greetings I'm just getting porting U-boot to (yet another) board but I'm not sure I understand how the Global Data area works. When still running from Flash, the Init_sequence list of functions is called and several of them write to the gd (clock rate & baudrate for example) but I thought this structure was in Flash. Is it in fact in RAM (i.e. the internal dual port RAM thats used during boot) in which case where is it initialised (or is it done on the fly?) I was expecting something built from the #defines in the board specific config file but not found it so far!! Just that I'm getting hung up in the first serial TX (display_info) and I'm guessing that the clocks to the SMC block are not getting set up correctly. -- Robin Gilks Senior Design Engineer Phone: (+64)(3) 357 1569 Tait Electronics Fax : (+64)(3) 359 4632 PO Box 1645 Christchurch Email : robin.gilks(a)tait.co.nz New Zealand

2 1

[U-Boot-Users] WARNING: use version 0.4.0, not top of CVS!
by Wolfgang Denk 29 Jun '03

29 Jun '03

Hello Everybody, I am right now checking in a couple of modifications to the CVS server which have not been completely tested yet. This is work in progress, and will probably break on most boards. Also, the user interface is (temporarily) different (no abbreviated command names). If you need a running system, please stick with the latest officially released version (CVS tag U-Boot-0_4_0) for the next few days while we clean up the mess. For the adventuresome of you: you are welcome if you want to help testing. The U-Boot command structure is now kept in a separate linker section. One reason to do that is to allow that standalone applications will be able to define their own commands and link these into U-Boots command table. 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 An Elephant is a mouse with an Operating System. - Knuth

1 1

[U-Boot-Users] Ethernet Address
by Dhanuka, Anupam 28 Jun '03

28 Jun '03

Hi When I first started up my board (ebony) with u-boot, I set the Ethernet address incorrectly. Instead of using the colon format (00:04:ac:e3:1c:4c) I entered the hex values all together(0004ace31c4c). So I think now the Ethernet address environment variable is permanently wrong. When I use the command bdi it says ethhaddr = 4c:00:00:00:00:00. Is there a way to fix this, may be by using the JTAG hardware debugger or something? Please help. Anupam This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.

2 1

[U-Boot-Users] FADS and ICU862 Environment problems
by Nye Liu 27 Jun '03

27 Jun '03

The current FADS code does not seem to restore the environment properly, and i can't figure out what it SHOULD do. Right now, relocate_code only relocates up to the end of text (_init_end), and since CFG_MONITOR_BASE + CONFIG_MONITOR_LEN is after CFG_ENV_ADDR, ENV_IS_EMBEDDED is set. Since ENV_IS_EMBEDDED is set, env_reloca_spec in flash.c does NOT memcpy(env_addr,CFG_ENV_ADDR,CFG_ENV_SIZE). There are several refereces to environment[] in start.S that are ifdefed out if CONFIG_FADS or CONFIG_ICU862, which don't look right. My fix is to remove those ifdefs, and make sure that ENV_IS_EMBEDDED is NOT set by reducing CFG_MONITOR_LEN to not include the environment. What is the correct behavior? TIA -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

3 23

RE: [U-Boot-Users] uploading OS over network instead of u-boot do wnloading it from a server.
by mvincent＠systemem.com 27 Jun '03

27 Jun '03

Hello Wolfgang, Charles. Sorry to jump in uninvited. I have been following this list for a while and this topic is particularly important to me so I thought I would add my 2 Pfennig's worth... > > This whole discussion may not be appropriate on this list. > I don't think so. It may be beneficial to many people, one way or > another. To be honest, the idea of running a server on the target > never even crossed my mind before. It is always a good thing to > discuss alternative solutions - and if it's only to come to the > conclusion that everything was done correctly :-) Background: I designed a MPC8250 board with both WiFi and GPRS onboard (plus serial, Ethernet and other goodies) and I am currently working on the bootloader and OS ports. When I mentionned that I wanted to use U-Boot, I was asked if it would be possible to upload new firmware/config/etc over the wireless links. The expectation is that whoever is handling this update wants to "push" it, ie. initiate it remotely (which is easier in our case since the hardware is meant to be installed in vehicles). My answer was that wireless links should be established only by the OS (Linux kernel and utilities in this case), not by the KISS bootloader. But more importantly, once you have a full OS running with spare memory and CPU cycles, it should not be a problem to run the standard servers (telnet, ftp...) that let you remotely manage anything that's on the filesystem, right? If security is a concern (it is for us), you can again rely on open standards such as SSH to secure your links. My point is I like Wolfgang's approach: keep the U-Boot simple (uhmmmm, a bit late for that! ;^) ), using standard protocols only, and primarily make it serve the developpers well. Of course, some people have special requirements (not enough flash...) that force them to boot from Ethernet, others may have a problem with BOOTP/DHCP, and some may simply have a different perspective. It's an open discussion. For the record, I have done my fair share of proprietary protocols, bootloaders and download utilities, and I don't care if I never have the "chance" to do another one! Heartfelt THANK YOU to all the contributors to U-Boot! Best regards, Marc Vincent ps: I apologize if you received this twice. My first attempt bounced on SF and I also goofed on the CC. I hate my mail setup...

1 0

RE: [U-Boot-Users] U-Boot-0.4.0 released
by Karoliya, Abhishek 27 Jun '03

27 Jun '03

Hi Wolfgang, I am trying to retrieve the code from the cvs with the tag "U-Boot-0_4_0" but this is what I got cvs [server aborted]: no such tag U-Boot-0_4_0 what am i missing???? Abhi -----Original Message----- From: Wolfgang Denk [mailto:wd@denx.de] Sent: Friday, 27 June 2003 1:44 PM To: u-boot-users(a)lists.sourceforge.net Cc: ppcboot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] U-Boot-0.4.0 released A new version of U-Boot has been released. It is named U-Boot-0.4.0 and tagged as "U-Boot-0_4_0" on the CVS server. A tarball is available at ftp://ftp.denx.de/pub/u-boot/u-boot-0.4.0.tar.bz2 Major news: * New boards: A3000, RMU, TQM862L, TQM8xxM, MIP405T, RBC823, PPC405EP, ASH405, BUBINGA405EP, CPCI405AB, PMC405, MIP405-3, ATC, GEN860_SC, TQM8255 * New processors: IBM 750FX, Atmel AT91RM9200DK, Intel PXA * Header file cleanup * Support for FAT filesystems * Support for MMC * Major reconstruction of networking code * Fix/extend nand flash support * Add splash-screen support ====================================================================== Changes for U-Boot 0.4.0: ====================================================================== * Patches by Robert Schwebel, 26 Jun 2003: - csb226 configuration updated - credits for logodl port updated - innokom configuration updated - logodl tree update, still with coding style inconsistencies - added OCM for ppc405 warning to README * Patch by Pantelis Antoniou, 25 Jun 2003: update NetVia with V2 board support * Header file cleanup for ARM * Patch by Murray Jensen, 24 Jun 2003: - make sure to use only U-boot provided header files - fix problems with ".rodata.str1.4" section as used by GCC-3.x * Patch by Stefan Roese, 24 Jun 2003: - Update esd ASH405 board files. - Update esd DASA_SIM config file. - Add ping command to some esd boards. * Patch by Yuli Barcohen, 23 Jun 2003: Update for MPC8260ADS board * Patch by Murray Jensen, 23 Jun 2003: - cleanup of GCC 3.x compiler warnings * Patch by Rune Torgersen, 4 Jun 2003: add large memory support for MPC8266ADS board * Patch by Richard Woodruff, 19 June 03: - Enabled standard u-boot device abstraction for ARM - Enabled console device for ARM - Initilized bi_baudrate for ARM * Patch by Bill Hargen, 23 Apr 2003: fix byte order for 824x I2C addresses (write op) * Patch by Murray Jensen, 20 Jun 2003: - hymod update - cleanup (especially for gcc-3.x compilers) * Patch by Tom Guilliams, 20 Jun 2003: added CONFIG_750FX support for IBM 750FX processors * Patch by Devin Crumb, 02 Apr 2003: Fix clock divider rounding problem in drivers/serial.c * Patch by Richard Woodruff, 19 June 03: - Fixed smc91c111 driver to sync with the u-boot environment (driver/smc91c111.c). - Added eth_init error return check in NetLoop (net/net.c). * Patch by Ken Chou, 19 June 2003: Added support for A3000 SBC board (Artis Microsystems Inc.) * Patches by Murray Jensen, 17 Jun 2003: - Hymod board database mods: add "who" field and new xilinx chip types - provide new "init_cmd_timeout()" function so code external to "common/main.c" can use the "reset_cmd_timeout()" function before entering the main loop - add DTT support for adm1021 (new file dtt/adm1021.c; config slightly different. see include/configs/hymod.h for an example (requires CONFIG_DTT_ADM1021, CONFIG_DTT_SENSORS, and CFG_DTT_ADM1021 defined) - add new "eeprom_probe()" function which has similar args and behaves in a similar way to "eeprom_read()" etc. - add 8260 FCC ethernet loopback code (new "eth_loopback_test()" function which is enabled by defining CONFIG_ETHER_LOOPBACK_TEST) - gdbtools copyright update - ensure that set_msr() executes the "sync" and "isync" instructions after the "mtmsr" instruction in cpu/mpc8260/interrupts.c - 8260 I/O ports fix: Open Drain should be set last when configuring - add SIU IRQ defines for 8260 - allow LDSCRIPT override and OBJCFLAGS initialization: change to config.mk to allow board configurations to override the GNU linker script, selected via the LDSCRIPT, make variable, and to give an initial value to the OBJCFLAGS make variable - 8260 i2c enhancement: o correctly extends the timeout depending on the size of all queued messages for both transmit and receive o will not continue with receive if transmit times out o ensures that the error callback is done for all queued tx and rx messages o correctly detects both tx and rx timeouts, only delivers one to the callback, and does not overwrite an earlier error o logic in i2c_probe now correct - add "vprintf()" function so that "panic()" function can be technically correct - many Hymod board changes * Patches by Robert Schwebel, 14 Jun 2003: - add support for Logotronic DL datalogger board - cleanup serial line after kermit binary download - add debugX macro (debug level support) - update mach-types.h to latest arm.linux.org.uk master list. * Patches by David Müller, 12 Jun 2003: - rewrite of the S3C24X0 register definitions stuff - "driver" for the built-in S3C24X0 RTC * Patches by Yuli Barcohen, 12 Jun 2003: - Add MII support and Ethernet PHY initialization for MPC8260ADS board - Fix incorrect SIUMCR initialisation caused by wrong Hard Reset configuration word supplied by FPGA on some MPC8260ADS boards * Patch by Pantelis Antoniou, 10 Jun 2003: Unify status LED interface * Add support for DS12887 RTC; add RTC support for ATC board * Patch by Nicolas Lacressonniere, 11 Jun 2003: Modifications for Atmel AT91RM9200DK ARM920T based development kit - Add Atmel DataFlash support for reading and writing. - Add possibility to boot a Linux from DataFlash with BOOTM command. - Add Flash detection on Atmel AT91RM9200DK (between Atmel AT49BV1614 and AT49BV1614A flashes) - Replace old Ethernet PHY layer functions - Change link address * Patch by Frank Smith, 9 Jun 2003: use CRIT_EXCEPTION for machine check on 4xx * Patch by Detlev Zundel, 13 Jun 2003: added implementation of the "carinfo" command in cmd_immap.c * Fix CONFIG_NET_MULTI support in include/net.h * Patches by Kyle Harris, 13 Mar 2003: - Add FAT partition support - Add command support for FAT - Add command support for MMC ---- - Add Intel PXA support for video - Add Intel PXA support for MMC ---- - Enable MMC and FAT for lubbock board - Other misc changes for lubbock board * Patch by Robert Schwebel, April 02, 2003: fix for SMSC91111 driver * Patch by Vladimir Gurevich, 04 Jun 2003: make ppc405 ethernet driver compatible with CONFIG_NET_MULTI option * Patch by Stefan Roese, 05 Jun 2003: - PPC4xx: Fix bug for initial stack in data cache as pointed out by Thomas Schaefer (tschaefer(a)giga-stream.de). Now inital stack in data cache can be used even if the chip select is in use. - CFG_RX_ETH_BUFFER added to set the ethernet receive buffer count (see README for further description). - Changed config files of CONFIG_EEPRO100 boards to use the CFG_RX_ETH_BUFFER define. * Add support for RMU board * Add support for TQM862L at 100/50 MHz * Patch by Pantelis Antoniou, 02 Jun 2003: major reconstruction of networking code; add "ping" support (outgoing only!) * Patch by Denis Peter, 04 June 2003: add support for the MIP405T board * Patches by Udi Finkelstein, 2 June 2003: - Added support for custom keyboards, initialized by defining a board-specific drv_keyboard_init as well as defining CONFIG_KEYBOARD . - Added support for the RBC823 board. - cpu/mpc8xx/lcd.c now automatically calculates the Horizontal Pixel Count field. * Fix alignment problem in BOOTP (dhcp_leasetime option) [pointed out by Nicolas Lacressonnière, 2 Jun 2003] * Patch by Mark Rakes, 14 May 2003: add support for Intel e1000 gig cards. * Patch by Nye Liu, 3 Jun 2003: fix critical typo in MAMR definition (include/mpc8xx.h) * Fix requirement to align U-Boot image on 16 kB boundaries on PPC. * Patch by Klaus Heydeck, 2 Jun 2003 Minor changes for KUP4K configuration * Patch by Marc Singer, 29 May 2003: Fixed rarp boot method for IA32 and other little-endian CPUs. * Patch by Marc Singer, 28 May 2003: Added port I/O commands. * Patch by Matthew McClintock, 28 May 2003 - cpu/mpc824x/start.S: fix relocation code when booting from RAM - minor patches for utx8245 * Patch by Daniel Engström, 28 May 2003: x86 update * Patch by Dave Ellis, 9 May 2003 + 27 May 2003: add nand flash support to SXNI855T configuration fix/extend nand flash support: - fix 'nand erase' command so does not erase bad blocks - fix 'nand write' command so does not write to bad blocks - fix nand_probe() so handles no flash detected properly - add doc/README.nand - add .jffs2 and .oob options to nand read/write - add 'nand bad' command to list bad blocks - add 'clean' option to 'nand erase' to write JFFS2 clean markers - make NAND read/write faster * Patch by Rune Torgersen, 23 May 2003: Update for MPC8266ADS board * Get (mostly) rid of CFG_MONITOR_LEN definition; compute real length instead CFG_MONITOR_LEN is now only used to determine _at_compile_ _time_ (!) if the environment is embedded within the U-Boot image, or in a separate flash sector. * Cleanup CFG_DER #defines in config files (wd maintained only) * Fix data abort exception handling for arm920t CPU * Fix alignment problems with flash driver for TRAB board * Patch by Donald White, 21 May 2003: fix calculation of base address in pci_hose_config_device() * Fix bug in command line parsing: "cmd1;cmd2" is supposed to always execute "cmd2", even if "cmd1" fails. Note that this is different to "run var1 var2" where the contents of "var2" will NOT be executed when a command in "var1" fails. * Add zero-copy ramdisk support (requires corresponding kernel support!) * Patch by Kyle Harris, 20 May 2003: In preparation for an ixp port, rename cpu/xscale and arch-xscale into cpu/pxa and arch-pxa. * Patch by Stefan Roese, 23 May 2003: - IBM PPC405EP port added. - CONFIG_UART1_CONSOLE added. If defined internal UART1 (and not UART0) is used as default U-Boot console. PPC4xx only! - esd ASH405 board added (PPC405EP based). - BUBINGA405EP board added (PPC405EP based - IBM Eval Board). - esd CPCI405AB board added. - esd PMC405 board added. - Update of some esd boards. * Patch by Denis Peter, 19 Mai 2003: add support for the MIP405-3 board * Patch by Dave Ellis, 22 May 2003: Fix problem with only partially cleared .bss segment * Patch by Rune Torgersen, 12 May 2003: get PCI to work on a MPC8266ADS board; incorporate change to cpu/mpc8260/pci.c to enable overrides of PCI memory parameters * Patch by Nye Liu, 1 May 2003: minor patches for the FADS8xx * Patch by Thomas Schäfer, 28 Apr 2003: Fix SPD handling for 256 ECC DIMM on Walnut * Add support for arbitrary bitmaps for TRAB's VFD command; allow to pass boot bitmap addresses in environment variables; allow for zero boot delay * Patch by Christian Geißinger, 19 May 2002: On TRAB: wait until the dummy byte has been completely sent * Patch by David Updegraff, 22 Apr 2003: update for CrayL1 board * Patch by Pantelis Antoniou, 21 Apr 2003: add boot support for ARTOS (a proprietary OS) * Patch by Steven Scholz, 11 Apr 2003: Add support for RTC DS1338 * Patch by Rod Boyce, 24 Jan 2003: Fix counting of extended partitions in diskboot command * Patch by Christophe Lindheimer, 20 May 2003: allow the use of CFG_LOADS when CFG_NO_FLASH is set * Fix SDRAM timing on Purple board * Add support for CompactFlash on ATC board (includes support for Intel 82365 and compatible PC Card controllers, and Yenta-compatible PCI-to-CardBus controllers) * Patch by Mathijs Haarman, 08 May 2003: Add lan91c96 driver (tested on Lubbock and custom PXA250 board only) * Fix problem with usage of "true" (undefined in current versions of bfd.h) * Add support for Promess ATC board * Patch by Keith Outwater, 28 Apr 2003: - Miscellaneous corrections and additions to GEN860T board specific code. - Added GEN860_SC variant to GEN860T. - Miscellaneous corrections to GEN860T documentation. - Correct duplicate entry in U-Boot CREDITS file. - Add GEN860T_SC entry in MAINTAINERS file. - Update CREDITS file with GEN860T_SC info. * Update Smiths Aerospace addresses in MAINTAINERS file * Fix error handling in hush's version of "run" command * LWMON extensions: - Splashscreen support - modem support - sysmon support - temperature dependend enabling of LCD * Allow booting from old "PPCBoot" disk partitions * Add support for TQM8255 Board / MPC8255 CPU ====================================================================== 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 "How is this place run - is it an anarchy?" "No, I wouldn't say so; it is not that well organised..." ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

4 4

[U-Boot-Users] U-Boot-0.4.0 will not execute on my TQM8260-AG board
by Kim Engedahl 27 Jun '03

27 Jun '03

Hello everyone just bought the TQM8260-AG board (and STK82XX.100 starterkit). I have been trying to execute U-Boot-0.4.0 without any luck. It seems to get stuck during power up, i.e. no characters on the SMC ports (checked both to be sure). I have also tried to test the SMCTX/SMCRX pins with an oscilloscope - there is no activity. I started out with ppcboot-2.0.0 and experienced the same problem. With ppcboot however I was able to use a Lauterbach debugger in order to try and trace the problem. It seems that ppcboot enters an endless loop just after entering cpu_init_f during powerup. As far as I can figure out using the Lauterbach débugger (which I am absolutely no expert at) the loop has something to do with either an DebugException or ppcstring.o. I am using Red Hat 9.0, ELDK 2.0.0 and are compiling using the following syntax (taken from the Denx TQM8xxL guide as there is no guide available for the TQM8260 board): make distclean make TQM8260_300MHz_config make all I download the resulting srec file using protect 1234 erase 40000000 4001ffff load 0 f ..and then sends the srec file Mt TQM8260 board is the TQM8260-AG.204 board from TQM. Has anyone got this board to work with Denx Linux?? Any help would be appreciated Thanks Kim Engedahl

1 0

RE: [U-Boot-Users] uploading OS over network instead of u-boot do wnloading it from a server.
by Wells, Charles 27 Jun '03

27 Jun '03

Wolfgang, Sorry for the delay, but I've been unexpectedly out of the office. You make some good points that I'd like to address. >> 1. You are assuming that Brian's customers are at least as sophisticated as >> Abatron customers. Brian's original statement leads me to believe this is >> not so. > >Indeed I think they are. Typing "tftpsrv" (or which other ways there >are to start the supplied application "tftpsrv.exe") is IMHO no a big >challenge. And this is all you need to do. Typing "tftpd" or whatever is not what I'd worry about. Many systems are installed and operated these days by folks with very limited technical skills. The problem I see is that 6 months after installation the customer's MIS group makes network changes and the target device stops working. At this point, the operator needs to diagnose the problem and determine what needs to be done. No matter how trivial that act of typing "tftpd" is, the person diagnosing the problem must first determine that the trivial act is required. While this diagnosis task is not hard for programmers and consultants, it may be quite a challenge for the customer. Now, some might say that the appropriate thing to do in such a situation is to call MIS or the help desk. My experience with MIS departments is they do a good job of networking together Windows (or Solaris or Linux) boxes and printers, but they want nothing to do with other TCP/IP devices. The customer is on their own. I've seen this problem kill a project. Remember, the customer doesn't have to be embarrassed by the triviality of typing "tftpd", they can just switch to a competitor's product. They don't even have to give your sales person a reason. >> U-boot supports the target-as-client method of downloading but does not >> support the target-as-server method. I've used both methods a number of >> times over the years and both have their advantages and disadvantages. Your > >Can you please explain the advantages of the boot loader providing >server function? It is a unavoidable fact of standard client/server pairs that the client has a-priori knowledge about the server, the server has no a-priori knowledge about the client. If the target is a multicast server, there is NO NETWORK SETUP AT ALL. In the case of target-as-client, the client must know at least the server's IP address (or DNS name). That knowledge increases the amount of setup. Further, during the course of maintenance and expansion, this information may become invalid. You can make the required information as small as possible, but you have to go through the analysis to test whether this is acceptable to the customer. My experience is that making the amount of information used by the client (that can be unilaterally changed by the MIS department) nil is the best approach. The key to this is that my download server uses standard UDP over multicast IP. This has a number of advantages, including the fact that the download server is receive-only and has no traditional TCP/IP stack (I won't go into error control here, but that's taken care of as well). Another advantage is that this technique can be used very early in the manufacturing process to load the software (via UDP/IP) that programs the MAC address (as well as model and serial numbers) into EEPROM. When this software is loaded, the target has no IP address or MAC address. I can even load many units in parallel on a test rack. >U-Boot is a Boot Loader, not an OS. > >U-Boot shall be powerful to use, yet simple in design to make it >easily portable to new boards and architectures. > >This means U-Boot will be strictly single-tasking; it will not use >virtual memory; it will use polling drivers (versus interrupt driven >ones) whenever possible. > >U-Boot shall use standard protocols and interfaces whenever possible. My server-loader meets all of these criteria, except the "powerful to use" one. It is not only extremely simple in design but also extremely simple in implementation (which explains its small size of less than 8k). It only does two things, it loads programs in to memory and jumps to that program. Occum's razor seemed appropriate since we have to strongly avoid updating the boot code in the field. Note that my boot code does have a FLASH boot component that I haven't discussed here. <> Standard Protocols and Custom Clients My loader uses standard protocols as well. It uses UDP over multicast IP. Since I wanted a passive, receive-only server loader, I rejected TFTP early because it wouldn't solve all my problems. You mentioned in a subsequent email to Brian that he would have to write a custom client. You are quite correct. My version of this client is written as a command-line tool that does the following: 0) create a standard multicast UDP socket and bind it appropriately, 1) open a file for binary read, 2) read 1k blocks from the file, 3) prefix a small payload header, and 4) send the block to the socket. Since we already had a socket library, this task took an afternoon and the result was just 5-6 pages of C code. This client hasn't been maintained after it's original creation and testing (although it has been extended with new features; e.g., alternate binary file formats, etc.). It's one thing to say that you have found a boot loader (u-boot) and an operating system (Linux) for free off the web and made them work. In fact, this is very well received by many managers. But, I do have to develop my own embedded-target and host applications. For this I need programmers. The overhead of writing this custom client program (using standard protocols) was tiny compared to the entire project. Further, we were able to code this functionality into the host-based Visual Basic client used by our field reps. with very little effort. This is, I believe one of the features that Brian is thinking about. >I'm sorry, but IMHO there is no advantage running a server in the >boot loader. I'm sorry, but IMHO YHO is wrong. :-) >Perhaps you might be so kind as to elucidate. Perhaps I have. <> Summary Ultimately, I believe the difference in the two approaches is in where the control is. I prefer to view the host as "in control" and the target as subservient. It has simply been my experience, over many projects, that this way works out better. This whole discussion may not be appropriate on this list. Since I did this work as a paid employee, I must honor my employeer's policies that prevent sharing source code. I can, however, freely discuss the details and answer questions If Brian or anyone else cares to find out more about this technique, they are welcome to contact me directly. Regards, Charlie Charles.Wells(a)nielsenmedia.com c.wells(a)ieee.org

2 2

[U-Boot-Users] SPI + SCC problem
by Yigit Can 27 Jun '03

27 Jun '03

Hello, I have a problem with TQM850L module + starter kit I am using an SPI driver with Tqm862L board and it works fine this board (tqm862 ) is configured as SCC1 ethernet but when I use the SPI driver with Tqm850L (configured as SCC2 by default ) it does not receive any byte. The problem i found is the SCC controllers when i select SCC1 from make menu screen my driver works but ethernet fails. I must use ethernet for my applications. I have tried the simple driver coming from eldk and it fails too. is there any way to use both with TQM 850L module ? Thanks for your help. Yigit Can

2 1

[U-Boot-Users] Newbie: create arm linux kernel image problem, please help
by Zhao Hongda 27 Jun '03

27 Jun '03

I've been a user of armboot about 4 months, since it's replaced by u-boot, I try to use u-boot instead of armboot. But I cann't create a bootable uImage now, the error is: (my kernel is arm-linux-2.4.19-rmk7-pxa1, my platform is lubbock-pxa250) I create uImage like: make lubbock_config make oldconfig make dep make zImage mkimage -A arm -O linux -C none -T kernel -a 0xa0008000 -e 0xa0008000 -n "uImage" -d zImage uImage then start u-boot: erase 1:1-4 loadb 0xa0008000(send uImage) cp.b 0xa0008000 0x40000 0x100000 bootm 0x40000 then I got the error like: ... Starting kernel ... Uncompressing Linux........(prefetch abort or hangs) if I create uImage like: arm-linux-objcopy -O binary -R .note -R .comment -S vmlinux linux.bin gzip -9 linux.bin mkimage -A arm -O linux -C gzip -T kernel -a 0xa0008000 -e 0xa0008000 -n "uImage" -d linux.bin.gz uImage then I got the error like: ... Starting kernel ... (hangs) what should I do, please help. Hongda Zhao

1 0

[U-Boot-Users] U-Boot-0.4.0 released
by Wolfgang Denk 27 Jun '03

27 Jun '03

A new version of U-Boot has been released. It is named U-Boot-0.4.0 and tagged as "U-Boot-0_4_0" on the CVS server. A tarball is available at ftp://ftp.denx.de/pub/u-boot/u-boot-0.4.0.tar.bz2 Major news: * New boards: A3000, RMU, TQM862L, TQM8xxM, MIP405T, RBC823, PPC405EP, ASH405, BUBINGA405EP, CPCI405AB, PMC405, MIP405-3, ATC, GEN860_SC, TQM8255 * New processors: IBM 750FX, Atmel AT91RM9200DK, Intel PXA * Header file cleanup * Support for FAT filesystems * Support for MMC * Major reconstruction of networking code * Fix/extend nand flash support * Add splash-screen support ====================================================================== Changes for U-Boot 0.4.0: ====================================================================== * Patches by Robert Schwebel, 26 Jun 2003: - csb226 configuration updated - credits for logodl port updated - innokom configuration updated - logodl tree update, still with coding style inconsistencies - added OCM for ppc405 warning to README * Patch by Pantelis Antoniou, 25 Jun 2003: update NetVia with V2 board support * Header file cleanup for ARM * Patch by Murray Jensen, 24 Jun 2003: - make sure to use only U-boot provided header files - fix problems with ".rodata.str1.4" section as used by GCC-3.x * Patch by Stefan Roese, 24 Jun 2003: - Update esd ASH405 board files. - Update esd DASA_SIM config file. - Add ping command to some esd boards. * Patch by Yuli Barcohen, 23 Jun 2003: Update for MPC8260ADS board * Patch by Murray Jensen, 23 Jun 2003: - cleanup of GCC 3.x compiler warnings * Patch by Rune Torgersen, 4 Jun 2003: add large memory support for MPC8266ADS board * Patch by Richard Woodruff, 19 June 03: - Enabled standard u-boot device abstraction for ARM - Enabled console device for ARM - Initilized bi_baudrate for ARM * Patch by Bill Hargen, 23 Apr 2003: fix byte order for 824x I2C addresses (write op) * Patch by Murray Jensen, 20 Jun 2003: - hymod update - cleanup (especially for gcc-3.x compilers) * Patch by Tom Guilliams, 20 Jun 2003: added CONFIG_750FX support for IBM 750FX processors * Patch by Devin Crumb, 02 Apr 2003: Fix clock divider rounding problem in drivers/serial.c * Patch by Richard Woodruff, 19 June 03: - Fixed smc91c111 driver to sync with the u-boot environment (driver/smc91c111.c). - Added eth_init error return check in NetLoop (net/net.c). * Patch by Ken Chou, 19 June 2003: Added support for A3000 SBC board (Artis Microsystems Inc.) * Patches by Murray Jensen, 17 Jun 2003: - Hymod board database mods: add "who" field and new xilinx chip types - provide new "init_cmd_timeout()" function so code external to "common/main.c" can use the "reset_cmd_timeout()" function before entering the main loop - add DTT support for adm1021 (new file dtt/adm1021.c; config slightly different. see include/configs/hymod.h for an example (requires CONFIG_DTT_ADM1021, CONFIG_DTT_SENSORS, and CFG_DTT_ADM1021 defined) - add new "eeprom_probe()" function which has similar args and behaves in a similar way to "eeprom_read()" etc. - add 8260 FCC ethernet loopback code (new "eth_loopback_test()" function which is enabled by defining CONFIG_ETHER_LOOPBACK_TEST) - gdbtools copyright update - ensure that set_msr() executes the "sync" and "isync" instructions after the "mtmsr" instruction in cpu/mpc8260/interrupts.c - 8260 I/O ports fix: Open Drain should be set last when configuring - add SIU IRQ defines for 8260 - allow LDSCRIPT override and OBJCFLAGS initialization: change to config.mk to allow board configurations to override the GNU linker script, selected via the LDSCRIPT, make variable, and to give an initial value to the OBJCFLAGS make variable - 8260 i2c enhancement: o correctly extends the timeout depending on the size of all queued messages for both transmit and receive o will not continue with receive if transmit times out o ensures that the error callback is done for all queued tx and rx messages o correctly detects both tx and rx timeouts, only delivers one to the callback, and does not overwrite an earlier error o logic in i2c_probe now correct - add "vprintf()" function so that "panic()" function can be technically correct - many Hymod board changes * Patches by Robert Schwebel, 14 Jun 2003: - add support for Logotronic DL datalogger board - cleanup serial line after kermit binary download - add debugX macro (debug level support) - update mach-types.h to latest arm.linux.org.uk master list. * Patches by David Müller, 12 Jun 2003: - rewrite of the S3C24X0 register definitions stuff - "driver" for the built-in S3C24X0 RTC * Patches by Yuli Barcohen, 12 Jun 2003: - Add MII support and Ethernet PHY initialization for MPC8260ADS board - Fix incorrect SIUMCR initialisation caused by wrong Hard Reset configuration word supplied by FPGA on some MPC8260ADS boards * Patch by Pantelis Antoniou, 10 Jun 2003: Unify status LED interface * Add support for DS12887 RTC; add RTC support for ATC board * Patch by Nicolas Lacressonniere, 11 Jun 2003: Modifications for Atmel AT91RM9200DK ARM920T based development kit - Add Atmel DataFlash support for reading and writing. - Add possibility to boot a Linux from DataFlash with BOOTM command. - Add Flash detection on Atmel AT91RM9200DK (between Atmel AT49BV1614 and AT49BV1614A flashes) - Replace old Ethernet PHY layer functions - Change link address * Patch by Frank Smith, 9 Jun 2003: use CRIT_EXCEPTION for machine check on 4xx * Patch by Detlev Zundel, 13 Jun 2003: added implementation of the "carinfo" command in cmd_immap.c * Fix CONFIG_NET_MULTI support in include/net.h * Patches by Kyle Harris, 13 Mar 2003: - Add FAT partition support - Add command support for FAT - Add command support for MMC ---- - Add Intel PXA support for video - Add Intel PXA support for MMC ---- - Enable MMC and FAT for lubbock board - Other misc changes for lubbock board * Patch by Robert Schwebel, April 02, 2003: fix for SMSC91111 driver * Patch by Vladimir Gurevich, 04 Jun 2003: make ppc405 ethernet driver compatible with CONFIG_NET_MULTI option * Patch by Stefan Roese, 05 Jun 2003: - PPC4xx: Fix bug for initial stack in data cache as pointed out by Thomas Schaefer (tschaefer(a)giga-stream.de). Now inital stack in data cache can be used even if the chip select is in use. - CFG_RX_ETH_BUFFER added to set the ethernet receive buffer count (see README for further description). - Changed config files of CONFIG_EEPRO100 boards to use the CFG_RX_ETH_BUFFER define. * Add support for RMU board * Add support for TQM862L at 100/50 MHz * Patch by Pantelis Antoniou, 02 Jun 2003: major reconstruction of networking code; add "ping" support (outgoing only!) * Patch by Denis Peter, 04 June 2003: add support for the MIP405T board * Patches by Udi Finkelstein, 2 June 2003: - Added support for custom keyboards, initialized by defining a board-specific drv_keyboard_init as well as defining CONFIG_KEYBOARD . - Added support for the RBC823 board. - cpu/mpc8xx/lcd.c now automatically calculates the Horizontal Pixel Count field. * Fix alignment problem in BOOTP (dhcp_leasetime option) [pointed out by Nicolas Lacressonnière, 2 Jun 2003] * Patch by Mark Rakes, 14 May 2003: add support for Intel e1000 gig cards. * Patch by Nye Liu, 3 Jun 2003: fix critical typo in MAMR definition (include/mpc8xx.h) * Fix requirement to align U-Boot image on 16 kB boundaries on PPC. * Patch by Klaus Heydeck, 2 Jun 2003 Minor changes for KUP4K configuration * Patch by Marc Singer, 29 May 2003: Fixed rarp boot method for IA32 and other little-endian CPUs. * Patch by Marc Singer, 28 May 2003: Added port I/O commands. * Patch by Matthew McClintock, 28 May 2003 - cpu/mpc824x/start.S: fix relocation code when booting from RAM - minor patches for utx8245 * Patch by Daniel Engström, 28 May 2003: x86 update * Patch by Dave Ellis, 9 May 2003 + 27 May 2003: add nand flash support to SXNI855T configuration fix/extend nand flash support: - fix 'nand erase' command so does not erase bad blocks - fix 'nand write' command so does not write to bad blocks - fix nand_probe() so handles no flash detected properly - add doc/README.nand - add .jffs2 and .oob options to nand read/write - add 'nand bad' command to list bad blocks - add 'clean' option to 'nand erase' to write JFFS2 clean markers - make NAND read/write faster * Patch by Rune Torgersen, 23 May 2003: Update for MPC8266ADS board * Get (mostly) rid of CFG_MONITOR_LEN definition; compute real length instead CFG_MONITOR_LEN is now only used to determine _at_compile_ _time_ (!) if the environment is embedded within the U-Boot image, or in a separate flash sector. * Cleanup CFG_DER #defines in config files (wd maintained only) * Fix data abort exception handling for arm920t CPU * Fix alignment problems with flash driver for TRAB board * Patch by Donald White, 21 May 2003: fix calculation of base address in pci_hose_config_device() * Fix bug in command line parsing: "cmd1;cmd2" is supposed to always execute "cmd2", even if "cmd1" fails. Note that this is different to "run var1 var2" where the contents of "var2" will NOT be executed when a command in "var1" fails. * Add zero-copy ramdisk support (requires corresponding kernel support!) * Patch by Kyle Harris, 20 May 2003: In preparation for an ixp port, rename cpu/xscale and arch-xscale into cpu/pxa and arch-pxa. * Patch by Stefan Roese, 23 May 2003: - IBM PPC405EP port added. - CONFIG_UART1_CONSOLE added. If defined internal UART1 (and not UART0) is used as default U-Boot console. PPC4xx only! - esd ASH405 board added (PPC405EP based). - BUBINGA405EP board added (PPC405EP based - IBM Eval Board). - esd CPCI405AB board added. - esd PMC405 board added. - Update of some esd boards. * Patch by Denis Peter, 19 Mai 2003: add support for the MIP405-3 board * Patch by Dave Ellis, 22 May 2003: Fix problem with only partially cleared .bss segment * Patch by Rune Torgersen, 12 May 2003: get PCI to work on a MPC8266ADS board; incorporate change to cpu/mpc8260/pci.c to enable overrides of PCI memory parameters * Patch by Nye Liu, 1 May 2003: minor patches for the FADS8xx * Patch by Thomas Schäfer, 28 Apr 2003: Fix SPD handling for 256 ECC DIMM on Walnut * Add support for arbitrary bitmaps for TRAB's VFD command; allow to pass boot bitmap addresses in environment variables; allow for zero boot delay * Patch by Christian Geißinger, 19 May 2002: On TRAB: wait until the dummy byte has been completely sent * Patch by David Updegraff, 22 Apr 2003: update for CrayL1 board * Patch by Pantelis Antoniou, 21 Apr 2003: add boot support for ARTOS (a proprietary OS) * Patch by Steven Scholz, 11 Apr 2003: Add support for RTC DS1338 * Patch by Rod Boyce, 24 Jan 2003: Fix counting of extended partitions in diskboot command * Patch by Christophe Lindheimer, 20 May 2003: allow the use of CFG_LOADS when CFG_NO_FLASH is set * Fix SDRAM timing on Purple board * Add support for CompactFlash on ATC board (includes support for Intel 82365 and compatible PC Card controllers, and Yenta-compatible PCI-to-CardBus controllers) * Patch by Mathijs Haarman, 08 May 2003: Add lan91c96 driver (tested on Lubbock and custom PXA250 board only) * Fix problem with usage of "true" (undefined in current versions of bfd.h) * Add support for Promess ATC board * Patch by Keith Outwater, 28 Apr 2003: - Miscellaneous corrections and additions to GEN860T board specific code. - Added GEN860_SC variant to GEN860T. - Miscellaneous corrections to GEN860T documentation. - Correct duplicate entry in U-Boot CREDITS file. - Add GEN860T_SC entry in MAINTAINERS file. - Update CREDITS file with GEN860T_SC info. * Update Smiths Aerospace addresses in MAINTAINERS file * Fix error handling in hush's version of "run" command * LWMON extensions: - Splashscreen support - modem support - sysmon support - temperature dependend enabling of LCD * Allow booting from old "PPCBoot" disk partitions * Add support for TQM8255 Board / MPC8255 CPU ====================================================================== 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 "How is this place run - is it an anarchy?" "No, I wouldn't say so; it is not that well organised..."

1 0

[U-Boot-Users] Booting from 4MB flash on Walnut derived board
by Thomas Schäfer 27 Jun '03

27 Jun '03

Hi Brian, we are using a custom board based on IBM walnut with 8 MB flash. The following configuration settings work for us: TEXT_BASE = 0xFFF80000 #define CFG_SDRAM_BASE 0x00000000 #define CFG_FLASH_BASE 0xFF800000 #define CFG_MONITOR_BASE 0xFFF80000 /* the last two sectors for the bootloader */ #define CFG_MONITOR_LEN (256 * 1024) /* Reserve 256 kB for Monitor */ #define CFG_MALLOC_LEN (128 * 1024) /* Reserve 128 kB for malloc() */ #define FLASH_BASE0_PRELIM CFG_FLASH_BASE /* FLASH bank #0 */ u-boot must be located in the upper part of the flash because the jump instruction after reset must be within 2MB. CFG_FLASH_CFI is not set in our configuration. Best regards, Thomas Schäfer ____________________________________ GIGA STREAM - UMTS Technologies 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

1 0

[U-Boot-Users] Booting from 4MB flash on Walnut derived board
by Brian S. Park 27 Jun '03

27 Jun '03

Hi all, I have custom board built based on IBM walnut demo board. It worked well when I was using 512KB flash. Since I want to burn all my application on the flash, I installed 4MB flash and u-boot no longer works. According to README file, I should set CFG_FLASH_BASE, CFG_MONITOR_BASE and TEXT_BASE to the beginning of the flash. When I did this, the processor was not able to pick up the instruction on the beginning of the flash. Probably because the EBC is not configured to access 4MB of flash when it boots up. Is there a way to make it come up with 4MB of flash? I'm using u-Boot 0.3.0 I tried changing the CFG_FLASH_BASE only but I get bus error when u-Boot tries to access the flash. I did setup pb0cr so that it can access 4MB address space. U-Boot 0.3.0 (Jun 26 2003 - 19:43:08) CPU: IBM PowerPC 405GP Rev. E at 200 MHz (PLB=100, OPB=50, EBC=50 MHz) PCI sync clock at 100 MHz, external PCI arbiter enabled 16 kB I-Cache 8 kB D-Cache Board: ### No HW ID - assuming WALNUT405 I2C: ready DRAM: 128 MB FLASH: Bus Fault @ 0x07fd2954, fixup 0x00000000 Machine check in kernel mode. Caused by (from msr): regs 07fadd08 Machine check signal - probably due to mm ft with mmu off NIP: 07FD2954 XER: 00000000 LR: 07FD219C REGS: 07fadd08 TRAP: 0200 DAR: 00000800 MSR: 00001000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00 GPR00: 00000090 07FADDF8 40000000 07FADE08 07FF1194 00000000 00000000 0110795E GPR08: 07FD9C84 FFC00000 00000002 0000051C 28000004 00000000 07FEF300 08050000 GPR16: 00000000 00000000 00000000 00000000 00001000 07FADDF8 00000000 07FD219C GPR24: 07FD2954 07FADF64 07FADF90 07FF1194 07FADF90 07FADF64 07FF0110 0000FFFF Call backtrace: machine check Any help will be appreciated. Thank you. Brian =============================================================== Brian S. Park brian(a)corelis.com (562) 926-6727 x143 --------------------------------------------------------------- Everything we do helps our customers get to market FASTER with HIGHER quality and LOWER cost ===============================================================

2 2

[U-Boot-Users] U-boot debugging using BDI2000
by Dheeraj Kaushik 26 Jun '03

26 Jun '03

Dear Friends, I am working with a MBX860 board to which U-boot is already ported.But i am not getting the prompt.So,in order to look into the system, i want to debug it.as i went through the mailing list for ppcboot as well as u-boot i came to know that BDI2000 is of great help in that case.So, i purchsed one for us. Now can anybody help me how to go about using it. This is the way i proceeded....... Hardware setup...... BDI2000 is connected to the board through BDM port. System Setup RedHat 8.0 system with toolchain from www.denx.de System has sufficient memory and other resources.... the board directory has TEXT_BASE value defined as 0xfe000000......so i burned the u-boot image at this address in the boards flash using BDI2000. Here is the BDI config file........ ; bdiGDB configuration file for MBX860-001B / 50MHz board ; ------------------------------------------------------- ; [INIT] ; init core register WSPR 638 0xFA200000 ;IMMR: internal memory at 0xFA200000 WSPR 158 0x00000007 ;ICTRL: not serialized, no show cycles ; init SIU register WM32 0xFA200000 0x00612900 ;SIUMCR: WM32 0xFA200004 0xFFFFFF88 ;SYPCR: enable bus monitor, disable software watchdog WM16 0xFA200200 0x00C2 ;TBSCR: stop timebase and decrementer while freeze is asserted WM32 0xFA200320 0x55CCAA33 ;RTCSCK: unlock real-time clock status and control register WM32 0xFA200324 0x55CCAA33 ;RTCK: unlock real-Time clock register WM32 0xFA200328 0x55CCAA33 ;RTSECK: unlock real-time alarm seconds WM32 0xFA20032C 0x55CCAA33 ;RTCALK: unlock real-time alarm register WM16 0xFA200220 0x00C2 ;RTCSC: stop real-time clock while freeze is asserted WM16 0xFA200240 0x0082 ;PISCR: stop periodic interrupt while freeze is asserted WM32 0xFA200280 0x62000000 ;SCCR: disable clock output WM32 0xFA200284 0x0000D000 ;PLPRCR: clear flags ; init UPM SUPM 0xFA200168 0xFA20017C ;Set address for MCR and MDR WUPM 0x00000000 0xCFAFC004 ;UPM: singel read WUPM 0x00000001 0x0FAFC404 ;UPM: singel read WUPM 0x00000002 0x0CAF8C04 ;UPM: singel read WUPM 0x00000003 0x10AF0C04 ;UPM: singel read WUPM 0x00000004 0xF0AF0C00 ;UPM: singel read WUPM 0x00000005 0xF3BF4805 ;UPM: singel read WUPM 0x00000006 0xFFFFC005 ;UPM: singel read WUPM 0x00000007 0xFFFFC005 ;UPM: singel read WUPM 0x00000008 0xCFAFC004 ;UPMA burst read WUPM 0x00000009 0x0FAFC404 ;UPMA burst read WUPM 0x0000000A 0x0CAF8C04 ;UPMA burst read WUPM 0x0000000B 0x00AF0C04 ;UPMA burst read WUPM 0x0000000C 0x07AF0C08 ;UPMA burst read WUPM 0x0000000D 0x0CAF0C04 ;UPMA burst read WUPM 0x0000000E 0x01AF0C04 ;UPMA burst read WUPM 0x0000000F 0x0FAF0C08 ;UPMA burst read WUPM 0x00000010 0x0CAF0C04 ;UPMA burst read WUPM 0x00000011 0x01AF0C04 ;UPMA burst read WUPM 0x00000012 0x0FAF0C08 ;UPMA burst read WUPM 0x00000013 0x0CAF0C04 ;UPMA burst read WUPM 0x00000014 0x10AF0C04 ;UPMA burst read WUPM 0x00000015 0xF0AF0C00 ;UPMA burst read WUPM 0x00000016 0xF3BF4805 ;UPMA burst read WUPM 0x00000017 0xFFFFC005 ;UPMA burst read WUPM 0x00000018 0xCFFF0004 ;UPMA single write WUPM 0x00000019 0x0FFF0404 ;UPMA single write WUPM 0x0000001A 0x0CFF0C00 ;UPMA single write WUPM 0x0000001B 0x13FF4804 ;UPMA single write WUPM 0x0000001C 0xFFFFC004 ;UPMA single write WUPM 0x0000001D 0xFFFFC005 ;UPMA single write WUPM 0x0000001E 0xFFFFC005 ;UPMA single write WUPM 0x0000001F 0xFFFFC005 ;UPMA single write WUPM 0x00000020 0xCFFF0004 ;UPMA burst write WUPM 0x00000021 0x0FFF0404 ;UPMA burst write WUPM 0x00000022 0x0CFF0C00 ;UPMA burst write WUPM 0x00000023 0x03FF0C0C ;UPMA burst write WUPM 0x00000024 0x0CFF0C00 ;UPMA burst write WUPM 0x00000025 0x03FF0C0C ;UPMA burst write WUPM 0x00000026 0x0CFF0C00 ;UPMA burst write WUPM 0x00000027 0x03FF0C0C ;UPMA burst write WUPM 0x00000028 0x0CFF0C00 ;UPMA burst write WUPM 0x00000029 0x13FF4804 ;UPMA burst write WUPM 0x0000002A 0xFFFFC004 ;UPMA burst write WUPM 0x0000002B 0xFFFFC005 ;UPMA burst write WUPM 0x0000002C 0xFFFFC005 ;UPMA burst write WUPM 0x0000002D 0xFFFFC005 ;UPMA burst write WUPM 0x0000002E 0xFFFFC005 ;UPMA burst write WUPM 0x0000002F 0xFFFFC005 ;UPMA burst write WUPM 0x00000030 0xFCFFC004 ;UPMA refresh WUPM 0x00000031 0xC0FFC004 ;UPMA refresh WUPM 0x00000032 0x01FFC004 ;UPMA refresh WUPM 0x00000033 0x0FFFC004 ;UPMA refresh WUPM 0x00000034 0x1FFFC004 ;UPMA refresh WUPM 0x00000035 0xFFFFC004 ;UPMA refresh WUPM 0x00000036 0xFFFFC005 ;UPMA refresh WUPM 0x00000037 0xFFFFC005 ;UPMA refresh WUPM 0x00000038 0xFFFFC005 ;UPMA refresh WUPM 0x00000039 0xFFFFC005 ;UPMA refresh WUPM 0x0000003A 0xFFFFC005 ;UPMA refresh WUPM 0x0000003B 0xFFFFC005 ;UPMA refresh WUPM 0x0000003C 0xFFFFC007 ;UPMA exception WUPM 0x0000003D 0xFFFFC007 ;UPMA exception WUPM 0x0000003E 0xFFFFC007 ;UPMA exception WUPM 0x0000003F 0xFFFFC007 ;UPMA exception ; init memory controller WM32 0xFA200104 0xFFE00940 ;OR0: Flash 2MB, all accesses, CS early negate, 4ws WM32 0xFA200100 0xFE000001 ;BR0: Flash at 0xFE000000, 32bit, R/W, no parity, use GPCM WM32 0xFA20010C 0xFFC00400 ;OR1: DRAM 4MB, all accesses WM32 0xFA200108 0x00000081 ;BR1: DRAM at 0x00000000, 32bit, R/W, no parity, use UPMA WM32 0xFA200124 0xFFE00930 ;OR4: NVRAM WM32 0xFA200120 0xFA000401 ;BR4: NVRAM WM32 0xFA20012C 0xA0000108 ;OR5: PCI I/O and Memory WM32 0xFA200128 0x80000001 ;BR5: PCI I/O and Memory WM32 0xFA200134 0xFFFF0108 ;OR6: PCI Bus Bridge WM32 0xFA200130 0xFA210001 ;BR6: PCI Bus Bridge WM32 0xFA20013C 0xFF800940 ;OR7: 8bit socketed Flash WM32 0xFA200138 0xFC000401 ;BR7: 8bit socketed Flash WM16 0xFA20017A 0x0200 ;MPTPR : divide by 32 WM32 0xFA200170 0x18801000 ;MAMR : PTA=24 (15.36us @ 50MHz) ; Setup MMU info WSPR 796 0x00000000 ;M_TWB invalidate TWB WM32 0x000000f0 0x00000000 ;invalidate page table pointer pointer [TARGET] CPUCLOCK 50000000 ;the CPU clock rate after processing the init list BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT) BREAKMODE HARD ;SOFT or HARD, HARD uses PPC hardware breakpoints ;MMU XLAT ;translate effective to physical address [HOST] IP 196.1.105.112 ;FILE c:/cdotdelhi/prog1/fibo.elf ;FORMAT ELF ;LOAD MANUAL ;load code MANUAL or AUTO after reset [FLASH] WORKSPACE 0xFA202000 ;workspace in target RAM for fast programming algorithm CHIPTYPE AM29F ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16) CHIPSIZE 0x80000 ;The size of one flash chip in bytes (e.g. AM29F010 = 0x20000) ;BUSWIDTH 8 ;for 0xfc000000 ;FILE redboot_ROM.bin ;FORMAT BIN 0xfc000000 ;ERASE 0xfc000000 ;ERASE 0xfc010000 ;ERASE 0xfc020000 ;ERASE 0xfc030000 ;ERASE 0xfc040000 ;ERASE 0xfc050000 ;ERASE 0xfc060000 ;ERASE 0xfc070000 BUSWIDTH 32 ;The width of the flash memory bus in bits (8 | 16 | 32) FILE uboot.elf ; the file to program FORMAT ELF ERASE 0xFE000000 ;erase sector 0 of flash ERASE 0xFE040000 ;erase sector 1 of flash ERASE 0xFE080000 ;erase sector 2 of flash ERASE 0xFE0C0000 ;erase sector 3 of flash ERASE 0xFE100000 ;erase sector 4 of flash ERASE 0xFE140000 ;erase sector 5 of flash ERASE 0xFE180000 ;erase sector 6 of flash ERASE 0xFE1C0000 ;erase sector 7 of flash [REGS] DMM1 0xFA200000 FILE reg860.def BDI2000 is showing the image at right location. Now i want to debug u-boot. So this is my approach. bdi>bi 0xfe000000 bdi>go 0xfe000000 now at the host system $ppc_8xx-gdb u-boot gdb>target remote bdi:2001 Remote debugging using 196.1.105.162:2001 0xfe000000 in ??() at /u-boot/cpu/mpc8xx/start.S:97 97 _start: gdb>c Continuing. Program received signal signal SIGTRAP , Trace/breakpoint trap. 0xfe000000 in ??() at /u-boot/cpu/mpc8xx/start.S:97 97 _start: gdb> Can anybody help me HOW CAN A DEBUG THE U-BOOT IMAGE USING BDI2000.I want to single step through the code. Your help is highly appreciated. Best Regards Dheeraj Kaushik ===== Dheeraj Kaushik Research Engineer IMT-2000 Transmission Division C-DOT 39,Main Pusa Road, New Delhi-110005 Phone : +91-11-25763041,25753350-59 Ext. 301 Fax : +91-11-25756378 Mobile No. : +91-11-31088262 __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com

2 1

[U-Boot-Users] CVS access at sourceforge
by Robin Gilks 26 Jun '03

26 Jun '03

Greetings I've not used sourceforge for CVS accesss before - is it usually as slow and as likely to drop the connection as it appears to be today? I've not had this sort of problem with CVS (for example wine) before so not sure it its my route to the repository or just that sf is rubbish!! -- Robin Gilks Senior Design Engineer Phone: (+64)(3) 357 1569 Tait Electronics Fax : (+64)(3) 359 4632 PO Box 1645 Christchurch Email : robin.gilks(a)tait.co.nz New Zealand

2 1

Re: [U-Boot-Users] [PPCBoot-users] Using gcc-3.4 to compile u-boo t on powerpc
by Murray Jensen 26 Jun '03

26 Jun '03

On Tue, 24 Jun 2003 10:08:00 +1000, Vuong My-Hong <My-Hong.Vuong(a)au.thalesgroup.com> writes: >Hi Murray, > >Is there a similar fix for gcc 3.0.4? > >Thanks, My Hong Sorry, I wouldn't know. Here is a posting where this define was proposed (14 Dec 2001) ... http://gcc.gnu.org/ml/gcc-patches/2001-12/msg01678.html and here is a post where it was proposed that the define be turned off in "linux.h" (29 Jan 2003) ... http://gcc.gnu.org/ml/gcc-patches/2003-01/msg02345.html If the second is before gcc 3.0.4, then this fix will apply, otherwise you have some other problem. 3.0.4 sounds like a long time ago, so my guess would be "no (you could check in the gcc cvs). Cheers! Murray... -- Murray Jensen, CSIRO Manufacturing & Infra. Tech. Phone: +61 3 9662 7763 Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853 Internet: Murray.Jensen(a)csiro.au Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/ To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference. The information contained in this e-mail may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this e-mail in error, please delete it immediately and notify Murray Jensen on +61 3 9662 7763. Thank you.

1 0

Re: [U-Boot-Users] uploading OS over network instead of u-boot do wnloading it from a server.
by Wells, Charles 25 Jun '03

25 Jun '03

Wolfgang, I feel obliged to comment on your response to Brian's post. >> It won't be practical (support nightmare!) for us to ask our customers to >> setup a tftp server in order to use our product. > >What's so complicated about this? See for example how Abatron ships >their BDI2000s - they include a free TFTP server on their floppy >disks which is so simple that even a Windoze user can start it. You're making assumptions here that I don't believe are appropriate: 1. You are assuming that Brian's customers are at least as sophisticated as Abatron customers. Brian's original statement leads me to believe this is not so. 2. You are assuming that you know more about Brian's customers than either he or his Marketing group does. Ultimately, it is the responsibility of a company's Marketing group to determine what a customer is capable of and will tolerate. >> However, if the boot loader is capable of receiving the OS image over the >> network, our PC side application can upload the OS and Ram disk image to >> our custom board the first time it connects to it. >> >> Is this not a good idea? > >No, it is not. You are trying to re-invent the wheel. This is certainly an emphatic statement. The least you could have done here is to prefix it with "IMHO". U-boot supports the target-as-client method of downloading but does not support the target-as-server method. I've used both methods a number of times over the years and both have their advantages and disadvantages. Your position seems to be that u-boot does everything useful for downloading. Therefore, if u-boot doesn't "do it", then "it" must be a duplication. I disagree. IMHO, target-as-server boot loading is a good idea. The two methods are useful in different circumstances and are not, IMHO, a reinvention. At the company I work for, we have three different MPC850 designs that work together to form our new system. The boot code in all three units contains a target-as-server (UDP over Ethernet) loader. We use this UDP/Ethernet boot loader in exactly the mode that Brian is referring to above. It supports Linux, VxWorks and stand-alone images. It's used every day by the Development team, SQA team and Field Support team. It works great. The main advantage is simplicity. Our boot code occupies less than 6k-bytes of FLASH (that would fit in a 2708 ;-) ). The small size attests to its simplicity as well as the capabilities of the Ethernet controller in the '850. It was written and debugged in a very short time over a year ago and has not required any maintenance since. No head-scratching, no hair-pulling, no patches. It just works. The way I see it, one of the benefits of these lists is discussion. To cut off discussion as you did is, IMHO, not productive. Regards, Charlie Charles.Wells(a)nielsenmedia.com

4 6

RE: [U-Boot-Users] uploading OS over network instead of u-boot do wnloading it from a server.
by Woodruff, Richard 24 Jun '03

24 Jun '03

If system requirements allow for it, adding in a simple zeroconf ip address assignment would seem to be ideal in a lot of situations. All you need to do is a hash on a mac, some arp broadcasts, and you up :) www.zeroconf.org . There also is some service discovery stuff but I've not looked to deeply at that aspect of it. Linux has a patch for it, microsoft and apple have been using it for a while. Next time you see a 169.x.x.x address you know where it came from. :) > -----Original Message----- > From: Brian S. Park [mailto:brian@corelis.com] > Sent: Tuesday, June 24, 2003 4:20 PM > To: Wolfgang Denk > Cc: 'u-boot-users(a)lists.sourceforge.net'; Wells, Charles > Subject: Re: [U-Boot-Users] uploading OS over network instead > of u-boot do wnloading it from a server. > > > Dear Wolfgang, > > > > The advantage I see is this. > > > 1. You ship 1 less piece of software. Less number of application > > > that > > needs > > > to be installed/started is always better, IMHO, when it comes to > > > support. > > > >Don't you have to ship a (proprietary?) upload client instead of the > >(standard) TFTP server? > > It could be integrated to our PC side application which can > upload it the > first time it connects to the target. Integrating TFTP server to our > application would require it to start before the user > powering up the target. > > > > > 2. It makes the network configuration a bit simpler. If > you do not > > > have a dedicated TFTP server, you must use serial console > to setup > > > the server IP before you can boot if you change the tftp server. > > > Users only have to > > worry > > > about 1 IP instead of 2 when setting up our product. Since large > > > number of our users are not very network savvy, things like this > > > make a difference when it comes to support. > > > >As mentioned before, the TFTP server which is used for > example by > >Abatron does not require any special setup on the host. > > > >In any case you will have to setup both the network > interfaces on the > >host and the target. > > With TFTP client approach, I need to set the serverip environmental > variable to IP of PC with the TFTP server. If I move the > controller to > another room, and found out that the PC with TFTP server is > not powered up, > I need to either change the serverip variable to the new PC I > intended to > use or go back to the other room and power up the PC. :) > > I think it's easiest for the user and the developer if the > firmware is > entirely stored on the flash. If we can upload the OS, we can > make it work > as if the firmware is on the target (i.e. hide TFTP stuff > from the user). > > > > I have no idea how complicated it will be to implement server > > > feature. > > > >It is not complicated. But IMHO not worth the effort. > > I always appreciate your comments and opinion. > > Thank you. > > Brian > > > =============================================================== > Brian S. Park brian(a)corelis.com (562) 926-6727 x143 > --------------------------------------------------------------- > Everything we do helps our customers get to market > FASTER with HIGHER quality and LOWER cost > =============================================================== > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: INetU > Attention Web Developers & Consultants: Become An INetU > Hosting Partner. Refer Dedicated Servers. We Manage Them. You > Get 10% Monthly Commission! INetU Dedicated Managed Hosting > http://www.inetu.net/partner/index.php > > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users >

1 0

RE: [U-Boot-Users] Generic ARM Error with respect to usage of r8 in start.S's.
by Woodruff, Richard 24 Jun '03

24 Jun '03

Let me restate my minor point hopefully more correctly. - gd/r8 is only used to reference things in the gd_t structure and its members. Given the way things currently stand for ARM something like the following might work as well and free up a register and remove an assembly dependency: #define DECLARE_GLOBAL_DATA_PTR gd_t *gd = &global_data ------------- gd_t global_data; /* global data declaration */ start_armboot() { #include <someheader with extern gd_t global_data> /* remove stack allocation of global */ } I'm NOT saying that I think this is needed. As far as a patch goes maybe (though I can't test on anything other than arm925), the one touchy point I noticed when looking at the code was the partially useful (in a forward looking way) "irq handling code" would have to regress or be redone to be made to work with the current level of the overall code. Regards, Richard W. > -----Original Message----- > From: Wolfgang Denk [mailto:wd@denx.de] > Sent: Tuesday, June 24, 2003 3:29 PM > To: Woodruff, Richard > Cc: u-boot-users(a)lists.sourceforge.net > Subject: Re: [U-Boot-Users] Generic ARM Error with respect to > usage of r8 in start.S's. > > > In message > <FD2AC9A020DDD51194710008C7089B20053D4CAD(a)dlee17.itg.ti.com> > you wrote: > > > > The u-boot for ARM code defines and uses global data which is not > > referenced using r8 (can be seen by all). The code as currently > > generated only uses r8 to access into the bd_info structure and its > > members. As it is, the bd_info > > No. All access to the "global data pointer" ("*gd") goes > through r8, as defined in "include/asm-arm/global_data.h": > > #define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("r8") > > > > structure is allocated on the C stack in start_armboot(), there is > > nothing special about the sdram which its allocated in. > The structure > > could have as > > As mentioned before, the ARM initialization sequence and > memory map do not exactly fit into the U-Boot model as it > was intended to be. The curerent state is a result of the > port done for the ARMBoot project, but this is a > temporary state which will be fixed in a future release. > > > Yes the flexibility to do different things is there which is good, > > unfortunately the leaving of expansion hooks which break > the existing > > code somewhat defeats its usefulness. > > The problem is that we obviously missed the exception > code when chosing r8. If you can, please submit a patch to > fix this problem. > > > 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 In an organization, each person rises to the level > of his own incom- > petency - The Peter Principle >

2 1