September 2003 - U-Boot

[U-Boot-Users] mkimage for DOS
by Dave Westwood 10 Jun '05

10 Jun '05

long shot really, but does anyone have a working executable mkimage for DOS or a dos window in windows (don't flame me for using windows !!)

2 1

[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] watchdog reset in mpc824x timer interrupt.
by gleb＠nbase.co.il 15 Dec '03

15 Dec '03

Hello, Attached patch makes timer_interrupt to perform watchdog reset on all boards that support watchdog and not only for OXC. CHANGELOG: perform watchdog reset in mpc824x timer interrupt on all boards that have watchdog. -- Gleb.

3 10

[U-Boot-Users] [PATCH][CFT] bring ARM memory layout in line with the documented behaviour
by Anders Larsen 07 Dec '03

07 Dec '03

Hi, here's a fairly lengthy patch against 0.4.8 that brings the memory layout of all supported ARM CPUs in line with the documentation. This has the positive side-effect of allowing U-Boot to actually run on PXA CPUs (the stock PXA implementation didn't set the start-address of the malloc pool at all!) The memory layout now more or less conforms to the standard as defined in the README (the absolute addresses are board-specific, of course). Since the stack and malloc-heap are now located below the U-Boot code, the TEXT_BASE of the supported ARM boards can be increased accordingly (for most (but not all) boards, the patch already does this). Memory layout example based on my PXA255 (TEXT_BASE = 0xA07E0000): 0xA079FF74 Monitor Stack (growing downwards) 0xA079FF80 Board Info Data and permanent copy of Global Data 0xA07A0000 Malloc Arena 0xA07E0000 RAM copy of Monitor Code ... optional: Frame Buffer 0xA07FFFFF [End of RAM] Since I only have access to PXA-based HW, I was only able to verify that U-Boot still *builds* for all supported ARMs; I have to rely on your help to see if it also *runs* correctly. CHANGELOG: Bring ARM memory layout in line with the documentation. Wolfgang: Please don't apply this patch until we have some feedback from the ARM maintainers. Robert: When/if this patch is eventually applied, you can probably push most of your PXA -ptx stuff without having it break things. Cheers Anders

5 16

[U-Boot-Users] what is wrong when calloc return bogus?
by Holger Schurig 06 Nov '03

06 Nov '03

I recently updated from u-boot 0.3.2 to CVS (0.4.5). Now blob stopped working. I tracked this down from device_init() to ListCreate() or NewHandle(). My debug output is: U-Boot 0.4.5 (Aug 15 2003 - 18:26:38) U-Boot code: A3000000 -> A300D4E0 BSS: -> A3024000 DRAM Configuration: Bank #0: a0000000 128 MB Flash: 32 MB 1 2 4 6 7 9 10 d1 d3 l1 n1 n2 memPtr=0badc0e8 n3 hanPtr=0badc108 n4 l2 l3 0badc108 list_t ListCreate (int elementSize) { list_t list; printf("l1\n"); list = (list_t) (NewHandle (sizeof (ListStruct))); /* create empty list */ printf("l2\n"); if (list) { printf("l3 %08x\n", list); (*list)->signature = LIST_SIGNATURE; (*list)->numItems = 0; (*list)->listSize = 0; (*list)->itemSize = elementSize; (*list)->percentIncrease = kDefaultAllocationPercentIncrease; (*list)->minNumItemsIncrease = kDefaultAllocationminNumItemsIncrease; } printf("l4\n"); return list; } Target is an Intel PXA255

3 2

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

10 Oct '03

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

3 8

[U-Boot-Users] Extending bootm command.
by Steven Scholz 09 Oct '03

09 Oct '03

Hi there, from time to time it might be necessary to (decompress and) copy some data from flash to ram. The configuration data for an Altera ACEX 1K FPGA for instance is about 163KB. The gzipped file (for a quite complex design) is only 54kB. So instead of wasting three flash sectors one could store a gzipped and mkimage wrapped version of the data in flash. If calling mkimage with the type STANDALONE like [1] proposes one could then use "bootm" to decompress and copy these data to ram. In order to call "fpga load" afterwards one need the location and the resulting size of the data. That is why I suggest the following patch: * Patch by Steven Scholz, 29 Sep 2003: - A second parameter for bootm overwrites the load address for "Standalone Application" images. - bootm sets environment variable "filesize" to the resulting data lenght for "Standalone Application" images when autostart is set to "no". Then one could do something like if bootm $fpgadata $some_free_ram ; then fpga load 0 $some_free_ram $filesize ; fi Cheers, Steven [1] https://www.denx.de/twiki/bin/view/DULG/HowCanILoadAndUncompressACompressed… + diff -u ./common/cmd_bootm.c.orig ./common/cmd_bootm.c --- ./common/cmd_bootm.c.orig Fri Aug 29 22:58:07 2003 +++ ./common/cmd_bootm.c Mon Sep 29 10:18:56 2003 @@ -247,6 +247,10 @@ switch (hdr->ih_type) { case IH_TYPE_STANDALONE: name = "Standalone Application"; + /* A second argument overwrites the load address */ + if (argc > 2) { + hdr->ih_load = simple_strtoul(argv[2], NULL, 16); + } break; case IH_TYPE_KERNEL: name = "Kernel Image"; break; @@ -347,8 +351,12 @@ /* load (and uncompress), but don't start if "autostart" * is set to "no" */ - if (((s = getenv("autostart")) != NULL) && (strcmp(s,"no") == 0)) + if (((s = getenv("autostart")) != NULL) && (strcmp(s,"no") == 0)) { + char buf[32]; + sprintf(buf, "%lX", len); + setenv("filesize", buf); return 0; + } appl = (int (*)(cmd_tbl_t *, int, int, char *[]))ntohl(hdr->ih_ep); (*appl)(cmdtp, flag, argc-1, &argv[1]); return 0;

2 3

[U-Boot-Users] Patch: Support for Zephyr Engineering ZPC.1900 board
by Yuli Barcohen 09 Oct '03

09 Oct '03

This patch adds support for Zephyr Engineering ZPC.1900 board. It's an MPC8265 based board for developing applications using Motorola security chips (MPC180, MPC184, MPC185, MPC190). -- ======================================================================== Yuli Barcohen | Phone +972-9-765-1788 | Software Project Leader yuli(a)arabellasw.com | Fax +972-9-765-7494 | Arabella Software, Israel ========================================================================

2 1

[U-Boot-Users] [PATCH] Calculate PLPRCR fields for MPC86x boards
by Pantelis Antoniou 09 Oct '03

09 Oct '03

Hi. The following patch adds a program in the tools directory which aids in the programming of the PLPRCR register for MPC86x based boards. That is given an input clock xin and a target clock gclk2 it will output (if possible) the values of the PCPRCR fields required. Regards Pantelis --- u-boot-cvs/tools/Makefile Tue Sep 16 11:50:30 2003 +++ u-boot-lastcvs/tools/Makefile Sun Aug 17 21:55:30 2003 @@ -30,11 +30,6 @@ OBJS += inca-swap-bytes.o endif -ifeq ($(ARCH),ppc) -BINS += mpc86x_clk$(SFX) -OBJS += mpc86x_clk.o -endif - LOGO_H = $(TOPDIR)/include/bmp_logo.h ifeq ($(LOGO_BMP),) @@ -141,10 +136,6 @@ $(CC) $(CFLAGS) $(HOST_LDFLAGS) -o $@ $^ $(STRIP) $@ -mpc86x_clk$(SFX): mpc86x_clk.o - $(CC) $(CFLAGS) $(HOST_LDFLAGS) -o $@ $^ - $(STRIP) $@ - envcrc.o: envcrc.c $(CC) -g $(CFLAGS) -c $< @@ -158,9 +149,6 @@ $(CC) -g $(CFLAGS) -c $< inca-swap-bytes.o: inca-swap-bytes.c - $(CC) -g $(CFLAGS) -c $< - -mpc86x_clk.o: mpc86x_clk.c $(CC) -g $(CFLAGS) -c $< subdirs: --- u-boot-cvs/tools/mpc86x_clk.c Tue Sep 16 12:58:43 2003 +++ u-boot-lastcvs/tools/mpc86x_clk.c Thu Jan 1 02:00:00 1970 @@ -1,206 +0,0 @@ -/* - * (C) Copyright 2003 Intracom S.A. - * Pantelis Antoniou <panto(a)intracom.gr> - * - * This little program makes an exhaustive search for the - * correct terms of pdf, mfi, mfn, mfd, s, dbrmo, in PLPRCR. - * The goal is to produce a gclk2 from a xin input, while respecting - * all the restrictions on their combination. - * - * Generaly you select the first row of the produced table. - * - * See file CREDITS for list of people who contributed to this - * project. - * - * This program is free software; you can redistribute it and/or - * modify it under the terms of the GNU General Public License as - * published by the Free Software Foundation; either version 2 of - * the License, or (at your option) any later version. - * - * This program is distributed in the hope that it will be useful, - * but WITHOUT ANY WARRANTY; without even the implied warranty of - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the - * GNU General Public License for more details. - * - * You should have received a copy of the GNU General Public License - * along with this program; if not, write to the Free Software - * Foundation, Inc., 59 Temple Place, Suite 330, Boston, - * MA 02111-1307 USA - */ - - -#include <stdio.h> -#include <stdlib.h> - -#define DPREF_MIN 10000000 -#define DPREF_MAX 32000000 - -#define DPGDCK_MAX 320000000 -#define DPGDCK_MIN 160000000 - -#define S_MIN 0 -#define S_MAX 2 - -#define MFI_MIN 5 -#define MFI_MAX 15 - -#define MFN_MIN 0 -#define MFN_MAX 15 - -#define MFD_MIN 0 -#define MFD_MAX 31 - -#define MF_MIN 5 -#define MF_MAX 15 - -#define PDF_MIN 0 -#define PDF_MAX 15 - -#define GCLK2_MAX 150000000 - -static int calculate(int xin, int target_clock, int ppm, int pdf, int mfi, int mfn, int mfd, int s, - int *dprefp, int *dpgdckp, int *jdbckp, int *gclk2p, int *dbrmop) -{ - unsigned int dpref, dpgdck, jdbck, gclk2, t1, t2, dbrmo; - - /* valid MFI? */ - if (mfi < MFI_MIN) - return -1; - - /* valid num, denum? */ - if (mfn > 0 && mfn >= mfd) - return -1; - - dpref = xin / (pdf + 1); - - /* valid dpef? */ - if (dpref < DPREF_MIN || dpref > DPREF_MAX) - return -1; - - if (mfn == 0) { - dpgdck = (2 * mfi * xin) / (pdf + 1) ; - dbrmo = 0; - } else { - /* 5 <= mfi + (mfn / mfd + 1) <= 15 */ - t1 = mfd + 1; - t2 = mfi * t1 + mfn; - if ( MF_MIN * t1 > t2 || MF_MAX * t1 < t2) - return -1; - - dpgdck = (unsigned int)(2 * (mfi * mfd + mfi + mfn) * (unsigned int)xin) / - ((mfd + 1) * (pdf + 1)); - - dbrmo = 10 * mfn < (mfd + 1); - } - - /* valid dpgclk? */ - if (dpgdck < DPGDCK_MIN || dpgdck > DPGDCK_MAX) - return -1; - - jdbck = dpgdck >> s; - gclk2 = jdbck / 2; - - /* valid gclk2 */ - if (gclk2 > GCLK2_MAX) - return -1; - - t1 = abs(gclk2 - target_clock); - - /* XXX max 1MHz dev. in clock */ - if (t1 > 1000000) - return -1; - - /* dev within range (XXX gclk2 scaled to avoid overflow) */ - if (t1 * 1000 > (unsigned int)ppm * (gclk2 / 1000)) - return -1; - - *dprefp = dpref; - *dpgdckp = dpgdck; - *jdbckp = jdbck; - *gclk2p = gclk2; - *dbrmop = dbrmo; - - return gclk2; -} - -int conf_clock(int xin, int target_clock, int ppm) -{ - int pdf, s, mfn, mfd, mfi; - int dpref, dpgdck, jdbck, gclk2, xout, dbrmo; - int found = 0; - - /* integer multipliers */ - for (pdf = PDF_MIN; pdf <= PDF_MAX; pdf++) { - for (mfi = MFI_MIN; mfi <= MFI_MAX; mfi++) { - for (s = 0; s <= S_MAX; s++) { - xout = calculate(xin, target_clock, ppm, pdf, mfi, 0, 0, s, &dpref, &dpgdck, &jdbck, &gclk2, &dbrmo); - if (xout < 0) - continue; - - if (found == 0) { - printf("pdf mfi mfn mfd s dbrmo dpref dpgdck jdbck gclk2 exact?\n"); - printf("--- --- --- --- - ----- ----- ------ ----- ----- ------\n"); - } - - printf("%3d %3d --- --- %1d %5d %9d %9d %9d %9d%s\n", - pdf, mfi, s, dbrmo, dpref, dpgdck, jdbck, gclk2, - gclk2 == target_clock ? " YES" : ""); - - found++; - } - } - } - - /* fractional multipliers */ - for (pdf = PDF_MIN; pdf <= PDF_MAX; pdf++) { - for (mfi = MFI_MIN; mfi <= MFI_MAX; mfi++) { - for (mfn = 1; mfn <= MFN_MAX; mfn++) { - for (mfd = 1; mfd <= MFD_MAX; mfd++) { - for (s = 0; s <= S_MAX; s++) { - xout = calculate(xin, target_clock, ppm, pdf, mfi, mfn, mfd, s, &dpref, &dpgdck, &jdbck, &gclk2, &dbrmo); - if (xout < 0) - continue; - - if (found == 0) { - printf("pdf mfi mfn mfd s dbrmo dpref dpgdck jdbck gclk2 exact?\n"); - printf("--- --- --- --- - ----- ----- ------ ----- ----- ------\n"); - } - - printf("%3d %3d %3d %3d %1d %5d %9d %9d %9d %9d%s\n", - pdf, mfi, mfn, mfd, s, dbrmo, dpref, dpgdck, jdbck, gclk2, - gclk2 == target_clock ? " YES" : ""); - - found++; - } - } - } - - } - } - - return found; -} - -int main(int argc, char *argv[]) -{ - int xin, want_gclk2, found, ppm = 100; - - if (argc < 3) { - fprintf(stderr, "usage: mpc86x_clk <xin> <want_gclk2> [ppm]\n"); - fprintf(stderr, " default ppm is 100\n"); - return 10; - } - - xin = atoi(argv[1]); - want_gclk2 = atoi(argv[2]); - if (argc >= 4) - ppm = atoi(argv[3]); - - found = conf_clock(xin, want_gclk2, ppm); - if (found <= 0) { - fprintf(stderr, "cannot produce gclk2 %d from xin %d\n", want_gclk2, xin); - return EXIT_FAILURE; - } - - return EXIT_SUCCESS; -}

