December 2004 - U-Boot

[U-Boot-Users] CLI over Ethernet
by Srivatsan 22 Dec '04

22 Dec '04

Hi all, Greetings. There is a requirement to provide CLI over Ethernet in uboot. 1) The CLI works over LAN (not using TCP/IP) using Logical link control Layer. (Is this possible?) 2) Anyone who has done a similar stuff has any advice for us? (Not in negative :-)) 3) Is there any documentation or RFC available which talks of (Ethernet) connectivity at LLC layer? Thanks and Best Regards, C.R.Srivatsan -----Original Message----- From: u-boot-users-admin(a)lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of u-boot-users-request(a)lists.sourceforge.net Sent: Wednesday, November 24, 2004 8:43 PM To: u-boot-users(a)lists.sourceforge.net Subject: U-Boot-Users digest, Vol 1 #1106 - 13 msgs Send U-Boot-Users mailing list submissions to u-boot-users(a)lists.sourceforge.net To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/u-boot-users or, via email, send a message with subject or body 'help' to u-boot-users-request(a)lists.sourceforge.net You can reach the person managing the list at u-boot-users-admin(a)lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of U-Boot-Users digest..." Today's Topics: 1. RE: CONFIG_BOOTBINFUNC for AT91RM9200 (Friedrich, Lars) 2. question on drive (zhonglei) 3. boot problem (Alessio Raccis) 4. Re: question on drive (Marc Leeman) 5. boot problem (Alessio Raccis) 6. R: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 (Paolo Broggini) 7. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Wolfgang Denk) 8. Re: boot problem (Wolfgang Denk) 9. Re: question on drive (Wolfgang Denk) 10. Re: question on drive (Marc Leeman) 11. RE: CONFIG_BOOTBINFUNC for AT91RM9200 (Paugam Luc) 12. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Steven Scholz) 13. Re: CONFIG_BOOTBINFUNC for AT91RM9200 (Wolfgang Denk) --__--__-- Message: 1 Subject: RE: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Date: Wed, 24 Nov 2004 08:46:45 +0100 From: "Friedrich, Lars" <lars.friedrich(a)wago.com> To: <u-boot-users(a)lists.sourceforge.net> > > Why is that so bad? It makes it possible to debug U-Boot > > with just loading the image into RAM using BDI2000. > Which is an unsupported mode of operation which works for a handfull > of experts and causes confusion with many, many newbees. How do these lines of code confuse a newbie more than any other code in the file? > > But how would you debug U-Boot? > As I always do. Attach the BDI, burn to flash, start in GDB. There are 53982 other hardware debuggers out there and only the minority (is there actually one besides the BDI?) support the burn to flash feature you rely on. So if you need to start U-Boot to flash U-Boot, you either do those few lines of code to skip the relocation or get/use another piece of actually redundant software to get the image on the flash. I don't know why the latter should save me time. > You can do this if you know exactly what you're doing, Isn't this what is assumed here anyway? Best regards, Lars Friedrich --=20 --__--__-- Message: 2 Date: Wed, 24 Nov 2004 15:25:07 +0800 From: "zhonglei" <zhonglei(a)RCS-9000.COM> Reply-To: <zhonglei(a)RCS-9000.COM> To: <u-boot-users(a)lists.sourceforge.net> Subject: [U-Boot-Users] question on drive hi Sorry for bothering you! But would you please give me a hand.When I insert a Intel Pro/100s server Adapter into the PCI slot on Lite5200(motorola MPC5200 development kit) and start the kernel,the kernel run into a dead lock. The reports are as follows: . . . IP-Config: Retrying forever (NFS root)... eth1: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. eth1: Waiting for the link to be up... eth1: status: link up, 100 Mbps Full Duplex, auto-negotiation complete. e100: eth0 NIC Link is Up 100 Mbps Full duplex Sending DHCP requests ...... timed out! Please tell me how can I handle it! Thanks in advance! Best Regards zhonglei --__--__-- Message: 3 From: "Alessio Raccis" <lolloz(a)tiscali.it> To: <u-boot-users(a)lists.sourceforge.net> Date: Wed, 24 Nov 2004 10:10:39 +0100 Subject: [U-Boot-Users] boot problem Hi all, I have a problem and now, it's weird to say, I pray to a kernel panic ! I'm working on smdk2410 and I have a u-boot version modified to boot from smartmedia. I want, or better I hope to boot 2.6.7 linux kernel. So, I create a zImage by compiling kernel and then I make: gzip -9 zImage ./mkimage -A arm -O linux -T kernel -C gzip -a 0x30008000 -e 0x30008000 -n "Linux Kernel Image" -d zImage.gz uimage At this point, I download uimage at 33000000 address from a tftp server. SMDK2410 # tftpboot 33000000 uimage TFTP from server 10.124.7.161; our IP address is 10.124.7.50 Filename 'uimage'. Load address: 0x33000000 Loading: ################################################################# ################################################################# ######################################################## done Bytes transferred = 950519 (e80f7 hex) Now I boot the kernel and I have: SMDK2410 # bootm ## Booting image at 33000000 ... Image Name: Linux Kernel Image Created: 2004-11-17 13:50:56 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 950455 Bytes = 928.2 kB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel ... Uncompressing Linux................................................................... done, booting the kernel. Nothing else !! Can anyone help me, please ? Which is my mistake ? thanks in advance. Best regards, Alex --__--__-- Message: 4 Date: Wed, 24 Nov 2004 10:14:33 +0100 From: Marc Leeman <marc.leeman(a)gmail.com> Reply-To: Marc Leeman <marc.leeman(a)gmail.com> To: zhonglei(a)rcs-9000.com Subject: Re: [U-Boot-Users] question on drive Cc: u-boot-users(a)lists.sourceforge.net I don't think this has to do with u-boot :) I think you should send this to the correct mailing list. > IP-Config: Retrying forever (NFS root)... > eth1: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. > eth1: Waiting for the link to be up... > eth1: status: link up, 100 Mbps Full Duplex, auto-negotiation complete. > e100: eth0 NIC Link is Up 100 Mbps Full duplex Maybe your board configuration of the kernel is not quite correct and/or some interrupt lines are wongly addressed. > Sending DHCP requests ...... timed out! > Please tell me how can I handle it! Thanks in advance! $ find . -name '*.c' | xargs grep Sending\ DHCP And start debugging/instrumenting from there. --=20 ash nazg durbatul=FBk, ash nazg gimbatul, ash nazg thrakatul=FBk agh burzum-ishi krimpatul --__--__-- Message: 5 From: "Alessio Raccis" <lolloz(a)tiscali.it> To: <u-boot-users(a)lists.sourceforge.net> Subject: [U-Boot-Users] boot problem Date: Wed, 24 Nov 2004 10:18:22 +0100 Hi all, I have a problem and now, it's weird to say, I pray to a kernel panic ! I'm working on smdk2410 and I have a u-boot version modified to boot from smartmedia. I want, or better I hope to boot 2.6.7 linux kernel. So, I create a zImage by compiling kernel and then I make: gzip -9 zImage ./mkimage -A arm -O linux -T kernel -C gzip -a 0x30008000 -e 0x30008000 -n "Linux Kernel Image" -d zImage.gz uimage At this point, I download uimage at 33000000 address from a tftp server. SMDK2410 # tftpboot 33000000 uimage TFTP from server 10.124.7.161; our IP address is 10.124.7.50 Filename 'uimage'. Load address: 0x33000000 Loading: ################################################################# ################################################################# ######################################################## done Bytes transferred = 950519 (e80f7 hex) Now I boot the kernel and I have: SMDK2410 # bootm ## Booting image at 33000000 ... Image Name: Linux Kernel Image Created: 2004-11-17 13:50:56 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 950455 Bytes = 928.2 kB Load Address: 30008000 Entry Point: 30008000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK Starting kernel ... Uncompressing Linux................................................................... done, booting the kernel. Nothing else !! Can anyone help me, please ? Which is my mistake ? thanks in advance. Best regards, Alex --__--__-- Message: 6 From: "Paolo Broggini" <pbroggini(a)softool.ch> To: "Friedrich, Lars" <lars.friedrich(a)wago.com>, <u-boot-users(a)lists.sourceforge.net> Subject: R: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Date: Wed, 24 Nov 2004 10:29:52 +0100 > -----Messaggio originale----- > Da: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net]Per conto di Friedrich, > Lars > Inviato: mercoledì, 24. novembre 2004 08:47 > A: u-boot-users(a)lists.sourceforge.net > Oggetto: RE: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 > > > > > Why is that so bad? It makes it possible to debug U-Boot > > > with just loading the image into RAM using BDI2000. > > Which is an unsupported mode of operation which works for a handfull > > of experts and causes confusion with many, many newbees. > > How do these lines of code confuse a newbie more than any other code > in the file? > > > > You can do this if you know exactly what you're doing, > > Isn't this what is assumed here anyway? > I fully agree with you !!! Regards -Paolo Broggini > Best regards, > Lars Friedrich > > -- > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users > --__--__-- Message: 7 To: "Friedrich, Lars" <lars.friedrich(a)wago.com> Cc: u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Date: Wed, 24 Nov 2004 11:26:56 +0100 Dear Lars, in message <AB4979EC12A5EB419810807434495A17283C1E(a)svex01001.wago.local> you wrote: > > > Which is an unsupported mode of operation which works for a handfull > > of experts and causes confusion with many, many newbees. > > How do these lines of code confuse a newbie more than any other code > in the file? It's not the lines of code, but the mode of operation. People tend to underestimate the complexity of the task and the impact of the required modifications. > > As I always do. Attach the BDI, burn to flash, start in GDB. > > There are 53982 other hardware debuggers out there and only the > minority (is there actually one besides the BDI?) support the > burn to flash feature you rely on. So if you need to start U-Boot C'me on. You must be joking. Please name a few commercial debuggers which do not support flash programming. Maybe we should add a list of such broken devices to our wiki so people can avoid them? Let me check: * Abatron BDI2000: ok (of course) * Windriver visionICE II: ok * Lauterbach Trace32: ok * Macraigor Wiggler / Raven / usbDemon: ok * Agilent 3070 Series etc: ok Even the free BDM4GDB project suports flash programming. Please be specific: which BDM/JTAG debugger cannot program flash? I really would like to know to be able to warn our customers. > > You can do this if you know exactly what you're doing, > > Isn't this what is assumed here anyway? Yes. People should think, machines should work ;-) There are areas, where small errors have small consequences which are easy to spot. AQnd there are really nasty problems. If you look back at the archives you will see that this is one of these nasty problem domains. And it's a FAQ. 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 The only thing necessary for the triumph of evil is for good men to do nothing. - Edmund Burke --__--__-- Message: 8 To: "Alessio Raccis" <lolloz(a)tiscali.it> Cc: u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] boot problem Date: Wed, 24 Nov 2004 11:32:35 +0100 In message <001e01c4d205$7e2ca120$cb077c0a@bart> you wrote: > > I have a problem and now, it's weird to say, I pray to a kernel panic ! Alternatively, try a post-mortem dump of the log_buf area, see http://www.denx.de/twiki/bin/view/DULG/LinuxPostMortemAnalysis Or even better: attach your BDI2000 and debug the Linux kernel code. 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 If God had a beard, he'd be a UNIX programmer. --__--__-- Message: 9 To: Marc Leeman <marc.leeman(a)gmail.com> Cc: zhonglei(a)rcs-9000.com, u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] question on drive Date: Wed, 24 Nov 2004 11:30:14 +0100 In message <1f729c4804112401141cd5deb7(a)mail.gmail.com> you wrote: > I don't think this has to do with u-boot :) I think you should send > this to the correct mailing list. thanks for pointing out. > > IP-Config: Retrying forever (NFS root)... > > eth1: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. > > eth1: Waiting for the link to be up... > > eth1: status: link up, 100 Mbps Full Duplex, auto-negotiation complete. > > e100: eth0 NIC Link is Up 100 Mbps Full duplex > > Maybe your board configuration of the kernel is not quite correct > and/or some interrupt lines are wongly addressed. No, you are wrong here. It seems the kernel is working perfectly fine. > > Sending DHCP requests ...... timed out! > > Please tell me how can I handle it! Thanks in advance! > > $ find . -name '*.c' | xargs grep Sending\ DHCP > And start debugging/instrumenting from there. Always try simple things first! Is there a DHCP server running to answer the DHCP requests from the target? Did you run a network sniffer and actually see the DHCP reply packets on the wire? 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 No one wants war. -- Kirk, "Errand of Mercy", stardate 3201.7 --__--__-- Message: 10 Date: Wed, 24 Nov 2004 11:47:25 +0100 From: Marc Leeman <marc.leeman(a)gmail.com> Reply-To: Marc Leeman <marc.leeman(a)gmail.com> To: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] question on drive > Always try simple things first! Is there a DHCP server running to > answer the DHCP requests from the target? Did you run a network > sniffer and actually see the DHCP reply packets on the wire? Hm, I assumed this was already checked since it the easiest to do :) I know, 'assuming' is bad... This would be (on the server) # tail -f /var/log/syslog to check the DCHP packages arriving at the server and the replies being sen= t. --=20 ash nazg durbatul=FBk, ash nazg gimbatul, ash nazg thrakatul=FBk agh burzum-ishi krimpatul --__--__-- Message: 11 Subject: RE: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Date: Wed, 24 Nov 2004 11:54:09 +0100 From: "Paugam Luc" <luc.paugam(a)thomson.net> To: "Wolfgang Denk" <wd(a)denx.de>, "Steven Scholz" <steven.scholz(a)imc-berlin.de> Cc: <u-boot-users(a)lists.sourceforge.net> Dear Steven & Wolfgang, There is perhaps a confusion between _relocation_ and _copy_. Beware to the fact that actually the AT91RM9200 starter code (especially = start.S) does not relocate any code from Flash to RAM (as we can see it into PowerPC starter code, for example) but rather do a simple copy of=20 u-boot code from Flash to RAM. _TEXT_BASE is still defined with a RAM address! This way to do is unfortunately inherited from ATMEL with their 2 stages = boot process. Regards - Luc > -----Original Message----- > From: u-boot-users-admin(a)lists.sourceforge.net > [mailto:u-boot-users-admin@lists.sourceforge.net]On Behalf Of Wolfgang > Denk > Sent: mardi 23 novembre 2004 17:43 > To: Steven Scholz > Cc: u-boot-users(a)lists.sourceforge.net > Subject: Re: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200=20 >=20 >=20 > In message <41A35A7E.1020605(a)imc-berlin.de> you wrote: > >=20 > > is there a standard way in U-Boot to prevent to the startup=20 > code from relocating=20 > > into RAM? >=20 > No. U-Boot will always relocate itself to RAM. Well, nearly always - > in any halfway sane implementation. >=20 > > I know that arm920t figures out the currebt address.=20 > compares it to _TEXT_BASE=20 > > and decides wether to relocate or not. > >=20 > > relocate: /* relocate U-Boot to=20 > RAM */ > > adr r0, _start /* r0 <- current=20 > position of code */ > > ldr r1, _TEXT_BASE /* test if we run from=20 > flash or RAM */ > > cmp r0, r1 /* don't reloc during=20 > debug */ >=20 > I wish that code was never written. >=20 > > So there might be no need for a define like=20 > CFG_DONT_RELOCATE. But how about=20 > > other cpus? >=20 > All CPUs always relocate the code to RAM. This is the general case. > Anything else is not supported. >=20 > > (I am asking cause you wrapped the relocate code in=20 > cpu/at91rm9200/start.S with=20 > > CONFIG_BOOTBINFUNC instead of using the above technique. >=20 > Please consider the CONFIG_BOOTBINFUNC as an optimization of effort > and effect (read: quick & dirty hack). Feel free to clean up as long > the result is working code, too. >=20 > Best regards, >=20 > Wolfgang Denk >=20 > --=20 > Software Engineering: Embedded and Realtime Systems, Embedded Linux > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(a)denx.de > Fools ignore complexity. Pragmatists suffer it. Some can avoid it. > Geniuses remove it. > - Perlis's Programming Proverb #58, SIGPLAN Notices, Sept. 1982 >=20 >=20 > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from=20 > real users. > Discover which products truly live up to the hype. Start reading now.=20 > http://productguide.itmanagersjournal.com/ > _______________________________________________ > U-Boot-Users mailing list > U-Boot-Users(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/u-boot-users >=20 --__--__-- Message: 12 Date: Wed, 24 Nov 2004 13:54:33 +0100 From: Steven Scholz <steven.scholz(a)imc-berlin.de> To: u-boot-users(a)lists.sourceforge.net Subject: Re: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Wolfgang Denk wrote: > In message <41A36CFE.9050900(a)imc-berlin.de> you wrote: > >>Hmm. So I suggest replacing it with CONFIG_INIT_LOWLEVEL or CONFIG_LOWLEVEL_INIT. > > > Hmmm.. CONFIG or CFG? And what exactly is low (vs. high?) level here? > > >>But then: these init steps (clocks and memory) are vital for U-Boot to run. So >>why do we need this define anyway if these steps should be done always... ? > > > Good question. The only reason I can think of is to allob such a > two-stage boot loader as used by Atmel on the AT91RM9200DK. So we check if all other arm920t boards have an implementation of memsetup(). Then kick out CONFIG_INIT_CRITICAL and introduce CONFIG_DO_NOT_MAKE_LOWLEVEL_INIT or something like that !? ;-) -- Steven Scholz --__--__-- Message: 13 To: Steven Scholz <steven.scholz(a)imc-berlin.de> Cc: u-boot-users(a)lists.sourceforge.net From: Wolfgang Denk <wd(a)denx.de> Subject: Re: [U-Boot-Users] CONFIG_BOOTBINFUNC for AT91RM9200 Date: Wed, 24 Nov 2004 16:06:46 +0100 In message <41A48489.80203(a)imc-berlin.de> you wrote: > > So we check if all other arm920t boards have an implementation of memsetup(). > Then kick out CONFIG_INIT_CRITICAL and introduce > CONFIG_DO_NOT_MAKE_LOWLEVEL_INIT or something like that !? ;-) Sounds like a plan to me - but let's use a better name, please. 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 Why can you only have two doors on a chicken coop? If it had four it would be a chicken sedan. --__--__-- _______________________________________________ U-Boot-Users mailing list U-Boot-Users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users End of U-Boot-Users Digest ********************************DISCLAIMER********************************** This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege of Deccanet Designs Ltd. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from retaining, using, copying, altering or disclosing the contents of this message. ****************************************************************************

