May 2003 - U-Boot

[U-Boot-Users] SIS55x based boards
by Frank 21 May '03

21 May '03

Has anybody ported u-boot to the SIS55x (x86) based boards... __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com

1 0

Re: [U-Boot-Users] file transfer server
by Wolfgang Denk 20 May '03

20 May '03

In message <2692A548B75777458914AC89297DD7DA021CCFDB(a)bronze.dolby.net> you wrote: > > Actually I want to run a server on the board, so that anyone on the > network can transfer files to it. So how easy would it be to implement > something like this. It is not exactly difficult, but it makes no sense either. U-Boot is a boot loader, not a file server. If you need server functions, run an OS. Boot into Linux, fire up inetd and a FTP or TFTP server. Voila. No need to implement any new features. 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 ultimate barrier is one's viewpoint. - Terry Pratchett, _The Dark Side of the Sun_

1 0

[U-Boot-Users] file transfer server
by Dhanuka, Anupam 20 May '03

20 May '03

Hi all I am using uboot for the ebony board. I want to be able to transfer a new firmware image to the board over the network. I would like to be able to connect to some sort of a server running on the board (by interrupting the boot sequence) through a client running on a remote system and interactively provide the server with a firmware image which can then be written by the server onto flash. Can someone tell me how this can be done? Thanks Anupam This message (including any attachments) may contain confidential information intended for a specific individual and purpose. If you are not the intended recipient, delete this message. If you are not the intended recipient, disclosing, copying, distributing, or taking any action based on this message is strictly prohibited.

2 1

RE: [U-Boot-Users] [patch] MPC8266 March-C memory test
by Rune Torgersen 20 May '03

20 May '03

The slow version is written in C and should work on any platfrom. The fast version might work. Don't know if the 8xx is FPU compatible with the 82xx -----Original Message----- From: Nye Liu [mailto:nyet@mrv.com] Sent: Monday, May 19, 2003 5:09 PM To: Rune Torgersen Cc: U-BOOT (E-mail) Subject: Re: [U-Boot-Users] [patch] MPC8266 March-C memory test Should this also be portable to the 8xx[F]ADS platforms? I am currently debugging UPM/memory problems, and a real memory test would be invaluable :) On Mon, May 19, 2003 at 04:26:47PM -0500, Rune Torgersen wrote: > Patch to do full March-C- memory test on the MPC8266ADS board. > > Later on I will probably include it as a command, right now it runs as > test_dram() which is called first thing after SDRAM is initializes, and > before anything uses the SDRAM. > > Note: Fast version uses floating point assembly and is therefore PPC > specific. Generic version takes more than twice the amount of time to > complete. > (Fast version: ~50 sec on 256MB RAM, slow version ~1:50 on 256MB RAM) > ADS > Rune Torgersen > Software Developer > Innovative Systems > 1000 Innovative Drive > Mitchell, SD 57301 > Phone: 605-995-6120 > Fax: 605-995-0084 > email: runet(a)innovsys.com > www.innovsys.com > > > > > -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

1 0

[U-Boot-Users] [PATCH] ARTOS boot support for u-boot
by Pantelis Antoniou 20 May '03

20 May '03

Wolfgang hi The following patch against u-boot-0.3.0 adds support for booting ARTOS images using u-boot. ARTOS is a custom in-house operating system in use by my company. We're in the process of moving some features of our in house boot-loader over to u-boot. I present the features to the mailing list in case someone else is working in anything similar, and would like to coordinate our efforts. o VLAN support and TOS configuration and support. o Two level access password support. o Different boot-modes. o Cisco router like command interface with history and command completion. o UDP-based same-LAN terminal access. o Factory testing framework. o More DHCP parameters support. o CDP support. o DHCP lease time information passed to the loaded kernel. Looking forward to hear your suggestions. Regards Pantelis diff -ruNb u-boot-0.3.0-orig/CREDITS u-boot-0.3.0/CREDITS --- u-boot-0.3.0-orig/CREDITS Wed Apr 16 10:56:20 2003 +++ u-boot-0.3.0/CREDITS Thu Apr 17 14:32:28 2003 @@ -286,3 +286,7 @@ E: azu(a)sysgo.de D: Overall improvements on StrongARM, ARM720TDMI; Support for Tuxscreen; initial PCMCIA support for ARM W: www.elinos.com + +N: Pantelis Antoniou +E: panto(a)intracom.gr +D: NETVIA board support, ARTOS support. diff -ruNb u-boot-0.3.0-orig/README u-boot-0.3.0/README --- u-boot-0.3.0-orig/README Wed Apr 16 10:56:20 2003 +++ u-boot-0.3.0/README Thu Apr 17 14:31:16 2003 @@ -343,7 +343,8 @@ CONFIG_GTH, CONFIG_RPXClassic, CONFIG_rsdproto, CONFIG_IAD210, CONFIG_RPXlite, CONFIG_sbc8260, CONFIG_EBONY, CONFIG_sacsng, CONFIG_FPS860L, - CONFIG_V37, CONFIG_ELPT860, CONFIG_CMI + CONFIG_V37, CONFIG_ELPT860, CONFIG_CMI, + CONFIG_NETVIA ARM based boards: ----------------- @@ -1726,7 +1727,7 @@ FPS850L_config Sandpoint8240_config sbc8260_config GENIETV_config TQM823L_config PIP405_config GEN860T_config EBONY_config FPS860L_config - ELPT860_config cmi_mpc5xx_config + ELPT860_config cmi_mpc5xx_config NETVIA_config Note: for some board special configuration names may exist; check if additional information is available from the board vendor; for @@ -2036,8 +2037,8 @@ * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD, 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, - LynxOS, pSOS, QNX; - Currently supported: Linux, NetBSD, VxWorks, QNX). + LynxOS, pSOS, QNX, ARTOS; + Currently supported: Linux, NetBSD, VxWorks, QNX, ARTOS). * Target CPU Architecture (Provisions for Alpha, ARM, Intel x86, IA64, MIPS, MIPS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; Currently supported: PowerPC). diff -ruNb u-boot-0.3.0-orig/common/cmd_bootm.c u-boot-0.3.0/common/cmd_bootm.c --- u-boot-0.3.0-orig/common/cmd_bootm.c Wed Apr 16 10:56:20 2003 +++ u-boot-0.3.0/common/cmd_bootm.c Wed Apr 16 13:24:15 2003 @@ -31,6 +31,7 @@ #include <image.h> #include <malloc.h> #include <zlib.h> +#include <environment.h> #include <asm/byteorder.h> #if (CONFIG_COMMANDS & CFG_CMD_DATE) || defined(CONFIG_TIMESTAMP) #include <rtc.h> @@ -104,6 +105,9 @@ int do_bootvx ( cmd_tbl_t *cmdtp, int flag, int argc, char *argv[] ); int do_bootelf (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[] ); #endif /* CFG_CMD_ELF */ +#ifdef CONFIG_PPC +static boot_os_Fcn do_bootm_artos; +#endif image_header_t header; @@ -326,6 +330,12 @@ addr, len_ptr, verify); break; #endif /* CFG_CMD_ELF */ +#ifdef CONFIG_PPC + case IH_OS_ARTOS: + do_bootm_artos (cmdtp, flag, argc, argv, + addr, len_ptr, verify); + break; +#endif } SHOW_BOOT_PROGRESS (-9); @@ -705,6 +715,88 @@ (*loader) (gd->bd, img_addr, consdev, cmdline); } +#ifdef CONFIG_PPC + +/* Function that returns a character from the environment */ +extern uchar (*env_get_char)(int); + +static void +do_bootm_artos (cmd_tbl_t *cmdtp, int flag, + int argc, char *argv[], + ulong addr, + ulong *len_ptr, + int verify) +{ + DECLARE_GLOBAL_DATA_PTR; + ulong top; + char *s, *cmdline; + char **fwenv, **ss; + int i, j, nxt, len, envno, envsz; + bd_t *kbd; + void (*entry)(bd_t *bd, char *cmdline, char **fwenv, ulong top); + image_header_t *hdr = &header; + + /* + * Booting an ARTOS kernel image + application + */ + + /* place data at the top of memory */ + top = gd->bd->bi_memstart + gd->bd->bi_memsize; + + /* first check the artos specific boot args, then the linux args*/ + if ((s = getenv("abootargs")) == NULL && (s = getenv("bootargs")) == NULL) + s = ""; + + /* get length of cmdline, and place it */ + len = strlen(s); + top = (top - (len + 1)) & ~0xF; + cmdline = (char *)top; + debug ("## cmdline at 0x%08lX ", top); + strcpy(cmdline, s); + + /* copy bdinfo */ + top = (top - sizeof(bd_t)) & ~0xF; + debug ("## bd at 0x%08lX ", top); + kbd = (bd_t *)top; + memcpy(kbd, gd->bd, sizeof(bd_t)); + + /* first find number of env entries, and their size */ + envno = 0; + envsz = 0; + for (i = 0; env_get_char(i) != '\0'; i = nxt + 1) { + for (nxt = i; env_get_char(nxt) != '\0'; ++nxt) + ; + envno++; + envsz += (nxt - i) + 1; /* plus trailing zero */ + } + envno++; /* plus the terminating zero */ + debug ("## %u envvars total size %u ", envno, envsz); + + top = (top - sizeof(char **)*envno) & ~0xF; + fwenv = (char **)top; + debug ("## fwenv at 0x%08lX ", top); + + top = (top - envsz) & ~0xF; + s = (char *)top; + ss = fwenv; + + /* now copy them */ + for (i = 0; env_get_char(i) != '\0'; i = nxt + 1) { + for (nxt = i; env_get_char(nxt) != '\0'; ++nxt) + ; + *ss++ = s; + for (j = i; j < nxt; ++j) + *s++ = env_get_char(j); + *s++ = '\0'; + } + *ss++ = NULL; /* terminate */ + + entry = (void (*)(bd_t *, char *, char **, ulong))ntohl(hdr->ih_ep); + (*entry)(kbd, cmdline, fwenv, top); +} +#endif + + #if (CONFIG_COMMANDS & CFG_CMD_BOOTD) int do_bootd (cmd_tbl_t *cmdtp, int flag, int argc, char *argv[]) { @@ -826,6 +918,7 @@ case IH_OS_VXWORKS: os = "VxWorks"; break; case IH_OS_QNX: os = "QNX"; break; case IH_OS_U_BOOT: os = "U-Boot"; break; + case IH_OS_ARTOS: os = "ARTOS"; break; default: os = "Unknown OS"; break; } diff -ruNb u-boot-0.3.0-orig/include/image.h u-boot-0.3.0/include/image.h --- u-boot-0.3.0-orig/include/image.h Wed Apr 16 10:56:20 2003 +++ u-boot-0.3.0/include/image.h Wed Apr 16 10:56:51 2003 @@ -45,6 +45,7 @@ #define IH_OS_PSOS 15 /* pSOS */ #define IH_OS_QNX 16 /* QNX */ #define IH_OS_U_BOOT 17 /* Firmware */ +#define IH_OS_ARTOS 18 /* ARTOS */ /* * CPU Architecture Codes (supported by Linux) diff -ruNb u-boot-0.3.0-orig/tools/mkimage.c u-boot-0.3.0/tools/mkimage.c --- u-boot-0.3.0-orig/tools/mkimage.c Wed Apr 16 10:56:20 2003 +++ u-boot-0.3.0/tools/mkimage.c Wed Apr 16 10:56:51 2003 @@ -92,6 +92,7 @@ { IH_OS_PSOS, "psos", "pSOS", }, { IH_OS_QNX, "qnx", "QNX", }, { IH_OS_U_BOOT, "u-boot", "U-Boot", }, + { IH_OS_ARTOS, "artos", "ARTOS", }, { -1, "", "", }, };