3 3

[U-Boot-Users] [PATCH] declare portio-commands nonstd.
by Anders Larsen 09 Oct '03

09 Oct '03

Hi, here's a patch against 0.4.8 that declares CMD_PORTIO nonstandard. Rationale: The commands in question are only implemented for the x86 architecture. CHANGELOG: add CMD_PORTIO to CFG_CMD_NONSTD Cheers Anders

2 1

[U-Boot-Users] [PATCH] Enable timed autoboot on PXA
by Anders Larsen 09 Oct '03

09 Oct '03

Hi, here's a patch that enables timed autoboot on PXA systems (blatantly copied from cpu/arm925t/interrupts.c) CHANGELOG: enable timed autoboot on PXA Cheers Anders

2 1

[U-Boot-Users] FEC 8xx
by Frank Müller 09 Oct '03

09 Oct '03

Hello, code in u-boot/cpu/mpc8xx/fec.c for MII speed seems to be wrong in the case that busfreq != intfreq (I have 133MHz internally and 66MHz bus) current code: fecp->fec_mii_speed = ((bd->bi_busfreq + 4999999) / 5000000) << 1; correct: fecp->fec_mii_speed = ((bd->bi_intfreq + 4999999) / 5000000) << 1; Frank

2 1

[U-Boot-Users] New Board support
by Sangmoon Kim 01 Oct '03

01 Oct '03

Hi, I ported u-boot to our new boards. I want to make them included on the official u-boot cvs tree. Is there any way? Regards, Sangmoon Kim

3 2

[U-Boot-Users] Support for AM29LV008B ( 1 M x 8 bit ) 8Megabit Bottom boot device
by Raghu 30 Sep '03

30 Sep '03

Hello, I am using u-boot release 0.4.0. I was looking for flash support for AMD's AM29LV008B 8Mbit bottom boot chip, didnt find one. Just curious to know if we already have one so that I dont have to re-invent the wheel :-) Warm Regards, Raghu. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 1

[U-Boot-Users] MPC852T FEC ping fail
by Raghu 30 Sep '03

30 Sep '03

Hello All, I am trying to get FEC up on a MPC852T processor based board that has a Intels LXT971A Network PHY chip. Connected as PHY Number 0. I am not able to get the "ping" requests and replies. Using "ethereal" to check the ICMP packets. But it is not receiving any packets. The MII clock is 25 Mhz for 100Mbps. The PHY register dump is as .... ***************************************************** =>ping 10.208.1.87 Trying FEC ETHERNET PHY type 0x13 pass 1 type PHY @ 0x0 pass 1 type LXT971 FEC: phyaddr = 0x0 phyno = 0 , reg[0] = 0x3100 phyno = 0 , reg[1] = 0x7809 phyno = 0 , reg[2] = 0x13 phyno = 0 , reg[3] = 0x78e2 phyno = 0 , reg[4] = 0x1e1 phyno = 0 , reg[5] = 0x0 phyno = 0 , reg[6] = 0x4 phyno = 0 , reg[7] = 0x2001 phyno = 0 , reg[8] = 0x0 phyno = 0 , reg[9] = 0x7fff phyno = 0 , reg[10] = 0x7fff phyno = 0 , reg[11] = 0x7fff phyno = 0 , reg[12] = 0x7fff phyno = 0 , reg[13] = 0x7fff phyno = 0 , reg[14] = 0x7fff phyno = 0 , reg[15] = 0x7fff phyno = 0 , reg[16] = 0x84 phyno = 0 , reg[17] = 0x100 phyno = 0 , reg[18] = 0x0 phyno = 0 , reg[19] = 0x54 phyno = 0 , reg[20] = 0x422 phyno = 0 , reg[21] = 0x0 phyno = 0 , reg[22] = 0x0 phyno = 0 , reg[23] = 0x0 phyno = 0 , reg[24] = 0x0 phyno = 0 , reg[25] = 0x0 phyno = 0 , reg[26] = 0x48 phyno = 0 , reg[27] = 0x0 phyno = 0 , reg[28] = 0x7fff phyno = 0 , reg[29] = 0x0 phyno = 0 , reg[30] = 0x0 phyno = 0 , reg[31] = 0x3768 sending ARP for 0ad00157 ARP broadcast 1 fec.c[135] fec_send: cycles: 9 status: c01 retry cnt: 0 ARP broadcast 2 fec.c[135] fec_send: cycles: 12 status: 2c01 retry cnt: 0 ping failed; host 10.208.1.87 is not alive => ***************************************************** Any clues ?? Warm Regards, Raghu. __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com

1 0

[U-Boot-Users] mkimage arguments?
by deya privi 30 Sep '03

30 Sep '03

Hi, I am using u-boot for PXA255. In u-boot with mkimage options what does this -a(load address) and -e(entry point) option represent? Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

1 0

[U-Boot-Users] SDRAM configuration?
by deya privi 30 Sep '03

30 Sep '03

Hi I am using U-boot(for lubbock). If I am using K4S561632E from Samsung then should I have to modify any in my SDRAM configuration(memsetup.S)? Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

1 0

[U-Boot-Users] Loading into and running from RAM
by Dhanuka, Anupam 30 Sep '03

30 Sep '03

Hi I was wondering if there is any way I can just load the u-boot executable into RAM using a debugger like the BDI2000 and then just run it from RAM. (Basically I want to avoid the flash programming step every time I make a change to u-boot for customization) Has anyone done this and how (do I need to compile it differently)? Thanks Best Regards Anupam Dhanuka 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.

1 0

[U-Boot-Users] Problems w/ SourceForge !?
by Steven Scholz 29 Sep '03

29 Sep '03

Hi there, when trying to update or checkout U-Boot from SourceForge I get ~/tmp> cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/u-boot co -P u-boot can't create temporary directory /tmp/cvs-serv16957 No space left on device Has someone else the same problem? Thanks, Steven

2 1

[U-Boot-Users] No space left on device
by Sangmoon Kim 29 Sep '03

29 Sep '03

Hi, While accessing u-boot anonymous cvs, I got following errors. can't create temporary directory /tmp/cvs-rv17677 No space left on device I used the following commands. cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/u-boot login cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/u-boot co u-boot Is there something wrong. Regards, Sangmoon Kim

1 0

[U-Boot-Users] (no subject)
by C Doyle 27 Sep '03

27 Sep '03

Hello all, Ive been trying to compile u-boot0.4 for the mpc8266ads board. I am using the hardhat ppc-cross compiler and am coming across problems with the compilation. First of all make fails at a bootp error which can be fixed by placing parenthesis around the #define. It next fails in the examples folder where I think it is trying the hello_world.bin & others and this can be fixed by doing a chmod on each of the examples it fails on. Just wondering if anyone is coming across the same problems and if any official fixes are available for this? After I change these the project compiles ok. Cheers _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus

2 1

[U-Boot-Users] gunzip command?
by Steven Scholz 26 Sep '03

26 Sep '03

Hi there, on my board U-Boot should program an FPGA before booting linux. Unfortunatly the file is quite big (>160KB). So I store a gzipped version of it in my flash. Actually I stored an image created with mkimage DAB4K2> imi 40040000 ## Checking Image at 40040000 ... Image Name: DAB4K_TEST- Created: 2003-09-22 8:20:19 UTC Image Type: PowerPC U-Boot Firmware (gzip compressed) Data Size: 56098 Bytes = 54.8 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK So what I need now is a way to uncompress the data to RAM before I can call "fpga load". My questions: 1. Should we add a "gunzip" command to U-Boot? 2. Should we add a command (similar to bootm) that takes an image, decompresses it and checks CRC etc.? 3. Or should we put this into the "fpga load" command? I would go for the first. Maybe the second. Third seems to be too limited. Any comments? Thanks, Steven

2 2

[U-Boot-Users] Can I use LAN91C113 with PXA255?
by deya privi 26 Sep '03

26 Sep '03

Hi, Can I use LAN91c113 with Intels xscale PXA255 processor? As LAN91C113 is 16-bit and PXA255 is 32-bit, will there be any conflict? If I could use LAN91C113 with PXA then I hope I can make some minor changes to LAN91C111 and use it for LAN91C113. Thanks in advance for any help! Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

2 1

[U-Boot-Users] I can't boot linux with CONFIG_CMDLINE_TAG
by Sangwoo Jin 26 Sep '03

26 Sep '03

Hellow. I used U-Boot 4.0 and Linux 2.4.18 on Samsung S32410(ARM920T). First, i have boot linux successfully without CONFIG_CMDLINE_TAG. But. with CONFIG_CMDLINE_TAG i can't boot linux. With CONFIG_CMDLINE_TAG, i can see the following log, and linux may hang "Starting kernel ..." Please let me know the solution of this problem. Regards Sangwoo Jin

3 2

[U-Boot-Users] linux driver for lan91c113?
by deya privi 25 Sep '03

25 Sep '03

Hi, Is there any driver available for Ethernet chip LAN91C113? Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

3 2

Fwd: Re: [U-Boot-Users] linux driver for lan91c113?
by Kyle Harris 25 Sep '03

25 Sep '03

On Thursday 25 September 2003 04:29 am, deya privi wrote: > Hi, > > Is there any driver available for Ethernet chip > LAN91C113? The 113 is essentially a 16 bit version of the 111. So the 91C111 driver should work with minor modification. I am currently working on the boot for a product that uses the 113. So, it is on my list, but may be a while before I get around to it. Kyle.

1 0

[U-Boot-Users] Post codes for PowerPC
by deya privi 25 Sep '03

25 Sep '03

Hi, What are the post codes generated for the PowerPC? ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

2 1

[U-Boot-Users] Startup for ARM boards?
by Steven Scholz 25 Sep '03

25 Sep '03

Hi there, I am trying to figure out how ARM based board start up. PPC boards basicly have a board_init_f(), doing initialization, then relocating the code from flash to ram using relocate_code(), and then continue in ram with board_init_r(). I can't find anything like this in the ARM based files? How is that done? Is that the same for all ARM boards? Thanks a million, Steven

4 7

RE: [U-Boot-Users] Ramdisk with u-boot
by Gupta, Kshitij 25 Sep '03

25 Sep '03

hi , here is the complete log. Both kernel and filesystem are stored in the flash. I see some differences in the do_bootm_linux function of ARM and PPC, and I am planning to look at these differences and get some hints. The way I think it should work is u-boot should copy the ramdisk fs to the load address mentioned in the image header and should also pass the initrd start address to the kernel. OMAP1510 Innovator # setenv bootargs console=ttyS0,115200n8 initrd=0x10800000,8M root=/dev/ram ip=off OMAP1510 Innovator # bootm 0x100000 0x300000 ## Booting image at 00100000 ... Image Name: Linux Kernel Image Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 686909 Bytes = 670.8 kB Load Address: 10c08000 Entry Point: 10c08000 Verifying Checks... OK Uncompressing Kere ... OK ## Loading Ramdisk Image 00300000 ... Image Name: Disk Image Type: Ainux RAMDisk Image (gzip compressed) Data Size: 3830 Bytes = 2.9 MB Load Address: 10800000 Entry Point: 10800000 Verifying Checksum OK Starting kernel ..Uncompressing Linux........................................... .... done, booting the kernel. Linux version 2.4.18_mvl30-innovator (a0875451@lxlab001) (gcc version 3.2.1 20020 (MontaVista)) #23 Wed Sep 24 10:47:10 IST 2003 CPU: ARM/TI925 m925Tsid(wb) revision 2 Machine: TI-Innoor/OMAP1510 On node 0 totalpage8192 zone(0): 8192 pageszone(1): 0 pages. zone(2): 0 pages. Kerel command line: console=ttyS0,115200n8 initrd=0x10800000,8M root=/dev/ram ip=off Console: colour dummy device 80x30 Calibrating delay lo.. 83.76 BogoMIPS Memory: 32MB = 32MB total Memory: 22440KB availe (1222K code, 304K data, 76K init) Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes) Inode-cache hash table entries: 2048 (order: 2, 16384 bytes) Mount-cache hashable entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table ries: 8192 (order: 3, 32768 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea Uersity Computer Society NET3.039 Initializing RT netlink socket Innovator FPGA Rv 2.1 Board Rev 16 Power Management for OMAP1510 is initialized pm_idle 0xc0023ecc apm: BIOS version 1.2Flags 0x02 (Driver version 1.13) Starting kswapd Disabling the OOf Memory Killer JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications AB. pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with no serial options enabled ttyS00 at 0xfff0000 (irq = 46) is a OMAP UART ttyS01 at 0xfffb00 (irq = 47) is a OMAP UART ttyS02 at 0xfffb9800rq = 15) is a OMAP UART block: 64 slots per queue, batch=16 RAMDISK driver initalized: 16 RAM disks of 8192K size 1024 blocksize smc9194.c:v0.15 12/15/00 by Erik Stahlman (erik(a)vt.edu) eth0: SMC91C94/91C96rev 9) at 0xe8000300 IRQ:93 INTF:TP MEM:6144b ADDR: 00:0b:36 :00:04:31 innovator-ts: registered OMAP flash 0: probin6-bit flash bus Using static patition definition Creating 4 MTD partits on "OMAP flash": 0x00000000-0x00020000"BootLoader" 0x00020000-0x000600: "Params" 0x00060000-0x00260000"Kernel" 0x00260000-0x010000 : "Flash0 FileSys" OMAP flash 1: pring 16-bit flash bus Using static partitn definition Creating 1 MTD parions on "OMAP flash": 0x00000000-0x01000 : "Flash1 FileSys" DSPLinux FB (c) 01 RidgeRun, Inc. Console: switching to colour frame buffer device 30x40 usb.c: registerenew driver usbdevfs usb.c: registered neriver hub usb-ohci.c: USB OHCI at membase 0xfffba000, IRQ 38 usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 3 ports detd NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 2048 bind 4096) NET4: Unix domain sock 1.0/SMP for Linux NET4.0. RAMDISK: Couldn' find valid RAM disk image starting at 0. Freeing initrd memory: 8192K cramfs: wrong magic Kernel panic: VFS: Unale to mount root fs on 01:00 regards -kshitij -----Original Message----- From: Detlev Zundel [mailto:dzu@denx.de] Sent: Wednesday, September 24, 2003 8:33 PM To: Gupta, Kshitij Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] Ramdisk with u-boot Hi Kshitij, > I am trying to boot the linux kernel with ramdisk support. > > The details of the ramdisk image are > Image Name: RAm Disk > Created: Wed Sep 24 11:55:02 2003 > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 3038830 Bytes = 2967.61 kB = 2.90 MB > Load Address: 0x10800000 > Entry Point: 0x10800000 > > The kernel is > Image Name: Linux Kernel Image > Created: Wed Sep 24 11:56:19 2003 > Image Type: ARM Linux Kernel Image (gzip compressed) > Data Size: 686909 Bytes = 670.81 kB = 0.66 MB > Load Address: 0x10C08000 > Entry Point: 0x10C08000 > > The bootargs : > setenv bootargs console=ttyS0,115200n8 initrd=0x10800000,8M root=/dev/ram > ip=off If you use U-Boot (at least on PowerPC) you do _not_ need an "initrd" argument, the RAM disk address is passed by U-Boot for you if a second parameter to bootm appears. > The kernel is compiled with ramdisk support. I store my kernel in the flash > at location 0x100000 and I download the ramdisk in the ram at location > 0x10000000 ( this is starting of my RAM). Now when I boot the kernel with > the > > $ bootm 0x100000 0x10000000 You are aware that U-Boot takes its input in hexadecimal per default, so this should rather be "bootm 100000 10000000". But as a kernel is started this might be a copy and paste problem. > I get the following error > > RAMDISK: Couldn'find valid RAM disk image starting at 0. Address 0 - looks bogus. > Freeing initrd memory: 8192K > cramfs: wrong magic > Kernel panic: Unable to mount root fs on 01:00 > > Am I missing some thing in my steps ?? Any comments will be greatly > appreciated. It would help a lot if you could provide us with a complete transcript of the failing attempt. Cheers Detlev -- Life is complex. It has real and imaginary components.

