From: zzs <zzs213@126.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] at91rm9200 undef runtime error with eldk 5.0
Date: Wed, 13 Jul 2011 19:20:25 +0800 [thread overview]
Message-ID: <20110713112024.GA20598@greatfirst.com> (raw)
In-Reply-To: <20110713105743.0C2C116F12CE@gemini.denx.de>
In message <20110713105743.0C2C116F12CE@gemini.denx.de> Wolfgang Denk wrote:
>
> > In my preloader some exception vector were setted to print message. So
> > it seems uboot.bin had some illegal asm code in it.
>
> Are you sure that your preloader analyses the binary image it loads
> and that it would detect specific assembler code in it? I tend to
> doubt that.
No, No, No it is impossibe, My preloader just set exception vector and
it jump to the message output code, It print out error message when a
undef instruction exception occurs.
>
>
> > So what compiler options should be use? I notice some u-boot compile
> > commandline has option '-march=armv4'. Why with this option it is still
> > generate wrong code
>
> Thi sis a strong statement, based on somewhat weak facts. Why are you
> so sure that there is any "wrong code" being generated? Please show
> which exact instructions you are talking about.
Because the code raised a 'undef instruction' exception, So I guess some
illegal code for arm920(may be legal for other armVs) exist.
I will try to objbump u-boot and analyses it later.
--
Best Regards,
zzs
next prev parent reply other threads:[~2011-07-13 11:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 6:13 [U-Boot] at91rm9200 undef runtime error with eldk 5.0 zzs
2011-07-13 8:40 ` Wolfgang Denk
2011-07-13 10:46 ` zzs
2011-07-13 10:57 ` Wolfgang Denk
2011-07-13 11:20 ` zzs [this message]
2011-07-15 16:15 ` [U-Boot] eldk5.0 generate illegal instruction for at91rm9200 zzs
2011-07-15 17:22 ` Wolfgang Denk
2011-07-15 18:00 ` Wolfgang Denk
2011-07-16 8:05 ` zzs
2011-07-16 8:30 ` Andreas Bießmann
2011-07-16 8:33 ` Wolfgang Denk
2011-07-16 8:10 ` Albert ARIBAUD
2011-07-16 8:34 ` Wolfgang Denk
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=20110713112024.GA20598@greatfirst.com \
--to=zzs213@126.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.