From: "Maik Hänig" <maik.haenig@s2000.tu-chemnitz.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Uboot can't start kernel after change from version 2009.01 to 2010.09
Date: Tue, 25 Jan 2011 12:03:53 +0100 [thread overview]
Message-ID: <4D3EAE19.4050007@hrz.tu-chemnitz.de> (raw)
In-Reply-To: <4D3EABE1.4030605@emk-elektronik.de>
Dear Reinhard,
sorry I copied the wrong log:
U-Boot 2010.09 (Jan 24 2011 - 17:45:54)
I2C: ready
DRAM: 64 MiB
Flash: 32 MiB
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
## Booting kernel from Legacy Image at 30060000 ...
Image Name: Linux Kernel
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 1084127 Bytes = 1 MiB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Starting kernel ...
I have to kernel Images in flash. The bootcmd is copied from printenv.
With the uboot version 2009.01 it works well. Is it nessesary to set a
console parameter in the bootcmd in uboot version 2010.09?
Mit freundlichen Gr??en
Maik H?nig
Am 25.01.2011 11:54, schrieb Reinhard Meyer:
> Dear Maik H?nig,
>> Hi,
>>
>>
>> I change my uboot version and after it the uboot don't starts the same
>> linux kernel:
>>
>> ## Booting kernel from Legacy Image at 10060000 ...
> _________________________________________????????
>> Image Name: Linux Kernel
>> Image Type: ARM Linux Kernel Image (gzip compressed)
>> Data Size: 1178673 Bytes = 1.1 MiB
>> Load Address: 20008000
>> Entry Point: 20008000
>> Verifying Checksum ... OK
>> Uncompressing Kernel Image ... OK
>>
>> Starting kernel ...
>>
>> *****LOG END*****
>>
>>
>> It's a board simular to the at91rm9200dk. I start the kernel with
>>
>> bootcmd2=setenv bootargs root=/dev/mtdblock9 rootfstype=squashfs
>> ETHADDR=$(ethaddr) RUNNING=$(runningimage) CFGFS=mtdblock10;bootm 0x30060000
> ______________________________________________________________________????????
>>
>> run bootcmd2
>
> First, I don't understand why those two addresses are not the same.
>
> Then, are you sure your "bootcmd2" ist really what you think it is?
> Try a "printenv" and see whats really there.
>
> Should you not have a "console=xxx" in your kernel parameters?
>
> Besides once "Starting kernel ..." shows, u-boot is about to give control
> to the kernel, all future output would be from the kernel itself, probably
> needing a sane "console=xxx" parameter.
>
> Best Regards,
> Reinhard
>
>
next prev parent reply other threads:[~2011-01-25 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 8:53 [U-Boot] Default base for numbers Alexander Holler
2011-01-25 9:16 ` Wolfgang Denk
2011-01-25 9:38 ` Alexander Holler
2011-01-25 10:13 ` [U-Boot] Uboot can't start kernel after change from version 2009.01 to 2010.09 Maik Hänig
2011-01-25 10:54 ` Reinhard Meyer
2011-01-25 11:03 ` Maik Hänig [this message]
2011-01-25 11:18 ` Maik Hänig
2011-01-25 11:29 ` Andreas Bießmann
2011-01-25 11:36 ` Maik Hänig
2011-01-25 13:04 ` Maik Hänig
2011-01-25 11:26 ` Andreas Bießmann
2011-01-25 11:43 ` Maik Hänig
2011-01-25 10:19 ` Maik Hänig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3EAE19.4050007@hrz.tu-chemnitz.de \
--to=maik.haenig@s2000.tu-chemnitz.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox