From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Mohannad Maklad <msala.work@gmail.com>,
qemu-discuss@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>
Subject: Re: stm32f429 flash writing
Date: Mon, 6 Apr 2020 12:14:41 +0200 [thread overview]
Message-ID: <e415fc55-359b-509b-15dc-79181b0a53d7@redhat.com> (raw)
In-Reply-To: <CADxp151=4QduaHYugXGD+gcKffUUdkxfzWNvk5xXAqMWRKEQGw@mail.gmail.com>
On 4/5/20 3:41 PM, Mohannad Maklad wrote:
> Hello all,
>
> I'm trying to write to stm32f429 discovery board on flash but it doesn't
> seem to work. Can I share the code with you?
You can certainly share your code/use case!
Note that the stm32f429 is not modeled in mainstream QEMU, only the
stm32f405.
Please also include the following emails:
- qemu-devel@nongnu.org
- qemu-arm@nongnu.org
If you want to share/attach example files, you can also fill a
bug/feature request here:
https://bugs.launchpad.net/qemu/+filebug
Regards,
Phil.
parent reply other threads:[~2020-04-06 10:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADxp151=4QduaHYugXGD+gcKffUUdkxfzWNvk5xXAqMWRKEQGw@mail.gmail.com>]
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=e415fc55-359b-509b-15dc-79181b0a53d7@redhat.com \
--to=philmd@redhat.com \
--cc=msala.work@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).