public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] bav335x support broken
Date: Tue, 17 Mar 2015 09:56:17 +0100	[thread overview]
Message-ID: <20150317095617.31dd4707@lilith> (raw)
In-Reply-To: <27EA6637-5F8E-42F2-A9C4-CA43A5CFCF1D@gigadevices.com>

Hello Gilles,

On Tue, 17 Mar 2015 01:09:04 -0700, Gilles <gilles@gigadevices.com>
wrote:
> Hi Anish,
> 
> Yes, actually my board support is based on an older sitara patch and it works when applied to v2015.01. But I was mistaken about the problem.
> I went back to my original patch applied to v2015.01 and it gives the same error but then moves on to SPL and boots ok.
> 
> http://pastebin.com/A23qKkj8
> 
> So I guess it's safe to say that the "fat" error is not the problem. The problem when I compile a74ef40a471d9d4bffb36a8c89744cf6fd631e6f is that it restarts over and over.
> 
> http://pastebin.com/wvjx4mB8

This is typically caused by the u-boot image being corrupt, or
corrupting the SPL somehow, frequently because some memory is being
mapped by both for conflicting uses. Check memory mappings for SPL and
U-Boot including stack, BSS and malloc area locations.

> Do you have any suggestions how how to find the cause of the constant restart? I actually don't have a debugger for this hardware :-(

What you can do is enable debugging (define DEBUG macro) globally,
rebuild SPL and look at the console output. You can also add your own
debug() or printf() calls to track which parts of your code get run and
which ones don't.

> Cheers,
> Gilles

Amicalement,
-- 
Albert.

      reply	other threads:[~2015-03-17  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14  5:06 [U-Boot] bav335x support broken Gilles
2015-03-14 17:55 ` Anish Khurana
2015-03-14 21:47   ` Albert ARIBAUD
2015-03-16  6:32   ` Gilles
2015-03-16 16:14     ` Anish Khurana
2015-03-17  8:09       ` Gilles
2015-03-17  8:56         ` Albert ARIBAUD [this message]

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=20150317095617.31dd4707@lilith \
    --to=albert.u.boot@aribaud.net \
    --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