[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1805445] Re: QEMU arm virt machine was stopped by STMF
From: |
Peter Maydell |
Subject: |
[Qemu-devel] [Bug 1805445] Re: QEMU arm virt machine was stopped by STMFD command while debug process |
Date: |
Tue, 26 Mar 2019 15:10:57 -0000 |
I think there isn't a QEMU bug to address here, so I'm going to close
this bug. Please let us know if there's anything we've missed.
** Changed in: qemu
Status: New => Invalid
--
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:
Invalid
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1805445] Re: QEMU arm virt machine was stopped by STMFD command while debug process,
Peter Maydell <=