2 10

[U-Boot-Users] [PATCH] Support for new I2C RTC
by Steven Scholz 20 May '03

20 May '03

Hi there, the attached patch adds support for a I2C RTC DS1338 for Dallas/Maxim. DS1307 and DS1338 are basicly the same, they only differ in their supply voltage. * Patches by Steven Scholz, 11 Apr 2003 - Add support for RTC DS1338 Cheers, Steven Index: README =================================================================== RCS file: /home/cvsroot/u-boot/README,v retrieving revision 1.1.1.1 diff -p -u -r1.1.1.1 README --- README 5 Apr 2003 00:13:43 -0000 1.1.1.1 +++ README 11 Apr 2003 10:42:22 -0000 @@ -638,6 +638,7 @@ The following options need to be configu CONFIG_RTC_MC146818 - use MC146818 RTC CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC + CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC CONFIG_RTC_DS164x - use Dallas DS164x RTC - Timestamp Support: Index: rtc/ds1307.c =================================================================== RCS file: /home/cvsroot/u-boot/rtc/ds1307.c,v retrieving revision 1.1.1.1 diff -p -u -r1.1.1.1 ds1307.c --- rtc/ds1307.c 6 Mar 2003 21:26:28 -0000 1.1.1.1 +++ rtc/ds1307.c 10 Apr 2003 11:27:09 -0000 @@ -25,7 +25,7 @@ /* * Date & Time support (no alarms) for Dallas Semiconductor (now Maxim) - * DS1307 Real Time Clock (RTC). + * DS1307 and DS1338 Real Time Clock (RTC). * * based on ds1337.c */ @@ -35,7 +35,8 @@ #include <rtc.h> #include <i2c.h> -#if defined(CONFIG_RTC_DS1307) && (CONFIG_COMMANDS & CFG_CMD_DATE) +#if (defined(CONFIG_RTC_DS1307) || defined(CONFIG_RTC_DS1338) ) && \ + (CONFIG_COMMANDS & CFG_CMD_DATE) /*---------------------------------------------------------------------*/ #undef DEBUG_RTC @@ -200,4 +201,4 @@ static unsigned char bin2bcd (unsigned i return (((n / 10) << 4) | (n % 10)); } -#endif /* CONFIG_RTC_DS1307 && (CFG_COMMANDS & CFG_CMD_DATE) */ +#endif /* (CONFIG_RTC_DS1307 || CONFIG_RTC_DS1338) && (CFG_COMMANDS & CFG_CMD_DATE) */

