From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] devkit8000: MMC/FAT booting problem with SPL
Date: Tue, 29 Nov 2011 19:41:37 +0100 [thread overview]
Message-ID: <4ED52761.3010601@gmail.com> (raw)
In-Reply-To: <4ED512FB.3040206@gmail.com>
On 11/29/2011 06:14 PM, Simon Schwarz wrote:
> On 11/29/2011 05:25 PM, Marek Vasut wrote:
> [SNIP]
>>
>> Stupid question -- isn't some stack corruption / memory corruption
>> going on ?
>>
>> M
>
> Not stupid at all. I don't think it is a stack corruption but IMHO it
> seems that the .bss section is overwritten somehow.
>
> The cur_dev pointer is 0x80000120 for the first sector and 0xe087c004
> before the second one. So either it is changed somewhere or somehow the
> pointer is overwritten by accident.
>
little status-report: The .bss-section is overwritten. Moving it into
the middle of RAM fixes the problem - although this is not a solution it
may help to find the root...
Regards
prev parent reply other threads:[~2011-11-29 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 11:11 [U-Boot] devkit8000: MMC/FAT booting problem with SPL Simon Schwarz
2011-11-29 14:41 ` Tom Rini
2011-11-29 15:11 ` Simon Schwarz
2011-11-29 16:25 ` Marek Vasut
2011-11-29 17:14 ` Simon Schwarz
2011-11-29 18:41 ` Simon Schwarz [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=4ED52761.3010601@gmail.com \
--to=simonschwarzcor@googlemail.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.