<span style=" font-size:10pt;font-family:sans-serif"><i>> Polled vs
interrupt console drivers?</i></span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I don't see how...
With tasks spawned with RTEMS_DEFAULT_MODES and CONFIGURE_MAXIMUM_PROCESSORS
set to 1, Task 2 should not be allowed to run until Task 1 completes -
so the output of "Starting" ( in "task_begin" of Task
2) should not be able to precede the output of "Computed" at
the end of Task1 - the relevant print should not have happened yet. </span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">I can understand
how console output can become garbled in tasks that are running concurrently
- but in this case, I would expect them to run in sequence.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">The only way for
this</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 0] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 0] Computed
the correct floating point result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 1] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 1] Computed
the correct integer result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 2] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 2] Computed
the correct floating point result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 3] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 3] Computed
the correct integer result.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">to turn into this</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">The expected result:</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 0] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 1] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 2] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 3] Starting...</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 0] Computed
the correct floating point result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 1] Computed
the correct integer result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 2] Computed
the correct floating point result.</span>
<br><span style=" font-size:10pt;font-family:sans-serif">[TASK 3] Computed
the correct integer result.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">...is if indeed,
the tasks are running concurrently with the ZynQ BSP.</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">So the question
is:</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif">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?</span>
<br>
<br><span style=" font-size:10pt;color:#000080;font-family:sans-serif"><b>Thanassis
Tsiodras</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">Real-time Embedded
Software Engineer </span>
<br><span style=" font-size:10pt;font-family:sans-serif">System, Software
and Technology Department</span>
<br>
<br><span style=" font-size:10pt;font-family:sans-serif"><b>ESTEC</b></span>
<br><span style=" font-size:10pt;font-family:sans-serif">Keplerlaan 1,
PO Box 299</span>
<br><span style=" font-size:10pt;font-family:sans-serif">NL-2200 AG Noordwijk,
The Netherlands</span>
<br><span style=" font-size:10pt;font-family:sans-serif">Thanassis.Tsiodras@esa.int
| </span><a href=www.esa.int><span style=" font-size:10pt;color:blue;font-family:sans-serif">www.esa.int</span></a>
<br><span style=" font-size:10pt;font-family:sans-serif">T +31 71 565 5332</span>
<br>
<br>
<br>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">From:
</span><span style=" font-size:9pt;font-family:sans-serif">"Chris
Johns" <chrisj@rtems.org></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">To:
</span><span style=" font-size:9pt;font-family:sans-serif">"Thanassis
Tsiodras (external)" <Thanassis.Tsiodras@esa.int></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Cc:
</span><span style=" font-size:9pt;font-family:sans-serif">"Gedare
Bloom" <gedare@rtems.org>, "rtems-users@rtems.org"
<users@rtems.org>, "Fernando Domínguez Pousa" <fdpousa@gmv.com></span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Date:
</span><span style=" font-size:9pt;font-family:sans-serif">01/05/2020
09:46</span>
<br><span style=" font-size:9pt;color:#5f5f5f;font-family:sans-serif">Subject:
</span><span style=" font-size:9pt;font-family:sans-serif">Re:
RTEMS tasks timesliced instead of running to completion. TIMESLICE flag
is not active!</span>
<br>
<hr noshade>
<br>
<br>
<br><tt><span style=" font-size:10pt">On 1/5/20 5:08 pm, Thanassis Tsiodras
(external) wrote:<br>
> Note that this test (complete code in <br>
> </span></tt><a href="https://gitrepos.estec.esa.int/ttsiodras/RTEMS-build-workflows/-/tree/master/OAR"><tt><span style=" font-size:10pt">https://gitrepos.estec.esa.int/ttsiodras/RTEMS-build-workflows/-/tree/master/OAR</span></tt></a><tt><span style=" font-size:10pt">)
<br>
> creates the proper - non-interleaved - output when compiled and executed
<br>
> for the GR712RC and GR740 boards... but creates the interleaved output
<br>
> in a ZynQ ZC706 board.<br>
<br>
Polled vs interrupt console drivers?<br>
<br>
Chris<br>
<br>
</span></tt>
<br>
<br><PRE>This message is intended only for the recipient(s) named above. It may contain proprietary information and/or
protected content. Any unauthorised disclosure, use, retention or dissemination is prohibited. If you have received
this e-mail in error, please notify the sender immediately. ESA applies appropriate organisational measures to protect
personal data, in case of data privacy queries, please contact the ESA Data Protection Officer (dpo@esa.int).
</PRE>