3 9

[U-Boot-Users] u-boot and linux-2.6.9
by jean-paul.saman＠philips.com 22 Dec '04

22 Dec '04

I am trying to boot on an ARM-Integrator AP a linux-2.6.9 kernel with u-boot. I tried u-boot-1.1.1 stable and cvs, but both result in "data abort" just at the point of "Starting kernel .... ". Here is the dump from minicom: Integrator-AP # bootm 24400000 Boot reached stage 1 ## Booting image at 24400000 ... Boot reached stage 2 Boot reached stage 3 Image Name: Linux-2.6.9 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1216080 Bytes = 1.2 MB Load Address: 00008000 Entry Point: 00008000 Boot reached stage 4 Boot reached stage 5 Boot reached stage 6 OK Boot reached stage 7 Boot reached stage 8 Boot reached stage 14 No initrd Boot reached stage 15 ## Transferring control to Linux (at address 00008000) ... Starting kernel ... data abort pc : [<0000801c>] lr : [<0100bcbc>] sp : 00fd7bd4 ip : 00fd7bc4 fp : 00fd7c10 r10: 00000000 r9 : 00fd7c84 r8 : 00fd7fdc r7 : 0100f1b4 r6 : 0100f1b4 r5 : 00000000 r4 : 24400040 r3 : e1a00001 r2 : 00000100 r1 : e1a00000 r0 : 00000000 Flags: nZCv IRQs off FIQs off Mode SVC_32 Resetting CPU ... Has anyone succeeded in booting a 2.6.x kernel with u-boot? Kind greetings, Jean-Paul Saman

