command bootu to start kernel

command bootu to start kernel

[Belisko Marek]

Hi,

I have mini2440 board with barebox running from RAM.
I try to start uImage kernel for that platform but I'm little bit
confused how to do it.

I do tftp uImage and the bootu uImage but it always hangs :

commandline: console=ttySAC0,115200
arch_number: 1999

I track down that theKernel pointer point to 0xffffffff (memmap return
(void*)-1) which is obviously wrong.
If I understand correctly bootu function take first parameter and try to
open a file and memmap. If file isn't opened successfully then convert
string address which is then taken for
theKernel pointer.

Is this correct procedure or do I something wrong?

Thanks for replies,

Marek


-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Juergen Beisert]

Belisko Marek wrote:
> I have mini2440 board with barebox running from RAM.
> I try to start uImage kernel for that platform but I'm little bit
> confused how to do it.
>
> I do tftp uImage and the bootu uImage but it always hangs :
>
> commandline: console=ttySAC0,115200
> arch_number: 1999
>
> I track down that theKernel pointer point to 0xffffffff (memmap return
> (void*)-1) which is obviously wrong.
> If I understand correctly bootu function take first parameter and try to
> open a file and memmap. If file isn't opened successfully then convert
> string address which is then taken for
> theKernel pointer.
>
> Is this correct procedure or do I something wrong?

Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do not 
work.

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Sascha Hauer]

Hi Marek,

On Wed, Oct 27, 2010 at 02:42:03PM +0200, Belisko Marek wrote:
> Hi,
> 
> I have mini2440 board with barebox running from RAM.
> I try to start uImage kernel for that platform but I'm little bit
> confused how to do it.
> 
> I do tftp uImage and the bootu uImage but it always hangs :

Uh, I can't remember why I named the bootu command this way, but it was
an unlucky decision. Actually this command starts raw kernel images.
What you are looking for is the bootm command which starts uimages. I
don't know why it's bootm, the command name is derived from U-Boot.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Sascha Hauer]

On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
> Belisko Marek wrote:
> > I have mini2440 board with barebox running from RAM.
> > I try to start uImage kernel for that platform but I'm little bit
> > confused how to do it.
> >
> > I do tftp uImage and the bootu uImage but it always hangs :
> >
> > commandline: console=ttySAC0,115200
> > arch_number: 1999
> >
> > I track down that theKernel pointer point to 0xffffffff (memmap return
> > (void*)-1) which is obviously wrong.
> > If I understand correctly bootu function take first parameter and try to
> > open a file and memmap. If file isn't opened successfully then convert
> > string address which is then taken for
> > theKernel pointer.
> >
> > Is this correct procedure or do I something wrong?
> 
> Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do not 
> work.

bootz is for starting zImages. At least this command has a convenient
name :)
bootz should work on your system aswell. If not, please complain loudly.
bootu is a bit tricky though. To start a raw linux image it has to be
copied to the exact address is is expected to run, for most boards this
is start of sdram + 0x8000, but this may differ on some boards (it's
basically PHYS_OFFSET + TEXT_OFFSET in the kernel)

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Wed, Oct 27, 2010 at 3:54 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
>> Belisko Marek wrote:
>> > I have mini2440 board with barebox running from RAM.
>> > I try to start uImage kernel for that platform but I'm little bit
>> > confused how to do it.
>> >
>> > I do tftp uImage and the bootu uImage but it always hangs :
>> >
>> > commandline: console=ttySAC0,115200
>> > arch_number: 1999
>> >
>> > I track down that theKernel pointer point to 0xffffffff (memmap return
>> > (void*)-1) which is obviously wrong.
>> > If I understand correctly bootu function take first parameter and try to
>> > open a file and memmap. If file isn't opened successfully then convert
>> > string address which is then taken for
>> > theKernel pointer.
>> >
>> > Is this correct procedure or do I something wrong?
>>
>> Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do not
>> work.
>
> bootz is for starting zImages. At least this command has a convenient
> name :)
> bootz should work on your system aswell. If not, please complain loudly.
Well it's not working.
tftp zImage
bootz zImage laed to:

ERROR: out of memory and device restart :(.

> bootu is a bit tricky though. To start a raw linux image it has to be
> copied to the exact address is is expected to run, for most boards this
> is start of sdram + 0x8000, but this may differ on some boards (it's
> basically PHYS_OFFSET + TEXT_OFFSET in the kernel)
T
>
> Sascha
>
> --
> Pengutronix e.K.                           |                             |
> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Juergen Beisert]

Sascha Hauer wrote:
> On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
> > Belisko Marek wrote:
> > > I have mini2440 board with barebox running from RAM.
> > > I try to start uImage kernel for that platform but I'm little bit
> > > confused how to do it.
> > >
> > > I do tftp uImage and the bootu uImage but it always hangs :
> > >
> > > commandline: console=ttySAC0,115200
> > > arch_number: 1999
> > >
> > > I track down that theKernel pointer point to 0xffffffff (memmap return
> > > (void*)-1) which is obviously wrong.
> > > If I understand correctly bootu function take first parameter and try
> > > to open a file and memmap. If file isn't opened successfully then
> > > convert string address which is then taken for
> > > theKernel pointer.
> > >
> > > Is this correct procedure or do I something wrong?
> >
> > Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do
> > not work.
>
> bootz is for starting zImages. At least this command has a convenient
> name :)
> bootz should work on your system aswell. If not, please complain loudly.

bootz works here. bootm always complains with the scripts from the generic 
environment:

booting kernel of type uimage from /dev/ram0.kernel
Bad Magic Number

But:

me@host$ file arch/arm/boot/uImage
arch/arm/boot/uImage: u-boot legacy uImage, Linux-2.6.31-00770-g54c3fe6-dir, 
Linux/ARM, OS Kernel Image (Not compressed), 2350016 bytes, Mon Oct 25 
16:58:30 2010, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC: 
0x17A7330B, Data CRC: 0x888DAA63

Anything wrong with the uImage (built with "make uImage") or the 
command 'bootm'?

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Wed, Oct 27, 2010 at 4:38 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
> Sascha Hauer wrote:
>> On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
>> > Belisko Marek wrote:
>> > > I have mini2440 board with barebox running from RAM.
>> > > I try to start uImage kernel for that platform but I'm little bit
>> > > confused how to do it.
>> > >
>> > > I do tftp uImage and the bootu uImage but it always hangs :
>> > >
>> > > commandline: console=ttySAC0,115200
>> > > arch_number: 1999
>> > >
>> > > I track down that theKernel pointer point to 0xffffffff (memmap return
>> > > (void*)-1) which is obviously wrong.
>> > > If I understand correctly bootu function take first parameter and try
>> > > to open a file and memmap. If file isn't opened successfully then
>> > > convert string address which is then taken for
>> > > theKernel pointer.
>> > >
>> > > Is this correct procedure or do I something wrong?
>> >
>> > Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do
>> > not work.
>>
>> bootz is for starting zImages. At least this command has a convenient
>> name :)
>> bootz should work on your system aswell. If not, please complain loudly.
>
> bootz works here. bootm always complains with the scripts from the generic
> environment:
bootz also work here but need to increase malloc size. Use 8M instead 4M.
>
> booting kernel of type uimage from /dev/ram0.kernel
> Bad Magic Number
>
> But:
>
> me@host$ file arch/arm/boot/uImage
> arch/arm/boot/uImage: u-boot legacy uImage, Linux-2.6.31-00770-g54c3fe6-dir,
> Linux/ARM, OS Kernel Image (Not compressed), 2350016 bytes, Mon Oct 25
> 16:58:30 2010, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC:
> 0x17A7330B, Data CRC: 0x888DAA63
>
> Anything wrong with the uImage (built with "make uImage") or the
> command 'bootm'?
Instead bootm for my uImage works:
bootm uImage
   Verifying Checksum ... OK
   Image Name:   Linux-2.6.32-rc8
   Created:      2010-09-27   8:36:01 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2058404 Bytes =  2 MB
   Load Address: 30008000
   Entry Point:  30008000
OK
commandline: console=ttySAC0,115200
arch_number: 1999

Starting kernel ...

