From: RTOS Pharos <1777777@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1777777] Re: arm9 clock pending (SP804)
Date: Mon, 23 Sep 2019 18:56:31 -0000 [thread overview]
Message-ID: <156926499196.13698.2399392543551586795.malone@gac.canonical.com> (raw)
In-Reply-To: 152947435461.1911.16896504402050089205.malonedeb@chaenomeles.canonical.com
Forgot to state the qemu argument, it's this one:
~/cross-compiler/qemu/2.5/bin/qemu-system-arm -M versatilepb -m 128M
-nographic -kernel myApplication
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1777777
Title:
arm9 clock pending (SP804)
Status in QEMU:
New
Bug description:
Hello all,
I'm using the versatilepb board and the timer Interrupt Mask Status
register (offset 0x14 of the SP804) does not seem to be working
properly on the latest qemu-2.12. I tried on the 2.5 (i believe this
is the mainstream version that comes with Linux) and it works
perfectly.
What happens is that the pending bit does not seem to be set in some
scenarios. In my case, I see the timer value decreasing to 0 and then
being reset to the reload value and neither does the interrupt is
triggered nor the pending bit is set.
I believe this is a matter of timing since in the "long" run the
system eventually catches up (after a few microseconds).
Thank you
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1777777/+subscriptions
next prev parent reply other threads:[~2019-09-23 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 5:59 [Qemu-devel] [Bug 1777777] [NEW] arm9 clock pending (SP804) RTOS Pharos
2018-06-20 17:10 ` [Qemu-devel] [Bug 1777777] " Peter Maydell
2018-07-30 18:12 ` RTOS Pharos
2018-07-30 18:38 ` Peter Maydell
2019-05-28 4:17 ` Launchpad Bug Tracker
2019-09-23 18:50 ` RTOS Pharos
2019-09-23 18:56 ` RTOS Pharos [this message]
2019-09-26 16:23 ` Peter Maydell
2019-09-26 16:34 ` Peter Maydell
2019-09-27 6:01 ` RTOS Pharos
2019-10-04 12:29 ` Peter Maydell
2020-01-09 17:18 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=156926499196.13698.2399392543551586795.malone@gac.canonical.com \
--to=1777777@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.