On Wed, Oct 14, 2020 at 5:39 AM Peter Maydell wrote:
>
> On Wed, 14 Oct 2020 at 01:42, Alistair Francis wrote:
> >
> > On Tue, Oct 13, 2020 at 5:29 PM Alistair Francis
> > wrote:
> > >
> > > On Mon, Oct 12, 2020 at 8:45 AM Peter Maydell
> > > wrote:
> > > >
> > > > The netduino2 and netduinop
On Wed, 14 Oct 2020 at 01:42, Alistair Francis wrote:
>
> On Tue, Oct 13, 2020 at 5:29 PM Alistair Francis wrote:
> >
> > On Mon, Oct 12, 2020 at 8:45 AM Peter Maydell
> > wrote:
> > >
> > > The netduino2 and netduinoplus2 boards forgot to set the
> > > system_clock_scale
> > > global, which m
On Tue, Oct 13, 2020 at 5:29 PM Alistair Francis wrote:
>
> On Mon, Oct 12, 2020 at 8:45 AM Peter Maydell
> wrote:
> >
> > The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
> > global, which meant that if guest code used the systick timer in "use
> > the processor clock
On Mon, Oct 12, 2020 at 8:45 AM Peter Maydell wrote:
>
> The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
> global, which meant that if guest code used the systick timer in "use
> the processor clock" mode it would hang because time never advances.
>
> Set the global to
The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
global, which meant that if guest code used the systick timer in "use
the processor clock" mode it would hang because time never advances.
Set the global to match the documented CPU clock speed of these boards.
Judging by
On Mon, Jul 27, 2020 at 9:26 AM Peter Maydell wrote:
>
> The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
> global, which meant that if guest code used the systick timer in "use
> the processor clock" mode it would hang because time never advances.
>
> Set the global to
On Mon, 27 Jul 2020 at 19:07, Philippe Mathieu-Daudé wrote:
> $ qemu-system-arm -M microbit
> qemu-system-arm: can not use systick with 'system_clock_scale = 0'
Yes, that's the other one on my list to do next (need to find
out what frequency it runs at though).
Good idea to have an automatic che
On 7/27/20 8:05 PM, Philippe Mathieu-Daudé wrote:
> On 7/27/20 6:26 PM, Peter Maydell wrote:
>> The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
>> global, which meant that if guest code used the systick timer in "use
>> the processor clock" mode it would hang because tim
On 7/27/20 6:26 PM, Peter Maydell wrote:
> The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
> global, which meant that if guest code used the systick timer in "use
> the processor clock" mode it would hang because time never advances.
>
> Set the global to match the docu
The netduino2 and netduinoplus2 boards forgot to set the system_clock_scale
global, which meant that if guest code used the systick timer in "use
the processor clock" mode it would hang because time never advances.
Set the global to match the documented CPU clock speed of these boards.
Judging by
10 matches
Mail list logo