From: Igor <generalrot@rambler.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1805445] Re: QEMU arm virt machine was stopped by STMFD command while debug process
Date: Tue, 27 Nov 2018 22:25:05 -0000 [thread overview]
Message-ID: <154335750647.32501.16309260409919023970.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 154332864629.32687.7125797278920412825.malonedeb@wampee.canonical.com
** Description changed:
Hello, i have a big problem with QEMU arm virtual machine. So...
I run QEMU machine with bare-metal ThreadX fullflash from Texet TM-333 phone (Spreadtrum platform)
[CODE]qemu-system-arm -S -gdb tcp::1234,ipv4 -drive file=C:\cygwin64\home\flash.bin,if=mtd,format=raw -M palmetto-bmc -cpu arm926 -m 64M[/CODE]
I use palmetto-bmc platform because it have ARM926EJ-S core and support SPI Flash.
Then, i attach to gdb qemu process from IDA and run code step-by-step.
- [IMG]https://pp.userapi.com/c847218/v847218546/13ec1c/iSIcre5-js4.jpg[/IMG]
+
When the IDA run 00032534 STR R11, [R10] command
- [IMG]https://pp.userapi.com/c846416/v846416708/133f60/GQzxORvf4Tg.jpg[/IMG]
+
instead of store R11 on R10 adress, it jump 000328DC STMFD SP!, {R0-R12,LR} instruction...
- [IMG]https://pp.userapi.com/c847218/v847218546/13ec26/32A0VcaJywg.jpg[/IMG]
- and virt machine not execute new instruction...
+
+ and virt machine not execute new instruction...
[IMG]https://pp.userapi.com/c850624/v850624111/528f3/N7FTpgloWVU.jpg[/IMG]
and why i did not change flash from n25q256a to n25q032a11 in aspeed.c
without rebuild qemu?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805445
Title:
QEMU arm virt machine was stopped by STMFD command while debug process
Status in QEMU:
New
Bug description:
Hello, i have a big problem with QEMU arm virtual machine. So...
I run QEMU machine with bare-metal ThreadX fullflash from Texet TM-333 phone (Spreadtrum platform)
[CODE]qemu-system-arm -S -gdb tcp::1234,ipv4 -drive file=C:\cygwin64\home\flash.bin,if=mtd,format=raw -M palmetto-bmc -cpu arm926 -m 64M[/CODE]
I use palmetto-bmc platform because it have ARM926EJ-S core and support SPI Flash.
Then, i attach to gdb qemu process from IDA and run code step-by-step.
When the IDA run 00032534 STR R11, [R10] command
instead of store R11 on R10 adress, it jump 000328DC STMFD SP!, {R0-R12,LR} instruction...
and virt machine not execute new instruction...
[IMG]https://pp.userapi.com/c850624/v850624111/528f3/N7FTpgloWVU.jpg[/IMG]
and why i did not change flash from n25q256a to n25q032a11 in aspeed.c
without rebuild qemu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1805445/+subscriptions
next prev parent reply other threads:[~2018-11-27 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 14:24 [Qemu-devel] [Bug 1805445] [NEW] QEMU arm virt machine was stopped by STMFD command while debug process Igor
2018-11-27 16:29 ` [Qemu-devel] [Bug 1805445] " Peter Maydell
2018-11-27 16:32 ` Peter Maydell
2018-11-27 18:26 ` Igor
2018-11-27 20:54 ` Peter Maydell
2018-11-27 21:45 ` Igor
2018-11-27 22:25 ` Igor [this message]
2018-11-28 0:01 ` Peter Maydell
2018-11-28 17:02 ` Igor
2018-11-28 21:53 ` Igor
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=154335750647.32501.16309260409919023970.launchpad@wampee.canonical.com \
--to=generalrot@rambler.ru \
--cc=1805445@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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.