As a more general note, you can't expect to be able to run a flash image from one Arm system (your phone) on a different Arm system. All Arm boards are completely different in their memory layout, where they put devices, what devices are present, and so on. Trying to run an image for the wrong machine will result in it crashing very early on, when the guest tries to read a device or RAM which isn't where it expects to be. The palmetto-bmc machine will only run code that's built for that system.
-- 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. [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... [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
