[U-Boot-Users] U-Boot and S3c2410

[U-Boot-Users] U-Boot and S3c2410

[Gerrit Van de Velde]

> ## 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

[U-Boot-Users] U-Boot and S3c2410

[asnua at eircom.net]

Wolfgang/Gerrit/Matt,
Thanks for your help....

I think that I finally figured out how to boot the kernel. 
I looked at the definitions for ZTEXTADDR and ZRELADDR and found that they were at 0x30008000. So I made my load and entry points to be that address.
I then offset my tftp address so that it would not overwrite
0x30008000.

Unfortunately, it dies after I get the message... Uncompressing Linux.... done, booting the kernel.





SMDK2410 # tftpboot 30a00000 myzImage.img
TFTP from server 192.xxx.xx.xx; our IP address is 192.xxx.xx.xx
Filename 'myzImage.img'.
Load address: 0x30a00000
Loading: #################################################################
         #################################################################
done
Bytes transferred = 662556 (a1c1c hex)
SMDK2410 # bootm
## Booting image at 30a00000 ...
   Image Name:   2.4.18 kernel
   Created:      2004-02-24  17:33:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    662492 Bytes = 647 kB
   Load Address: 30008000
   Entry Point:  30008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................ done, bootin
g the kernel.

[U-Boot-Users] U-Boot and S3c2410

[Wolfgang Denk]

In message <20040223152655.1C51E42F39@denx.de> you wrote:
> So what is the difference between the load and entry addresses? All

The load address is where the kernel gets loaded into  RAM  when  you
run the "bootm" command, and the entry point address is the address -
um - of the entrypoint, i. e. the first exacutable instruction.

> of the examples I've seen have the load and entry addresses set to be
> the same...ish. 0x00000000 & 0x0000000c for PPC

Wong. Both are 0x000 on PowerPC by default.

> In my case my SDRAM starts at 0x30000000 and ends at 0x33FFFFFF. My
> Flash and hence U-Boot is at 0x00.

> Does the load and entry address vary depending on whether you are using vmlinux/vmlinux compressed/zImage?

It depends on what your Linux kernel's linker script  does.  I  don;t
know  your  kernel  source  tree,  so I have no idea which values are
correct for you.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
FORTRAN? The syntactically incorrect statement "DO 10 I = 1.10"  will
parse  and  generate  code  creating  a  variable, DO10I, as follows:
"DO10I = 1.10" If that doesn't terrify you, it should.

[U-Boot-Users] U-Boot and S3c2410

[Gerrit Van de Velde]

I'm far from an expert on the matter ;)
But I would try to set the addresses to 0x30000000 then. The kernel will
be expanded to RAM first and then a jump will be made to the address in
the RAM to start executing the kernel.

In my situation, I used 0x0 as start/entry. RAM starts on that address
too.

Regards,
Gerrit


On Mon, 2004-02-23 at 16:20, asnua at eircom.net wrote:
> So what is the difference between the load and entry addresses? All of the examples I've seen have the load and entry addresses set to be the same...ish. 0x00000000 & 0x0000000c for PPC
> In my case my SDRAM starts at 0x30000000 and ends at 0x33FFFFFF. My Flash and hence U-Boot is at 0x00.
> 
> Does the load and entry address vary depending on whether you are using vmlinux/vmlinux compressed/zImage?
> 
> Thanks,
> Dave

[U-Boot-Users] U-Boot and S3c2410

[Wolfgang Denk]

In message <1077551762.4835.50.camel@nios> you wrote:
> I'm far from an expert on the matter ;)
> But I would try to set the addresses to 0x30000000 then. The kernel will

This depends on how the kernel was linked.

> be expanded to RAM first and then a jump will be made to the address in
> the RAM to start executing the kernel.
> 
> In my situation, I used 0x0 as start/entry. RAM starts on that address
> too.

This is correct on PowerPC, but wrong on all other systems.

The address to be used  is  defined  in  the  Linux  kernel's  linker
commands  /  scripts;  seach which value of PTEXTADDR gets defined in
"arch/arm/Makefile" for your board; in your  "arch/arm/boot/Makefile"
you should then have a build target like this:

uImage:	compressed/piggy.gz
	mkimage -A arm -O linux -T kernel -C gzip \
	-a $(PTEXTADDR) -e $(PTEXTADDR) \
	-n 'ARM Linux-$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)' \
	-d compressed/piggy.gz $@


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
It may be that your whole purpose in life is simply  to  serve  as  a
warning to others.

[U-Boot-Users] U-Boot and S3c2410

[asnua at eircom.net]

So what is the difference between the load and entry addresses? All of the examples I've seen have the load and entry addresses set to be the same...ish. 0x00000000 & 0x0000000c for PPC
In my case my SDRAM starts at 0x30000000 and ends at 0x33FFFFFF. My Flash and hence U-Boot is at 0x00.