2 1

[U-Boot-Users] Loading from a CF card on the PCMCIA interface A P atch
by Rod Boyce 20 May '03

20 May '03

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

2 1

[U-Boot-Users] Patch to allow CFG_NO_FLASH & CFG_LOADS.
by Christophe.LINDHEIMER＠fr.thalesgroup.com 20 May '03

20 May '03

Hi. A little patch to allow the use of CFG_NO_FLASH & CFG_LOADS. Chris. --- u-boot-0.3.0/common/cmd_boot.c 2003-04-07 10:39:32.000000000 +0200 +++ u-boot-0.3.1/common/cmd_boot.c 2003-05-20 10:27:48.000000000 +0200 @@ -332,6 +332,7 @@ load_serial (ulong offset) case SREC_DATA3: case SREC_DATA4: store_addr = addr + offset; +#ifndef CFG_NO_FLASH if (addr2info(store_addr)) { int rc; @@ -340,9 +341,14 @@ load_serial (ulong offset) flash_perror (rc); return (~0); } - } else { + } else + + { +#endif memcpy ((char *)(store_addr), binbuf, binlen); - } +#ifndef CFG_NO_FLASH + } +#endif if ((store_addr) < start_addr) start_addr = store_addr; if ((store_addr + binlen - 1) > end_addr)

2 1

[U-Boot-Users] QNX
by Rune Torgersen 20 May '03

20 May '03

Hi Does anybody know how to get a QNX image to boot using u-boot (QNX 6.2.1) Rune Torgersen Software Developer Innovative Systems 1000 Innovative Drive Mitchell, SD 57301 Phone: 605-995-6120 Fax: 605-995-0084 email: runet(a)innovsys.com www.innovsys.com

3 4

RE: [U-Boot-Users] Please explain this code in drivers/pci.c
by Rune Torgersen 20 May '03

20 May '03

>Subject: [U-Boot-Users] Please explain this code in drivers/pci.c >The value of bar_response is 0xffff8008 which looks good. This gives bar size of >0x8000 which also looks good. The value of mem is initially 0x90000000. So, >(mem - 1) = 0x8fffffff and (bar_size - 1) = 0x7fff). When these are or'd one gets >0x8fffffff and adding 1 gives 0x90000000. This result is that the card is given 4 >address bases all at 0x90000000. If the card wants 4 different memory regiuons, I assume it has 4 BAR registers? Each BAR must have the correct base address, so you have to add the size of the last region to the memory pointer before writing the address to the next BAR

