public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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:43:45 +0100	[thread overview]
Message-ID: <4D3EB771.4000008@hrz.tu-chemnitz.de> (raw)
In-Reply-To: <4D3EB35D.4090905@gmail.com>

Dear Andreas Bie?mann,

> please do not hijack a thread!

sorry I didn't want do this. I wanted to give some more information.

> Ok, you use 2010.09. This was last release before relocate changes.
> Therefore it has no connection with the relocation stuff.

yes I. I tried to make a patch for 2010.12 but the uboot don't starts so 
I tried in the first step the version before. It is a similar board to 
the at91rm9200dk. It hangs in the low level_init file. But I have only a 
keil jtag debugger and couldn't debug it. or is there any possibility to 
use it with the gdb?

I found the problem in the board.c of the arm architecture. But can't 
see why. Line 303 is reached but line 312 not. Also line 306 is not 
reached. I don't know why, maybe you can give me a hint?

I think if the problem is found the problem with the at91rm9200dk is 
also found.

>> Is it nessesary to set a
>> console parameter in the bootcmd in uboot version 2010.09?
>
> We don't know your configuration. What tells your working setup in
> kernel log messages about 'Command line'? ->  /proc/cmdline

I only give the MAC and the running image in the cmdline. I think the 
problem must be in the uboot.

>
> What is your board exactly? Is it currently in official u-boot or do you
> have another tree?
> at91rm9200dk is most likely broken with current u-boot (2010.12) and
> will be removed for 2011.03. So if you have a at91rm9200dk at hand
> please try to get the current u-boot working with that board and provide
> patches. You may see my patches for at91rm9200ek which at least make
> at91rm9200ek boot from SDRAM when setup correctly with an jtag (->
> booting with at91bootstrab should also work but is untested).

It isn't in official u-boot tree. You can have a look in the patch.


Best regards / Mit freundlichen Gr??en

Maik H?nig
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-2010.12.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20110125/3b524908/attachment.asc 

  reply	other threads:[~2011-01-25 11:43 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
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 [this message]
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=4D3EB771.4000008@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