From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38863) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRlxR-0008Dg-LL for qemu-devel@nongnu.org; Tue, 27 Nov 2018 17:35:55 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRlxN-00070n-MM for qemu-devel@nongnu.org; Tue, 27 Nov 2018 17:35:53 -0500 Received: from indium.canonical.com ([91.189.90.7]:49260) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gRlxM-0006zX-CB for qemu-devel@nongnu.org; Tue, 27 Nov 2018 17:35:49 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1gRlxI-0004xc-JA for ; Tue, 27 Nov 2018 22:35:44 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 87E002E80C0 for ; Tue, 27 Nov 2018 22:35:44 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 27 Nov 2018 22:25:05 -0000 From: Igor Reply-To: Bug 1805445 <1805445@bugs.launchpad.net> Sender: bounces@canonical.com References: <154332864629.32687.7125797278920412825.malonedeb@wampee.canonical.com> Message-Id: <154335750647.32501.16309260409919023970.launchpad@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1805445] Re: QEMU arm virt machine was stopped by STMFD command while debug process List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ** 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 ph= one (Spreadtrum platform) [CODE]qemu-system-arm -S -gdb tcp::1234,ipv4 -drive file=3DC:\cygwin64\ho= me\flash.bin,if=3Dmtd,format=3Draw -M palmetto-bmc -cpu arm926 -m 64M[/CODE] I use palmetto-bmc platform because it have ARM926EJ-S core and support S= PI 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[/IM= G] + = = When the IDA run 00032534 STR R11, [R10] command - [IMG]https://pp.userapi.com/c846416/v846416708/133f60/GQzxORvf4Tg.jpg[/IM= G] + = = instead of store R11 on R10 adress, it jump 000328DC STMFD SP!, {R0-R12,L= R} instruction... - [IMG]https://pp.userapi.com/c847218/v847218546/13ec26/32A0VcaJywg.jpg[/IM= G] - 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 ph= one (Spreadtrum platform) [CODE]qemu-system-arm -S -gdb tcp::1234,ipv4 -drive file=3DC:\cygwin64\ho= me\flash.bin,if=3Dmtd,format=3Draw -M palmetto-bmc -cpu arm926 -m 64M[/CODE] I use palmetto-bmc platform because it have ARM926EJ-S core and support S= PI 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,L= R} 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