From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44727) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gS7tJ-0005j1-6W for qemu-devel@nongnu.org; Wed, 28 Nov 2018 17:01:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gS7tB-0001ox-Nr for qemu-devel@nongnu.org; Wed, 28 Nov 2018 17:01:03 -0500 Received: from indium.canonical.com ([91.189.90.7]:52486) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gS7t9-0001n5-OR for qemu-devel@nongnu.org; Wed, 28 Nov 2018 17:00:56 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1gS7t7-0006cL-4j for ; Wed, 28 Nov 2018 22:00:53 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 2283B2E80C8 for ; Wed, 28 Nov 2018 22:00:53 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Nov 2018 21:53:31 -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: <154344201117.10002.17688761335470201785.malone@chaenomeles.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 /* * Allocate RAM after the memory controller has checked the size * was valid. If not, a default value is used. */ ram_size =3D object_property_get_uint(OBJECT(&bmc->soc), "ram-size", &e= rror_abort); memory_region_allocate_system_memory(&bmc->ram1, NULL, "ram1", ram_size= ); memory_region_allocate_system_memory(&bmc->ram2, NULL, "ram2", ram_size= ); memory_region_allocate_system_memory(&bmc->ram3, NULL, "ram3", ram_size= ); memory_region_add_subregion(get_system_memory(), sc->info->sdram_base= [1], &bmc->ram1); memory_region_add_subregion(get_system_memory(), sc->info->sdram_base= [0], &bmc->ram2); memory_region_add_subregion(get_system_memory(), sc->info->sdram_base= [2], &bmc->ram3); object_property_add_const_link(OBJECT(&bmc->soc), "ram1", OBJECT(&bmc->= ram1), &error_abort); object_property_add_const_link(OBJECT(&bmc->soc), "ram2", OBJECT(&bmc->= ram2), &error_abort); object_property_add_const_link(OBJECT(&bmc->soc), "ram3", OBJECT(&bmc->= ram3), &error_abort); And I can create 3 RAM section for avoid exeption handler! Maybe any devices from this adress does not appear in 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