strange but true ;)
>
> jbe
>
> --
> Pengutronix e.K.                              | Juergen Beisert             |
> Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
> Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 8:08 AM, Belisko Marek <marek.belisko@gmail.com> wrote:
> On Wed, Oct 27, 2010 at 4:38 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
>> Sascha Hauer wrote:
>>> On Wed, Oct 27, 2010 at 03:33:15PM +0200, Juergen Beisert wrote:
>>> > Belisko Marek wrote:
>>> > > I have mini2440 board with barebox running from RAM.
>>> > > I try to start uImage kernel for that platform but I'm little bit
>>> > > confused how to do it.
>>> > >
>>> > > I do tftp uImage and the bootu uImage but it always hangs :
>>> > >
>>> > > commandline: console=ttySAC0,115200
>>> > > arch_number: 1999
>>> > >
>>> > > I track down that theKernel pointer point to 0xffffffff (memmap return
>>> > > (void*)-1) which is obviously wrong.
>>> > > If I understand correctly bootu function take first parameter and try
>>> > > to open a file and memmap. If file isn't opened successfully then
>>> > > convert string address which is then taken for
>>> > > theKernel pointer.
>>> > >
>>> > > Is this correct procedure or do I something wrong?
>>> >
>>> > Try to start a zImage with "bootz". On my system 'bootm' and 'bootu' do
>>> > not work.
>>>
>>> bootz is for starting zImages. At least this command has a convenient
>>> name :)
>>> bootz should work on your system aswell. If not, please complain loudly.
>>
>> bootz works here. bootm always complains with the scripts from the generic
>> environment:
> bootz also work here but need to increase malloc size. Use 8M instead 4M.
>>
>> booting kernel of type uimage from /dev/ram0.kernel
>> Bad Magic Number
>>
>> But:
>>
>> me@host$ file arch/arm/boot/uImage
>> arch/arm/boot/uImage: u-boot legacy uImage, Linux-2.6.31-00770-g54c3fe6-dir,
>> Linux/ARM, OS Kernel Image (Not compressed), 2350016 bytes, Mon Oct 25
>> 16:58:30 2010, Load Address: 0x40008000, Entry Point: 0x40008000, Header CRC:
>> 0x17A7330B, Data CRC: 0x888DAA63
>>
>> Anything wrong with the uImage (built with "make uImage") or the
>> command 'bootm'?
> Instead bootm for my uImage works:
> bootm uImage
>   Verifying Checksum ... OK
>   Image Name:   Linux-2.6.32-rc8
>   Created:      2010-09-27   8:36:01 UTC
>   Image Type:   ARM Linux Kernel Image (uncompressed)
>   Data Size:    2058404 Bytes =  2 MB
>   Load Address: 30008000
>   Entry Point:  30008000
> OK
> commandline: console=ttySAC0,115200
> arch_number: 1999
>
> Starting kernel ...
Despite of loading kernel is working kernel isn't started for
mini2440(from u-boot works fine). It hang at:
Uncompressing Linux..................................................................................................................................
done, booting the kernel.

Same boot zImage and uImage kernels.
>
> strange but true ;)
>>
>> jbe
>>
>> --
>> Pengutronix e.K.                              | Juergen Beisert             |
>> Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
>> Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
>> Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>>
>
> thanks,
>
> marek
>
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> icq: 290551086
> web: http://open-nandra.com
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Marc Reilly]

Hi,

I have no experience with the mini2440, but:

On Friday, October 29, 2010 06:49:52 pm Belisko Marek wrote:
> On Fri, Oct 29, 2010 at 8:08 AM, Belisko Marek <marek.belisko@gmail.com> 
> >> me@host$ file arch/arm/boot/uImage
> >> arch/arm/boot/uImage: u-boot legacy uImage,
> >> Linux-2.6.31-00770-g54c3fe6-dir, Linux/ARM, OS Kernel Image (Not
> >> compressed), 2350016 bytes, Mon Oct 25 16:58:30 2010, Load Address:
> >> 0x40008000, Entry Point: 0x40008000, Header CRC: 0x17A7330B, Data CRC:
> >> 0x888DAA63
> >> 
> >> Anything wrong with the uImage (built with "make uImage") or the
> >> command 'bootm'?

The load and entry point are 0x400...  here

> > 
> > Instead bootm for my uImage works:
> > bootm uImage
> >   Verifying Checksum ... OK
> >   Image Name:   Linux-2.6.32-rc8
> >   Created:      2010-09-27   8:36:01 UTC
> >   Image Type:   ARM Linux Kernel Image (uncompressed)
> >   Data Size:    2058404 Bytes =  2 MB
> >   Load Address: 30008000
> >   Entry Point:  30008000
> > OK

and 0x300.. here


I've no idea how your RAM is mapped, but verify that it is being loaded to the 
correct address. (also check that it's not overlapping your barebox, malloc or 
stack)

> > commandline: console=ttySAC0,115200
> > arch_number: 1999
> > 
> > Starting kernel ...
> 
> Despite of loading kernel is working kernel isn't started for
> mini2440(from u-boot works fine). It hang at:
> Uncompressing
> Linux.....................................................................
> ............................................................. done, booting
> the kernel.