5 7

[U-Boot-Users] Bad ecc error in 16bit nand flash
by Pankaj GOYAL 22 Dec '04

22 Dec '04

Hi all, I m using the 16bit Nand flash from the STMicro on a arm based CPU.I m selecting the option of calculating and storing the ecc on the out of bound data.When I write some data on the nand and read the same data I m getting the Bad ECC error.Can someone plase tell me that is there any problem in the data writing to the Nand Bye

1 0

[U-Boot-Users] Re: What does the Kernel get from U-boot ?
by Federico Lucifredi 22 Dec '04

22 Dec '04

Hello Booters, Just a quick newbie-style question: what is passed between U-boot and the kernel? Just the bootargs env variable or is there any other (more intimate :-) relationship between the two? What I am asking is, what does the kernel get from U-boot aside from the location of the root filesystem? I guess the answer is 'nothing', but if it turns out there is more, I'd like to know =) -Federico _________________________________________ -- "'Problem' is a bleak word for challenge" - Richard Fish Muad'Dib of Caladan (Federico L. Lucifredi)- Harvard University & BU http://metcs.bu.edu/~lucifred

3 2

[U-Boot-Users] Restoring the Planet Core Boot Loader Image in EP8260
by Vikrant_Basotra 22 Dec '04

22 Dec '04

