mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Rolf Evers-Fischer <embedded24@evers-fischer.de>,
	barebox@lists.infradead.org
Subject: Re: Problems with pyhBoard-Wega-AM335x
Date: Mon, 7 Jul 2014 08:04:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407070803160.7478@localhost> (raw)
In-Reply-To: <20140707120019.GN23235@pengutronix.de>

On Mon, 7 Jul 2014, Sascha Hauer wrote:

> 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:

  from memory, i noticed earlier that when i configured for
am335x_defconfig, then did "make menuconfig", i was asked whether i
wanted to build the MLO file as well. does that mean i can generate
both the MLO and second stage from a single build? or am i
misunderstanding what i saw?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-07-07 12:05 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 [this message]
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
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=alpine.LFD.2.11.1407070803160.7478@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=barebox@lists.infradead.org \
    --cc=embedded24@evers-fischer.de \
    --cc=s.hauer@pengutronix.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