Also enable low level debugging and the earlyprintk in your kernel - maybe the 
kernel is running but crashes before it gets ti initializing the console.


Cheers
Marc


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 10:04 AM, Marc Reilly <marc@cpdesign.com.au> wrote:
> Hi,
>
> I have no experience with the mini2440, but:
>
> On Friday, October 29, 2010 06:49:52 pm Belisko Marek wrote:
>> On Fri, Oct 29, 2010 at 8:08 AM, Belisko Marek <marek.belisko@gmail.com>
>> >> me@host$ file arch/arm/boot/uImage
>> >> arch/arm/boot/uImage: u-boot legacy uImage,
>> >> Linux-2.6.31-00770-g54c3fe6-dir, Linux/ARM, OS Kernel Image (Not
>> >> compressed), 2350016 bytes, Mon Oct 25 16:58:30 2010, Load Address:
>> >> 0x40008000, Entry Point: 0x40008000, Header CRC: 0x17A7330B, Data CRC:
>> >> 0x888DAA63
>> >>
>> >> Anything wrong with the uImage (built with "make uImage") or the
>> >> command 'bootm'?
>
> The load and entry point are 0x400...  here
This post was from Juergen where bootm doesn't work. You're maybe
right wrong load address
is there. For s3c shoudl be 0x30008000 like for working example below.
>
>> >
>> > Instead bootm for my uImage works:
>> > bootm uImage
>> >   Verifying Checksum ... OK
>> >   Image Name:   Linux-2.6.32-rc8
>> >   Created:      2010-09-27   8:36:01 UTC
>> >   Image Type:   ARM Linux Kernel Image (uncompressed)
>> >   Data Size:    2058404 Bytes =  2 MB
>> >   Load Address: 30008000
>> >   Entry Point:  30008000
>> > OK
>
> and 0x300.. here
>
>
> I've no idea how your RAM is mapped, but verify that it is being loaded to the
> correct address. (also check that it's not overlapping your barebox, malloc or
> stack)
>
>> > commandline: console=ttySAC0,115200
>> > arch_number: 1999
>> >
>> > Starting kernel ...
>>
>> Despite of loading kernel is working kernel isn't started for
>> mini2440(from u-boot works fine). It hang at:
>> Uncompressing
>> Linux.....................................................................
>> ............................................................. done, booting
>> the kernel.
>
> Also enable low level debugging and the earlyprintk in your kernel - maybe the
> kernel is running but crashes before it gets ti initializing the console.
I have 2.6.32 kernel but early_printk isn't available and I enable
lowlevel debugging but
don't get nothing else on console. Anyway thanks.
>
>
> Cheers
> Marc
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Baruch Siach]

Hi Belisko,

On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
> I have 2.6.32 kernel but early_printk isn't available and I enable
> lowlevel debugging but
> don't get nothing else on console. Anyway thanks.

Try this patch to see the low level console output:

commit 5c31454464ed655401c31c68c895b16eafd2bde5
Author: Baruch Siach <baruch@tkos.co.il>
Date:   Mon Jan 19 10:41:47 2009 +0200

    arm, printk: the famous printascii() hack

diff --git a/kernel/printk.c b/kernel/printk.c
index 5052b54..d685f8a 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
 	/* Emit the output into the temporary buffer */
 	printed_len += vscnprintf(printk_buf + printed_len,
 				  sizeof(printk_buf) - printed_len, fmt, args);
