From: "Premi, Sanjeev" <premi@ti.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: [PATCH] omap3 towards thumb2 support
Date: Tue, 17 Jan 2012 11:14:31 +0000 [thread overview]
Message-ID: <E28AAFD00EFAA646AE3DF9B89CD24A89317FCED7@DBDE01.ent.ti.com> (raw)
In-Reply-To: <E28AAFD00EFAA646AE3DF9B89CD24A89317FB2B7@DBDE01.ent.ti.com>
[-- Attachment #1: Type: text/plain, Size: 3403 bytes --]
> -----Original Message-----
> From: barebox-bounces@lists.infradead.org
> [mailto:barebox-bounces@lists.infradead.org] On Behalf Of
> Premi, Sanjeev
> Sent: Monday, January 16, 2012 9:47 PM
> To: Sascha Hauer
> Cc: barebox@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@pengutronix.de]
> Sent: Monday, January 16, 2012 9:16 PM
> To: Premi, Sanjeev
> Cc: barebox@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@lists.infradead.org
> > > [mailto:barebox-bounces@lists.infradead.org] On Behalf Of
> > > Premi, Sanjeev
> > > Sent: Monday, January 16, 2012 5:32 PM
> > > To: Sascha Hauer
> > > Cc: barebox@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
[-- Attachment #2: barebox_err.jpg --]
[-- Type: image/jpeg, Size: 140279 bytes --]
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-01-17 11:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 10:18 Sascha Hauer
2012-01-16 10:18 ` [PATCH 01/10] ARM omap3: remove OMAP3_COPY_CLOCK_SRAM Sascha Hauer
2012-01-16 10:18 ` [PATCH 02/10] ARM omap3 beagle xload: Move stack to SRAM Sascha Hauer
2012-01-16 10:18 ` [PATCH 03/10] ARM omap3: move board_init to pure_initcall Sascha Hauer
2012-01-16 10:18 ` [PATCH 04/10] ARM omap3: call a_init from board code Sascha Hauer
2012-01-16 10:18 ` [PATCH 05/10] ARM omap3 clock: move pll tables to C code Sascha Hauer
2012-01-16 10:18 ` [PATCH 06/10] ARM omap3: remove vector setup from lowlevel code Sascha Hauer
2012-01-16 10:18 ` [PATCH 07/10] ARM omap3: reimplement setup_auxcr in pure asm Sascha Hauer
2012-01-16 10:18 ` [PATCH 08/10] ARM cache-armv7: Add additional ISB Sascha Hauer
2012-01-16 10:18 ` [PATCH 09/10] mtd omap nand: fix driver without CONFIG_PARAMETER Sascha Hauer
2012-01-16 10:34 ` Sascha Hauer
2012-01-16 10:18 ` [PATCH 10/10] ARM omap3: make omap3_core.S thumb safe Sascha Hauer
2012-01-16 11:30 ` [PATCH] omap3 towards thumb2 support Premi, Sanjeev
2012-01-16 11:52 ` Sascha Hauer
2012-01-16 12:01 ` Premi, Sanjeev
2012-01-16 12:42 ` Premi, Sanjeev
2012-01-16 15:46 ` Sascha Hauer
2012-01-16 16:16 ` Premi, Sanjeev
2012-01-17 11:14 ` Premi, Sanjeev [this message]
2012-01-17 12:12 ` Sascha Hauer
2012-01-17 12:24 ` Premi, Sanjeev
2012-01-17 13:10 ` Sascha Hauer
2012-01-17 13:20 ` Premi, Sanjeev
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=E28AAFD00EFAA646AE3DF9B89CD24A89317FCED7@DBDE01.ent.ti.com \
--to=premi@ti.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.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