From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=44358 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PYlmS-0000e8-QS for qemu-devel@nongnu.org; Fri, 31 Dec 2010 15:41:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PYlmE-0000fH-1t for qemu-devel@nongnu.org; Fri, 31 Dec 2010 15:40:43 -0500 Received: from adelie.canonical.com ([91.189.90.139]:37952) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PYlmD-0000eq-RC for qemu-devel@nongnu.org; Fri, 31 Dec 2010 15:40:42 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by adelie.canonical.com with esmtp (Exim 4.69 #1 (Debian)) id 1PYlmC-0007mk-9y for ; Fri, 31 Dec 2010 20:40:40 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 304AA2E806B for ; Fri, 31 Dec 2010 20:40:40 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 31 Dec 2010 20:30:43 -0000 From: Frikkie Thirion <696094@bugs.launchpad.net> Sender: bounces@canonical.com References: <20101231203043.711.86363.malonedeb@potassium.ubuntu.com> Message-Id: <20101231203043.711.86363.malonedeb@potassium.ubuntu.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 696094] [NEW] TI Stellaris lm3s811evb (ARM Cortex-M3) : Systick interrupt not working Reply-To: Bug 696094 <696094@bugs.launchpad.net> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: I've tried to create a small project that uses the CMSIS as base library. The problem is that the SysTick_interrupt_handler() doesn't get executed wh= en the systick event is detected in QEMU. Furthermore, it seems asif QEMU g= ets stuck in an endless loop. QEMU doesn't respond to Ctrl-C on the command= line and the GDB session also stalls. 'kill -9' is the only way to stop QE= MU. It seems asif the initialisation of the NVIC works fine. I've traced the fu= nction calls in QEMU as follows: stellaris.c: stellaris_init() - Perform generic armv7 init: armv7m_init() armv7m.c: armv7m_init() - Create and init the nvic: nvic =3D qdev_create(NULL, "armv7m_nvic"); env->nvic =3D nvic; qdev_init_nofail(nvic); - Configure the programmable interrupt controlle= r: Call: arm_pic_init_cpu() = qemu_allocate_irqs(arm_pic_cpu_hand= ler) - Initialise 64 interrupt structures. The following call sequence is observed when the systick event occur: armv7m_nvic.c: systick_timer_tick(): set pending interrupt armv7m_nvic.c: armv7m_nvic_set_pending() for irq:15 arm_gic.c: gic_set_pending_private(): GIC_SET_PENDING(15,) arm_gic.c: gic_update() - Raise IRQ with qemu_set_irq() irq.c: eqmu_set_irq() - Call the irq->handler = -- I assume the irq handler is 'arm_pic_cpu_= handler()', since that was passed as the parameter wh= en qemu_allocate_irqs() was called in ... arm_pic.c: arm_pic_cpu_handler() - After evaluation, call cpu_int= errupt() exec.c: cpu_interrupt() is called. = The tools that were used during the testing of this project: GCC: Codesourcery ARM eabi 2010q3 QEMU: Checked out on 31/12/2010 - Last commit: 0fcec41eec0432c77645b4a407= d3a3e030c4abc4 The project files are attached, for reproducing of the errors. Note: The CMSIS wants to perform byte accesses to the NVIC. For the Cort= ex-M3, unaligned 8 bit and 16 bit accesses are allowed. The current QEMU im= plementation doesn't yet cater for it. As a work around, updated versions of arm_gic.c armv7m_nvic.h armv7m_nvic.c is also included. Launch project with: go_gdb.sh Attach debugger with: arm-none-eabi-gdbtui --command=3DgdbCommands_tui (s =3D step, n =3D next, c =3D continue, Ctrl-C =3D stop, print = to look at variable contents) ** Affects: qemu Importance: Undecided Status: New -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/696094 Title: TI Stellaris lm3s811evb (ARM Cortex-M3) : Systick interrupt not working Status in QEMU: New Bug description: I've tried to create a small project that uses the CMSIS as base library. The problem is that the SysTick_interrupt_handler() doesn't get executed wh= en the systick event is detected in QEMU. Furthermore, it seems asif QEMU g= ets stuck in an endless loop. QEMU doesn't respond to Ctrl-C on the command= line and the GDB session also stalls. 'kill -9' is the only way to stop QE= MU. It seems asif the initialisation of the NVIC works fine. I've traced the fu= nction calls in QEMU as follows: stellaris.c: stellaris_init() - Perform generic armv7 init: armv7m_init() armv7m.c: armv7m_init() - Create and init the nvic: nvic =3D qdev_create(NULL, "armv7m_nvic"); env->nvic =3D nvic; qdev_init_nofail(nvic); - Configure the programmable interrupt controlle= r: Call: arm_pic_init_cpu() = qemu_allocate_irqs(arm_pic_cpu_hand= ler) - Initialise 64 interrupt structures. The following call sequence is observed when the systick event occur: armv7m_nvic.c: systick_timer_tick(): set pending interrupt armv7m_nvic.c: armv7m_nvic_set_pending() for irq:15 arm_gic.c: gic_set_pending_private(): GIC_SET_PENDING(15,) arm_gic.c: gic_update() - Raise IRQ with qemu_set_irq() irq.c: eqmu_set_irq() - Call the irq->handler = -- I assume the irq handler is 'arm_pic_cpu_= handler()', since that was passed as the parameter wh= en qemu_allocate_irqs() was called in ... arm_pic.c: arm_pic_cpu_handler() - After evaluation, call cpu_int= errupt() exec.c: cpu_interrupt() is called. = The tools that were used during the testing of this project: GCC: Codesourcery ARM eabi 2010q3 QEMU: Checked out on 31/12/2010 - Last commit: 0fcec41eec0432c77645b4a407= d3a3e030c4abc4 The project files are attached, for reproducing of the errors. Note: The CMSIS wants to perform byte accesses to the NVIC. For the Cort= ex-M3, unaligned 8 bit and 16 bit accesses are allowed. The current QEMU im= plementation doesn't yet cater for it. As a work around, updated versions of arm_gic.c armv7m_nvic.h armv7m_nvic.c is also included. Launch project with: go_gdb.sh Attach debugger with: arm-none-eabi-gdbtui --command=3DgdbCommands_tui (s =3D step, n =3D next, c =3D continue, Ctrl-C =3D stop, print = to look at variable contents)