Matt, Thanks for the suggestion. I have tried it and it improves things a little in that I don't get my system re-booting to U-boot. But now it just hangs at 'Starting Kernel....' By the way what tftp load address do you use ? I've been using 30008000. Any why do you use 30f00000 for the mkimage?
Thanks, Dave
SMDK2410 # bootm ## Booting image at 3000a000 ... Image Name: Linux Kernel Image Created: 2004-02-20 17:35:01 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 620436 Bytes = 605.9 kB Load Address: 30f00000 Entry Point: 30f00000 Verifying Checksum ... OK Uncompressing Kernel Image ... OK
Starting kernel ...
"Matt Matoushek" mmatoushek@invocon.com wrote:
< < This is a multi-part message in MIME format. < < ------=_NextPart_000_00B1_01C3F79D.D0FB4480 < Content-Type: text/plain; < charset="us-ascii" < Content-Transfer-Encoding: 7bit < < Howdy Dave, < < See if the attached file helps. This is the script I use to create my < uImage for U-Boot with a Mizi kernel on the SMDK2410. < < Matt < < > -----Original Message----- < > From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users- < > admin@lists.sourceforge.net] On Behalf Of asnua@eircom.net < > Sent: Friday, February 20, 2004 9:10 AM < > To: Gerrit Van de Velde; asnua@eircom.net < > Cc: u-boot-users@lists.sourceforge.net < > Subject: Re: [U-Boot-Users] U-Boot and S3c2410 < > < > (1) I looked back at my errors and I've begun to realise that an < Error: a < > is the correct answer whenever you issue a 'go' to the kernel address < as < > r0/r1 have no chance of being setup correctly i.e. I'm using 'go' as < my < > bootloader.So with that in mind the bootm is the correct approach. < > < > I tried the suggestion from Gerrit and it didn't work fully. However, < I < > don't get the register dump anymore so the load and entry addresses of < > 0x00000000 certainly has an effect on something. But in the end it < just < > resets to U-boot. See below: < > < > SMDK2410 # tftpboot 30008000 myUbootzimage_comp15.img < > TFTP from server 192.xxx.xx.xx; our IP address is 192.xxx.xx.xx < > Filename 'myUbootzimage_comp15.img'. < > Load address: 0x30008000 < > Loading: < ################################################################# < > < ################################################################# < > ## < > done < > Bytes transferred = 670764 (a3c2c hex) < > SMDK2410 # imi < > < > ## Checking Image at 30008000 ... < > Image Name: 2.4.18 15th attempt < > Created: 2004-02-19 16:59:39 UTC < > Image Type: ARM Linux Kernel Image (uncompressed) < > Data Size: 670700 Bytes = 655 kB < > Load Address: 00000000 < > Entry Point: 00000000 < > Verifying Checksum ... OK < > SMDK2410 # bootm < > ## Booting image at 30008000 ... < > Image Name: 2.4.18 15th attempt < > Created: 2004-02-19 16:59:39 UTC < > Image Type: ARM Linux Kernel Image (uncompressed) < > Data Size: 670700 Bytes = 655 kB < > Load Address: 00000000 < > Entry Point: 00000000 < > Verifying Checksum ... OK < > OK < > < > Starting kernel ... < > < > < > U-Boot 1.0.0 (Feb 13 2004 - 15:17:52) < > < > U-Boot code: 33F80000 -> 33F96740 BSS: -> 33F99FA0 < > DRAM Configuration: < > Bank #0: 30000000 64 MB < > Flash: 1 MB < > In: serial < > Out: serial < > Err: serial < > Hit any key to stop autoboot: 0 < > < > (2) Gerrit....Are you also using the S3C2410? < > < > (3) So why isn't it booting. Or more correctly why is it resetting < after < > it issues the 'Starting kernel ...' message!! < > Am I missing some bootarguments? < > < > (4) I've looked at the VIVI bootloader (from SAMSUNG) and I can see a < > 'mach-type' parameter which can be edited from the monitor interface. < I < > forced it to 100 (from 193) to get MIZI to fail in the same way with < an < > 'Error :a'. Does U-Boot have a similar parameter ? < > < > Thanks again, < > Dave < > < > Gerrit Van de Velde gvd@denayer.wenk.be wrote: < > < > < < > < < > < > ## Checking Image at 30008000 ... < > < > Image Name: 2.4.18 6th attempt < > < > Created: 2004-02-12 13:25:43 UTC < > < > Image Type: ARM Linux Kernel Image (uncompressed) < > < > Data Size: 1814955 Bytes = 1.7 MB < > < > Load Address: 30008000 < > < > Entry Point: 30008000 < > < > Verifying Checksum ... OK < > < > < > < < > < I'm not able to answer all your questions but I had this problem < too. < > < When making image of the kernel, use start address and entry points < > < 0x00000000 instead of the address where the image is stored. That < > solved < > < the problem for me. < > < < > < Kind regards, < > < Gerrit Van de Velde < > < < > < < > < < > < < > < > < > < > < > ------------------------------------------------------- < > SF.Net is sponsored by: Speed Start Your Linux Apps Now. < > Build and deploy apps & Web services for Linux with < > a free DVD software kit from IBM. Click Now! < > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click < > _______________________________________________ < > U-Boot-Users mailing list < > U-Boot-Users@lists.sourceforge.net < > https://lists.sourceforge.net/lists/listinfo/u-boot-users < < ------=_NextPart_000_00B1_01C3F79D.D0FB4480 < Content-Type: application/octet-stream; < name="mkuImage.sh" < Content-Transfer-Encoding: quoted-printable < Content-Disposition: attachment; < filename="mkuImage.sh" < < #/bin/bash=0A= < =0A= < arm-linux-objcopy -O binary =0A= < -R .note -R .comment =0A= < -S vmlinux linux.bin=0A= < =0A= < gzip -9 linux.bin=0A= < =0A= < mkimage -A arm -O linux -T kernel -C gzip =0A= < -a 0x30f00000 -e 0x30f00000 -n "Linux Kernel Image" =0A= < -d linux.bin.gz uImage=0A= < =0A= < =0A= < < ------=_NextPart_000_00B1_01C3F79D.D0FB4480-- < <