+	{
+		extern void printascii(const char *);
+		printascii(printk_buf);
+	}
 
 
 	/*

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

HI Baruch,

On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Belisko,
>
> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>> I have 2.6.32 kernel but early_printk isn't available and I enable
>> lowlevel debugging but
>> don't get nothing else on console. Anyway thanks.
>
> Try this patch to see the low level console output:
>
> commit 5c31454464ed655401c31c68c895b16eafd2bde5
> Author: Baruch Siach <baruch@tkos.co.il>
> Date:   Mon Jan 19 10:41:47 2009 +0200
>
>    arm, printk: the famous printascii() hack
>
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 5052b54..d685f8a 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>        /* Emit the output into the temporary buffer */
>        printed_len += vscnprintf(printk_buf + printed_len,
>                                  sizeof(printk_buf) - printed_len, fmt, args);
> +       {
> +               extern void printascii(const char *);
> +               printascii(printk_buf);
> +       }
>
>
>        /*
>
> --
>                                                     ~. .~   Tk Open Systems
> =}------------------------------------------------ooO--U--Ooo------------{=
>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>
Patch works like charm. Output from my kernel startup:

<5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
(Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: MINI2440
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 0
<1>bootmem alloc of 32768 bytes failed!
<0>Kernel panic - not syncing: Out of memory


thanks,

marek
-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Marc Kleine-Budde]

[-- Attachment #1.1: Type: text/plain, Size: 2297 bytes --]

On 10/29/2010 10:45 AM, Belisko Marek wrote:
> HI Baruch,
> 
> On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>> Hi Belisko,
>>
>> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>>> I have 2.6.32 kernel but early_printk isn't available and I enable
>>> lowlevel debugging but
>>> don't get nothing else on console. Anyway thanks.
>>
>> Try this patch to see the low level console output:
>>
>> commit 5c31454464ed655401c31c68c895b16eafd2bde5
>> Author: Baruch Siach <baruch@tkos.co.il>
>> Date:   Mon Jan 19 10:41:47 2009 +0200
>>
>>    arm, printk: the famous printascii() hack
>>
>> diff --git a/kernel/printk.c b/kernel/printk.c
>> index 5052b54..d685f8a 100644
>> --- a/kernel/printk.c
>> +++ b/kernel/printk.c
>> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>>        /* Emit the output into the temporary buffer */
>>        printed_len += vscnprintf(printk_buf + printed_len,
>>                                  sizeof(printk_buf) - printed_len, fmt, args);
>> +       {
>> +               extern void printascii(const char *);
>> +               printascii(printk_buf);
>> +       }
>>
>>
>>        /*
>>
>> --
>>                                                     ~. .~   Tk Open Systems
>> =}------------------------------------------------ooO--U--Ooo------------{=
>>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>
> Patch works like charm. Output from my kernel startup:
> 
> <5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
> (Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
> CPU: VIVT data cache, VIVT instruction cache
> Machine: MINI2440
> Memory policy: ECC disabled, Data cache writeback
> <7>On node 0 totalpages: 0
> <1>bootmem alloc of 32768 bytes failed!
> <0>Kernel panic - not syncing: Out of memory

do you have a "MEM=32" on your command line?

Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 10:50 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 10/29/2010 10:45 AM, Belisko Marek wrote:
>> HI Baruch,
>>
>> On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>> Hi Belisko,
>>>
>>> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>>>> I have 2.6.32 kernel but early_printk isn't available and I enable
>>>> lowlevel debugging but
>>>> don't get nothing else on console. Anyway thanks.
>>>
>>> Try this patch to see the low level console output:
>>>
>>> commit 5c31454464ed655401c31c68c895b16eafd2bde5
>>> Author: Baruch Siach <baruch@tkos.co.il>
>>> Date:   Mon Jan 19 10:41:47 2009 +0200
>>>
>>>    arm, printk: the famous printascii() hack
>>>
>>> diff --git a/kernel/printk.c b/kernel/printk.c
>>> index 5052b54..d685f8a 100644
>>> --- a/kernel/printk.c
>>> +++ b/kernel/printk.c
>>> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>>>        /* Emit the output into the temporary buffer */
>>>        printed_len += vscnprintf(printk_buf + printed_len,
>>>                                  sizeof(printk_buf) - printed_len, fmt, args);
>>> +       {
>>> +               extern void printascii(const char *);
>>> +               printascii(printk_buf);
>>> +       }
>>>
>>>
>>>        /*
>>>
>>> --
>>>                                                     ~. .~   Tk Open Systems
>>> =}------------------------------------------------ooO--U--Ooo------------{=
>>>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>>
>> Patch works like charm. Output from my kernel startup:
>>
>> <5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
>> (Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
>> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
>> CPU: VIVT data cache, VIVT instruction cache
>> Machine: MINI2440
>> Memory policy: ECC disabled, Data cache writeback
>> <7>On node 0 totalpages: 0
>> <1>bootmem alloc of 32768 bytes failed!
>> <0>Kernel panic - not syncing: Out of memory
>
> do you have a "MEM=32" on your command line?
Well I add it but same result:
bootz zImage
loaded zImage from zImage with size 2059064
commandline: console=ttySAC0,115200 mem=32
arch_number: 1999
Uncompressing Linux..................................................................................................................................
done, booting the kernel.
<5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
(Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
CPU: VIVT data cache, VIVT instruction cache
Machine: MINI2440
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 0
<1>bootmem alloc of 32768 bytes failed!
<0>Kernel panic - not syncing: Out of memory
>
> Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Marc Kleine-Budde]

[-- Attachment #1.1: Type: text/plain, Size: 2847 bytes --]

On 10/29/2010 11:04 AM, Belisko Marek wrote:
> On Fri, Oct 29, 2010 at 10:50 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> On 10/29/2010 10:45 AM, Belisko Marek wrote:
>>> HI Baruch,
>>>
>>> On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>>> Hi Belisko,
>>>>
>>>> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>>>>> I have 2.6.32 kernel but early_printk isn't available and I enable
>>>>> lowlevel debugging but
>>>>> don't get nothing else on console. Anyway thanks.
>>>>
>>>> Try this patch to see the low level console output:
>>>>
>>>> commit 5c31454464ed655401c31c68c895b16eafd2bde5
>>>> Author: Baruch Siach <baruch@tkos.co.il>
>>>> Date:   Mon Jan 19 10:41:47 2009 +0200
>>>>
>>>>    arm, printk: the famous printascii() hack
>>>>
>>>> diff --git a/kernel/printk.c b/kernel/printk.c
>>>> index 5052b54..d685f8a 100644
>>>> --- a/kernel/printk.c
>>>> +++ b/kernel/printk.c
>>>> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>>>>        /* Emit the output into the temporary buffer */
>>>>        printed_len += vscnprintf(printk_buf + printed_len,
>>>>                                  sizeof(printk_buf) - printed_len, fmt, args);
>>>> +       {
>>>> +               extern void printascii(const char *);
>>>> +               printascii(printk_buf);
>>>> +       }
>>>>
>>>>
>>>>        /*
>>>>
>>>> --
>>>>                                                     ~. .~   Tk Open Systems
>>>> =}------------------------------------------------ooO--U--Ooo------------{=
>>>>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>>>
>>> Patch works like charm. Output from my kernel startup:
>>>
>>> <5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
>>> (Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
>>> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
>>> CPU: VIVT data cache, VIVT instruction cache
>>> Machine: MINI2440
>>> Memory policy: ECC disabled, Data cache writeback
>>> <7>On node 0 totalpages: 0
>>> <1>bootmem alloc of 32768 bytes failed!
>>> <0>Kernel panic - not syncing: Out of memory
>>
>> do you have a "MEM=32" on your command line?
> Well I add it but same result:

BTW: It must be "mem=", in lowercase, but you did this.

What I was meant to ask was, if you forget to add the "M" to "32".
Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
your ATAGs are broken, Linux might not see the whole RAM or any if it.

Cheers, Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 11:12 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 10/29/2010 11:04 AM, Belisko Marek wrote:
>> On Fri, Oct 29, 2010 at 10:50 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>>> On 10/29/2010 10:45 AM, Belisko Marek wrote:
>>>> HI Baruch,
>>>>
>>>> On Fri, Oct 29, 2010 at 10:34 AM, Baruch Siach <baruch@tkos.co.il> wrote:
>>>>> Hi Belisko,
>>>>>
>>>>> On Fri, Oct 29, 2010 at 10:20:46AM +0200, Belisko Marek wrote:
>>>>>> I have 2.6.32 kernel but early_printk isn't available and I enable
>>>>>> lowlevel debugging but
>>>>>> don't get nothing else on console. Anyway thanks.
>>>>>
>>>>> Try this patch to see the low level console output:
>>>>>
>>>>> commit 5c31454464ed655401c31c68c895b16eafd2bde5
>>>>> Author: Baruch Siach <baruch@tkos.co.il>
>>>>> Date:   Mon Jan 19 10:41:47 2009 +0200
>>>>>
>>>>>    arm, printk: the famous printascii() hack
>>>>>
>>>>> diff --git a/kernel/printk.c b/kernel/printk.c
>>>>> index 5052b54..d685f8a 100644
>>>>> --- a/kernel/printk.c
>>>>> +++ b/kernel/printk.c
>>>>> @@ -685,6 +685,10 @@ asmlinkage int vprintk(const char *fmt, va_list args)
>>>>>        /* Emit the output into the temporary buffer */
>>>>>        printed_len += vscnprintf(printk_buf + printed_len,
>>>>>                                  sizeof(printk_buf) - printed_len, fmt, args);
>>>>> +       {
>>>>> +               extern void printascii(const char *);
>>>>> +               printascii(printk_buf);
>>>>> +       }
>>>>>
>>>>>
>>>>>        /*
>>>>>
>>>>> --
>>>>>                                                     ~. .~   Tk Open Systems
>>>>> =}------------------------------------------------ooO--U--Ooo------------{=
>>>>>   - baruch@tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
>>>>>
>>>> Patch works like charm. Output from my kernel startup:
>>>>
>>>> <5>Linux version 2.6.32-rc8 (open-nandra@linux) (gcc version 4.3.5
>>>> (Buildroot 2010.08-rc1) ) #14 Fri Oct 29 10:40:20 CEST 2010
>>>> CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
>>>> CPU: VIVT data cache, VIVT instruction cache
>>>> Machine: MINI2440
>>>> Memory policy: ECC disabled, Data cache writeback
>>>> <7>On node 0 totalpages: 0
>>>> <1>bootmem alloc of 32768 bytes failed!
>>>> <0>Kernel panic - not syncing: Out of memory
>>>
>>> do you have a "MEM=32" on your command line?
>> Well I add it but same result:
>
> BTW: It must be "mem=", in lowercase, but you did this.
>
> What I was meant to ask was, if you forget to add the "M" to "32".
> Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
> your ATAGs are broken, Linux might not see the whole RAM or any if it.
yes it was typo I forgot put M after 32. Kernel now properly boot :).
U-boot somehow
add kernel this parameter? Because for u-boot I don't need to set this
parameter.
>
> Cheers, Marc
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Marc Kleine-Budde]

[-- Attachment #1.1: Type: text/plain, Size: 1074 bytes --]

On 10/29/2010 11:21 AM, Belisko Marek wrote:
>>>> do you have a "MEM=32" on your command line?
>>> Well I add it but same result:
>>
>> BTW: It must be "mem=", in lowercase, but you did this.
>>
>> What I was meant to ask was, if you forget to add the "M" to "32".
>> Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
>> your ATAGs are broken, Linux might not see the whole RAM or any if it.

> yes it was typo I forgot put M after 32. Kernel now properly boot :).

How much RAM you you have? Adjust mem= accordingly.

> U-boot somehow
> add kernel this parameter? Because for u-boot I don't need to set this
> parameter.

Nope - u-boot and barebox set up this information in the ATAG list.
Seems something is broken with your ATAG list.

cheers, Marc

-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Uwe Kleine-König]

On Fri, Oct 29, 2010 at 11:26:14AM +0200, Marc Kleine-Budde wrote:
> On 10/29/2010 11:21 AM, Belisko Marek wrote:
> >>>> do you have a "MEM=32" on your command line?
> >>> Well I add it but same result:
> >>
> >> BTW: It must be "mem=", in lowercase, but you did this.
> >>
> >> What I was meant to ask was, if you forget to add the "M" to "32".
> >> Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
> >> your ATAGs are broken, Linux might not see the whole RAM or any if it.
> 
> > yes it was typo I forgot put M after 32. Kernel now properly boot :).
> 
> How much RAM you you have? Adjust mem= accordingly.
> 
> > U-boot somehow
> > add kernel this parameter? Because for u-boot I don't need to set this
> > parameter.
> 
> Nope - u-boot and barebox set up this information in the ATAG list.
> Seems something is broken with your ATAG list.
It's setup in setup_memory_tags (arch/arm/lib/armlinux.c).  So you
probably need to call armlinux_add_dram.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 11:26 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
> On 10/29/2010 11:21 AM, Belisko Marek wrote:
>>>>> do you have a "MEM=32" on your command line?
>>>> Well I add it but same result:
>>>
>>> BTW: It must be "mem=", in lowercase, but you did this.
>>>
>>> What I was meant to ask was, if you forget to add the "M" to "32".
>>> Because with mem=32 you tell Linux just to use 32 bytes of memory. Maybe
>>> your ATAGs are broken, Linux might not see the whole RAM or any if it.
>
>> yes it was typo I forgot put M after 32. Kernel now properly boot :).
>
> How much RAM you you have? Adjust mem= accordingly.
Have 64M I will adjust.
>
>> U-boot somehow
>> add kernel this parameter? Because for u-boot I don't need to set this
>> parameter.
>
> Nope - u-boot and barebox set up this information in the ATAG list.
> Seems something is broken with your ATAG list.
Could be a problem thats I load barebox directly to ram and run it and
then RAM size isn't probed
and correctly set in atags?
>
> cheers, Marc
>
> --
> Pengutronix e.K.                  | Marc Kleine-Budde           |
> Industrial Linux Solutions        | Phone: +49-231-2826-924     |
> Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |
>
>

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Juergen Beisert]

Belisko Marek wrote:
> On Fri, Oct 29, 2010 at 11:26 AM, Marc Kleine-Budde <mkl@pengutronix.de> 
wrote:
> > On 10/29/2010 11:21 AM, Belisko Marek wrote:
> >>>>> do you have a "MEM=32" on your command line?
> >>>>
> >>>> Well I add it but same result:
> >>>
> >>> BTW: It must be "mem=", in lowercase, but you did this.
> >>>
> >>> What I was meant to ask was, if you forget to add the "M" to "32".
> >>> Because with mem=32 you tell Linux just to use 32 bytes of memory.
> >>> Maybe your ATAGs are broken, Linux might not see the whole RAM or any
> >>> if it.
> >>
> >> yes it was typo I forgot put M after 32. Kernel now properly boot :).
> >
> > How much RAM you you have? Adjust mem= accordingly.
>
> Have 64M I will adjust.
>
> >> U-boot somehow
> >> add kernel this parameter? Because for u-boot I don't need to set this
> >> parameter.
> >
> > Nope - u-boot and barebox set up this information in the ATAG list.
> > Seems something is broken with your ATAG list.
>
> Could be a problem thats I load barebox directly to ram and run it and
> then RAM size isn't probed
> and correctly set in atags?

No, you need something like that:

[...]
static struct memory_platform_data ram_pdata = {
	.name		= "ram0",
	.flags		= DEVFS_RDWR,
};

struct device_d mini_sdram_dev = {
	.id		= -1,
	.name		= "mem",
	.map_base	= CS6_BASE,
	.size		= 64 * 1024 * 1024,
	.platform_data	= &ram_pdata,
};

[...]

static int mini2440_devices_init(void)
{
[...]
	register_device(&mini2440_sdram_dev);
[...]
	armlinux_add_dram(&mini2440_sdram_dev);
[...]
}

jbe

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: command bootu to start kernel

[Belisko Marek]

On Fri, Oct 29, 2010 at 2:36 PM, Juergen Beisert <jbe@pengutronix.de> wrote:
> Belisko Marek wrote:
>> On Fri, Oct 29, 2010 at 11:26 AM, Marc Kleine-Budde <mkl@pengutronix.de>
> wrote:
>> > On 10/29/2010 11:21 AM, Belisko Marek wrote:
>> >>>>> do you have a "MEM=32" on your command line?
>> >>>>
>> >>>> Well I add it but same result:
>> >>>
>> >>> BTW: It must be "mem=", in lowercase, but you did this.
>> >>>
>> >>> What I was meant to ask was, if you forget to add the "M" to "32".
>> >>> Because with mem=32 you tell Linux just to use 32 bytes of memory.
>> >>> Maybe your ATAGs are broken, Linux might not see the whole RAM or any
>> >>> if it.
>> >>
>> >> yes it was typo I forgot put M after 32. Kernel now properly boot :).
>> >
>> > How much RAM you you have? Adjust mem= accordingly.
>>
>> Have 64M I will adjust.
>>
>> >> U-boot somehow
>> >> add kernel this parameter? Because for u-boot I don't need to set this
>> >> parameter.
>> >
>> > Nope - u-boot and barebox set up this information in the ATAG list.
>> > Seems something is broken with your ATAG list.
>>
>> Could be a problem thats I load barebox directly to ram and run it and
>> then RAM size isn't probed
>> and correctly set in atags?
>
> No, you need something like that:
>
> [...]
> static struct memory_platform_data ram_pdata = {
>        .name           = "ram0",
>        .flags          = DEVFS_RDWR,
> };
>
> struct device_d mini_sdram_dev = {
>        .id             = -1,
>        .name           = "mem",
>        .map_base       = CS6_BASE,
>        .size           = 64 * 1024 * 1024,
>        .platform_data  = &ram_pdata,
> };
Suppose similar must be done for a9m24xx boards?
>
> [...]
>
> static int mini2440_devices_init(void)
> {
> [...]
>        register_device(&mini2440_sdram_dev);
> [...]
>        armlinux_add_dram(&mini2440_sdram_dev);
> [...]
> }
>
> jbe
>
> --
> Pengutronix e.K.                              | Juergen Beisert             |
> Linux Solutions for Science and Industry      | Phone: +49-8766-939 228     |
> Vertretung Sued/Muenchen, Germany             | Fax:   +49-5121-206917-5555 |
> Amtsgericht Hildesheim, HRA 2686              | http://www.pengutronix.de/  |
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox