public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Crash in env_relocate_spec() of env_mmc.c
Date: Fri, 08 Oct 2010 09:53:52 +0200	[thread overview]
Message-ID: <4CAECE10.9070400@denx.de> (raw)
In-Reply-To: <AANLkTinsa4o3ipnZqqY-qLT1Kob2R1K2gBX2gSDKr8tx@mail.gmail.com>

Steve Sakoman wrote:
Hi Steve,

> I've been attempting to get the OMAP4 boards working post the ARM
> relocation changes.
> 
> Panda was simple.  The OMAP4430SDP is proving to be more challenging,
> as it freezes after printing the DRAM size message.
> 
> Adding a few printfs revealed that the crash occurs in env_mmc.c's
> env_relocate_spec() routine.
> 
> Has anyone else run into this issue?  Any advice?

I tested, I can see the same issue. The main problem is that
mmc_initialize is not called before mmc_init() in arch/arm/lib/board.c
if relocation is active. In start_armboot it is called before.

The second problem I see is that env_relocate_spec should call
env_import() as already done by other environment (I checked with env_nand).

I can send a patch that at least on my target solves the problem. Could
you test it ?

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2010-10-08  7:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08  3:45 [U-Boot] Crash in env_relocate_spec() of env_mmc.c Steve Sakoman
2010-10-08  7:53 ` Stefano Babic [this message]
2010-10-08 13:32   ` Steve Sakoman

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=4CAECE10.9070400@denx.de \
    --to=sbabic@denx.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