From: Alistair Francis <alistair23@gmail.com>
To: Seth K <skintigh@gmail.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Baremetal Netduino2 -- cannot output on UARTs 2-4
Date: Tue, 4 Oct 2016 09:59:28 -0700 [thread overview]
Message-ID: <CAKmqyKPeDQOVUEoMw+P_J4gW_AmkBNGqB55=9xB8qH+Re4B+bg@mail.gmail.com> (raw)
In-Reply-To: <CAErn8fSL18qvQ9X6gr9R0U8uJj49at=K0SC+z-2G3+OzV+yUWw@mail.gmail.com>
On Mon, Oct 3, 2016 at 1:25 PM, Seth K <skintigh@gmail.com> wrote:
> I have made a bare metal "Hello World" program for the Netduino2. I have
> pushed it here:
>
> https://github.com/skintigh/baremetal_netduino2
>
> It should output "Test 1/4" to USART 1, "Test 2/4" to USART 2, "Test 3/4"
> to USART 3 and "Test 4/4" to UART 4.
>
> What actually happens in QEMU is only the first string is output. That may
> be a command line argument error on my part, so for a sanity check I put
> printf statements in the function stm32f2xx_usart_write in
> qemu/hw/char/stm32f2xx_usart.c and recompiled qemu. The result is text sent
> to UART1 and UART4 make is to the function (though only 1 is output), while
> writes to 2 and 3 simply disappear and never make it to that function. I
> assumed all writes to UARTs would go to that function.
>
> Am I doing something dumb? Is this a bug? Any help would be greatly
> appreciated.
Hello Seth,
I haven't looked at the multiple UART problem in a while. It sounds
like your command line arguments are incorrect.
Have a look at this wiki page for details on what the serial options
should look like:
https://github.com/alistair23/qemu/wiki/Getting-Started
If that doesn't work can you copypaste your command line arguments?
Thanks,
Alistair
>
> Thanks,
> Seth
next prev parent reply other threads:[~2016-10-04 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 20:25 [Qemu-devel] Baremetal Netduino2 -- cannot output on UARTs 2-4 Seth K
2016-10-04 16:59 ` Alistair Francis [this message]
[not found] ` <CAErn8fS_FhRBfXyb5iqYXbVYUAW+_TuuY9n8Zt219BcipfGuOw@mail.gmail.com>
[not found] ` <CAKmqyKOmT1GQWZHAYtZFYLsosaywtkd8iZ2Oc52=-P_S28opjg@mail.gmail.com>
2016-10-06 21:52 ` Seth K
2016-10-06 23:54 ` Alistair Francis
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='CAKmqyKPeDQOVUEoMw+P_J4gW_AmkBNGqB55=9xB8qH+Re4B+bg@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=skintigh@gmail.com \
/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.