RE: Barebox on a 3730

RE: Barebox on a 3730

[Cory Walker]

[-- Attachment #1.1: Type: text/plain, Size: 79 bytes --]

Any updates on this? I'd like a copy of the patch so I could test it on my
XM.

[-- Attachment #1.2: Type: text/html, Size: 83 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

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

Re: Barebox on a 3730

[Orjan Friberg]

On 2011-01-04 03:13, Cory Walker wrote:
> Any updates on this? I'd like a copy of the patch so I could test it on
> my XM.

FWIW, I just tried the 2011.02 tag and RAM booting works just fine on my 
3730 board.  (I haven't kept up with the flow of patches though.)

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

Barebox on a 3730

[Orjan Friberg]

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.

Anyone here rambooted a 3730 with barebox?  (Just to rule out that I 
need to do any software changes.)

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.


Thanks,
Orjan

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

Re: Barebox on a 3730

[Orjan Friberg]

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

Re: Barebox on a 3730

[Belisko Marek]

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 ;)
>
> Anyone here rambooted a 3730 with barebox?  (Just to rule out that I need to
> do any software changes.)
>
> 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.
>
>
> Thanks,
> Orjan
>
> --
> Orjan Friberg
> FlatFrog Laboratories AB
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

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

Re: Barebox on a 3730

[Orjan Friberg]

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).

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

RE: Barebox on a 3730

[Premi, Sanjeev]

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

Re: Barebox on a 3730

[Orjan Friberg]

On 2010-12-02 19:34, Premi, Sanjeev wrote:
>> 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

Any specific section you were thinking of?  I did look in the UART 
section of the TRM before and established that it was still driven by a 
48 MHz clock.

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

Re: Barebox on a 3730

[Belisko Marek]

On Fri, Dec 3, 2010 at 8:23 AM, Orjan Friberg <of@flatfrog.com> wrote:
> On 2010-12-02 19:34, Premi, Sanjeev wrote:
>>>
>>> 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
>
> Any specific section you were thinking of?  I did look in the UART section
> of the TRM before and established that it was still driven by a 48 MHz
> clock.
Yes clock for UART is also 48Mhz. I think difference is how to setup main clock
which will be then also used for UART. Just quessing you have latest beagleboard
revision which have 3730?
>
> --
> Orjan Friberg
> FlatFrog Laboratories AB
>

thanks,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
icq: 290551086
web: http://open-nandra.com

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

Re: Barebox on a 3730

[Orjan Friberg]

On 2010-12-03 08:33, Belisko Marek wrote:
> Yes clock for UART is also 48Mhz. I think difference is how to setup main clock
> which will be then also used for UART. Just quessing you have latest beagleboard
> revision which have 3730?

The board I'm trying to RAM boot with barebox is our own design, but I'd 
be happy to try it on a BeagleBoard xM if there's a way (mine is an A2 
revision).

I'll take a look at arch/arm/mach-omap/omap3_clock.c.

Thanks,
Orjan

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

Re: Barebox on a 3730

[Orjan Friberg]

On 2010-12-03 09:08, Orjan Friberg wrote:
> I'll take a look at arch/arm/mach-omap/omap3_clock.c.

Ok, that stuff looks like it's a bit out of my league.  I guess you'd 
need to read the TRM very carefully and/or have a JTAG debugger handy to 
get it right.

Sanjeev, if you're able to make a patch I'd be grateful.

(On a related note, is everyone using MMC for bootstrapping?  I'm 
finding very little related to rambooting the 35x or 37x.)

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

RE: Barebox on a 3730

[Premi, Sanjeev]

 

> -----Original Message-----
> From: Orjan Friberg [mailto:of@flatfrog.com] 
> Sent: Friday, December 03, 2010 2:42 PM
> To: Belisko Marek; Premi, Sanjeev
> Cc: barebox@lists.infradead.org
> Subject: Re: Barebox on a 3730
> 
> On 2010-12-03 09:08, Orjan Friberg wrote:
> > I'll take a look at arch/arm/mach-omap/omap3_clock.c.
> 
> Ok, that stuff looks like it's a bit out of my league.  I guess you'd 
> need to read the TRM very carefully and/or have a JTAG 
> debugger handy to 
> get it right.
> 
> Sanjeev, if you're able to make a patch I'd be grateful.

Just started to refresh the repo. I do hope I can get it done
over this weekend...
Haven't looked at barebox sources for quite long; will give
my best shot...

> 
> (On a related note, is everyone using MMC for bootstrapping?  I'm 
> finding very little related to rambooting the 35x or 37x.)
> 
> -- 
> Orjan Friberg
> FlatFrog Laboratories AB
> 
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

RE: Barebox on a 3730

[Premi, Sanjeev]

> -----Original Message-----
> From: Orjan Friberg [mailto:of@flatfrog.com] 
> Sent: Friday, December 03, 2010 2:42 PM
> To: Belisko Marek; Premi, Sanjeev
> Cc: barebox@lists.infradead.org
> Subject: Re: Barebox on a 3730
> 
> On 2010-12-03 09:08, Orjan Friberg wrote:
> > I'll take a look at arch/arm/mach-omap/omap3_clock.c.
> 
> Ok, that stuff looks like it's a bit out of my league.  I guess you'd 
> need to read the TRM very carefully and/or have a JTAG 
> debugger handy to 
> get it right.
> 
> Sanjeev, if you're able to make a patch I'd be grateful.
> 
Looks like I got into more than I could chew for a weekend!

I found many things missing in the process of creating the
patch; and ended with a big lst of 'dirty' patches. I will
be able to try them on the EVM today; but clean-up can take
another day.

If I can get the board to boot, I can send the patches to
you off-the-list for you to get started while I clean-up;
...if helps you.

~sanjeev

> (On a related note, is everyone using MMC for bootstrapping?  I'm 
> finding very little related to rambooting the 35x or 37x.)
> 
> -- 
> Orjan Friber
> FlatFrog Laboratories AB
> 
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

Re: Barebox on a 3730

[Orjan Friberg]

On 2010-12-06 03:40, Premi, Sanjeev wrote:
> If I can get the board to boot, I can send the patches to
> you off-the-list for you to get started while I clean-up;
> ...if helps you.

Please do, I'd be happy to give it a spin.

Thanks,
Orjan

-- 
Orjan Friberg
FlatFrog Laboratories AB

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

RE: Barebox on a 3730

[Premi, Sanjeev]

Just fixed the issue. give me 30 mins and I will send you zip of patches to apply on latest master.

~sanjeev 

> -----Original Message-----
> From: Orjan Friberg [mailto:of@flatfrog.com] 
> Sent: Monday, December 06, 2010 4:05 PM
> To: Premi, Sanjeev
> Cc: Belisko Marek; barebox@lists.infradead.org
> Subject: Re: Barebox on a 3730
> 
> On 2010-12-06 03:40, Premi, Sanjeev wrote:
> > If I can get the board to boot, I can send the patches to
> > you off-the-list for you to get started while I clean-up;
> > ...if helps you.
> 
> Please do, I'd be happy to give it a spin.
> 
> Thanks,
> Orjan
> 
> -- 
> Orjan Friberg
> FlatFrog Laboratories AB
> 
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

RE: Barebox on a 3730

[Premi, Sanjeev]

_______________________________________
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

Re: Barebox on a 3730

[Orjan Friberg]

On 2010-12-02 17:43, Premi, Sanjeev wrote:
> [sp] How urgent is your need? I could make a patch - but you may have
>        to wait for couple of days.

Well, that would be great.  I'd be happy to help out if I can.

-- 
Orjan Friberg
FlatFrog Laboratories AB

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