ith some BSPs
(ZynQ), but not with others (GR712RC, GR740).
Thanassis Tsiodras
Real-time Embedded Software Engineer
System, Software and Technology Department
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
thanassis.tsiod...@esa.int | www.esa.int
T +31 71 565 5332
F
the log at
the end.
If we see that the values are generated in the proper sequence, then it is
indeed the console output that causes this pre-emption.
Does anyone know if the ZynQ's BSP uses a small enough console buffer that
would be filled up with just printing "[TASK 0] Starting...&q
already mentioned...
none.
Thanassis Tsiodras
Real-time Embedded Software Engineer
System, Software and Technology Department
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
thanassis.tsiod...@esa.int | www.esa.int
T +31 71 565 5332
From: "Thomas Doerfler"
To:
rrect integer result.
...is if indeed, the tasks are running concurrently with the ZynQ BSP.
So the question is:
Given the task spawning parameters ("RTEMS_DEFAULT_MODES") and
CONFIGURE_MAXIMUM_PROCESSORS set to 1, is it right to experience
timeslicing on the ZynQ ZC706?
Thanass
ed and executed
for the GR712RC and GR740 boards... but creates the interleaved output in
a ZynQ ZC706 board.
Thanassis Tsiodras
Real-time Embedded Software Engineer
System, Software and Technology Department
ESTEC
Keplerlaan 1, PO Box 299
NL-2200 AG Noordwijk, The Netherlands
thanassis
contrib
At some point I need to create a Dockerfile to completely automate this
thing - there's too many variables to consider and people can easily trip
over one of them.
Cheers,
Thanassis.
Thanassis Tsiodras
Real-time Embedded Software Engineer
System, Software and Technology Departme