1 0

[U-Boot-Users] I2C Problem (EP862)
by Jeff Stevens 24 Sep '03

24 Sep '03

I am having problems with my i2c devices on my EP862 under Linux. Under U-Boot I can read from the Xicor EEPROM, and LM75 temp. sensor fine. However, when I boot into ELDK linux with i2c and lm75 support built into the kernel it hangs when lm75.o is loaded. I have also ran the kernel with only i2c support built in, and it only shows one device. When I try to read that device with i2cdetect I just get the address back as the data (i.e. 00: 00, 01:01, ... ,f0: f0, etc.). Has anyone else had a problem with I2C support with ELDK, or can anyone give me any pointers on how to get this working? Thanks in advance, - Jeff Stevens __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

[U-Boot-Users] Ramdisk with u-boot
by Gupta, Kshitij 24 Sep '03

24 Sep '03

hi, I am trying to boot the linux kernel with ramdisk support. The details of the ramdisk image are Image Name: RAm Disk Created: Wed Sep 24 11:55:02 2003 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3038830 Bytes = 2967.61 kB = 2.90 MB Load Address: 0x10800000 Entry Point: 0x10800000 The kernel is Image Name: Linux Kernel Image Created: Wed Sep 24 11:56:19 2003 Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 686909 Bytes = 670.81 kB = 0.66 MB Load Address: 0x10C08000 Entry Point: 0x10C08000 The bootargs : setenv bootargs console=ttyS0,115200n8 initrd=0x10800000,8M root=/dev/ram ip=off The kernel is compiled with ramdisk support. I store my kernel in the flash at location 0x100000 and I download the ramdisk in the ram at location 0x10000000 ( this is starting of my RAM). Now when I boot the kernel with the $ bootm 0x100000 0x10000000 I get the following error RAMDISK: Couldn'find valid RAM disk image starting at 0. Freeing initrd memory: 8192K cramfs: wrong magic Kernel panic: Unable to mount root fs on 01:00 Am I missing some thing in my steps ?? Any comments will be greatly appreciated. regards -kshitij

2 1

[U-Boot-Users] Updating ELDK Kernel
by Jeff Stevens 24 Sep '03

24 Sep '03

Has anyone succesfully updated the ELDK kernel, or know when ELDK plans on updating to YDL 3.0? __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

[U-Boot-Users] LCD Driver
by Doris Bella 24 Sep '03

24 Sep '03

I am searching the driver for the LCD module MTB-046 in Linux. It is 128x64 graphics display LCD. The processor it supports is PXA255(ARM). MTB-046 MTB : Board assembly and custom design LCD Type : STN Yellow Green Rear Polarizer : Transflective Backlight Type : LED, External Power, 5V input Backlight Color : Yellow Green Temperature Range : Wide EL Driver IC : Not Buildin Touch Screen : Without Module Size - 74.6(W) x 52.7(H) x 9.0(D)Max Dot Size - 0.40(W)mm x 0.40(H)mm Dot Pitch - 0.43(W)mm x 0.43(H)mm Resolution - 128(W) x 64(H) Dots Matrix Duty Ratio - 1/64 Duty LCD Display Mode - STN(Yellow mode) Viewing Direction- 6 o' clock Backlight - LED Controller - KS0108 or compatible EL Driver - Without DC/DC Converter - Optional Is there a LCD driver available for the above LCD module (MTB-046)?. The interface is through the GPIO pins provided in the PXA255 processor?. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

[U-Boot-Users] cpu./8245x/spped.c patch
by Sangmoon Kim 23 Sep '03

23 Sep '03

Hi, It seems that pll_pci_to_mem_multiplier array in cpu./8245x/spped.c has some wrong value. This patch fixes that Regargs, Sangmoon Kim

1 0

RE: [U-Boot-Users] Problem with sourceforge cvs tarball download?
by Dave Ellis 22 Sep '03

22 Sep '03

Pantelis Antoniou wrote: > Sent: Monday, September 22, 2003 4:43 AM > I'm trying to prepare some patches against the current cvs head > and I'm having trouble downloading the current cvs tarball > from sourceforge. > > Is anyone else having the same problem? Yes, I got '404 Not Found' last Friday and today. I can get other projects, but not u-boot. Dave Dave Ellis ~~~~~~~~~~~~~~~~~~~~~~~~~~ SIXNET - "Leading the Industrial Ethernet Revolution" 331 Ushers Road, P.O. Box 767, Clifton Park, NY 12065 USA Tel +1 (518) 877-5173 Fax +1 (518) 877-8346 Email me at: dge(a)sixnetio.com Detailed product info: www.sixnetio.com ~~~~~~~~~~~~~~~~~~~~~~~~~~

2 1

[U-Boot-Users] Documented feature list anyone?
by Robin Gilks 22 Sep '03

22 Sep '03

Greetings Does anyone have a u-boot 'feature list' I could cut 'n paste into a document that justifies the use of u-boot in a project? I started picking a few things from the README file and from the top of my head but it all sounds very dry and unexciting :-)) I'm sure that someone has composed some prose that is elequent and technically correct without being bloated by too much 'boiler plating' !! Many thanks -- 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] Relocating in start.S for MPC5xxx
by Jonas Mark-r50740 22 Sep '03

22 Sep '03

Hello, I'm trying to add to U-Boot for MPC5xxx is the possibility to start from Boot Low and make it look as if the processor booted from Boot High. The reason is that I want the same image of U-Boot to run from Boot Low as well as from Boot High. What I don't want to do is adapt CFG_SDRAM_BASE and TEXT_BASE. I already tried that and made it work on IceCube by fixing a few things in icecube.c but I didn't like the result (I'll send a patch once I found out how to use SourceForge, move my code from 0.4.8 to the latest on CVS and make a patch). To make a Boot Low look like a Boot High I need to change CSBoot setup and the IP bit in the MSR. First I move CSBoot Stop to 0xFFF80000, then I change the point of execution from the current of execution 0x0000???? to 0xFFF0???? and then I move CSBoot Start to 0xFFF00000. My problem is that I have no good idea how to implement the jump from the current of execution 0x0000???? to 0xFFF0????. What I tried is lis r3, boothigh_jump@h /* Jump to Boot High location */ ori r3, r3, boothigh_jump@l mtlr r3 blr boothigh_jump: but that doesn't work as I get the error message "Error: Relocation cannot be done when using -mrelocatable". Any suggestions how to implement this? My current idea is the following which compiles without an error but I'm not sure whether it is the most clever way how to do it. I fear I'm just fooling the compiler here: bl boothigh_jump1 /* get current address */ bh_jump1: mflr r3 lis r4, 0xFFF00000@h /* add new base address */ add r3, r3, r4 lis r4, (bh_jump2 - bh_jump1)@h /* move forward to jump target */ ori r4, r4, (bh_jump2 - bh_jump1)@l add r3, r3, r4 mtlr r3 /* jump */ bh_jump2: By the way: I guard my code with "#if !defined(CFG_RAMBOOT), put it before the call of init_5xxx_core and also update r5 (contains a copy of MSR). Is that enough to not break something else? TIA Mark

1 0

[U-Boot-Users] Re: Patch s3c2410 nand-boot.
by Wolfgang Denk 22 Sep '03

22 Sep '03

Dear Gianluca, in message <3F68D1DF.7020007(a)libero.it> you wrote: > > I send you my patch for s3c2410 ARM processor. This patch implements > boot directly from nandflash. I haven't created new board in board > directory but I have writed new config-file (smdk2410nand.h) that use > smdk2410 board. I have forwarded your patch to David Müller who is the maintainer for the SMDK2410 board; I cannot test it myself. > I tested with MAKEALL ARM9 my patch. > I changed the frequency of internal clock of s3c2410 (for smdk2410 > borad) because (only) in this way the Linux Mizi kernel can boot correctly. > The patch is based on u-boot 0.4.8. > > This is my first contribution to open source and I hope that it is > useful to someone. It is definitely useful, but I have a couple of questions: * Which problem are you trying to address which is not supported by the existing NAND code? * Is it necessary to implement this in a processor specific way? * You add new configuration options like CONFIG_S3C2410_NAND_BOOT but do not include any dosumentation. At least, please provide an explantion of these options for the README fie. If you feel longer explanations are needed create a new file doc/README.NAND-Boot or so. David, I've forwarded the patch to you. Can you please have a look at the implementation details? Thanks. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "If God had wanted us to use the metric system, Jesus would have had 10 apostles."

4 4

[U-Boot-Users] need help for u-boot on flash of csb226
by renjithgopal 22 Sep '03

22 Sep '03

Has any one able to put u-boot on the flash of csb 226.. is there a patch available for that? Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets on Air Sahara Flights at Prices Lower Than Before. Just log on to http://airsahara.indiatimes.com and Bid Now!

2 1

[U-Boot-Users] Problem with sourceforge cvs tarball download?
by Pantelis Antoniou 22 Sep '03

22 Sep '03

Hi I'm trying to prepare some patches against the current cvs head and I'm having trouble downloading the current cvs tarball from sourceforge. Is anyone else having the same problem? Regards Pantelis

1 0

[U-Boot-Users] using bdi2000 to debug ppcboot on mpc7455
by Q-ha Park 22 Sep '03

22 Sep '03

Oh. I hope this question is not off topic in this mailing list:u-boot. I'm new to BDI2000, and after reading a manual that came with the tool, I tried to debug ppcboot using bdi2000 and gdb. The problem is I just can't set the breakpoint whether be it software or hardware breakpoint; For example, when I set the break point at "boot_cold" and type "continue", the program just runs without ever stopping at the breakpoint where it's supposed to stop! Here's what I did: a. turn on bdi2000. b. connect to bdi2000 in gdb session. c. set the breakpoint d. type "continue" ========== 90 li r21, BOOTFLAG_COLD /* Normal Power-On: Boot from FLASH */ (gdb) l 85 .ascii CONFIG_IDENT_STRING, "\0" 86 87 . = EXC_OFF_SYS_RESET 88 .globl _start 89 _start: 90 li r21, BOOTFLAG_COLD /* Normal Power-On: Boot from FLASH */ 91 b boot_cold 92 sync 93 94 . = EXC_OFF_SYS_RESET + 0x10 (gdb) b boot_cold Breakpoint 1 at 0xfff02000: file /home/users/qpark/hobby/ppcboot-1.1.6/cpu/74xx_7xx/start.S, line 253. (gdb) cont Continuing. (continues for good...) ========== What am I probably doing wrong? FYI, I tried to remove H/W breakpoint before I entered "go" Any help would be greatly appreciated!! ::::::::::::::::::::::::::::::::::::::::::::::::: Q-ha Park

1 0

RE: [U-Boot-Users] Re: Patch s3c2410 nand-boot.
by Woodruff, Richard 22 Sep '03

22 Sep '03

