command bootu to start kernel

Belisko Marek marek.belisko at gmail.com
Fri Oct 29 03:49:52 EDT 2010


On Fri, Oct 29, 2010 at 8:08 AM, Belisko Marek <marek.belisko at gmail.com> wrote:
> On Wed, Oct 27, 2010 at 4:38 PM, Juergen Beisert <jbe at 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 at 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 at 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



More information about the barebox mailing list