Does the load and entry address vary depending on whether you are using vmlinux/vmlinux compressed/zImage?

Thanks,
Dave


Wolfgang Denk <wd@denx.de> wrote:

<  
<  In message <4036262C.4020600@denayer.wenk.be> you wrote:
<  > 
<  > >(2) Gerrit....Are you also using the S3C2410? 
<  ...
<  > No, a Motorola MPC5200 Lite evaluation board.
<  > But I thought that my suggestion is pretty board-independent :)
<  
<  There are huge differences between architectures.  While  on  PowerPC
<  you  usually  have  flash  at  some  high addresses and RAM mapped at
<  0x0000, you will see flash at 0x0000 and RAM @ high  addresses  on
<  ARM.
<  
<  You really guessed wrong here.
<  
<  > $ mkimage -n 'Linux PPC MPC5200 2.4' -A ppc -O linux -T kernel -C gzip 
<  > -a 00000000 -e 00000000 -d arch/ppc/boot/images/vmlinux.gz 
<  > /tftpboot/MPC5200/vmlinux.img
<  
<  ... which is OK for PowerPC, but seriously broken for all ARM systems
<  I know.
<  
<  >(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?
<  > >
<  > you don't need to have bootarguments set to see at leaste *some* output 
<  > I think.. Something more severe is going on I believe
<  
<  You have to know the memory map of your system, and you  have  to  be
<  aware  wat  the  load address (-a option to mkimage), entry point (-e
<  option) and the address "addr" where your image is stored in RAM when
<  you type "bootm addr" mean.
<  
<  Best regards,
<  
<  Wolfgang Denk
<  
<  -- 
<  Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
<  Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
<  He'd been wrong, there _was_ a light@the end of the tunnel, and it
<  was a flamethrower.                         - Terry Pratchett, _Mort_
<  

[U-Boot-Users] U-Boot and S3c2410

[Matt Matoushek]

Howdy Dave,

tftp 0x30800000 initrd    (I'm using a ramdisk)
tftp 0x33000000 uImage
bootm

The Mizi kernel is expecting the compressed kernel image to be located
at 0x30f00000.  I would need to verify where this came from, but I've
been using it this way for a while.

Also, be sure you have your serial port access configured the same in
both U-Boot and the Mizi kernel.  I have had problems in the past (don't
remember exact details) that were related to having the kernel and
U-boot set to different Baud rates.  I believe this is talked about in
the U-boot documentation some-where, or has been discussed on this list.

Matt

> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net [mailto:u-boot-users-
> admin at lists.sourceforge.net] On Behalf Of asnua at eircom.net
> Sent: Friday, February 20, 2004 11:46 AM
> To: Matt Matoushek; asnua at eircom.net
> Cc: u-boot-users at lists.sourceforge.net
> Subject: RE: [U-Boot-Users] U-Boot and S3c2410
> 
> 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 at lists.sourceforge.net
[mailto:u-boot-users-
> <  > admin at lists.sourceforge.net] On Behalf Of asnua at eircom.net
> <  > Sent: Friday, February 20, 2004 9:10 AM
> <  > To: Gerrit Van de Velde; asnua at eircom.net
> <  > Cc: u-boot-users at 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 at 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--
> <
> <
> 
> 
> 
> 
> -------------------------------------------------------
> 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users

[U-Boot-Users] U-Boot and S3c2410

[asnua at eircom.net]

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 at lists.sourceforge.net [mailto:u-boot-users-
<  > admin at lists.sourceforge.net] On Behalf Of asnua at eircom.net
<  > Sent: Friday, February 20, 2004 9:10 AM
<  > To: Gerrit Van de Velde; asnua at eircom.net
<  > Cc: u-boot-users at 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 at 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--
<  
<  

[U-Boot-Users] U-Boot and S3c2410

[Matt Matoushek]

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 at lists.sourceforge.net [mailto:u-boot-users-
> admin at lists.sourceforge.net] On Behalf Of asnua at eircom.net
> Sent: Friday, February 20, 2004 9:10 AM
> To: Gerrit Van de Velde; asnua at eircom.net
> Cc: u-boot-users at 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 at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mkuImage.sh
Type: application/octet-stream
Size: 245 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040220/44aa0c09/attachment.obj 

[U-Boot-Users] U-Boot and S3c2410

[Gerrit Van de Velde]

asnua at eircom.net wrote:

>(2) Gerrit....Are you also using the S3C2410? 
>
>  
>
No, a Motorola MPC5200 Lite evaluation board.
But I thought that my suggestion is pretty board-independent :)

this is how i created my image:

$ mkimage -n 'Linux PPC MPC5200 2.4' -A ppc -O linux -T kernel -C gzip 
-a 00000000 -e 00000000 -d arch/ppc/boot/images/vmlinux.gz 
/tftpboot/MPC5200/vmlinux.img

and then in U-Boot:

=> tftpboot 100000 MPC5200/vmlinux.img

=> cp.b 100000 FF100000 $(filesize)

=> bootm FF100000

>(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?
>  
>
you don't need to have bootarguments set to see at leaste *some* output 
I think.. Something more severe is going on I believe

-- 
Kind regards,
ing. Gerrit Van de Velde

Onderzoeksgroep Digitale Technieken
W & K, Campus De Nayer
J. De Nayerlaan 5
2860 Sint-Katelijne-Waver

Tel. 015 / 31 69 44
Fax. 015 / 31 74 53
http://emsys.denayer.wenk.be 

[U-Boot-Users] U-Boot and S3c2410

[Wolfgang Denk]

In message <4036262C.4020600@denayer.wenk.be> you wrote:
> 
> >(2) Gerrit....Are you also using the S3C2410? 
...
> No, a Motorola MPC5200 Lite evaluation board.
> But I thought that my suggestion is pretty board-independent :)

There are huge differences between architectures.  While  on  PowerPC
you  usually  have  flash  at  some  high addresses and RAM mapped at
0x0000, you will see flash at 0x0000 and RAM  at  high  addresses  on
ARM.

You really guessed wrong here.

> $ mkimage -n 'Linux PPC MPC5200 2.4' -A ppc -O linux -T kernel -C gzip 
> -a 00000000 -e 00000000 -d arch/ppc/boot/images/vmlinux.gz 
> /tftpboot/MPC5200/vmlinux.img

... which is OK for PowerPC, but seriously broken for all ARM systems
I know.

>(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?
> >
> you don't need to have bootarguments set to see at leaste *some* output 
> I think.. Something more severe is going on I believe

You have to know the memory map of your system, and you  have  to  be
aware  wat  the  load address (-a option to mkimage), entry point (-e
option) and the address "addr" where your image is stored in RAM when
you type "bootm addr" mean.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
He'd been wrong, there _was_ a light at the end of the tunnel, and it
was a flamethrower.                         - Terry Pratchett, _Mort_

[U-Boot-Users] U-Boot and S3c2410

[asnua at eircom.net]

(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
<  
<  
<  
<  

[U-Boot-Users] U-Boot and S3c2410

[asnua at eircom.net]

Has anyone succeeded in booting MIZI Linux from U-boot on the S3C2410 dev kit?
Here's where I'm at:

(1) Built U-boot for S3C2410 (ARM 9) --- OK
(2) Put it on AMD 1Mbyte FLASH --- OK
(3) U-Boot runs fine. get monitor prompt. ---OK
(4) Have set up tftp server on another machine. ---OK
(5) Can tftpboot the linux kernel to RAM.--- OK
(6) Can Do Mkimage --- OK
(6) Try to execute linux kernel at RAM address --- NOT OK
See below: Get an Error a: which I believe having trawled through Kernel is an invalid architecture????

tftpboot 30008000 compressed_vmlinux
TFTP from server 192.xxx.xx.xx; our IP address is 192.xxx.xx.xx
Filename 'compressed_vmlinux'.
Load address: 0x30008000
Loading: #################################################################
         #################################################################
         ##
done
Bytes transferred = 673293 (a460d hex)
SMDK2410 # go 30008000
## Starting application at 0x30008000 ...
Uncompressing Linux................................................ done, bootin
g the kernel.

Error: a

(7) Try to issue bootm --- NOT OK
tftpboot 30008000 myvmlinux6.img
TFTP from server 192.xxx.xx.xx; our IP address is xxx.xxx.xx.xx
Filename 'myvmlinux6.img'.
Load address: 0x30008000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################
done
Bytes transferred = 1815019 (1bb1eb hex)
SMDK2410 # imi

## 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

SMDK2410 # bootm
## Booting 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
   XIP Kernel Image ... OK

Starting kernel ...

data abort
pc : [<30008008>]    lr : [<33f9135c>]
sp : 33fb9bb4  ip : 33fb9ba4  fp : 33fb9be8
r10: 33fb9c5c  r9 : 00000001  r8 : 33fb9f54
r7 : 33f98db4  r6 : 30008000  r5 : 00000000  r4 : 00000000
r3 : 30008000  r2 : 50000000  r1 : 000000c1  r0 : 00000000
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

MY QUESTIONS:
(1)r2 does look odd as I don't have any RAM at that address!! I've read that it should contain the physical address of tagged list in RAM
(2) How do I ensure that r0, r1, r2 are correctly set up?
(3) Has anyone used U-boot with the S3C2410?
(4) ANy pointers to how I can move forward?
(5) How do I get the load and entry point addresses correct?

Thanks for any help received,
Dave