The CONFIG_OMAP1510 defines in cmd_nand.c aren't really CPU specific, they are NAND specific (for NAND parts which have their WP pins hooked up). It happens that our design hooked them up to a BIU signal which matched up to its functionality. Woodhouse had indicated to me that the general NAND MTD code would be changing to handle the selective control of the WP signal also as other devices are showing up with it connected. I think he said the parts he had previously worked with just globally disabled the wp function. Those defines should probably be renamed and inlined like the other control pin def's. I still need to put a patch in as write_oob won't work from the command line interface if the WP pin is enabled. Regards, Richard W. -----Original Message----- From: "David Müller (ELSOFT AG)" [mailto:d.mueller@elsoft.ch] Sent: Friday, September 19, 2003 5:16 AM To: Gianluca Cc: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] Re: Patch s3c2410 nand-boot. Hello Gianluca wrote: > I have changed NAND code only to remove warning beacuse I don't use > some variable an then I rewrite "unsigned long nandptr = nand->IO_ADDR;" in > "unsigned long nandptr; nandptr = nand->IO_ADDR;". > Wolfgang and I have agreed, that direct hardware accesses and board specific implementation details should be removed from "cmd_nand.c", but should be implemented in a cpu and / or board specific low level NAND flash driver instead. Please take a look at the NAND part of the Linux MTD drivers to get an idea how it should work.

2 1

[U-Boot-Users] looking for 8266.cfg file
by Currie Reid 20 Sep '03

20 Sep '03

Hello all, I am moving from bdiPro to bdiGDB and am having a difficult time getting the bdi2000 working with my mcp8266ads-pci board. I had thought that the mpc8260 cfg file would have been sufficient to accomplish this: MPC8260>prog 0xfff00000 /tftpboot/u-boot.srec srec Programming /tftpboot/u-boot.srec , please wait .... Programming flash passed MPC8260>verify 0xfff00000 /tftpboot/u-boot.srec srec Verifying /tftpboot/u-boot.srec , please wait .... Verifying target memory passed But then I do a reset, and a "go", but see nothing on the serial console. MPC8260>reset - TARGET: processing user reset request - BDI asserts HRESET - Reset JTAG controller passed - Bypass check: 0x55 => 0xAA - Bypass check: 0x55 => 0xAA - JTAG exists check passed - Target PVR is 0x80911014 - COP status is 0x01 - Check running state passed - BDI scans COP freeze command - BDI removes HRESET - COP status is 0x05 - Check stopped state passed - Check LSRL length passed - BDI sets breakpoint at 0xFFF00100 - BDI resumes program execution - Waiting for target stop passed - TARGET: Target PVR is 0x80911014 - TARGET: resetting target passed - TARGET: processing target startup .... - TARGET: processing target startup passed MPC8260>go - TARGET: target has entered debug mode I am using the same u-boot that I compiled for use with bdiPro, so I am pretty sure that it works for the board - I have been using it for some time. I am very new to hardware programming, so please bear with me if I am missing the painfully obvious. Incidentally, the reason I had to switch from bdiPro was that during kernel testing, u-boot stopped working after a boot - at which point tried to re-flash and this failed - it turned out that somehow flash sector 27 had becomed locked, and there was no way to unlock it from bdiPro; thus subsequent attempts to flash the board would fail. Now that I am using bdiGDB, I would like not to have to switch between the 2 to accomplish different tasks ( obviously ), and I very much like the idea of having an alternative to printk's to conduct kernel debugging ( how I got in this mess in the first place). Again, thank you very much for any assistance. Currie ; bdiGDB configuration file for MPC8260-ADS board ; ----------------------------------------------- ; [INIT] ; init core register WREG MSR 0x00000000 ;clear MSR WM32 0x0F0101A8 0x04700000 ;IMMR : internal space @ 0x04700000 WM32 0x04710004 0xFFFFFFC3 ;SYPCR: disable watchdog WM32 0x04710C80 0x00000001 ;SCCR : normal operation ; init memory controller WM32 0x04710104 0xFF800836 ;OR0: Flash 8MB, CS early negate, 6 w.s., Timing relax WM32 0x04710100 0xFF801801 ;BR0: Flash @0xFF800000, 32bit, no parity WM32 0x0471010C 0xFFFF8010 ;OR1: BCSR 32KB, all types accesse, 1 w.s. WM32 0x04710108 0x04501801 ;BR1: BCSR @0x04500000, 32bit, no parity WM32 0x04500004 0x3D000000 ;BCSR1: enable RS232-1 ; init SDRAM Init (PPC bus) WM16 0x04710184 0x1900 ;MPTPR: Divide Bus clock by 26 WM8 0x0471019C 0x21 ;PSRT : Divide MPTPR output by 34 ;WM8 0x0471019C 0x14 ;PSRT : Divide MPTPR output by 21 WM32 0x04710114 0xFF000C80 ;OR2 : 16MB, 2 banks, row start at A9, 11 rows WM32 0x04710110 0x00000041 ;BR2 : SDRAM @0x00000000, 64bit, no parity WM32 0x04710190 0x296EB452 ;PSDMR: Precharge all banks WM8 0x00000000 0xFF ;Access SDRAM WM32 0x04710190 0x096EB452 ;PSDMR: CBR Refresh WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM8 0x00000000 0xFF ;Access SDRAM WM32 0x04710190 0x196EB452 ;PSDMR: Mode Set WM8 0x00000000 0xFF ;Access SDRAM WM32 0x04710190 0x416EB452 ;PSDMR: enable refresh, normal operation [TARGET] CPUTYPE 8260 ;the CPU type (603EV,750,8240,8260) JTAGCLOCK 0 ;use 16 MHz JTAG clock BOOTADDR 0xfff00100 ;boot address used for start-up break WORKSPACE 0x00000000 ;workspace in target RAM for fast download BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT | GATEWAY) BREAKMODE SOFT ;SOFT or HARD, HARD uses PPC hardware breakpoints ;STEPMODE HWBP ;TRACE or HWBP, HWPB uses a hardware breakpoint VECTOR CATCH ;catch unhandled exceptions DCACHE NOFLUSH ;data cache flushing (FLUSH | NOFLUSH) ;MMU XLAT ;translate effective to physical address POWERUP 5000 ;start delay after power-up detected in ms ;REGLIST SPR ;select register to transfer to GDB ;REGLIST ALL ;select register to transfer to GDB ;VIO 7 9600 ;TCP port for virtual IO, BCSR1: enable RS232-1 !!! ;SIO 7 9600 ;TCP port for serial IO, check BCSR1: enable RS232-1 !!! [HOST] IP 47.129.82.27 FILE /tftpboot/u-boot.srec ;FILE E:\cygnus\root\usr\demo\mpc8260\fibo.exe FORMAT SREC LOAD MANUAL ;load code MANUAL or AUTO after reset DEBUGPORT 2001 PROMPT MPC8260> ;new prompt for Telnet DUMP /tftpboot/dump.bin ;DUMP dump.bin ;Linux: dump.bin must already exist and public writable [FLASH] CHIPTYPE I28BX8 ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16) ;CHIPTYPE AM29BX8 CHIPSIZE 0x200000 ;The size of one flash chip in bytes (e.g. AM29F010 = 0x20000) BUSWIDTH 32 ;The width of the flash memory bus in bits (8 | 16 | 32 | 64) ;WORKSPACE 0x04700000 ;workspace in dual port RAM WORKSPACE 0x00400000 ;workspace in SDRAM ;FILE E:\tornado\target\config\ads8260\test.hex ;The file to program ;FORMAT SREC 0x01000000 ;FILE E:\cygnus\root\usr\demo\mpc8260\init8260.S3 FILE /tftpboot/u-boot.srec ;FILE E:\cygnus\root\usr\demo\mpc8260\ads8260.sss ; ERASE 0xFF800000 ;erase sector 0 of flash SIMM (LH28F016SCT) ERASE 0xFF840000 ;erase sector 1 of flash SIMM ERASE 0xFF880000 ;erase sector 2 of flash SIMM ERASE 0xFF8C0000 ;erase sector 3 of flash SIMM ERASE 0xFF900000 ;erase sector 4 of flash SIMM ERASE 0xFF940000 ;erase sector 5 of flash SIMM ERASE 0xFF980000 ;erase sector 6 of flash SIMM ERASE 0xFF9C0000 ;erase sector 7 of flash SIMM ERASE 0xFFA00000 ;erase sector 8 of flash SIMM ERASE 0xFFA40000 ;erase sector 9 of flash SIMM ERASE 0xFFA80000 ;erase sector 10 of flash SIMM ERASE 0xFFAC0000 ;erase sector 11 of flash SIMM ERASE 0xFFB00000 ;erase sector 12 of flash SIMM ERASE 0xFFB40000 ;erase sector 13 of flash SIMM ERASE 0xFFB80000 ;erase sector 14 of flash SIMM ERASE 0xFFBC0000 ;erase sector 15 of flash SIMM ERASE 0xFFC00000 ;erase sector 16 of flash SIMM ERASE 0xFFC40000 ;erase sector 17 of flash SIMM ERASE 0xFFC80000 ;erase sector 18 of flash SIMM ERASE 0xFFCC0000 ;erase sector 19 of flash SIMM ERASE 0xFFD00000 ;erase sector 20 of flash SIMM ERASE 0xFFD40000 ;erase sector 21 of flash SIMM ERASE 0xFFD80000 ;erase sector 22 of flash SIMM ERASE 0xFFDC0000 ;erase sector 23 of flash SIMM ERASE 0xFFE00000 ;erase sector 24 of flash SIMM ERASE 0xFFE40000 ;erase sector 25 of flash SIMM ERASE 0xFFE80000 ;erase sector 26 of flash SIMM ERASE 0xFFEC0000 ;erase sector 27 of flash SIMM ERASE 0xFFF00000 ;erase sector 28 of flash SIMM ERASE 0xFFF40000 ;erase sector 29 of flash SIMM ERASE 0xFFF80000 ;erase sector 30 of flash SIMM ERASE 0xFFFC0000 ;erase sector 31 of flash SIMM [REGS] DMM1 0x04700000 FILE /tftpboot/reg8260.def

2 1

[U-Boot-Users] porting u-boot to WindRiver MDP PRO???????????????
by wang cheng 20 Sep '03

20 Sep '03

hello,all! I'm trying to put u-boot-0.4.0 to the WindRiver MDP PRO board(with a daughter board Mpc823),I use the FADS823 as my model to modify. I use the vision ICEII BDM interface to program flash and debug the code. 1.in the cpu/mpc8xx/cpu_init.c :when I masked the or/br set clause,the info can displayed on the console, when not, nothing displayed 2.After I masked the OR/BR in the cpu_init.c,when I debug with the vision ICEII BDM,everything is OK; when without the BDM, the u-boot can run to relocate_code() in lib_ppc/board.c: with vision ICE： U-Boot 0.4.0 (Sep 19 2003 - 11:12:10) CPU: PPC823ZTnnB2 at 25 MHz: 2 kB I-Cache 1 kB D-Cache Board: bcsr3=0x1000000c *((uint *)BCSR3)=0xbbbbbbbb WindRiver with db MPC823 rev MDP PRO I2C: ready DRAM: bcsr2=0x10000008 (uint *)bcsr2=0x10000008 *((uint *)bcsr2)=0xbbbbbbbb k=0x7 4 MB before relocate_code() in board.c FLASH: value=0x1 value=0xa4 size_b1=0x80000value=0x1 value=0xa4 512 kB In: serial Out: serial Err: serial Net: SCC ETHERNET => without vision ICE： U-Boot 0.4.0 (Sep 19 2003 - 11:12:10) CPU: PPC823ZTnnB2 at 25 MHz: 2 kB I-Cache 1 kB D-Cache Board: bcsr3=0x1000000c *((uint *)BCSR3)=0x2e342e30 WindRiver with db MPC823 rev MDP PRO I2C: ready DRAM: bcsr2=0x10000008 (uint *)bcsr2=0x10000008 *((uint *)bcsr2)=0x6f742030 k=0xe 4 MB before relocate_code() in board.c I have been trapped here for 3 weeks.Some guy told me that my dram hasn't been initialized correctly! I have modified the UPM table,the OR/BR, but it doesn't work! Can you tell me how to initialize the dram ? Any advices are appriciated!

1 0

[U-Boot-Users] porting u-boot to WindRiver MDP PRO???????????????
by wang cheng 20 Sep '03

20 Sep '03

1 0

[U-Boot-Users] CSB336 (dragonball mx1) port
by Bryan Larsen 19 Sep '03

19 Sep '03

I've ported U-Boot to the Cogent CSB336 single board computer. The CSB336 uses a Motorola MC9328MXL (Dragonball ARM920T) processor. The attached patch is against the latest release version (0.4.0). We're not going to be using the CSB336 for very long, so I'm not particularly concerned whether or not this makes it into the main distribution. There's probably a couple of things in there that Wolfgang does not like, anyways. But the patch should be useful for the next person who wants a CSB336 or Dragonball MX1 port. cheers, Bryan P.S. Patch removed because the list rejected it as too big. Email me if you want it.

1 0

[U-Boot-Users] uboot compatible 8266 BDI cfg
by Allen Curtis 18 Sep '03

18 Sep '03

This matches the uboot memory configuration.

2 1

[U-Boot-Users] U-Boot for AT91RM9200
by Steven Scholz 18 Sep '03

18 Sep '03

Hi there, I will have a AT91RM9200 based board real soon now. So I started browsing the U-Boot source etc to see what I'll have to do then. But I am already confused! I read a document by ATMEL which states that I need a Urloader to decompress and start a gzipped version of U-Boot. Does it have to be this way? Why this two-step procedure? Is that the reason why I can't find any SDRAM init code in the sources? Are there any other boards out there using the AT91RM9200 processor except the eval board AT91RM9200DK ??? Thanks a million for any pointers. Steven

1 0

[U-Boot-Users] RE: [PATCH][CFT] bring ARM memory layout in line with the documen ted behaviour
by Gupta, Kshitij 18 Sep '03

18 Sep '03

hi Anders, the patch works for omap(omap1510/omap1610) based boards. But now should we change our TEXT_BASE to accomodate for malloc() memory allocations. regards -kshitij -----Original Message----- From: Anders Larsen [mailto:alarsen@rea.de] Sent: Thursday, September 18, 2003 5:45 PM To: Wolfgang Denk Cc: Peter Figuli; Marius Grger; Kyle Harris; Gary Jennejohn; Gupta, Kshitij; David Mller; Rolf Offermanns; Robert Schwebel; Alex Z pke; u-boot-users(a)lists.sourceforge.net Subject: Re: [PATCH][CFT] bring ARM memory layout in line with the documented behaviour Wolfgang Denk <wd(a)denx.de> schreibt: >in message <fc.004c4e48001cba02004c4e48001cba02.1cba71(a)rea.de> you wrote: >> >> Since the stack and malloc-heap are now located below the U-Boot code, >> the TEXT_BASE of the supported ARM boards can be increased accordingly >> (for most (but not all) boards, the patch already does this). > >This is actually the biggest "problem" with the existing ARM code (as >inherited from ARMBoot): with the orginal philosophy of PPCBoot, >TEXT_BASE should not play ANY role here. > >The way I would like to soo this implemented, and as it _is_ >implemented in PPCBoot (and in U-Boot for PowerPC) is as follows: > >TEXT_BASE determines the start address in FLASH memory which is used >before relocation. > >The RAM initialization code is, among other things, responsible to >determine the size of the RAM, and the relocation address is then >calculated DYNAMICALLY dependend on the RAM size found. This allows >that boards with different RAM sizes will always provide maximum free >RAM under U-Boot. Dear Wolfgang, are you saying that the patch doesn't go far enough? (I feared that the patch might have gone too far :-) It looks like a substantial amount of work to implement your wishes (but its doable, I believe). Would you accept the patch as is as a first step in that direction (in order not to change too much in one step) provided the other ARM board maintainers don't object? > >> Memory layout example based on my PXA255 (TEXT_BASE = 0xA07E0000): >> >> 0xA079FF74 Monitor Stack (growing downwards) >> 0xA079FF80 Board Info Data and permanent copy of Global Data >> 0xA07A0000 Malloc Arena >> 0xA07E0000 RAM copy of Monitor Code >> ... optional: Frame Buffer >> 0xA07FFFFF [End of RAM] > >I still see references to _armboot_start, _armboot_end_data, and >_armboot_end - which role do these play now? Can we get rid of them? > >How are they (should they be) set in your memory map above? _armboot_start contains the value of TEXT_BASE (0xA07E0000); it seems TEXT_BASE and _armboot_start are both used for the same purpose in different parts of the (ARM) code. Furthermore, the startup code (cpu/<arm>/start.S) internally uses another variable (_TEXT_BASE) with the same content as _armboot_start. I agree that this mess should be cleaned up. _armboot_end_data is the end address of the initialized data section, and is only used in one place (board/logodl/flash.c - the reference in lib_arm/board.c is purely informational). _armboot_end is the end address of the BSS and is used to determine the address of the VFD buffer. Eliminating those should be doable, and at least the patch already eliminates _armboot_real_end. > >I think some more code should be changed like the allocation of >display memory (see CONFIG_VFD in "lib_arm/board.c") - this should be >done like we do for PowerPC, too. Again, my available HW doesn't have a display, so I can't test it. I'll take a look at it anyway, though. > > >Any test results / comments from the other board maintainers? Any comment is appreciated! Cheers Anders

1 0

[U-Boot-Users] [PATCH] build on Cygwin
by Anders Larsen 18 Sep '03

18 Sep '03

Hi, here's a patch against 0.4.8 that allows U-Boot to be built on a Cygwin- hosted platform. Problems solved: - mkimage.c, img2srec.c and bmp_logo.c wouldn't compile - mkimage converted all 0x0a to 0x0d 0x0a in the binary image CHANGELOG: allow mkimage to build and run on Cygwin-hosted systems Cheers Anders

3 4

[U-Boot-Users] AT91RM2000DK: Location of U-Boot?
by Steven Scholz 18 Sep '03

18 Sep '03

Hi there, where is U-Boot stored on the AT91RM9200DK eval board? At the beginning of the parallel flash? Or in the 128kB two-wire EEPROM? Thanks, Steven

1 0

[U-Boot-Users] 回覆：[U-Boot-Users] Re: Patch s3c2410 nand-boot.
by KevinLiao＠iei.com.tw 18 Sep '03

18 Sep '03

3 2

[U-Boot-Users] bdiGDB configuration for AT91RM9200DK ??
by Steven Scholz 18 Sep '03

18 Sep '03

Hi there, has someone a bdiGDB configuration for Atmel AT91RM9200DK evaluation board? Thanks, Steven

1 0

[U-Boot-Users] [PATCH] MPC8266 default config...
by Rune Torgersen 18 Sep '03

18 Sep '03

A few things had to be changed to get the board to run correctly on using u-boot 0.4.8. CHANGELOG * Changed sdam parameter init so Page Based mode works for standard 16MB DIMM * Changed reset addess (CFG_RESET_ADDRESS) * Added SDRAM init delay for standard 16MB DIMM This is the weird part. On my 8266ADS board, If I don't have a delay between memory init and code relocation, u-boot hangs, but only when using the 16MB DIMM that came with the board. Using any other DIMM works great. Rune Torgersen System Developer Innovative Systems LLC 1000 Innovative Drive Mitchell, SD 57301 Ph: 605-995-6120 www.innovsys.com

2 1

[U-Boot-Users] [PATCH] enable 3.rd UART on PXA
by Anders Larsen 18 Sep '03

18 Sep '03

Hi, here's a patch against 0.4.8 that enables the 3.rd UART (ST-UART) on the PXA(XScale) CPUs. Furthermore, it enables watchdog-support in the same way it's already implemented on numerous other devices. CHANGELOG: Allow the PXA ST-UART to be used as console Cheers Anders

2 1

[U-Boot-Users] [PATCH] allow CFG_ALT_MEMTEST to be used on ARM
by Anders Larsen 18 Sep '03

18 Sep '03

Hi, here's a patch against 0.4.8 that allows CFG_ALT_MEMTEST to be used on systems where writing to address zero crashes the system. On ARM (well, at least on my PXA255) writing to address zero causes a "data abort" (which, IMHO, is a Good Thing(tm)). This patch allows the board-specific config to define an alternative scratch-address (CFG_MEMTEST_SCRATCH) to be used by the extensive memory test. CFG_MEMTEST_SCRATCH does not have to point to physical RAM, it only has to point to a writeable (not necessarily readable) address. CHANGELOG: Allow CFG_ALT_MEMTEST on systems where address zero isn't writeable Cheers Anders

2 1

[U-Boot-Users] [PATCH] fix potential crash-window
by Anders Larsen 18 Sep '03

18 Sep '03

Hi, here's a patch against 0.4.8 that closes a window where any console-I/O would crash U-Boot. Specifically, the setting of GD_FLG_DEVINIT is delayed until the console is completely initialized. CHANGELOG: don't declare "all devices initialized" until they really are... Cheers Anders

2 1

[U-Boot-Users] [PATCH] fix spelling errors
by Anders Larsen 18 Sep '03

18 Sep '03

Hi, here's a patch against 0.4.8 that fixes some spelling mistakes CHANGELOG: fix spelling mistakes Cheers Anders

2 1

[U-Boot-Users] RE: Determining the UPMA. UPMB SDRAM table
by Keith Outwater 17 Sep '03

17 Sep '03

> -----Original Message----- > From: Raghu [mailto:raghu_dk@yahoo.com] > Sent: Tuesday, September 16, 2003 8:30 PM > To: u-boot > Subject: [U-Boot-Users] Determining the UPMA. UPMB SDRAM table > > > Hello, > > Just courious to know how does one determine the SDRAM > table to MPC8xx family of processors ?? > > Warm Regards > Raghu. Raghu - As Robin Gilks pointed out in another post, Motorola has a tool called MCUinit on their web site that also includes a tool called UPM860. UPM860 allows you to graphically edit the SDRAM timing waveforms and then generate a UPM table. Very handy (I used UPM860). I also found Motorola application note AN2066/D very helpful when designing my SDRAM hardware interface and writing the UPM tables and SDRAM init code. Finally, take a look at the SDRAM initializations of 860 based boards in the U-Boot sources. You can get a good head start by doing this and depending on the SDRAM you use, you may be able to copy the UPM tables and initializations. Many SDRAMs from different manufacturers use the same or similar init sequence and timing. Just remember that if you copy the UPM tables from another board, be sure to determine which UPM outputs are connected to which SDRAM pins. The MPC860 provides a lot of flexibility in this area and different hardware designs may use different pin assignments. Read your SDRAM datasheet carefully and implement the required initialization. One final tip: if you copy the UPM tables, feed the tables back into UPM860 and you'll get a graphical representation of the timing. This reverse-engineering step will allow you to see what's going on and make any changes that may be appropriate for your particular hardware. The port I did of U-Boot to my generic MPC860T design (GEN860T) may be a possible starting point. I tried to make the SDRAM init clear and straightforward. Hope this helps, Keith Keith Outwater Sr. Staff Engineer Microvision, Inc. 19910 N. Creek Parkway Bothell, WA 98011

1 0

RE: [U-Boot-Users] MPC8266ADS
by Rune Torgersen 17 Sep '03

17 Sep '03

Make sure you burn the flash image for U-Boot at the very start of flash (no matter where that is). If you program it with the jumper in the default position, start programming at 0xff800000. This will place the image correctly. (New HRCW _must_ be at very start of memory) > I should have said, the latest u-boot-0.4.x. I did a cvs > checkout last night > which shows me the LABEL_2003_09_13_2100 for mpc8266ads.c. > And I confirmed > that mpc8266ads.c does indeed have the PBI turned off. Will verify latest later today.

1 0

[U-Boot-Users] data abort
by Glenson Muthedan 17 Sep '03

17 Sep '03

Hello everybody! First of all thanks to Wolfgang Denk and Robert Schwebel for the helpful instructions to get started with U-Boot and BDI2000. Now, I've a new problem: When U-Boot starts I can see following outsputs through "cu", before the system stops due to a data abort. (My board: PXA250, 32MB SDRAM, 32MB Strataflash, etc.) **************************************************** U-Boot 0.4.0 (Sep 15 2003 - 12:09:08) U-Boot code: A1FE0000 -> A1FF5728 BSS: -> A1FF6BD4 DRAM Configuration: Bank #0: a0000000 32 MB Flash: 32 MB data abort undefined instruction undefined instruction undefined instruction **************************************************** I put some printf-lines(beginning with GM) in the soucecode to see where the execution stops. Here, my debug-output: **************************************************** U-Boot 0.4.0 (Sep 15 2003 - 12:23:05) U-Boot code: A1FE0000 -> A1FF5870 BSS: -> A1FF6D1C DRAM Configuration: Bank #0: a0000000 32 MB Flash: 32 MB GM: lib_arm/board.c; entering devices_init() GM: common/devices.c; entering ListCreate() GM: common/lists.c; after 'list = (list_t) (NewHandle (sizeof (ListStruct)))' GM: common/lists.c; list = 0badc108 GM: common/lists.c; *list = a1ff10a0 data abort prefetch abort prefetch abort prefetch abort prefetch abort **************************************************** If I understand right, this exception occurs due to access to the contents of the created list. For example at the line(lists.c: ListCreate): (*list)->numItems = 0; Why does this happen? I'm quite sure that my Flash and SDRAM are working properly. Can somebody suggest a way to workaround this problem? Thanks. Glenson Muthedan.

4 12

[U-Boot-Users] MPC8266ADS
by Jeff Angielski 17 Sep '03

17 Sep '03

>The current configuration in U-BOOT works, and boots Linux with no problem. >It will, however, not work on a virgin ADS development board. You have to >change one jumper to get the CPU to use the Hardware Configuration word from >Flash, and not from BCSR... (JP3 I think). Can somebody confirm that the latest u-boot-0.4.0 with default settings on all jumpers except for JP3 works correctly. I just downloaded the latest code from CVS and it is not working for me. Incidentally, u-boot-0.3.0 works on the board with the default jumper settings (including JP3 on 2-3 BCSR) and no code changes right out of the box. Also, does anybody have a BDI2000 config file for the MPC8266ADS that matches the new configuration from u-boot-0.4.0? -- ==================================================== Jeff Angielski jeff(a)ThePTRGroup.com ====================================================

3 4

[U-Boot-Users] New board...
by Anders Larsen 17 Sep '03

17 Sep '03

Hi Wolfgang, I'm currently porting U-Boot to a PXA-based industrial device developed by my employer. Since the code I write/modify/adapt is covered by the GPL I'd like to know what to do with it - can I push it to you for inclusion in U-Boot (although we do not sell the naked board) or must I follow the provisions of the GPL (e.g. ship the source code with the device)? Cheers Anders

3 2

[U-Boot-Users] Determining the UPMA. UPMB SDRAM table
by Raghu 17 Sep '03

17 Sep '03

Hello, Just courious to know how does one determine the SDRAM table to MPC8xx family of processors ?? Warm Regards Raghu. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

RE: [U-Boot-Users] data abort
by Woodruff, Richard 16 Sep '03

16 Sep '03

I had similar problems with the 925 when I first enabled devices via devices_init, the arm code does not do selective remapping. Inside devices_init() should be a conditional for ARM only. I suspect your -pxa patch wiped this or other such code out. Regards, Richard W. > -----Original Message----- > From: Glenson Muthedan [mailto:glenson@gmx.de] > Sent: Tuesday, September 16, 2003 1:44 PM > To: u-boot-users(a)lists.sourceforge.net > Subject: Re: [U-Boot-Users] data abort > > > Hello! > > Thank you guys for your kind help. My SDRAM initialization was not > correct. Now, having done some changes, everything seems to work > smoothly except one line in devices_init() in the file > common/devices.c > > The execution stops at the line > gd->flags |= GD_FLG_DEVINIT; /* device initialization done */ > > Then, sometimes a "prefetch abort" occurs, sometimes it just hangs. > > When I comment this line, U-Boot runs up to the bootloader-prompt > without any problem. So I hope, the line above is not a > crucial one if I > only have to do with the serial console. But I'm interested > to know what > you think about this temporary solution; am I running into > problems later? > > Regards. > Glenson. > > > Wolfgang Denk wrote: > > Fix your SDRAM initialization. > > Robert Schwebel wrote: > > Sounds like memory problems. Are you sure you did your RAM > > initialization correct? > > Anders Larsen wrote: > > ...or because ListCreate() can't allocate a (writable) > block of RAM. > ... > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users >