Hello All, We are working on the EP8260M1.3 Embedded planet board. We have erased the planet core bootloader image from the board and downloaded our U-boot image for ep8260. We now want to restore the planet core bootloader image back. We have tried the following steps: 1.We tried burning the image with Code Warrior.We were unsuccessful in getting the Planet Core boot loader Command prompt. 2. We decided to try burning the Planet core bootloader using the Flash burner Application bundled along with the board. Embedded Planet provides both these images in srec format (PCL82xx106.ep, PCB82xx105.ep). We converted both these Srec images to Bin using MOT2BIN utility. We placed the Planet core bootloader Bin image at 0x00100000 and the Flash burner Bin image at 0x00200000.We then gave the command "go 0x00200000" to launch the Flash burner. But we get the message: ## Starting application at 0x00200000 ... NIP: 00200000 XER: 00000000 LR: 01FA2EEC REGS: 01f37ca0 TRAP: 0700 DAR: 00000067 MSR: 0008a002 EE: 1 PR: 0 FP: 1 ME: 0 IR/DR: 00 GPR00: 01FA2EDC 01F37D90 FFFFFFFF 00000001 01F7827C 00000010 FFFFFFFE 00000005 GPR08: 00000041 F0000088 00000000 F0000091 00000030 FFFFFFFF 01FCC000 02098000 GPR16: 00000000 00000000 00000000 0000000B 00000000 00000000 00000001 00000000 GPR24: 00000000 00000000 00000000 01F7827C 00200000 01F37F6C 01FCC664 00000001 Call backtrace: 01FA2EDC 01FAF31C 01FAF544 01FAF910 01FB0A10 01FB0B80 01FA18F4 01F9CEEC 01F9B570 Program Check Exception After this Uboot begins. Can anyone help us proceed. ************************************************************************** This email (including any attachments) is intended for the sole use of the intended recipient/s and may contain material that is CONFIDENTIAL AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or distribution or forwarding of any or all of the contents in this message is STRICTLY PROHIBITED. If you are not the intended recipient, please contact the sender by email and delete all copies; your cooperation in this regard is appreciated. **************************************************************************

