[PATCH] omap3 towards thumb2 support

Premi, Sanjeev premi at ti.com
Tue Jan 17 06:14:31 EST 2012


 

> -----Original Message-----
> From: barebox-bounces at lists.infradead.org 
> [mailto:barebox-bounces at lists.infradead.org] On Behalf Of 
> Premi, Sanjeev
> Sent: Monday, January 16, 2012 9:47 PM
> To: Sascha Hauer
> Cc: barebox at lists.infradead.org
> Subject: RE: [PATCH] omap3 towards thumb2 support
> 
> (responding via webmail. Won't be able to quote properly)
> ________________________________________
> From: Sascha Hauer [s.hauer at pengutronix.de]
> Sent: Monday, January 16, 2012 9:16 PM
> To: Premi, Sanjeev
> Cc: barebox at lists.infradead.org
> Subject: Re: [PATCH] omap3 towards thumb2 support
> 
> On Mon, Jan 16, 2012 at 12:42:36PM +0000, Premi, Sanjeev wrote:
> >
> > > -----Original Message-----
> > > From: barebox-bounces at lists.infradead.org
> > > [mailto:barebox-bounces at lists.infradead.org] On Behalf Of
> > > Premi, Sanjeev
> > > Sent: Monday, January 16, 2012 5:32 PM
> > > To: Sascha Hauer
> > > Cc: barebox at lists.infradead.org
> > > Subject: RE: [PATCH] omap3 towards thumb2 support
> > >
> >
> > [snip]
> >
> > > > >
> > > > > I was able to pull in your branch and encountered a minor
> > > > > issue - fixed by the patch at end of this mail.
> > > > >
> > > > > How can I enable thumb2? Didn't find aything obvious in
> > > > > omap3530_beagle_xload_defconfig.
> > > >
> > > > Did you merge the work/thumb2 branch into your branch? Then
> > > you should
> > > > find THUMB2_BAREBOX in menuconfig.
> > >
> > > Found it. I was searching in a "cached" version of the 
> file already
> > > in my editor. Will try immediately.
> > >
> >
> > I discarded the patches that I had manually merged last week and
> > pulled work/thumb2 instead.
> >
> > The size of MLO dropped from 47604 to 35052 bytes. However, 
> it didn't
> > boot successfully on the board. The MLO generated after removing
> > CONFIG_THUMB2_BAREBOX came up fine.
> 
> Please check that CONFIG_STACK_BASE really is 0x4020F000. It 
> may be set
> differently if you started from an older config.
> 
> [sp} Already did this.
> 
> Also, the resulting binary should also be startable as a second stage
> loader in which case you might get some stack trace if you 
> have enabled
> this in the first stage.
> 
> [sp] Okay, this could be the issue. I was always building as 
> first stage
>      bootloader only - as i was looking for the banner to appear.
> 
>      Will try using emulator tomorrow to debug further.
> 
> >
> > BTW, I while merging this patch, I saw a warning that could be fixed
> > before merging the patch into master.
> >   8917ac1 : Applying: ARM: move exception vectors away from 
> start of binary
> >
> > /home/premi/barebox/.git/rebase-apply/patch:236: new blank 
> line at EOF.
> > +
> > warning: 1 line adds whitespace errors.
> 
> Ok, will fix.
> 
> I attached my binary MLO file. Could you check if it works for you? I
> just checked this binary and it comes up with:
> 
> [sp] I will try tomorrow morning.

Sascha,
  Your MLO boots fine. But I couldn't make repeat success on either
  beagle or the omap3evem on my side.

  Each time there is an exception on entry of setup_auxcr() on both
  boards. See attached image.

  I noticed that the size of the generated MLO for beagle were different
  for us - 35224(yours) vs. 35572(mine).

  I am building with CodeSourcery 2011.03-41.

~sanjeev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: barebox_err.jpg
Type: image/jpeg
Size: 140279 bytes
Desc: barebox_err.jpg
URL: <http://lists.infradead.org/pipermail/barebox/attachments/20120117/0b5b2ff0/attachment-0001.jpg>


More information about the barebox mailing list