1 0

[U-Boot-Users] compile u-boot (error)
by Chien-Lung Wu 16 Sep '03

16 Sep '03

Hi, I am working on a project to bring up MPC 8240/8245. I try to use u-boot. However, I got error when I compile u-boot source code. Since I am working a hardware by our company, I follow the instruction to create related files and then compile u-boot. The error message is: gcc -Wall -pedantic -I ../include -I.. -D TEXT_BASE=0xFFF00000 -DUSE_HOSTCC -O -o img2srec.exe imag2srec.o /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/ld: cannot find -lcygwin collect2: ld returned 1 exit status. ( I am working on window NT/cygwin platform.) Do anyone have similar experience? Your suggestions and opinion will be great helpful for me. TIA. David,

2 1

[U-Boot-Users] SDRAM Table for K4561633C - RL 75
by Raghu 16 Sep '03

16 Sep '03

Hello All, I have a board that has Samsung K4S561633C - RL75 SDRAM. Two chips of ( 32 Mbit each total of 64MByte ) I want the sdram_table[] parameters, where can I get them ? The same chip is used in wepep250 board for ARM architecture, but I could not locate the SDRAM table. Warm Regards, Raghu. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

2 1

[U-Boot-Users] What are the Post codes generated?
by deya privi 16 Sep '03

16 Sep '03

Hi What are the post codes and error codes genereted by u-boot for PXA255? Thanks in advance for any help! Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

2 1

[U-Boot-Users] question about standalone application
by Chan Queenie-r54684 16 Sep '03

16 Sep '03

Hi all, I'm new to U-Boot. I'd like to run an application after my custom board is booted up. In the U-Boot readme file, I learned there is a command called "loads" which will download the *.srec from the host to the board through serial line. So I want to download the hello world demo and see how it works. I don't know how I should setup my board and my host. My host run on Windows 2000 and connects to the board using HyperTerminal. With that, I'm able to see the bootup message. When I type "loads", it shows the following: => loads ## Ready for S-Record download ... but the next line "~>examples/hello_world.srec" never comes out. Must I use Linux as the host? I downloaded C-Kermit for Linux and Windows XP, too. But I couldn't set it up correctly. In Linux, I entered the following commands and expected to see the bootup message as in HyperTerminal, but I didn't. set line <my device> set speed 115200 set serial 8N1 set carrier-watch off connect And I couldn't make a connection using Kermit 95 for Windows XP either. What have I done wrong? Please help! Your advice is appreciated. Best Regards, Queenie Chan NCSD Application Engineer

2 1

[U-Boot-Users] Conditional 'hush' script examples anyone?
by Robin Gilks 16 Sep '03

16 Sep '03

Greetings I've RTFM'd and I've FAQ'd but I still can't find a single example of the use of conditionals with the u-boot hush shell command line. I assume its only usable with an autoscript or can environmental variables hold complete conditional blocks. Most interested in this so that I can make sensible decisions about what to do if an image CRC is bad for example (or when to boot a different image after an upgrade). Examples, examples, examples is what I'm looking for rather than a dry explanation about hush (which I can get close to from any book that documents bash!!) Many thanks -- 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

6 14

RE: [U-Boot-Users] hi
by erik.teose＠exgate.tek.com 16 Sep '03

16 Sep '03

OK, Wolfgang, want to take this one? :-) Erik -----Original Message----- From: Dannel_Zhang To: u-boot-users(a)lists.sourceforge.net Sent: 9/15/2003 9:25 PM Subject: [U-Boot-Users] hi

2 1

[U-Boot-Users] [Q] MPC8245 A3000 board
by 배장식 16 Sep '03

16 Sep '03

hi.... i use a A3000 board (mpc8245) i find piece which is strange.. The time flows slowly.. blow factor is a result which it confirms as an date command date command realtime ( my pc time) Artis:~>date Thu Jun 13 20:02:13 KST 2002 Thu Sep 16 12:12:13 1 minute later check result Artis:~>date Thu Jun 13 20:02:28 KST 2002 Thu Sep 16 12:13:13 It probably is like this why, it is anxious Best Regard~~

1 0

[U-Boot-Users] hi
by Dannel_Zhang 16 Sep '03

16 Sep '03

1 0

[U-Boot-Users] U-Boot-CVS mailing list available
by Wolfgang Denk 15 Sep '03

15 Sep '03

As requested, I have created a new U-Boot related mailing list: U-Boot-CVS(a)lists.sourceforge.net You can subscribe at http://lists.sourceforge.net/mailman/listinfo/u-boot-cvs All ckeck-ins to the CVS (change log plus context diffs) will be posted to this list. Hope this helps. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de The software required `Windows 95 or better', so I installed Linux.

1 0

[U-Boot-Users] memory map?
by deya privi 14 Sep '03

14 Sep '03

Hi, As per the U-boot at what locations should the bootloader image and kernel image shall be placed in Flash memory? Thanks in advance. Regards, Deya. ________________________________________________________________________ Yahoo! India Matrimony: Find your partner online. Go to http://yahoo.shaadi.com

2 1

[U-Boot-Users] Porting U-Boot to custom board
by sharad＠buckeye.ece.drexel.edu 14 Sep '03

14 Sep '03

Hi, I am new to this group. I am involved with porting U-boot to a custom board based on PowerPC 7455. Right now, we are at the point where we have just got our bus slave working so U-boot is our next logical step. And ultimately, Linux kernel. Looking at the README and the source code it seems like with the support of this group, we shall be able to do it. One note, just browsing through include/asm-ppc/processor.h ... it seems like the SPR numbers for [DI]BAT4[UL]-[DI]BAT7[UL] have been interchanged i.e upper register gets the SPR number of the lower register and vice-versa. Just thought to bring this to notice. Looking forward to your support, Sharad Gupta

2 1

[U-Boot-Users] Re: Patches for U-Boot
by Wolfgang Denk 13 Sep '03

13 Sep '03

In message <3F62CC58.8060604(a)elsoft.ch> you wrote: > > The attached patch fixes the following issues: > > Makefile: add $(CC) to "-print-libgcc-filename" so compiler gets > correct libgcc file Description and patch disagree. In the patch, you add not "$(CC)" [which is already there - obviously], but "$(CFLAGS)". What makes you think that options like "-Wall" or "-Wstrict-prototypes" would change the behaviour of "-print-libgcc-filename" ?? Rejected. > README: mention VCMA9 board > > board/mpl/vcma9/* various changes to VCMA9 board specific files Added. > common/cmd_nand.c prepare S3C2410 support (more to follow) I think it's a bad idea to ``#include "../board/mpl/vcma9/vcma9.h"'' in a common source file. Either vcma9.h contains definitions valid and necessary for all S3C24xx boards, then those should be moved into to common header file; or they include board specific stuff, and then they should not be needed in common/cmd_nand.c Rejected. > drivers/s3c24x0_i2c.c adjust delay value and some cleanup Please explain why you think that this modification: - i = I2C_TIMEOUT * 1000; + i = I2C_TIMEOUT * 10000; status = i2c->IICCON; while ((i > 0) && !(status & I2CCON_IRPND)) { - udelay(1000); + udelay(100); status = i2c->IICCON; i--; } changes or improves the behaviour. I see no advantages. Rejected for now. I see no advantages. Rejected for now. > rtc/s3c24x0_rtc.c remove unnecessary enable/disable stuff and cleanup Do you think the enable/disable stuff hurts? Left as is, rest applied. Changes will show up on CVS "soon". Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "To IBM, 'open' means there is a modicum of interoperability among some of their equipment." - Harv Masterson

1 0

[U-Boot-Users] need help regarding u-boot for csb226
by renjithgopal 13 Sep '03

13 Sep '03

Hello I am a beginner I was trying to compie u-boot for csb226. but it is giving some compiler error. make[1]: Entering directory `/uboot/lib_generic' arm-linux-gcc -g -Os -fno-strict-aliasing -fno-common -ffixed-r8 -mshort-load-bytes -msoft-float -D__KERNEL__ -DTEXT_BASE=0xa1fe0000 -I/uboot/include -fno-builtin -ffreestanding -nostdinc -isystem include -pipe -DCONFIG_ARM -D__ARM__ -mapcs-32 -march=armv4 -mtune=strongarm1100 -Wall -Wstrict-prototypes -c -o crc32.o crc32.c as: unrecognized option `-marmv4' In file included from /uboot/include/common.h:77, from crc32.c:12: /uboot/include/image.h:148: output pipe has been closed cpp0: output pipe has been closed make[1]: *** [crc32.o] Error 1 make[1]: Leaving directory `/uboot/lib_generic' make: *** [subdirs] Error 1 but when i asked some of my friends they told it should work fine with out any problem.. i am using u-boot 0.4.6 and arm-linux-gcc 2.95.3 i am also attaching the log of compilation ... please tell me what to do? Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com Bid for for Air Tickets on Air Sahara Flights at Prices Lower Than Before. Just log on to http://airsahara.indiatimes.com and Bid Now!

4 8

[U-Boot-Users] RTC on ebony
by Dhanuka, Anupam 13 Sep '03

13 Sep '03

Hi all I have been using u-boot for the IBM ebony board (it works very well :)). The Ebony board has an RTC. However, in my custom board I am planning not to have the RTC. Will this affect u-boot in any way? Basically what I am trying to ask is that, does u-boot use the RTC? Thanks Anupam S/W Design Engineer Dolby Labs 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

RE: [U-Boot-Users] MPC8266ADS patch
by Curtis, Allen 13 Sep '03

13 Sep '03

> > < $(OBJCOPY) -O binary $< $@ 2>/dev/null > > --- > > > $(OBJCOPY) -O ppcboot $< $@ 2>/dev/null > > Please explain why. Does the MontaVista version of the binutils doe > not understand "binary" output format any longer? > > The MontaVista tools will not convert binary to srec. You get an error > message about unknown architecture. However I discovered the ppcboot options > which works fine. Another solution is to use "dd" to strip the 64k header. Well, this is a bug in the MV toolchain then. Complain at MV. We will NOT add this to the Makefile as it breaks all other systems. My suggestion was to add this as a comment to the Makefile. > > Index: board/mpc8266ads/config.mk > > ================================================================== > > RCS file: /cvsroot/u-boot/u-boot/board/mpc8266ads/config.mk,v > > retrieving revision 1.2 > > diff -r1.2 config.mk > > 30c30 > > < TEXT_BASE = 0xfe000000 > > --- > > > TEXT_BASE = 0xfff00000 > > Please explain why you think this is necessary. > > The reset vector for 8260 is 0xfff00100. The easiest way to u-boot to put > code at this location is to change TEXT_BASE. This is the same as the > MPC8260 config.mk file.... There is no relation between the reset vector and TEXT_BASE. You can have the reset vector at 0x100 and TEXT_BASE - say - at 0x40000000. I don't think I want to change this configuration (which seems to be working to several people) without a really good reason. The reset address is either 0x00000100 or 0xfff00100. The current u-boot configuration doesn't locate any code at these locations. The MPC8260 configuration specified TEXT_BASE as 0xfff00000 and it works. The current u-boot configuration does not boot. > FLASH_BASE 0xff800000 - the board ships with a 8MB SIMM. This is the base > address. You can map the flash at any arbitrary address. I don't see why 0xFF800000 would be any better than 0xFE000000 - on contrary - mapping it at 0xFE000000 leaves enough room if there should ever be a board with bigger flash chips. As long as something responds to the 0xfff00xxx address range you are correct. > CFG_BCSR & CFG_PCI_INIT - according to the memory map in the MPC8266ADS > manual, these are the physical addresses. You need to access the BCSR to > enable the serial and Ethernet ports. Physical addresses on a 82xx are programmable. The programming of the memory controller decides where a device shows up in the physiacal memory map. Please ignore the memory map given in the manyal - it is just one example out of many possible, and it is an example which will NOT work with Linux. If the only hardware requirement is chip-select generation, this is correct. It would be better to move these to another location. > Actually I think it is a bug to map the BCSR at a low address like > 0x04500000. Are you really, really sure that this will work with > Linux? > > Virtual address != Physical address > These are correct according to the documentation You are wrong. There are certain address ranges in Linux which are mapped with virtual"physical 1:1. The IMMR and BCSR areas are among them. This is very implementation specific. There have been several discussions about the use of BATs with these architectures. > This works. The current u-boot implementation does not work. Perhaps the > current configuration works with a different board configuration. If that is > true, then there should be a big note somewhere with detailed configuration > notes. I doubt that you have any Linux applications running with your configuration. I see Linux and u-boot as two very different things. In my opinion it is useful to have the BIOS follow the documented configuration. This helps the person who is trying to bring up, and probably learn, a new platform. As they become comfortable with the hardware they can deviate from the standard configuration. The difference is that they made those changes and didn't need to refer to several documents (or source code) to figure out a memory map. When Linux boots, it assumes the BIOS is brain-dead and reconfigures everything. The BCSR and IMMR will be relocated to what makes sense for that operating environment.

2 2

[U-Boot-Users] MPC8266ADS PBI memory patch
by Rune Torgersen 12 Sep '03

12 Sep '03

Changed default memory option on MPC8266ADS to not be Page Based Interleave, since this doesn't work very well with the standard 16MB DIMM > > Only other issue I know about (in u-boot-0.4.5) is that the memory > > controller is set to use Page Based Interleave (PBI), which > I do not > > think works with the standard 16MB DIMM that comes with the eval > > board. There were some discussion about setting the SDAM > field of the > > PSDMR differently to fix this, but I havent gotten that to > work. Fix > > is to use bigger than 16MB DIMM, or turn off PBI (top of > > board/mpc8266ads/mpc8266ads.c) This should probaby be changed... > > If you know for sure, can you please submit a patch?

2 1

Re: [U-Boot-Users] Uncompressing kernel ..... OK (Hangs here)
by James Bates 12 Sep '03

12 Sep '03

Thanks everyone, Loads of issues were pointed out there for me to solve (Thanks) but the main one was to do with my console baud rate after all. When I changed my terminal emulator to 9600 linux was there up and running all along. The problem was that U-boot was configured to run at 115200 and linux at 9600. The problem I have now is changing my u-boot baud rate to 9600 (which is what the powers that be have decided). I tried changing CONFIG_BAUDRATE to 9600 but it has no effect, it just stays at 115200. Any ideas? Thanks again, James Bates This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.

3 3

[U-Boot-Users] PXA (XScale) memory layout
by Anders Larsen 12 Sep '03

12 Sep '03

Hi folks, is there any particular reason why the PXA uses a different memory layout than the other ARMs? It seems to be causing a certain amount of grief (and dirty workarounds, like e.g. in board/wepep250/wepep250.c lines 43..53) that cpu/pxa/start.S places stack (and heap) below the code instead of above. I'd be grateful if somebody could enlighten me on this. cheers Anders

4 8

[U-Boot-Users] Unable to compile the U-boot-0.4.8 version for OMAP1610/1510/smdk2410
by Rahul Shanbhag 12 Sep '03

12 Sep '03

Hi All, I am not able to compile the new u-boot tar ball i.e. u-boot-0.4.8, u-boot-0.4.7 compiles fine . I got the following error message after make omap1610inn_config make command "In file included from /home/rahul/omap1610/0-4-8/u-boot-0.4.8/include/common.h:4 0, from uboot_drv.c:26: /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:43: parse error before `__gnuc_va_list' /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:43: warning: data defin ition has no type or storage class /usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h:110: parse error before `va_list' " can anybody tell me what is the problem. Thanks Rahul

3 4

Re: [U-Boot-Users] Kernel hangs after decompressing.
by DavidHo＠nanometrics.ca 12 Sep '03

12 Sep '03

Hi Wolfgang, >> I copied the bd_info structure from u-boot.h to rpxclassic.h in the kernel > This is wrong. You should include ppcboot.h in rpxclassic.h. Okay, I originally copied the structure from u-boot.h to ppcboot.h. But seeing that another bd_t structure was declared in rpxclassic.h, I decided to replace the structure in rpxclassic.h. Your approach is definitely more elegant. Made the change to rpxclassic.h. > This cannot work. The powerpc kernel requires load address == entry > point = 0x0000. Correct me if I'm wrong, I thought the kernel can be booted from any location in memory, the startup code in the i386 tree can boot the kernel from low and high memory. I should've been more faithful to the documentation. =) I set the kenrel load address back to 0x0000. I had to move the tftp load address to 0x400000 so that it had enough space to decompress the kernel to low memory. That was the problem I had before because by default tftp loads uImage to 0x100000. But I'm back to the same problem again that as soon as u-boot passes control to the kernel, it hangs without spitting a single meaningful message to the console. I really need someone to tell me what could possibly go wrong here. =) I switched on the debug messages in hope you might spot something interesting there. >> I made the uImage from vmlinux in the top level directory and the >> vmlinux.gz from arch/ppc but they hanged at the same point. > Did you read the README? You should. I used the very first method shown in the README to build the uImage from vmlinux. I converted the it to a binary file, gzipped it and used mkimage to build the final image file. I then used the typical way of building the image that makes use of the vmlinux.gz in arch/ppc/boot/images and run mkimage directly on it. The only thing I haven't tried is building one from an uncompressed image. Regards, David Ho U-Boot 0.4.0 (Sep 11 2003 - 14:44:53) CPU: XPC860xxZPnnD4 at 50 MHz: 16 kB I-Cache 8 kB D-Cache FEC present Board: EP860 I2C: ready DRAM: 16 MB Top of RAM usable for U-Boot at: 01000000 Reserving 130k for U-Boot at: 00fdf000 Reserving 132k for malloc() at: 00fbe000 Reserving 64 Bytes for Board Info at: 00fbdfc0 Reserving 44 Bytes for Global Data at: 00fbdf94 Stack Pointer at: 00fbdf78 New Stack Pointer is: 00fbdf78 Now running in RAM - U-Boot at: 00fdf000 FLASH: 16 MB In: serial Out: serial Err: serial U-Boot relocated to 00fdf000 Net: FEC ETHERNET ### main_loop entered: bootdelay=5 ### main_loop: bootcmd="tftpboot; setenv bootargs root=/dev/nfs rw nfsroot =$(ser verip):$(rootpath) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask): $(hostname): :off; bootm" Hit any key to stop autoboot: 0 => tftp Trying FEC ETHERNET TFTP from server 199.71.138.8; our IP address is 199.71.138.25 Filename 'uImage'. Load address: 0x400000 Loading: ################################################################# ################################################################# ########################################### done Bytes transferred = 883653 (d7bc5 hex) => bootm ## Booting image at 00400000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 883589 Bytes = 862.9 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x00FBDBF0 => set upper limit to 0x00800000 ## cmdline at 0x007FFF00 ... 0x007FFF61 bd address = 0x00FBDFC0 memstart = 0x00000000 memsize = 0x01000000 flashstart = 0xFC000000 flashsize = 0x01000000 flashoffset = 0x00000000 sramstart = 0x00000000 sramsize = 0x00000000 immr_base = 0xFA200000 bootflags = 0x00000001 intfreq = 50 MHz busfreq = 50 MHz ethaddr = 00:10:EC:80:3B:49 IP addr = 199.71.138.25 baudrate = 9600 bps No initrd ## Transferring control to Linux (at address 00000000) ...

2 1

[U-Boot-Users] u-boot on Memec P4/7-FG456 (w/ virtex II pro)?
by jds 12 Sep '03

12 Sep '03

hi, has anyone done any u-boot porting work for the Memec Virtex-II Pro P4/7-FG456 evaluation board? as you can see from the link below this is a development board which has the Virtex-II Pro (w/ single 405GP core) along with SDRAM, NV stroage via compact flash, and so forth. http://www.memec.com/cgi-bin/bvutf8/memec/scripts/local/manuDetailArticle.j… we are considering using this board as an R&D platfrom for an upcoming project. thanks! -- Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. - Antoine de Saint-Exupery

2 2

RE: [U-Boot-Users] MPC8266ADS patch
by Rune Torgersen 11 Sep '03

11 Sep '03

> When Linux > boots, it assumes the BIOS is brain-dead and reconfigures > everything. The BCSR and IMMR will be relocated to what makes > sense for that operating environment. This is not enirely true for PPC Linux. It is true for x86. On PPC, Linux assumes that the BIOS or bootloader initalizes all the board or CPU specific hardware. Like the FCCs for ehternet, serial ports (for initial debug output), IO pins used by FCCs, and serial ports.(linux doesn't touch thesse) Some of the meory map (specifically where the IMMR and to a lesser extent BCSR) Linux depends on the bootloader to tell it where they are.

1 0

RE: [U-Boot-Users] MPC8266ADS patch
by Rune Torgersen 11 Sep '03

11 Sep '03

> > This works. The current u-boot implementation does not > work. Perhaps > > the current configuration works with a different board > configuration. > > If that is true, then there should be a big note somewhere with > > detailed configuration notes. > > I doubt that you have any Linux applications running > with your configuration. > > Rune, are you reading this? I don't have a MPC8266ADS > board to actually test this, but you are the board > maintainer. What is your comment? > The current configuration in U-BOOT works, and boots Linux with no problem. It will, however, not work on a virgin ADS development board. You have to change one jumper to get the CPU to use the Hardware Configuration word from Flash, and not from BCSR... (JP3 I think) There is a huge textbox in the start of the MPC8266ADS.h file that explains this. There is absolutely no reason to change the BCSR and PCI_INT addresses. They work fine as they are set now. I don't know how the unified PQ2 port (which should work on all the MPC826xDAS boards and the new PQ2 boards) is set up. Haven't tried it. Only other issue I know about (in u-boot-0.4.5) is that the memory controller is set to use Page Based Interleave (PBI), which I do not think works with the standard 16MB DIMM that comes with the eval board. There were some discussion about setting the SDAM field of the PSDMR differently to fix this, but I havent gotten that to work. Fix is to use bigger than 16MB DIMM, or turn off PBI (top of board/mpc8266ads/mpc8266ads.c) This should probaby be changed...

2 1

[U-Boot-Users] Kernel hangs after decompressing.
by DavidHo＠nanometrics.ca 11 Sep '03

11 Sep '03

Hi, I am trying to bring up an uImage made from a Timesys 4.0 kernel on a EP860 board with u-boot 4.0 as the bootloader. I did a small port to make u-boot run on the EP860, mainly making changes to the SDRAM initialization and Flash configuration code. Once this is done. I went back to the Timesys kernel, which uses the RPXClassic configuration - the kernel runs fine in this configuration on the EP860. I copied the bd_info structure from u-boot.h to rpxclassic.h in the kernel and I had to add a bi_nvram_size field to the structure since the board requires it. I know the IMAP_ADDR is important so I'm absolutely sure this matches CFG_IMMR. When I try autobooting the kernel image from the tftp server, it hangs soon after the kernel is uncompressed. U-Boot 0.4.0 (Sep 11 2003 - 12:37:07) CPU: XPC860xxZPnnD4 at 50 MHz: 16 kB I-Cache 8 kB D-Cache FEC present Board: EP860 I2C: ready DRAM: 16 MB FLASH: 16 MB In: serial Out: serial Err: serial Net: FEC ETHERNET Hit any key to stop autoboot: 0 TFTP from server 199.71.138.8; our IP address is 199.71.138.25 Filename 'uImage'. Load address: 0x100000 Loading: ################################################################# ################################################################# ########################################### done Bytes transferred = 883654 (d7bc6 hex) ## Booting image at 00100000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 883590 Bytes = 862.9 kB Load Address: 00100000 Entry Point: 00100000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK B I had to move the load address up from 0x0 to pass the uncompressing stage. I'm not sure why loading to 0x0 causes problems since the examples in the readme all use 0x0 as the load address. I made the uImage from vmlinux in the top level directory and the vmlinux.gz from arch/ppc but they hanged at the same point. I can boot the zImage (kernel built with its own boot loader) by tftping the zImage to RAM and jumping to the start of the image. So the kernel works smoothly with its boot loader. I would really appreciate any suggestions you can give me to try on the board. I can give you any other information if there's anything I missed here. Thanks in advance, David Ho Nanometrics Inc.

2 1

[U-Boot-Users] Uncompressing kernel ..... OK (Hangs here)
by James Bates 11 Sep '03

11 Sep '03

Hi All, I have now managed to get the image to be read in and kernel image uncompressed etc. I am getting the problem where it hangs after Uncompression though. My previous issue with Bad Magic Number errors was due to the compilation of the mkimage tool. It was producing images with the wrong endianness in the header. Not sure if this may still be my problem tho :) I have tried both settings of clocks_in_mhz and have made sure that I copied u-boot.h from uboot to ppcboot.h in Linux. I have made sure that IMAP_ADDR is correct but I still get the same thing, just hangs after uncompression. I am totally stumped. My board is an adaptation of the MPC8260ADS. I am using BlueCat 4.0 and u-boot 4.8 (tried 4.0 and 4.7) etc and have tried booting both the uImage and kdi files (after turning them into u-boot images with mkimgage). Here is a print out with extra debug info when trying a kdi image called Q319.img: ---------------------------------------------------------------------------- -------------- => tftpboot 100000 Q319.img Trying FCC2 ETHERNET TFTP from server 192.168.1.1; our IP address is 192.168.1.2 Filename 'Q319.img'. Load address: 0x100000 Loading: ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################################################# done Bytes transferred = 3637824 (378240 hex) => bootm common/cmd_bootm.c before attempting to boot an image ## Booting image at 00100000 ... common/cmd_bootm.c Image header has correct magic number common/cmd_bootm.c Image header has correct checksum Image Name: Linux Kernel Image Image Type: PowerPC LynxOS Kernel Image (uncompressed) Data Size: 3637760 Bytes = 3.5 MB Load Address: 00500000 Entry Point: 00507000 Verifying Checksum ... OK common/cmd_bootm.c Image data has correct checksum common/cmd_bootm.c Architecture check OK common/cmd_bootm.c Image Type check OK OK common/cmd_bootm.c Uncompression OK common/cmd_bootm.c Image Type check OK Booting Bluecat KDI ... loaded at: 00507000 005121DC zimage at: 0050D000 0057366C initrd at: 00575000 00878200 relocated to: 00576000 00879200 avail ram: 0087A000 04000000 Linux/PPC load: root=/dev/ram root=/dev/ram rw ramdisk_size=28472 hda=bswap hdb=bswap hdc=bswap hdd=bswap root=101 Uncompressing Linux...done. Now booting the kernel (Hangs here) ---------------------------------------------------------------------------- ---------------- Another example which does not use a kdi image but simply takes a mkimaged zipped vmlinux file as follows. => tftpboot 100000 uImage Trying FCC2 ETHERNET TFTP from server 192.168.1.1; our IP address is 192.168.1.2 Filename 'uImage'. Load address: 0x100000 Loading: ################################################################# ################# done Bytes transferred = 419502 (666ae hex) => bootm common/cmd_bootm.c before attempting to boot an image ## Booting image at 00100000 ... common/cmd_bootm.c Image header has correct magic number common/cmd_bootm.c Image header has correct checksum Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 419438 Bytes = 409.6 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK common/cmd_bootm.c Image data has correct checksum common/cmd_bootm.c Architecture check OK common/cmd_bootm.c Image Type check OK Uncompressing Kernel Image ... OK common/cmd_bootm.c Uncompression OK common/cmd_bootm.c Image Type check OK ## Current stack ends at 0x03F6CBD8 => set upper limit to 0x00800000 ## cmdline at 0x007FFF00 ... 0x007FFF10 bd address = 0x03F6CFB4 memstart = 0x00000000 memsize = 0x04000000 flashstart = 0xFE000000 flashsize = 0x7FCFFFF7 flashoffset = 0x0002E000 sramstart = 0x00000000 sramsize = 0x00000000 immr_base = 0xFA200000 bootflags = 0x00000001 vco = 266.666 MHz sccfreq = 66.666 MHz brgfreq = 66.666 MHz intfreq = 199.999 MHz cpmfreq = 133.333 MHz busfreq = 66.666 MHz ethaddr = 00:00:00:10:18:82 IP addr = 192.168.1.2 baudrate = 115200 bps common/cmd_bootm.c No initial ramdisk, no multifile, continue. No initrd ## Transferring control to Linux (at address 00000000) ... common/cmd_bootm.c All preparation done, transferring control to OS (hangs here) Any ideas anyone? You help is much appreciated. Regards, James Bates PS: Apologies for this signature at the bottom of my posts, it is attached by my employer out of my control. This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error please return the message immediately to the sender and delete the message from your systems. Thank you.

6 7

[U-Boot-Users] Changes to NAND flash handling
by Wolfgang Denk 11 Sep '03

11 Sep '03

Hi, I don't really like the way how NAND flash is handled right now. Ii is inconsistent with the handling of other types of memory. I've changed the behaviour now so that it looks more like what we get for other types of memory (RAM, flash), i. e. for example it now prints: ... Board: PPChameleon EVB SN PPCN 310300 A8 I2C: ready DRAM: 32 MB FLASH: 4 MB NAND: 32 MB Hit any key to stop autoboot: 0 ... I tried to modify all affected boards, but I cannot test it. Will the board maintainers please have a look and complain (and/or send patches) if my changes broke anything? The new stuff is checked in now. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd(a)denx.de "If you own a machine, you are in turn owned by it, and spend your time serving it..." - Marion Zimmer Bradley, _The Forbidden Tower_

1 0

Re: [U-Boot-Users] MPC8266ADS patch
by Wolfgang Denk 11 Sep '03

11 Sep '03

Dear Allen, please keep the u-boot-users list Cc:ed. In message <FA06AA2C99BCD511951200005A99441003BE1706@IRVEXCH1> you wrote: > > I am sorry about the format. Between fighting the corporate IT guys and > Windoz I feel lucky that it works at all. It's not usable, though. We need context or unified diff's or any simple change elsewhere in the file (which causes the line numbers to shift) will break it. > > < $(OBJCOPY) -O binary $< $@ 2>/dev/null > > --- > > > $(OBJCOPY) -O ppcboot $< $@ 2>/dev/null > > Please explain why. Does the MontaVista version of the binutils doe > not understand "binary" output format any longer? > > The MontaVista tools will not convert binary to srec. You get an error > message about unknown architecture. However I discovered the ppcboot options > which works fine. Another solution is to use "dd" to strip the 64k header. Well, this is a bug in the MV toolchain then. Complain at MV. We will NOT add this to the Makefile as it breaks all other systems. > > Index: board/mpc8266ads/config.mk > > ================================================================== > > RCS file: /cvsroot/u-boot/u-boot/board/mpc8266ads/config.mk,v > > retrieving revision 1.2 > > diff -r1.2 config.mk > > 30c30 > > < TEXT_BASE = 0xfe000000 > > --- > > > TEXT_BASE = 0xfff00000 > > Please explain why you think this is necessary. > > The reset vector for 8260 is 0xfff00100. The easiest way to u-boot to put > code at this location is to change TEXT_BASE. This is the same as the > MPC8260 config.mk file.... There is no relation between the reset vector and TEXT_BASE. You can have the reset vector at 0x100 and TEXT_BASE - say - at 0x40000000. I don't think I want to change this configuration (which seems to be working to several people) without a really good reason. > > diff -r1.4 MPC8266ADS.h > > 236,237c236,237 > > < #define CFG_FLASH_BASE 0xFE000000 > > < #define FLASH_BASE 0xFE000000 > > --- > > > #define CFG_FLASH_BASE 0xFF800000 > > > #define FLASH_BASE 0xFF800000 > > 252,253c252,253 > > < #define CFG_BCSR 0xF8000000 > > < #define CFG_PCI_INT 0xF8200000 /* PCI interrupt > controller > > */ > > --- > > > #define CFG_BCSR 0x04500000 > > > #define CFG_PCI_INT 0x04730000 /* PCI interrupt > > controller */ > > Please explain why you think this is necessary. > > FLASH_BASE 0xff800000 - the board ships with a 8MB SIMM. This is the base > address. You can map the flash at any arbitrary address. I don't see why 0xFF800000 would be any better than 0xFE000000 - on contrary - mapping it at 0xFE000000 leaves enough room if there should ever be a board with bigger flash chips. > CFG_BCSR & CFG_PCI_INIT - according to the memory map in the MPC8266ADS > manual, these are the physical addresses. You need to access the BCSR to > enable the serial and Ethernet ports. Physical addresses on a 82xx are programmable. The programming of the memory controller decides where a device shows up in the physiacal memory map. Please ignore the memory map given in the manyal - it is just one example out of many possible, and it is an example which will NOT work with Linux. > Actually I think it is a bug to map the BCSR at a low address like > 0x04500000. Are you really, really sure that this will work with > Linux? > > Virtual address != Physical address > These are correct according to the documentation You are wrong. There are certain address ranges in Linux which are mapped with virtual"physical 1:1. The IMMR and BCSR areas are among them. > This works. The current u-boot implementation does not work. Perhaps the > current configuration works with a different board configuration. If that is > true, then there should be a big note somewhere with detailed configuration > notes. I doubt that you have any Linux applications running with your configuration. Rune, are you reading this? I don't have a MPC8266ADS board to actually test this, but you are the board maintainer. What is your comment? 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 It is a good thing for an uneducated man to read books of quotations. - Sir Winston Churchill _My Early Life_ ch. 9

1 0

RE: [U-Boot-Users] Uncompressing kernel ..... OK (Hangs here)
by Rune Torgersen 11 Sep '03

11 Sep '03

> changing CONFIG_BAUDRATE to 9600 but it has no effect, it > just stays at 115200. Any ideas? Note that that CONFIG parameter is ONLY used if there is no baudrate settin on the environment in flash. Change the environment variable, and it should work. (Same thing with CONFIG_CLOCK_IN_MHZ....)

1 0

RE: [U-Boot-Users] Kernel hangs after decompressing.
by Muhammad Sarwar 11 Sep '03

11 Sep '03

Make sure you don't have clock_in_mhz in your environment settings. Regards, Muhammad Sarwar Mangrove Systems Inc. -----Original Message----- From: DavidHo(a)nanometrics.ca [mailto:DavidHo@nanometrics.ca] Sent: Thursday, September 11, 2003 2:10 PM To: u-boot-users(a)lists.sourceforge.net Subject: [U-Boot-Users] Kernel hangs after decompressing. Hi, I am trying to bring up an uImage made from a Timesys 4.0 kernel on a EP860 board with u-boot 4.0 as the bootloader. I did a small port to make u-boot run on the EP860, mainly making changes to the SDRAM initialization and Flash configuration code. Once this is done. I went back to the Timesys kernel, which uses the RPXClassic configuration - the kernel runs fine in this configuration on the EP860. I copied the bd_info structure from u-boot.h to rpxclassic.h in the kernel and I had to add a bi_nvram_size field to the structure since the board requires it. I know the IMAP_ADDR is important so I'm absolutely sure this matches CFG_IMMR. When I try autobooting the kernel image from the tftp server, it hangs soon after the kernel is uncompressed. U-Boot 0.4.0 (Sep 11 2003 - 12:37:07) CPU: XPC860xxZPnnD4 at 50 MHz: 16 kB I-Cache 8 kB D-Cache FEC present Board: EP860 I2C: ready DRAM: 16 MB FLASH: 16 MB In: serial Out: serial Err: serial Net: FEC ETHERNET Hit any key to stop autoboot: 0 TFTP from server 199.71.138.8; our IP address is 199.71.138.25 Filename 'uImage'. Load address: 0x100000 Loading: ################################################################# ################################################################# ########################################### done Bytes transferred = 883654 (d7bc6 hex) ## Booting image at 00100000 ... Image Name: Linux Kernel Image Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 883590 Bytes = 862.9 kB Load Address: 00100000 Entry Point: 00100000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK B I had to move the load address up from 0x0 to pass the uncompressing stage. I'm not sure why loading to 0x0 causes problems since the examples in the readme all use 0x0 as the load address. I made the uImage from vmlinux in the top level directory and the vmlinux.gz from arch/ppc but they hanged at the same point. I can boot the zImage (kernel built with its own boot loader) by tftping the zImage to RAM and jumping to the start of the image. So the kernel works smoothly with its boot loader. I would really appreciate any suggestions you can give me to try on the board. I can give you any other information if there's anything I missed here. Thanks in advance, David Ho Nanometrics Inc. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

1 0

[U-Boot-Users] Debugging U-Boot with BDI2000
by Glenson Muthedan 11 Sep '03

11 Sep '03

Hello! I'm quite new to U-Boot and trying to get started with the Bootloader-Stuff for some weeks now. My Board is similar to Accelent IDP or CSB226(PXA250 with 32 MB Strataflash and 32 MB SDRAM). U-Boot seems to crash on my board before it can output something through the serial line. So I wanted step through U-Boot right from the very first instruction using BDI2000 while booting. The problem is that the information the bdi user manual gives, is quite confusing. I tried out various configurations for BDI2000, but really don't know what to do with the vector table in the "Mini IC" and the debug handler stuff. The situation now is as following: The target is in debug mode right from the start and the PC is pointing to 0xffff0004. "go" or "ti" doesn't work because of access to an invalid memory address. (My configuration file now contains a blank [INIT] section and no vector table/debug handler stuff in the [TARGET] part) I'd be very thankful if someone could answer my questions: 1) Is it possible to debug U-Boot with BDI2000 (Linux host) at all? (eg. step through the instructions) 2) Do somebody have a working configuration file for BDI2000 (Linux host) to be used with a PXA250-target? Hope, you can give me at least a hint. Regards, Glenson Muthedan.

3 2

[U-Boot-Users] PATCH: USB & FAT fixes
by Denis Peter 11 Sep '03

11 Sep '03

Hello, sorry thath the patch 'usb-bulk-transfer.diff' did not apply. It seems that the sourceforge CVS is not up to date. The usb-bulk-tansfer is already implemented in the current tarball. Here two additionally small patches for USB and FAT: usb_stor_fix.diff: Fixes usb data pointer assignment for bulk only transfer. fat-ls-fix.diff: Prevents to display erased directories. With best regards, Denis

2 1

[U-Boot-Users] MPC8266ADS patch
by Curtis, Allen 11 Sep '03

11 Sep '03

Here is a patch to get a 8266 booting with the default board configuration. Notes: 1. The patch to examples/Makefile should be included as a comment. People with MontaVista 2.0 (possibly other versions too) need this change. 2. This assumes that you have the small flash module. (should work fine with larger modules) 3. I followed some of the messages regarding booting the 8266. None of them appeared to address the address differences for the BCSR and PCI interrupt controller. (include/configs/MPC8266ADS.h) Index: board/mpc8266ads/config.mk ================================================================== RCS file: /cvsroot/u-boot/u-boot/board/mpc8266ads/config.mk,v retrieving revision 1.2 diff -r1.2 config.mk 30c30 < TEXT_BASE = 0xfe000000 --- > TEXT_BASE = 0xfff00000 Index: examples/Makefile ================================================================== RCS file: /cvsroot/u-boot/u-boot/examples/Makefile,v retrieving revision 1.7 diff -r1.7 Makefile 81c81 < $(OBJCOPY) -O binary $< $@ 2>/dev/null --- > $(OBJCOPY) -O ppcboot $< $@ 2>/dev/null Index: include/configs/MPC8266ADS.h ================================================================== RCS file: /cvsroot/u-boot/u-boot/include/configs/MPC8266ADS.h,v retrieving revision 1.4 diff -r1.4 MPC8266ADS.h 236,237c236,237 < #define CFG_FLASH_BASE 0xFE000000 < #define FLASH_BASE 0xFE000000 --- > #define CFG_FLASH_BASE 0xFF800000 > #define FLASH_BASE 0xFF800000 252,253c252,253 < #define CFG_BCSR 0xF8000000 < #define CFG_PCI_INT 0xF8200000 /* PCI interrupt controller */ --- > #define CFG_BCSR 0x04500000 > #define CFG_PCI_INT 0x04730000 /* PCI interrupt controller */

2 1

[U-Boot-Users] Re: PATCH: FAT support for IDE and SCSI
by Wolfgang Denk 10 Sep '03

10 Sep '03

Dear Denis, in message <200309090847.h898llqu005516(a)pip5.mpl.ch> you wrote: > > attached are several patches against the CVS from 03.09.03 (I wasn't able to > check-out the current CVS): > > - pip405-mip405-update.diff: > Some fixes for the boards PIP405 and MIP405 Added. > - DOC-fixes.diff: > Minor fix for Disk On Chip (UnitSizeFactor=0) Added. > - usb-bulk-transfer.diff: > Added bulk-only transfer for USB *** NOT ADDED *** This patch does not apply to current version in CVS. Please review, and re-submit. Sorry. > - fat-support.diff: > Added FAT support for IDE, SCSI and USB interface > This patch changes the behaviour of the fatxx commands, > which are only used for the board lubbock so far. I sent it > to the maintainer of this board and got his Ok. Added. > - fat-fast.diff: > increasing the speed of the FAT access by allowing > to transfer more than one block per read command. > This patch must be applied AFTER the fat-support.diff. Added. 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 Bumper sticker: Auntie Em: Hate you, hate Kansas, taking dog. Dorothy

1 0

[U-Boot-Users] [PATCH] POST doesn't compile on MPC824X
by gleb＠nbase.co.il 10 Sep '03

10 Sep '03

Hello, POST compilation fails in post/ether.c and post/uart.c on MPC824X even though I didn't configure CFG_POST_ETHER and CFG_POST_UART Attached patch moves checking of these options before error occurs. -- Gleb.

2 1