December 2004 - U-Boot

[U-Boot-Users] Debugging u-boot onto at91rm9200dk with BDI2000
by Paugam Luc 10 Dec '04

10 Dec '04

Hi all, Board used: ATMEL AT91RM9200-DK U-Boot version: Latest from CVS I try to debug u-boot code starting in Flash (only u-boot present in Flash, there is not boot.bin 1st ATMEL bootloader) with a BDI2000 connected to JTAG. The PC is set to 0x0 while the Flash base address is at 0x1000.0000 At which address should be set the PC in order to start correctly u-boot code ? When I set the PC to 0x0, u-boot doesn't start. When I set the PC to 0x1000.0000, u-boot starts but I get an Abort signal at address 0x1000.041C inside lowlevel_init What did I miss ? Thanks for your contribution. Luc

1 0

[U-Boot-Users] DiskOnChip G3 support
by Ara Avanesyan 10 Dec '04

10 Dec '04

Any plans to supporting DOC G3 in u-boot? Thanks, Ara

1 0

[U-Boot-Users] USB support in U-boot
by MuthuGanesh M 10 Dec '04

10 Dec '04

Hello, I am working with MPC8xx processor. Is there any USB Support for that in u-boot. If so how to proceed ? Thankyou, Muthuganesh.M

2 1

RE: [U-Boot-Users] Overwriting protected flash memory!!!
by Cabral, Kevin 09 Dec '04

09 Dec '04

<Wolfgang Denk wrote...> > What makes you think so? The boot messages above seem to indicate > that the old boot loader came up just fine and started to load the > linux kernel. Sorry, for not being more specific but when I try to enter the (i-boot) bootloader I get the i-boot prompt but then the system freezes. This would probably suggest that part of the bootloader is corrupt but not the entire thing. Perhaps only part of the bootloader that didn't get over written still works (i.e. Just enough to try and load the kernel). <Wolfgang Denk wrote...> > This is an explicitely unsupported mode of use, and reason enough NOT > to answer any of your other questions in this message. See the FAQ > (http://www.denx.de/twiki/bin/view/DULG/CanUBootBeConfiguredSuchThatItCanBeS…) Until reading this article I wasn't aware that loading u-boot into RAM was an unsupported mode of use. Instead, I may will try loading u-boot into flash. (Thanks for the article) <Wolfgang Denk wrote...> > The "protect" stuff is something that is intended to prevent > accidental data loss by a istyped command etc. It cannot protect you > from doing stupid things. Thanks for the explanation of "protect" for flash in u-boot. Originally, I had the impression that my bootloader in flash was safe, even from doing stupid things, which would allow me experiment since I'm just a newbie at these things but I guess I learned the hard way. I appreciate your responses and insight. Your right, there were a couple of serious errors made on my part. But as you can see from my original post that I was aware of most of these errors; unfortunately, I wasn't aware of these errors before it was too late. Thanks for your help

1 0

[U-Boot-Users] Is there a plan for the next release?
by Tom Armistead 09 Dec '04

09 Dec '04

Hi, I was wondering if there is a planned date for the next u-boot release? Thanks, Tom Armistead __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

[U-Boot-Users] Overwriting protected flash memory!!!
by Cabral, Kevin 09 Dec '04

09 Dec '04

I'm trying to experiment with u-boot as a possible replacement for my current bootloader (iboot). I've encountered a problem where u-boot is overwriting flash protected memory on my cerfcube pxa250. This is my current situation: I am using CerfBoard/CerfCube (PXA250): Here is the flash layout - Bootloader = 0x0 - 0x3FFFF Flash Block 0 - Bootloader Reserved = 0x40000 - 0xBFFFF Flash Blocks 1 and 2 - Kernel = 0xC0000 - 0x1BFFFF Flash Blocks 3 - 10 (inclusive) - FS = 0x1C0000 - end* Flash blocks 11-127* (inclusive) RAM starts at: 0xA0000000 Currently, the cerfboard has the i-boot bootloader installed in flash memory at sector 0. I've been trying to experiment with u-boot by loading it into RAM and then downloading a kernel into RAM through tftp and trying to boot from it. These are the steps I took: Download u-boot.bin into RAM and jump to it iboot$ download tftp:192.168.100.10 u-boot.bin 0xa0100000 iboot$ jump 0xa0100000 Now I'm successfully running u-boot. By default only sectors 0 & 1 are write protected but I need to make sure that the first 3 sectors are write protected and not just the first 2 sectors so I don't overwrite my default bootloader (iboot) and red boot partitions (sector 1 & 2). Looking at the table produced by flinfo confirms that the first three sectors of flash are read only uboot$ protect on 1:0-2 uboot$ flinfo On my host PC I ran mkimage to generate the tag header for my kernel: $ ./mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n "Linux 2.6.9-Cerf1" -d zImage uImage On my target platform I downloaded the kernel image and booted from it uboot$ tftp 0xa0300000 uImage uboot$ bootm 0xa0300000 uImage ## Booting image at a0300000 ... Image Name: Linux 2.6.9-Cerf1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 876940 Bytes = 856.4 kB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 00000000 ... Bad Magic Number resetting ... ************************************************** ** Intrinsyc Bootloader (IBoot) ** ** Copyright 2001-2003 Intrinsyc Software Inc. ** ** Version: 1.8 (Jun 11 2003) PXA255 ** ** Support: http://www.intrinsyc.com ** ************************************************** Using FFUART 24LC64 not detected! (using 000000AC) SMSC LAN91C111 Found at Address 0x04000000 Auto-negotiation result: 100BaseT Full-Duplex 0 Storing EEPROM contents in tagged format Relocating zImage from 000C0000 to A0008000 (len=00100000) Proper ARM zImage ID found. Booting... Uncompressing Linux... invalid compressed format (err=2) -- System haltedÿ I just realized while writing this post that I had accidently passed in an extra argument into bootm, which was "uImage". This probably led to the error "## Loading Ramdisk Image at 00000000 ... Bad Magic Number". Regardless of this error, the default bootloader (iboot) is now corrupt and the kernel that was originally stored in flash @ 0xC0000 (sector 3) is also corrupt. This means that the bootm command must have tried to copy the kernel image to the load address (0x8000) specified in the tag header in uImage. Thus, overwriting flash memory. I do understand that I probably should have specified a load address and a entry point of 0xA0008000 instead of 0x8000 so that the kernel would have loaded from RAM but even making a mistake like that should not have overwritten flash memory or even protected flash memory!!! I thought that as long as my first 3 sectors in flash were write protected that it wouldn't be able to overwrite them. Is this a bug or a known behavior of u-boot? Could someone please shed some light on why this might have happened.

3 5

[U-Boot-Users] Question to install ELDK
by 灰色轨迹 09 Dec '04

09 Dec '04

Hi. I had download ELDK3.1 for arm(arm-2004-11-09.iso). And I prepared a host environment with a full installation of Red Hat Linux 9, and mount the iso file in my host OS, to execute #./install -d /ELDK arm without errors. Add ELDK's bin directory to $PATH. After doing these, can I use this ELDK compile u-boot? Does the Environment variable CROSS_COMPILE MUST be set?

5 6

[U-Boot-Users] How to hardcoded linux kernel command line
by nick 09 Dec '04

09 Dec '04

Hi, I know that in U-boot, you can set up bootargs in the command prompt. But because I do not have specificated flash space for u-boot to store those data, can I hard-code the linux kernel command line? I mean just write it in the source code. If I can, where should I go? Thank you. Nick Lo ----------------- John14:6 - Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me.

2 1

[U-Boot-Users] Re: help porting u-boot for customized ixdp425 board
by Ara Avanesyan 09 Dec '04

09 Dec '04

Hi again, and thanks all for the answers... Well, seems i was unable to give you an idea what I really needed, pity:) My only problem (at this stage) is regarding those nesty flash stuff. As for building, downloading, debugging etc these are pretty easy. And why really I've asked for help, coz I do not have the target board yet and i can't do any tests for now, i just want to make sure u-boot can be adapted for my target. Ok, specific questions are: as in my board's booting flash is different from the original ixdp and i do not keep anything in this flash do i (ok, u-boot) need to recognize it at all? why? as my second flash (OS, fs etc) is DOC, what shell I add/modify/remove to make u-boot to understand this guy? and... do i understand it correctly - if i want doc commands to work i need the previous step be done? sorry if the questions are lame, i'm really noob here... |-:) Thanks, Ara ----- Original Message ----- From: Ara Avanesyan To: u-boot-users(a)lists.sourceforge.net Sent: Thursday, December 02, 2004 7:23 PM Subject: help porting u-boot for customized ixdp425 board Hi all, I'm noob in hardware, flashes and I need some help to porting u-boot to our customized ixdp425 hardware. This hardware contains a small CFI compliant bootable flash for u-boot (512kb) and another one 64 Mb DiskOnChip flash for OS, FS and programs. I've read readme and the online manual. I have some basic knowledge about the things and some guesses what to do. However these are only guesses without any confirmation. I do not want go through tries and failures way. Anybody familiar with those things please give me some advices where to start the porting or whatever might be useful... Any help is greatly appreciated. Thanks, Ara P.S. Btw, the doc/README.ixdp is still missing. Kyle? :)

4 6

[U-Boot-Users] Questions of uImage on sbc8260 board
by duo dong 09 Dec '04

09 Dec '04

The uImage is loaded onto RAM of sbc8260/ATM board. After starting the uImage, the msg shows: =>bootm ## Booting image at 00100000 ... Image Name: Linux-2.4.24-pre2 Created: 2004-12-03 0:48:37 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 632448 Bytes = 617.6 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x03F75B60 => set upper limit to 0x00800000 ## cmdline at 0x007FFF00 ... 0x007FFF00 bd address = 0x03F75FB4 memstart = 0x00000000 memsize = 0x04000000 flashstart = 0x40000000 flashsize = 0x00400000 flashoffset = 0x00025000 sramstart = 0x00000000 sramsize = 0x00000000 immr_base = 0xF0000000 bootflags = 0x00000001 vco = 264 MHz sccfreq = 66 MHz brgfreq = 66 MHz intfreq = 198 MHz cpmfreq = 132 MHz busfreq = 33 MHz ethaddr = 00:A0:1E:A8:7B:CB IP addr = 10.0.0.99 baudrate = 115200 bps No initrd ## Transferring control to Linux (at address 00000000) ... Memory BAT mapping: BAT2=64Mb, BAT3=0Mb, residual: 0Mb Linux version 2.4.24-pre2 (root(a)localhost.localdomain) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a_1)) #1 Thu Dec 2 19:38:30 EST 2004 On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: Warning: real time clock seems stuck! <<-- ??? Calibrating delay loop... 131.89 BogoMIPS Memory: 63220k available (1096k kernel code, 384k data, 56k init, 0k highmem) Dentry cache hash table entries: 8192 (order: 4, 65536 bytes) Inode cache hash table entries: 4096 (order: 3, 32768 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB. CPM UART driver version 0.01 ttyS0 on SMC1 at 0x0000, BRG7 ttyS1 on SMC2 at 0x0040, BRG8 ttyS2 on SCC1 at 0x8000, BRG1 ttyS3 on SCC2 at 0x8100, BRG2 pty: 256 Unix98 ptys configured eth0: FCC2 ENET Version 0.4, 00:A0:1E:A8:7B:CC RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize CFI: Found no TQM8260 Bank 0 device at location zero <<--?? TQM8260: No supported flash chips found! <<-- ?? NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Cannot open root device "" or 00:00 <<--?? Please append a correct "root=" boot option <<--?? Kernel panic: VFS: Unable to mount root fs on 00:00 <<--?? <0>Rebooting in 180 seconds.. Then, system hung. The u-boot envs are: => printenv bootcmd=version;echo;bootp;setenv bootargs root=/dev/nfs rw nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip):$(gatewayip):$(netmask):$(hostname)::off;bootm bootdelay=5 baudrate=9600 ethaddr=00:a0:1e:a8:7b:cb loads_echo=1 do_echo=1 ipaddr=10.0.0.99 serverip=10.0.0.2 netmask=255.0.0.0 hostname=sbc8260 stdin=serial stdout=serial stderr=serial ver=U-Boot 1.0.2 (Nov 27 2004 - 10:55:29) Environment size: 392/262140 bytes The uImage is build by using TQM8260_config. Q1. Can the uImage build by using TQM8260_config can be used on sbc8260 board? If can not, which config I should use? Q2. I marked several places above by "<<--??". Any one see those before? If you do, please let me know how to fix them. Thanks, dd __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 9