All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i.MX28: Fix VDDIO and VDDA setup
Date: Tue, 31 Jan 2012 13:45:02 +0100	[thread overview]
Message-ID: <201201311345.02661.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAOMZO5B98nSdeq6a5gZP4Risf6S8SEQpdtyE5DyTj862DNe6zQ@mail.gmail.com>

> On 1/30/12, Marek Vasut <marek.vasut@gmail.com> wrote:
> > Note: Guys, please give this a testrun. I think it might fix the issue
> > Robert
> > was observing. I dug into the imx-bootlets and the bootrom X-Files and
> > found this paranormal piece of code. Adding it fixes the boot issue on
> > my crappy board.
> 
> Tried your patch and my mx28evk still hangs after a "reboot" command.
> It reads the scratch registers as 0, report the total RAM size as 0
> and then U-boot hangs.

Right, because RAM size is 0. I see, so DRAM init fails somewhere. I think 
though it doesn't hang in the POWER init code anymore. Can you trace mem_init() 
in the SPL? Simply define CONFIG_SPL_SERIAL_SUPPORT for example and run 
serial_init() before, then run serial_puts() every now and then when fit.

M

> 
> Regards,
> 
> Fabio Estevam

  reply	other threads:[~2012-01-31 12:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  0:00 [U-Boot] [PATCH] i.MX28: Fix VDDIO and VDDA setup Marek Vasut
2012-01-31 10:24 ` Matthias Fuchs
2012-01-31 11:38   ` Marek Vasut
2012-01-31 13:03     ` Matthias Fuchs
2012-01-31 12:26 ` Fabio Estevam
2012-01-31 12:45   ` Marek Vasut [this message]
2012-01-31 17:21     ` Robert Deliën
2012-01-31 18:08       ` Marek Vasut
2012-01-31 18:33       ` Marek Vasut
2012-02-01 16:55         ` Robert Deliën
2012-02-02 15:30         ` Robert Deliën
2012-01-31 15:13   ` Robert Deliën
2012-02-07 17:03 ` Stefano Babic

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=201201311345.02661.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.