From: Orjan Friberg <of@flatfrog.com>
To: barebox@lists.infradead.org
Subject: Re: Barebox on a 3730
Date: Thu, 2 Dec 2010 16:06:43 +0100 [thread overview]
Message-ID: <4CF7B603.6090407@flatfrog.com> (raw)
In-Reply-To: <4CF7AB25.3010604@flatfrog.com>
On 2010-12-02 15:20, Orjan Friberg wrote:
> Anyone here rambooted a 3730 with barebox? (Just to rule out that I
> need to do any software changes.)
I do have an BeagleBoard xM but it seems the user button doesn't affect
the boot sequence like it did on the original BeagleBoard, so I don't
have any other hardware to try this on.
> When setting the board in boot mode "60" is printed on the serial port
... with "60" being "\x36\x30" in printable characters. I did a hexdump
of the garbled output and its basically a lot of 0xc0 with 0x00
sprinkled in between.
I'd appreciate any clue as to what's happening.
Thanks,
Orjan
--
Orjan Friberg
FlatFrog Laboratories AB
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-12-02 15:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 14:20 Barebox on a 3730 Orjan Friberg
2010-12-02 15:06 ` Orjan Friberg [this message]
2010-12-02 15:13 ` Belisko Marek
2010-12-02 16:39 ` Orjan Friberg
2010-12-02 18:34 ` Premi, Sanjeev
2010-12-03 7:23 ` Orjan Friberg
2010-12-03 7:33 ` Belisko Marek
2010-12-03 8:08 ` Orjan Friberg
2010-12-03 9:11 ` Orjan Friberg
2010-12-03 12:30 ` Premi, Sanjeev
2010-12-06 2:40 ` Premi, Sanjeev
2010-12-06 10:34 ` Orjan Friberg
2010-12-06 13:35 ` Premi, Sanjeev
2010-12-02 16:43 ` Premi, Sanjeev
2010-12-02 17:19 ` Orjan Friberg
-- strict thread matches above, loose matches on Subject: below --
2011-01-04 2:13 Cory Walker
2011-03-01 13:17 ` Orjan Friberg
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=4CF7B603.6090407@flatfrog.com \
--to=of@flatfrog.com \
--cc=barebox@lists.infradead.org \
/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.