2 1

[U-Boot-Users] [PATCH] MPC8266ADS PCI support
by Rune Torgersen 19 May '03

19 May '03

Rune Torgersen Software Developer Innovative Systems 1000 Innovative Drive Mitchell, SD 57301 Phone: 605-995-6120 Fax: 605-995-0084 email: runet(a)innovsys.com www.innovsys.com

1 0

[U-Boot-Users] Please explain this code in drivers/pci.c
by Donald White 19 May '03

19 May '03

Group, Please help me to understand the following code. It occurs in drivers/pci.c in the function pci_hose_config_device(). I have ported U-Boot 0.3.0 and HHL 2.0 to our custom MPC8265A board. It has one device on the PCI bus. The driver develop was wanting a specific memory space allocation for the device. So I created a PCI configuration table with the memory base of 0x90000000. The card wants 4 regions 0f 0x8000 bytes in size. The driver writer thinks this should be 0x90000000, 0x90008000, 0x90010000 and 0x90018000. This brings us to the code snippet: bar_size = ~(bar_response & PCI_BASE_ADDRESS_MEM_MASK) + 1; bar_value = mem; mem = ((mem - 1) | (bar_size - 1)) + 1; The value of bar_response is 0xffff8008 which looks good. This gives bar size of 0x8000 which also looks good. The value of mem is initially 0x90000000. So, (mem - 1) = 0x8fffffff and (bar_size - 1) = 0x7fff). When these are or'd one gets 0x8fffffff and adding 1 gives 0x90000000. This result is that the card is given 4 address bases all at 0x90000000. Thanks for any help, Don

1 0

RE: [U-Boot-Users] U-boot for 8245 boards
by Karoliya, Abhishek 18 May '03

18 May '03

Thanks Chris for the message but that isnt the case really. On startup ,typing INFO does give "COP freeze (startup)" but on typing ti gives "trace" and typing go gives "TARGET : entered Debug state " and than typing info Debug entry cause gives <reserved 0>. thanks Abhishek -----Original Message----- From: Chris Hallinan [mailto:clh@net1plus.com] Sent: Saturday, 17 May 2003 12:58 AM To: Karoliya, Abhishek; u-boot-users(a)lists.sourceforge.net Cc: u-boot-users(a)lists.sourceforge.net Subject: RE: [U-Boot-Users] U-boot for 8245 boards Abhishek Karoliya wrote: > I am trying to port U-boot to a customised 8245 board . > For the Initial bring up , I am using a working U-Boot > for another very > similar board. The problem is that, using > BDI 2000 debugger , The telnet Interface reports it to be > at reset address > fff0 0100 all the time and no amount of ti or go works > When I use gdb it also reports it to be stuck there and a > step command > results in gdb reporting that a stop signal received . > I tried setting break points ahead but no use. > > The BDI set-up is working as i tried it with working > image of vxWorks loader > bootrom. This does not necessarily indicate your setup is correct, which it likely isn't. When you do an 'info' command from Telnet, after typing 'ti' or 'go', do you see "Debug entry cause " COP freeze (startup)? This generally indicates that the 8245 has entered check stop state due to a hardware/configuration/setup/procesor initialization issue. You will have to debug it. Regards, Chris Hallinan DS4.COM, Inc

2 1

[U-Boot-Users] MPC86xADS support
by Nye Liu 17 May '03

17 May '03

I just recieved the MPC86xADS eval board... anybody here have experience with it? -- Nye Liu nliu(a)mrv.com (818) 772-6235x248 "Who would be stupid enough to quote a fictitious character?" -- Don Quixote

1 1

[U-Boot-Users] About define CFG_CMD_LOADS and CFG_NO_FLASH.
by Christophe.LINDHEIMER＠fr.thalesgroup.com 17 May '03

17 May '03

Hi. Why can't I use CFG_CMD_LOADS & CFG_NO_FLASH. It doesn't compile because load_serial function ( in cmd_boot.c ) needs some function for flash access ( not sure to understand why ... ) Need to add #ifndef CFG_NO_FLASH in load_serial ?? Thanks Chris

