From: Manfred Huber <man.huber@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Beagleboard: SPL hangs on serial init
Date: Wed, 20 Mar 2013 00:52:06 +0100 [thread overview]
Message-ID: <5148FA26.3090703@arcor.de> (raw)
In-Reply-To: <20130319144957.GF25919@bill-the-cat>
On 2013-03-19 15:49, Tom Rini wrote:
> On Sat, Mar 16, 2013 at 02:13:54PM +0100, Manfred Huber wrote:
>
>> I'm surprised that no one is interested in a functioning
>> Beagleboard. Has no one tested the Beagleboard since 2012-09-19?
>
> I don't see this problem on mine (classic and xM), which is probably
> part of the why. I'm inclined to accept the patch, but can you try two
> things please:
> - How reproducible is this problem, with the host and beagleboard
> combination you have? 100%?
> - Do you have another beagleboard or another host PC (or USB-Serial
> dongle) you can try?
>
> Thanks!
>
Thanks for your answer. I have only one Beagleboard Revision C4
(CONTROL_IDCODE of the OMAP3530 is 0x4B7AE02F). My host is a Ubuntu
12.10 (Quantal Quetzal) and I use the gcc-arm-linux-gnueabihf
cross-compiler version 4.7.2-1.
Compiling the actual u-boot leaded to the reported error. All version
since commit cb55b3320014b7f6014416c556fe506efbf0a84b led to the
hanging. All version before boots correctly.
Adding the define to omap3_beagle.h leads to a correct booting for all
versions. Also a reset of the uart at the beginning of the init function
leads to a correct booting. So I exclude that the hardware is defective.
If you can tell me your compiler and version I can try to use your
cross-compiler.
Best regards,
Manfred
next prev parent reply other threads:[~2013-03-19 23:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 13:09 [U-Boot] Beagleboard: SPL hangs on serial init man.huber at arcor.de
2013-03-16 13:13 ` Manfred Huber
2013-03-19 14:49 ` Tom Rini
2013-03-19 23:52 ` Manfred Huber [this message]
2013-03-20 0:05 ` Javier Martinez Canillas
2013-03-20 1:27 ` Tom Rini
2013-03-20 23:09 ` Manfred Huber
2013-03-21 21:08 ` Javier Martinez Canillas
2013-03-23 10:11 ` Manfred Huber
2013-03-21 19:03 ` [U-Boot] [PATCH] omap3_beagle: Enable CONFIG_SYS_NS16550_BROKEN_TEMT Manfred Huber
2013-03-21 21:28 ` Javier Martinez Canillas
2013-03-21 22:21 ` Tom Rini
2013-03-21 22:28 ` Scott Wood
2013-03-25 22:02 ` [U-Boot] [PATCH 1/1 v2] omap3_beagle: Enabling UART3 first allows the Transmitter to be empty Manfred Huber
2013-03-27 4:50 ` Manfred Huber
2013-03-27 9:29 ` Javier Martinez Canillas
2013-03-27 13:57 ` Tom Rini
2013-03-28 5:55 ` Manfred Huber
2013-03-29 8:19 ` Manfred Huber
2013-03-28 15:21 ` Tom Rini
2013-03-27 13:37 ` Andreas Bießmann
2013-03-27 17:22 ` Javier Martinez Canillas
2013-03-28 6:06 ` Manfred Huber
2013-03-28 8:45 ` Andreas Bießmann
2013-03-28 9:11 ` Javier Martinez Canillas
2013-03-28 9:50 ` Andreas Bießmann
2013-03-28 15:21 ` Tom Rini
2013-03-29 8:33 ` Manfred Huber
2013-03-29 9:20 ` [U-Boot] [PATCH 1/1 v3] " Manfred Huber
2013-03-29 9:43 ` Albert ARIBAUD
2013-03-29 12:34 ` Tom Rini
2013-03-29 12:42 ` [U-Boot] [PATCH 1/1 v4] omap3_beagle: Flush UART3 xmit on enable if TEMT is broken Manfred Huber
2013-03-29 12:52 ` [U-Boot] [PATCH 1/1 v5] " Manfred Huber
2013-04-02 7:46 ` Javier Martinez Canillas
2013-04-02 8:59 ` Andreas Bießmann
2013-04-08 16:56 ` [U-Boot] [U-Boot, 1/1, " Tom Rini
2013-04-10 22:12 ` [U-Boot] [PATCH v1 1/1] omap3: Display MHz instead of mHz on the console Manfred Huber
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=5148FA26.3090703@arcor.de \
--to=man.huber@arcor.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox