From: Jiahuan Zhang <jiahuanzhang90@gmail.com>
To: qemu-arm@nongnu.org
Subject: [Qemu-arm] How to debug peripheral device
Date: Wed, 4 Jan 2017 08:05:49 +0100 [thread overview]
Message-ID: <CAJy91CYscXEOQ=cFeDt_NF2ZatL1PBOyYmTJg4xhytpWUtpaRQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hi everyone,
This is my first time to use QEMU. I am emulating the atmel at91sam9261
board. I want to debug the functionalities of the emulated peripherals.
What I am doing now is to *printf* the reading and writing memory offsets
and values for the periperals when running a linux uImage. And according to
the emulated periperals' *read* and *write* behaviours, I rectify their
resigters in terms of their corresponding functions in the board's
datasheet.
However, not all the printed offsets are expected. And some offsets that I
expected to be written are not be written, so that some functions will
never be enabled and some peripherals are never be driven. Any solution for
this offset missing?
What is the right way for peripheral debugging? Getting stuck for almost
two months, I am really upset now.
Best regards,
Jiahuan
[-- Attachment #2: Type: text/html, Size: 1075 bytes --]
reply other threads:[~2017-01-04 7:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJy91CYscXEOQ=cFeDt_NF2ZatL1PBOyYmTJg4xhytpWUtpaRQ@mail.gmail.com' \
--to=jiahuanzhang90@gmail.com \
--cc=qemu-arm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).