2 1

[U-Boot-Users] U-boot for 8245 boards
by Karoliya, Abhishek 16 May '03

16 May '03

Hi, I am trying to port U-boot to a customised 8245 board . For the Initial bring up , I am using a working U-Boot for another very similar board. The problem is that, using BDI 2000 debugger , The telnet Interface reports it to be at reset address fff0 0100 all the time and no amount of ti or go works When I use gdb it also reports it to be stuck there and a step command results in gdb reporting that a stop signal received . I tried setting break points ahead but no use. The BDI set-up is working as i tried it with working image of vxWorks loader bootrom. Am I missing anything in u-boot compilation or anything to BDI to work or some problem with the code. Please illuminate... Thanks Abhishek

2 1

[U-Boot-Users] About ColdFire port
by Ales Makarov 16 May '03

16 May '03

Some time ago there was some ColdFire port (5272 only) of PPCBoot from Bernhard Kuhn. I haven't chance to try it, but I was very statisfied with PPCBoot on PPC405. Now we play with ColdFire 5407 and it would be nice to have the U-Boot here. How is it with ColdFire port of U-Boot? Thanks. Ales

1 0

[U-Boot-Users] linux image
by Nghiem, Tien 15 May '03

15 May '03

Hi everyone, I try to build a linux image for the MPC8260ADS: # cd <patch>/linux-2.4 # make MPC8260ADS_config I got the following error: # make MPC8260ADS_config make: *** No rule to make target `MPC8260ADS_config'. Stop. I got the same error if I did : # make ep8260_config make: *** No rule to make target `ep8260_config'. Stop. Could you tell me what I miss here? Thank you Tien Nghiem

2 1

[U-Boot-Users] The problem on porting to similar FADS860 board
by John 15 May '03

15 May '03

Hello list! I've checked the archives, but have not found anyone using the 860 with my problem. I have a MPC860 board ported from FADS860 board. ( TEXT_BASE is also 0x2800000, but IMMR is 0x2200000). I have vxworks run OK on it. But when I am porting U-Boot on it. I met booting problem on it. For Example as following: (ELDK1.0 + U-boot-0.3.0) -------------------------------------------------------- located in /cpu/mpc8xx/start.S .globl _start .extern testLed _start: lis r3, 0x220 /* my IMMR addr is 0x2200000 */ ori r3, r3, 0x0000 mtspr 638, r3 /*IMMR SPR is 638*/ bl testLed /* this is to light LEDs on board(PA0 - PA3)*/ ---------------------------------------------------------- located in /cpu/mpc8xx/cpu_init.c void testLed(void) { int i,k; for(k=0;k<5;k++) { * ( (volatile unsigned short *) (0x2200000 + 0x950) ) = 0xA000; /* light LED */ for (i=0; i<0xFFFF;i++) {;}; * ( (volatile unsigned short *) (0x2200000 + 0x950) ) = 0x0000; /* unlight LED */ for (i=0; i<0xFFFF;i++) {;}; }; }; When I build to *.bin and burn into bootrom flash, after power on, the LEDs of board are not lighting. But, I tested these codes under Vxworks Bootrom code (rominit.S), that's OK. maybe it is linking problem? I 'm confused. Could you like to help me or give me any comments ? Thanks in advance! John

2 5

[U-Boot-Users] 8260 64 bit access
by Rune Torgersen 15 May '03

15 May '03

Anybody know a efficient way of doing 64 bit loads, stores and compares? (on a 826x) I am doing a March-C based memory test, and need to get the number of instructions used in the loops down as much as possible. Rune Torgersen Software Developer Innovative Systems 1000 Innovative Drive Mitchell, SD 57301 Phone: 605-995-6120 Fax: 605-995-0084 email: runet(a)innovsys.com www.innovsys.com

2 1

Re: [U-Boot-Users] [mpc8250 pci]
by Wolfgang Denk 15 May '03

15 May '03

