From: Frede Florian <florian.frede@ma-info.de>
To: Rolf Evers-Fischer <embedded24@evers-fischer.de>,
Teresa Gamez <t.gamez@phytec.de>
Cc: barebox@lists.infradead.org
Subject: Re: Problems with pyhBoard-Wega-AM335x
Date: Wed, 09 Jul 2014 14:32:09 +0200 [thread overview]
Message-ID: <53BD3649.6040408@ma-info.de> (raw)
In-Reply-To: <alpine.DEB.2.10.1407090838160.10300@9VTHT2J-D520>
Hello Rolf,
after I apply the Patch from Teresa I got the ">".
Yes the last barebox worked. Yesterday I configured the new barebox in
the same way as the old one and got the ">" the size of my image is only
93260 bytes so it should work but it do not work. So I will spend no
more time with the phyWega and wait for the phyCore Kit and start there
my next try.
Thanks for your helping
Florian
Am 09.07.2014 08:47, schrieb Rolf Evers-Fischer:
> Hello Florian,
>
> On Tue, 8 Jul 2014, Teresa Gamez wrote:
>
>> Hello Florian,
>>
>> I guess you having the default kit WEGA, which does have 256MB RAM. The mainline supported
>> phyCORE Kit does have 512MB. Thats probably why it does not start up.
>>
>> I'll have a look at it.
>>
>> Teresa
>>
> I'm not 100% sure, but I can imagine that the ">" should also appear when
> the SDRAM configuration is not correct. But nevertheless the correct
> SDRAM setting is important. Maybe, you can check the SDRAM setting of your
> previous barebox-2013.11. I assume, the old barebox was running properly,
> wasn't it?
>
>>> Sorry but I have no idea which information I can send you to help me
>>> with my problem...
>>>
> Florian, could you please check the size of your 1st stage bootloader
> (MLO) binary?
> It must not exceed 111616 byte! Otherwise it will not boot.
> You can shrink the size by removing all unnecessary stuff from the
> barebox_mlo configuration.
>
> Best regards,
> Rolf
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-07-09 12:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:26 Problems with pyhBoard-Wega-AM335x Rolf Evers-Fischer
[not found] ` <53BA5442.6020708@ma-info.de>
2014-07-07 8:04 ` Frede Florian
2014-07-07 10:05 ` Rolf Evers-Fischer
2014-07-07 11:14 ` Frede Florian
2014-07-07 12:00 ` Sascha Hauer
2014-07-07 12:04 ` Robert P. J. Day
2014-07-07 12:16 ` Sascha Hauer
2014-07-07 12:29 ` Rolf Evers-Fischer
2014-07-08 9:29 ` Frede Florian
2014-07-08 10:01 ` Teresa Gamez
2014-07-09 6:47 ` Rolf Evers-Fischer
2014-07-09 12:32 ` Frede Florian [this message]
2014-07-21 9:34 ` Frede Florian
2014-07-22 7:20 ` Holger Schurig
-- strict thread matches above, loose matches on Subject: below --
2014-07-04 10:12 Frede Florian
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=53BD3649.6040408@ma-info.de \
--to=florian.frede@ma-info.de \
--cc=barebox@lists.infradead.org \
--cc=embedded24@evers-fischer.de \
--cc=t.gamez@phytec.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.