From: David Gaydou <dgaydou@gmail.com>
To: sid@sources.redhat.com
Subject: msr instruction dont change cpsr bits
Date: Thu, 26 Feb 2009 21:54:00 -0000 [thread overview]
Message-ID: <loom.20090226T190729-528@post.gmane.org> (raw)
Hi,
i've just discover this fantastic tool and i'm playing around with it to lern a
bit.
I've started with
configrun-sid --cpu=arm --gdb=2004 -EL --save-temps --no-run control.elf
where control.elf was built using arm-elf-gcc and tested with arm-elf-gdb
target=sim. When i simulate on sid, gdb i r show that the instruction msr dont
change the bits on cpsr register:
.
.
.
r11 0x0 0
r12 0x0 0
sp 0x0 0
lr 0x0 0
pc 0x60 96
fps 0x0 0
cpsr 0xd3 211
(gdb) s
stacks_init () at head.s:78
78 msr CPSR_c, #FIQ_MODE|IRQ_DISABLE|FIQ_DISABLE
(gdb) i r
r0 0x40004000 1073758208
r1 0xaa 170
r2 0x55 85
r3 0x3 3
r4 0x0 0
r5 0x0 0
r6 0x0 0
r7 0x0 0
r8 0x0 0
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x0 0
sp 0x0 0
lr 0x0 0
pc 0x64 100
fps 0x0 0
cpsr 0xd3 211
(gdb)
The value of cpsr after msr instruction should be 0xd1 (arm-elf-gdb, target=sim
confirm this).
Apart from this, the rest of the instructions seem to be excecuted correctly.
Is there any solution for this problem, what im doing wrong?
Thanks for your help!
reply other threads:[~2009-02-26 21:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=loom.20090226T190729-528@post.gmane.org \
--to=dgaydou@gmail.com \
--cc=sid@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).