In message <002201bf8dc4$b8309000$240110ac@jsbae> you wrote: > This is a multi-part message in MIME format. > > ------=_NextPart_000_001F_01BF8E10.27DEFF90 > Content-Type: text/plain; > charset="Windows-1252" > Content-Transfer-Encoding: base64 > > SGFzIGFueW9uZSBkb25lIGFueSB3b3JrIHdpdGggVS1Cb290IG9yIGxpbnV4IGtlcm5lbCBvbiBt > cGM4MjUwIHByb2Nlc3Nvcj8NCkNhbiBhbnlib2R5IGV4cGxhaW4gbWUgODI1MCBwY2kgYnJpZGdl > IHNldHRpbmcgZm9yIGluaXRpYWwgLi4uLg0KaSB1c2UgTW9udGF2aXN0YSBMaW51eCBrZXJuZWwg ... Please do not post base64 encoded messages. Post plain text only. > ------=_NextPart_000_001F_01BF8E10.27DEFF90 > Content-Type: text/html; > charset="Windows-1252" > Content-Transfer-Encoding: base64 > > PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv > L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu ... Please no not post HTML. Please do not post base64 encoded messages. Post plain text only. Message unreadable, ignored. 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 Winners never talk about glorious victories. That's because they're the ones who see what the battlefield looks like afterwards. It's only the losers who have glorious victories. - Terry Pratchett, _Small Gods_

1 0

RE: [U-Boot-Users] [mpc8250 pci]
by Rune Torgersen 15 May '03

15 May '03

Should be very similar to the 8265 and 8266 (since they are using the 8250 init function) You could also try some of the existing board configs that use 8250. -----Original Message----- From: ??? [mailto:jsbae@imctech.co.kr] Sent: Tuesday, March 14, 2000 8:51 AM To: U-BOOT Subject: [U-Boot-Users] [mpc8250 pci] Has anyone done any work with U-Boot or linux kernel on mpc8250 processor? Can anybody explain me 8250 pci bridge setting for initial .... i use Montavista Linux kernel 2.4.17 ..but this kernel is referenced ep8260board... this kernel not consideration to pic bridge .. **************************************************************************** ******* ??? (? ? ?) (?)IMC?? ????? ??2? ??:042-822-3486 ??:042-822-3483 ????: 019-434-2975 Jang-Sik Bae R&D Development Team 2 IMC Tech Co.,Ltd. Korea Tel:+82-42-822-3486 FAX:+82-42-822-3483 Mobile:+82-19-434-2975 E-mail : jsbae(a)imctech.co.kr <mailto:jsbae@imctech.co.kr> MSN ID : Feb_Overset(a)hotmail.com <mailto:Feb_Overset@hotmail.com> **************************************************************************** *******

1 0

[U-Boot-Users] U-Boot on Alchemy AU1000
by Chris Hallinan 15 May '03

15 May '03

Has anyone done any work with U-Boot on the AU1000 processor? I would like to understand the level of effort required to port U-Boot to a board based on this processor. I am intimately familiar with PPCBoot/U-Boot on PowerPC platforms and numerous PPC implementations. However, I'm just starting the climb up the 'MIPS' learning curve. :) According to the AMD documentation, the AU1000 is based in the 'MIPS32' instruction set/architecture, which I presume is different from R3000/R4000 for which I see some level of support in the current U-Boot release. Grepping through a recent Linux source tree, I do see there is a specific CONFIG_CPU_* for MIPS32, and I've taken a brief look at where this is used. Specifically MMU and some CPU features appear to be handled differently from R3K/4K. I'd appreciate any input/feedback on what would be required to add support in U-Boot for this processor/architecture. Thanks in advance, Chris Hallinan DS4.COM, Inc.

1 0

[U-Boot-Users] SDRAM I2C Rom contents
by Roel Loeffen 15 May '03

15 May '03

Hello, I'm compiling U-Boot for the EVB64260, which reads the SDRAM settings from a I2C rom. We've build our own board an also the I2C Rom is installed. Where can I find what the I2C Rom contents layout should be for SDRAM information? Thx Roel

2 1

[U-Boot-Users] use and syntax of "=r"
by Paul,Kunal 15 May '03

15 May '03

hi all, i came across "=r" in the code of u-boot many times...can anybody explain me its use... i have been trying to copy a variable to SPR...will this help me.. thnx, kunal

1 0