3 2

[U-Boot-Users] Re: Intel StrataFlash 28F128J3 vs. 28F256K3
by Craig A. Vanderborgh 21 Dec '04

21 Dec '04

To Robert Whaley & Wolfgang Denk: THANK YOU ONE MILLION TIMES. You have just saved my holidays!! I have been able to get the K3 flash working correctly on my board, and it's simply terrific. The big problem was that I did not fully understand that I should be using the canonical CFI driver. Robert sent me his configs for a simliar board, and through this I learned that I should be using the CFI driver, and not a board-specific one. After some additional configuration for & futzing with the CFI driver, it is all working very well. This has been a huge hurdle for me and I thank both of you - and the creators of u-boot - for making it possible for us to surmount it. Happy Holidays!!

1 0

[U-Boot-Users] Reading or writing jffs2 - how?
by Martin Egholm Nielsen 21 Dec '04

21 Dec '04

Hi there, I have tried to create a jffs2-image of the linux-filesystem I wish to use, and then write it to my flash using "nand write.jffs2 100000 0 $(filesize)". But with no luck... Then I began to investigate the fundamental "ls" and "nand erase" commands, but neither there did I have any success. Below is a trace of what I've tried in order to get something working. In section 2, I'd expect the nand to be mountable from Linux - but's it's not. In section 3, I'd expect the filesystem to be ls'ed correct from u-boot - but it's not... Can someone tell me if there is something I've misunderstood? ******************************** ********** 1 U-Boot ************ ******************************** U-Boot 1.1.2 (Nov 27 2004 - 11:50:10) CPU: IBM PowerPC 405EP Rev. B at 333.333 MHz (PLB=111, OPB=55, EBC=37 MHz) ==== 8< 8< 8< ==== NAND:Probing at 0xff400000 64 MB ==== 8< 8< 8< ==== => nand erase clean NAND erase: device 0 offset 0, size 67108864 ... OK => ls Scanning JFFS2 FS: done. => ******************************* ********** 2 Linux ************ ******************************* # cat /proc/mtd dev: size erasesize name mtd0: 04000000 00004000 "Trampoline Nand Flash (128 MB)" # mount -t jffs2 /dev/mtdblock0 mnt/nand0 jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB) instead Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes empty_blocks 1325, bad_blocks 4, c->nr_blocks 2048 mount: Mounting /dev/mtdblock0 on /mnt/nand0 failed: Invalid argument # eraseall /dev/mtd0 Erasingnand_erase: attempt to erase a bad block at p 16 Kibyte @ 400age 0x00000020 0 -- 0 % complenand_erase: attempt to erase te. eraseall: /a bad block at page 0x00000040 dev/mtd0: MTD Ernand_erase: attempt to erasase failure: Inpe a bad block at page 0x00000060 nand_erase: attempt to erase a bad blo Erasing 16 Kibck at page 0x00000080 yte @ 8000 -- 0nand_erase: attempt to er % complete. erase a bad block at page 0x000000a0 aseall: /dev/mtd0: MTD Erase fainalure: Input/outpnd_erase: attempt to erase a b ad block at page 0x000000c0 ut error Erasinand_erng 16 Kibyte @ case: attempt to erase a bad block at page 0x000000e0 000 -- 0 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erasing 16 Kibyte @ 10000 -- 0 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erasing 16 Kibyte @ 14000 -- 0 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erasing 16 Kibyte @ 18000 -- 0 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erasing 16 Kibyte @ 1c000 -- 0 % complete. eraseall: /dev/mtd0: MTD Erase failure: Input/output error Erased 65536 Kibyte @ 0 -- 100% complete. # mount -t jffs2 /dev/mtdblock0 /mnt/nand0/ jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB) instead # touch /mnt/nand0/testfile # mkdir /mnt/nand0/testdir # umount /mnt/nand0 jffs2: No clean, dirty _or_ erasable blocks to GC from! Where are they all? jffs2: Couldn't find erase block to garbage collect! # mount -t jffs2 /dev/mtdblock0 /mnt/nand0/ jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB) instead # ls -l /mnt/nand0/ drwxr-xr-x 2 0 0 0 Feb 8 05:59 testdir -rw-r--r-- 1 0 0 0 Feb 8 05:59 testfile ******************************** ********** 3 U-Boot ************ ******************************** => ls Scanning JFFS2 FS: done. => Best regards, Martin Egholm

