January 2005 - U-Boot

[U-Boot-Users] FCC2 issue on PQ2FADS
by Kumar Gala 08 Jan '05

08 Jan '05

I've got a new PQ2FADS board and am having issues with FCC2. I'm using the 1.1.2 release, we seem to be able to transmit but not receive packets. Any ideas? - kumar

3 4

[U-Boot-Users] U-Boot-Users -- confirmation of subscription -- request 915980
by matthew.sheahan＠comcast.net 07 Jan '05

07 Jan '05

1 0

[U-Boot-Users] where i can download hynix hms30c7202 u-boot source?
by xiaoyin 07 Jan '05

07 Jan '05

your help will be appreciated

4 3

[U-Boot-Users] PATCH: Force TFTP to use a fixed UDP port
by Jerry Van Baren 07 Jan '05

07 Jan '05

Hi Wolfgang, Attached is a patch to allow the user to set an environment variable "tftpourport" to force TFTP to use that value for "TftpOurPort" (our UDP port). As discussed yesterday on this list, this is helpful for "punching through" a firewall such as is installed with Windows XP SP2. Making it an environment variable is cute but an overkill. If there is an outcry over the level of overkill, I would be willing to make the UDP port a simple #define of a compile time constant, in which case it would actually save a few bytes of ROM over the pseudo-random algorithm :-). Thanks, gvb CHANGELOG: * Patch by Jerry Van Baren 05 Jan 2005 - Make the u-boot TFTP source port be configurable using the environment variable "tftpourport": * If set, use that port as the u-boot source port * If not set, use the current method of using a pseudo random port - The additional code can be totally removed by setting the #define TFTP_PORT_FROM_ENV (in the net/tftp.c file) to zero. - The purpose behind this change is that our customer will modify their TFTP server so that it blindly starts the TFTP transfer using the pre-configured target IP address and UDP port. This will have the effect of "punching through" the (Windows XP) firewall, allowing the remainder of the TFTP transfer to proceed normally. Index: net/tftp.c =================================================================== RCS file: /cvsroot/u-boot/u-boot/net/tftp.c,v retrieving revision 1.9 diff -p -u -r1.9 tftp.c --- net/tftp.c 15 Apr 2004 21:48:55 -0000 1.9 +++ net/tftp.c 6 Jan 2005 03:20:41 -0000 @@ -24,6 +24,9 @@ /* (for checking the image size) */ #define HASHES_PER_LINE 65 /* Number of "loading" hashes per line */ +#define TFTP_PORT_FROM_ENV 1 /* define this to allow setting the */ + /* TFTP source port in the environment */ + /* variable "tftpourport" */ /* * TFTP operations. */ @@ -301,6 +304,8 @@ TftpTimeout (void) void TftpStart (void) { + char *ep; /* Environment pointer */ + if (BootFile[0] == '\0') { IPaddr_t OurIP = ntohl(NetOurIP); @@ -354,7 +359,13 @@ TftpStart (void) TftpServerPort = WELL_KNOWN_PORT; TftpTimeoutCount = 0; TftpState = STATE_RRQ; + /* Use a pseudo-random port unless a specific port is set */ TftpOurPort = 1024 + (get_timer(0) % 3072); +#if TFTP_PORT_FROM_ENV + if ((ep = getenv("tftpourport")) != NULL) { + TftpOurPort= simple_strtol(ep, NULL, 10); + } +#endif TftpBlock = 0; /* zero out server ether in case the server ip has changed */

3 3

[U-Boot-Users] mpc5200 relocation problem
by Giorgio Delmondo 07 Jan '05

07 Jan '05

Hi, I designed an MPC5200 with 256MB RAM (4 x 512Mb chips; MT48LC32M16A2, 8x16bitx4banks). When I force U-boot to just use the first 128 MB, everything is ok (I force the return value from the routine exploring the RAM size). If I try to use the full 256 MB it crashes in the relocation phase (not always at the same point). I'm quite sure the RAM is working, as a test RAM program, residing in the low RAM and testing the full memory from 0x08000000 to 0x0fffffff, always gives result ok (it's started from U-boot running in low memory). I'm using u-boot 1.1.1 Any suggestion? Many thanks

3 2

[U-Boot-Users] [Patch] au1xx0 ethernet dma init
by Leif Lindholm 07 Jan '05

07 Jan '05

Since I'm a very impatient guy, I'm submitting this patch on behalf of Andrew :) CHANGELOG: * Patch by Andrew Dyer, 29 Dec 2004 Fix ethernet dma init on au1xx0 systems to get rid of rx/tx timeouts. regards / Leif

1 0

[U-Boot-Users] Re: How to pause u-boot after serial init
by Nishant Galange 07 Jan '05

07 Jan '05

The exact situation: console_init_f() executes properly. Execution stops at printf() inside display_options(). hang() kept _after_ display_options() is never reached. Even if hang() is removed, the problem remains. Execution stops (as expected) at hang() if it is placed before display_options(). Hope that explained the problem. Regards, Nishant. Ps. SDRAM is not yet initialized at this point. Could that be the cause? Is it necessary to see any statements on the serial console? -----Original Message----- From: Wolfgang Denk <wd(a)denx.de> To: "Nishant Galange" <nishant.subs(a)myrealbox.com> Date: Thu, 06 Jan 2005 18:15:41 +0100 Subject: Re: [U-Boot-Users] How to pause u-boot after serial init In message <1105027245.41d677cnishant.subs(a)myrealbox.com> you wrote: > > I have a query regarding my custom board (8266 based PMC card, 512K boot fl > ash, Himem (top boot), 32 MB main flash, 128 MB SDRAM, u-boot 1.1.1). > > Will you please use a shorter linelength, say 70 characters or so as > suggested by the netiquette? Thanks. > > When trying to bring up the serial port, I want to stop execution after ser > ial initialization. So, I inserted an infinite loop ('hang') in init_sequ > ence[] in lib_ppc/board.c. I don't understand what this would be good for, but if you really want to do this... > The problem is that a 'hang' placed just after console_init_f works but I c > an't see any display on Hype Terrminal, because no prints have happened y > et. That's what you asked for... > And a 'hang' placed after 'display options' dosen't even load! The data lin > es (seen on a Logic Analyzer) show all 0s What do you mean by "does not load"? And which data lines are you talking about, and when do you sample these data lines? > Can anybody please shed some light on this problem? Any help / hints will b > e greatly appreciated. I have no idea what you're trying to do, but attaching a BDI2000 and running the code under GDB is probably the fastest way to find out what's going on on your system. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de An armed society is a polite society.

2 1

[U-Boot-Users] Kernel 2.4.19-rmk7 & Unlock Before Erase w/Strataflash K3
by Craig A. Vanderborgh 07 Jan '05

07 Jan '05

Hello, booters - and Happy New Year! I am looking for a bit of advice on a seemingly messy problem. Our PXA-255 board uses the K3-type Intel Strataflash chips, the kind you have to "unlock before you can erase". If I do a "protect off all" in u-boot BEFORE I boot my kernel, my target board boots the kernel correctly, and is able to mount its JFFS2 root filesystem. If I DON'T do "protect off all", the boot fails because Linux cannot write to the JFFS2 - because my kernel does not currently "unlock" before it tries to erase... I put an "unlock before erase" fix into my u-boot port - that's why it works correctly. The question is - What is the best way to deal with this in the Linux kernel? Is there some "correct" and/or straightforward way to accomplish this?? Thanks in advance, craig vanderborgh voxware incorporated

2 1

[U-Boot-Users] Re: How to pause u-boot after serial init?
by Nishant Galange 07 Jan '05

07 Jan '05

The exact situation: console_init_f() executes properly. Execution stops at printf() inside display_options(). hang() kept _after_ display_options() is never reached. Even if hang() is removed, the problem remains. Execution stops (as expected) at hang() if it is placed before display_options(). Hope that explained the problem. Regards, Nishant. Ps. SDRAM is not yet initialized at this point. Could that be the cause? Is it necessary to see any statements on the serial console? -----Original Message----- From: Wolfgang Denk <wd(a)denx.de> To: "Nishant Galange" <nishant.subs(a)myrealbox.com> Date: Thu, 06 Jan 2005 18:15:41 +0100 Subject: Re: [U-Boot-Users] How to pause u-boot after serial init In message <1105027245.41d677cnishant.subs(a)myrealbox.com> you wrote: > > I have a query regarding my custom board (8266 based PMC card, 512K boot fl > ash, Himem (top boot), 32 MB main flash, 128 MB SDRAM, u-boot 1.1.1). > > Will you please use a shorter linelength, say 70 characters or so as > suggested by the netiquette? Thanks. > > When trying to bring up the serial port, I want to stop execution after ser > ial initialization. So, I inserted an infinite loop ('hang') in init_sequ > ence[] in lib_ppc/board.c. I don't understand what this would be good for, but if you really want to do this... > The problem is that a 'hang' placed just after console_init_f works but I c > an't see any display on Hype Terrminal, because no prints have happened y > et. That's what you asked for... > And a 'hang' placed after 'display options' dosen't even load! The data lin > es (seen on a Logic Analyzer) show all 0s What do you mean by "does not load"? And which data lines are you talking about, and when do you sample these data lines? > Can anybody please shed some light on this problem? Any help / hints will b > e greatly appreciated. I have no idea what you're trying to do, but attaching a BDI2000 and running the code under GDB is probably the fastest way to find out what's going on on your system. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de An armed society is a polite society.

1 0

[U-Boot-Users] SystemACE error
by Jeff Angielski 07 Jan '05

07 Jan '05

The reading of the systemace compact flash is periodically setting the configuration read error (CFGREADERR) bit in the error register. Has anybody out there seen this behavior or have any ideas? For instance, just reading the error register when entering and exiting the systemace_read() in common/cmd_ace.c I see the following output when using the FAT commands: => fatinfo ace 0 fatinfo ace 0 systemace_read: >> error reg=0x0 systemace_read: << error reg=0x0 systemace_read: >> error reg=0x0 systemace_read: << error reg=0x0 systemace_read: >> error reg=0x0 systemace_read: << error reg=0x0 systemace_read: >> error reg=0x0 systemace_read: << error reg=0x80 <<<<<< ERROR!!!! Partition 1: Filesystem: FAT16 " The problem manifests itself when the Linux device driver comes up and tries to identify the device but finds the chip is already in an errror state. Thanks, Jeff Angielski

1 0