mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Premi, Sanjeev" <premi@ti.com>
To: Orjan Friberg <of@flatfrog.com>, Belisko Marek <marek.belisko@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: Barebox on a 3730
Date: Fri, 3 Dec 2010 00:04:59 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB5930247B9A457@dbde02.ent.ti.com> (raw)
In-Reply-To: <4CF7CBD0.7080609@flatfrog.com>

> -----Original Message-----
> From: barebox-bounces@lists.infradead.org 
> [mailto:barebox-bounces@lists.infradead.org] On Behalf Of 
> Orjan Friberg
> Sent: Thursday, December 02, 2010 10:10 PM
> To: Belisko Marek
> Cc: barebox@lists.infradead.org
> Subject: Re: Barebox on a 3730
> 
> On 2010-12-02 16:13, Belisko Marek wrote:
> > 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 ;)
> 
> Clocking looks like it should be the same but just out of curiosity, 
> what issue did you have with the clock setup?  (What was bad, 
> how did it 
> manifest itself.)
> 
> I haven't found any 3530 vs. 3730 diffs in the uart configuration in 
> u-boot or linux (though there is a silicon errata fix in the latest 
> linux-omap-2.6 kernel related to not reading from an empty FIFO).
> 
Look for the AM37x TRM here:
http://focus.ti.com/docs/prod/folders/print/am3715.html

> But then again, they could potentially both be relying on the first 
> stage bootloader setting things upp correctly (and then not 
> touching it).
> 
> 
> Thanks,
> Orjan
> 
> -- 
> Orjan Friberg
> FlatFrog Laboratories AB
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2010-12-02 18:35 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 [this message]
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
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=B85A65D85D7EB246BE421B3FB0FBB5930247B9A457@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