(per the last paragraph in 4.1).
Can you please provide documentation for implementing the latter?
Regards,
Seth
From: Peter Maydell
Sent: Tuesday, November 5, 2019 1:55 PM
To: Stefan Hajnoczi
Cc: Hanson, Seth; qemu-devel@nongnu.org
Subject: [EXTERNA
ked.
Please advise.
Respectfully,
Seth
?)
Line 279/280 of hw/adc/stm32f2xx_adc.c seems to use 0xFF
memory_region_init_io(&s->mmio, obj, &stm32f2xx_adc_ops, s,
TYPE_STM32F2XX_ADC, 0xFF); Probably just confusion on my part, but thought
I would mention it just in case.
Thanks,
Seth
PS: Sorry if you are all the wrong people to
Thanks for all your help and I'm glad to contribute.
Seth
On Tue, Nov 20, 2018 at 12:15 PM Alistair Francis
wrote:
> On Mon, Nov 19, 2018 at 3:35 AM Philippe Mathieu-Daudé
> wrote:
> >
> > On Mon, Nov 19, 2018 at 12:08 PM Peter Maydell
> wrote:
> > > On
From: Seth Kintigh
I corrected these 2 memory regions based on specifications from the chip
manufacturer. The existing ranges seem to overlap and and cause odd
behavior and/or crashes when trying to set up multiple UARTs,
Signed-off-by: Seth Kintigh
---
Phil, I hope this is the right format
that in this patch as I never fully tested its
effects.
This is my first patch, I hope I did it correctly,
Seth Kintigh
---
hw/char/stm32f2xx_usart.c | 2 +-
hw/timer/stm32f2xx_timer.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/char/stm32f2xx_usart.c b/hw/char
of 3804 which means
nothing.
On Wed, Oct 12, 2016 at 6:25 PM, Seth K wrote:
> It's a bare metal program so I don't really have anywhere to print to,
> other than my custom function to output to the uart. I did double check all
> the address to make sure they agreed with the
zy?
I don't understand Qemu enough to know what should be calling the functions
that handle UART read/write. Is there something I should look at in Qemu
and try to intercept?
On Fri, Oct 7, 2016 at 6:27 PM, Alistair Francis
wrote:
> On Fri, Oct 7, 2016 at 1:04 PM, Seth K wrote:
> >
ote:
> > On Fri, Oct 7, 2016 at 8:59 AM, Seth K wrote:
> >> The only machine I saw listed in the help output is "netduino2." I
> pulled
> >> QEMU from github, was that the right thing to do?
> >>
> >> I found the specifications for the st
help
On Thu, Oct 6, 2016 at 8:18 PM, Alistair Francis
wrote:
> QEMU only supports the Netduino (not Netduino 2) it is possible that
> the base addresses are different and that is why you aren't seeing the
> serial output.
>
> Thanks,
>
> Alistair
>
>
> On We
T4 to /tmp/uart4. 2 and 3
still disappear but that seems to be a bug and I have reported it. Now to
test this on a chip with 8 UARTS...
Thanks again!
On Wed, Oct 5, 2016 at 5:21 PM, Alistair Francis
wrote:
> On Wed, Oct 5, 2016 at 10:45 AM, Seth K wrote:
> > Thanks for that link.
> &
Public bug reported:
Writes to UART 2 and 3 disappear. As 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 confirmed
text sent to UART1 and UART4 are sent to that function while text sent
to UART 2 and 3
nd 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.
Thanks,
Seth
sure about SPIs either.
My next thought was to make 1 board with all three chips, but have some way
to sniff the UARTs/SPIs/GPIOs between chips. Is that possible in QEMU?
Thank you!
Seth
Hello -
I'm using ssh with the -X switch to get onto a server where I have kvm
installed. I've made a virtual disk and I'm issuing the following command:
kvm -name livecd-debian -monitor vc -no-quit -m 1024 -usb -drive
media=disk,if=ide,index=0,file=mastodonhdd1.qcow2,snapshot=off -drive
media
Hi,
With qemu 0.12.4 (and earier revisions), I see:
unknown keycodes `sun(type6_usb)_aliases(qwerty)', please report to
qemu-devel@nongnu.org
Let me know if you need anything further.
Thanks,
--S
Quoting Jonathan Kalbfeld, who wrote the following on Wed, 3 Mar 2010:
Hey Seth,
Do you know if it builds on Sparc at all? On Oracle Solaris ;)
Yes, with the below caveats, it does build and operate on SPARC as well :).
--S
jonathan
On Wed, Mar 3, 2010 at 6:24 PM, Seth G wrote
Hi,
I just sent a fair amount of time trying to figure out problems
with the qemu build and resulting binary. The first problem (which
is no longer a problem due to the shell OpenSolaris uses) was that
`sh' was used in rules.mak to perform commands -- I had a /bin/sh
that was not bash-compatib
18 matches
Mail list logo
