From: Angelo Dureghello <angelo70@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] toolchain for u-boot
Date: Sat, 30 Jul 2011 13:47:13 +0200 [thread overview]
Message-ID: <4E33EF41.9030804@gmail.com> (raw)
In-Reply-To: <20110730110531.GO6256@leila.ping.de>
On 30/07/2011 13:05, Wolfgang Wegner wrote:
> Hi Angelo,
>
> On Sat, Jul 30, 2011 at 11:06:56AM +0200, Angelo Dureghello wrote:
>> hi all,
>>
>> i have some issues with an mcf5307 (coldfire, see my previous post of 38 Jul).
>>
>> I am now suspecting of some differences in the toolchain.
>>
>> Is there a specific gcc toolchain (or gcc version) required to build u-boot ?
>
> I had good results using CodeSourcery Light (don't remember the exact version,
> something from 2009) for MCF5373 and MCF54455 in early 2010.
>
> Unfortunately I am currently not working on it any more.
>
> Best regards,
> Wolfgang
>
many thanks,
i have a very strange issue:
on a timer interupt i ger a vector 3 error:
_int_handler:
// commeneted all, only rte left, exception in rte
rte
*** Unexpected exception ***
Vector Number: 3 Format: 04 Fault Status: 4
PC: 00fe910a SR: 00002000 SP: 00ed8af0
D0: 00002c1b D1: 0000001b D2: 00400000 D3: 00ee8b76
D4: ffc12d08 D5: ffffffff D6: 00ffad57 D7: 00ee8b76
A0: 00ee8b76 A1: 00fe9604 A2: 00ee8bc6 A3: 00ffd400
A4: 00ff8167 A5: 00ffbb00 A6: 00ed8b48
there is nothing inside the interrupt handler, so there would be apparently any reason to get the exception on "rte", so my only suspect is about toolchain/compiler.
every help is welcome
Reagards,
angelo
next prev parent reply other threads:[~2011-07-30 11:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 9:06 [U-Boot] toolchain for u-boot Angelo Dureghello
2011-07-30 11:05 ` Wolfgang Wegner
2011-07-30 11:47 ` Angelo Dureghello [this message]
2011-07-30 14:49 ` Angelo Dureghello
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=4E33EF41.9030804@gmail.com \
--to=angelo70@gmail.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.