From: "Premi, Sanjeev" <premi@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>, Orjan Friberg <of@flatfrog.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: Barebox on a 3730
Date: Thu, 2 Dec 2010 22:13:09 +0530 [thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB5930247466DBA@dbde02.ent.ti.com> (raw)
In-Reply-To: <AANLkTimHbFqqTZ3_oqWCTg+dYHuKA2jHqWCymmy++qTO@mail.gmail.com>
_______________________________________
From: barebox-bounces@lists.infradead.org [barebox-bounces@lists.infradead.org] On Behalf Of Belisko Marek [marek.belisko@gmail.com]
Sent: Thursday, December 02, 2010 8:43 PM
To: Orjan Friberg
Cc: barebox@lists.infradead.org
Subject: Re: Barebox on a 3730
Hi,
On Thu, Dec 2, 2010 at 3:20 PM, Orjan Friberg <of@flatfrog.com> wrote:
> Hi,
>
> We have successfully used Barebox as bootloader on one of our own boards
> with an OMAP 3530. Same board, but with a 3730 instead (and a few auxiliary
> components changed) I'm getting completely garbled output on the serial
> port. I tried changing the baud rate from 115200 to 38400 and 19200 to no
> avail.
Not have omap3530 or other but have same issue with different board type.
Problem was with clock setup for serial. Just an idea check if clock is correct
according data sheet. Maybe 37xx differs from 35xx ;)
[sp] Yes. There is a difference between the 35x and 37x clock settings.
>
> Anyone here rambooted a 3730 with barebox? (Just to rule out that I need to
> do any software changes.)
[sp] If the support does exist yet - changes are necessary.
[sp] How urgent is your need? I could make a patch - but you may have
to wait for couple of days.
>
> When setting the board in boot mode "60" is printed on the serial port by
> the boot ROM, the same way "40W" was printed by the 3530 so it's not like
> the serial port isn't working at all. I can bootstrap via either USB or
> serial port. We're using the omap3530_beagle_per_uart_defconfig.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-12-02 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 14:20 Orjan Friberg
2010-12-02 15:06 ` Orjan Friberg
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 [this message]
2010-12-02 17:19 ` Orjan Friberg
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=B85A65D85D7EB246BE421B3FB0FBB5930247466DBA@dbde02.ent.ti.com \
--to=premi@ti.com \
--cc=barebox@lists.infradead.org \
--cc=marek.belisko@gmail.com \
--cc=of@flatfrog.com \
/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