3 12

[U-Boot-Users] Intel StrataFlash 28F128J3 vs. 28F256K3
by Craig A. Vanderborgh 21 Dec '04

21 Dec '04

Hello, I am bringing up u-boot on a new revision of our board and I am having a problem with flash. Both boards have share *exactly* the same schematic, with just one difference. The newer board has 2 Intel 28F256K3 flash chips in a single bank versus 2 Intel 28F128J3 flash chips in a single bank on the older board. I am inexperienced with this flash stuff, so bear with me. What I am seeing is very strange. The board comes up, and everything works except flash. u-boot comes up, serial works fine, DRAM works fine. Flash does not work right. Here is what I am seeing. 1. Using JTAG, I can program the 1st sector of flash successfully. This works and I am using this mechanism to boot the board. 2. Using JTAG or u-boot flash commands, erasing appears to work for all sectors > sector 0. Programming does NOT work. The low-order bits (for bytes 1&2) are programmed correctly. The high-order bits (for bytes 3&4) are LOST, and thus every 32-bit word contains "ff" as the high-order bytes after programming. I have made ABSOLUTELY CERTAIN that all my PXA register settings are correct. The same flash code (within u-boot) works correctly on the older board (with the J3's). I am very stuck - and I would appreciate some help. I have spent a vast amount of time on this problem and I would dearly love any bone that might be tossed from the U-Boot gurus. Thansk in advance, craig vanderborgh voxware incorporated

3 2

[U-Boot-Users] Registering Interrupt Handlers for ARM920T-Based boards
by Rodel Miguel 21 Dec '04

21 Dec '04

Hi Group, How do I register an interrupt handler in U-Boot? My customer is persistent in flow controls in binary image downloading. I am now free to support hardware flow control or XON/XOFF. Can somebody please give me guidelines on how to create support for hardware flow control on my ns16550-based serial driver? I am using smdk2410 as my template. Maybe, the initial step is how do I register my interrupt handlers? Thank you very much for your time. Best Regards, Rodel Miguel

2 1

[U-Boot-Users] minor changes brings system to hang
by Jonas Dietsche 21 Dec '04

21 Dec '04

Hello list, I have a strange behaviour when I try to modify my u-boot image (u-boot-1.1.0). The same results with u-boot-1.1.1. I use a ARM9 of NetSilicon, uclibc toolchain. When I modify e.g. CONFIG_BOOTCOMMAND or add a define in my config file u-boot hangs booting. Maybe I'm blind and don't see what I have forgotten... I disassembled the working and a not working version and compared them. They looked completely different - about 800 differences - although I deleted only two characters in the CONFIG_BOOTCOMMAND string. What catched my eye were the start, bss_start and bss_end addresses. Here the output of the working image: 00f80044 <_armboot_start>: f80044: 00f80000 rsceqs r0, r8, r0 00f80048 <_bss_start>: f80048: 00f9e308 rsceqs lr, r9, r8, lsl #6 00f8004c <_bss_end>: f8004c: 00fa2784 rsceqs r2, sl, r4, lsl #15 and the output of the damaged one 00f80044 <_armboot_start>: f80044: 00f80000 rsceqs r0, r8, r0 00f80048 <_bss_start>: f80048: 00f9e300 rsceqs lr, r9, r0, lsl #6 00f8004c <_bss_end>: f8004c: 00fa277c rsceqs r2, sl, ip, ror r7 The output fragment I get when u-boot boots is ot code: 00F80000 -> 00F9E308 BSS: -> 00FA2784 Stack: 0badc0de Stack: 0badc0de Configuration: #0: 00000000 16 MB? The bss_start and bss_end addresses do not correspond to the addresses of the disassembled image. Any suggestions? Thanks for your help, -- Jonas Dietsche

2 2