Hello Erich,
My original 2019 problem of "why can't I redirect emit to output to my
LCD from a task" is perhaps most simply addressed by an addition to the
documentation. Once (I) it is understood that the user area a task has
access to needs to be explicitly populated, it all works as expected.
Y
Hello Tristan,
back to mulitasking on AmForth.
I spend an afternoon to create a background task, which does some
output by itself (see code below). There is nothing really new in
this. If I equip the background tasks with base and pointers to emit
(and emit?), it does work, including pictured o
Hello Tristan,
Tristan Williams writes:
> Hello Erich,
>
> Within task-init from multitask.frt I think a task's entire tcb/user
> area is filled with zeros and then only the values from the task's
> (flash) tib are copied across to the task's tcb/user area. A value for
> BASE is not stored withi
Hello Erich,
Within task-init from multitask.frt I think a task's entire tcb/user
area is filled with zeros and then only the values from the task's
(flash) tib are copied across to the task's tcb/user area. A value for
BASE is not stored within the tib. Only sp0, sp0-- and rp0 are stored
in the t
Hello Tristan,
thanks for your message.
My below answers/comments only regard AVR8. I have currently no
idea, how this is similar or different in the other 3 targets.
> I revisited "Redirecting emit from within a task in AmForth",
> as I still like the idea of having a self contained task tha
