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