From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: florian.frede@ma-info.de
Cc: barebox@lists.infradead.org
Subject: Re: Problems with pyhBoard-Wega-AM335x
Date: Mon, 7 Jul 2014 14:29:21 +0200 (CEST) [thread overview]
Message-ID: <899032957.1340888.1404736162014.open-xchange@oxbsltgw04.schlund.de> (raw)
In-Reply-To: <20140707120019.GN23235@pengutronix.de>
Hello Florian,
> Sascha Hauer <s.hauer@pengutronix.de> hat am 7. Juli 2014 um 14:00
> geschrieben:
>
>
> On Mon, Jul 07, 2014 at 01:14:35PM +0200, Frede Florian wrote:
> > Hello Rolf,
> >
> > thank you very much...
> > after I selected the mentioned entry in the menu the problem was solved...
> > but the board do not prompt any thing on the UART1... so I do not
> > know if barebox is loaded
>
> When using mainline barebox please build the am335x_mlo_defconfig for
> the MLO and the am335x_defconfig for the main binary. The images
> are then found under:
>
> images/barebox-am33xx-phytec-phycore-mlo.img
> images/barebox-am33xx-phytec-phycore.img
>
> I diffed you config against the mainline config and the following
> options are really crucial to let the binary work correctly:
>
> -CONFIG_TEXT_BASE=0x0
> -CONFIG_MALLOC_SIZE=0x0
> -CONFIG_MALLOC_TLSF=y
> -CONFIG_RELOCATABLE=y
> +CONFIG_TEXT_BASE=0x402F0400
> +CONFIG_STACK_SIZE=0x1600
> +CONFIG_MALLOC_SIZE=0x1000000
>
in fact, these settings are essential.
If you still can't see anything, you can also enable the config item "Debugging"
-> "low level debug messages". With this option enabled, you should at least see
a '>' on UART1 right after power-on. This character will be output at the end of
function pcm051_board_init().
If you like to debug the further startup, you could also enable the "Debugging"
-> "Trace initcalls" option in barebox_mlo config.
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-07 12:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 13:26 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 [this message]
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
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=899032957.1340888.1404736162014.open-xchange@oxbsltgw04.schlund.de \
--to=embedded24@evers-fischer.de \
--cc=barebox@lists.infradead.org \
--cc=florian.frede@ma-info.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