Hi,
I've been developing some tests and observed some task behaviour that i
can't understand and couldn't find any documentation about it.
I have tests where I create 2 extra tasks (Workers) and then those tasks
are blocked and unlocked using semaphores and barriers. However, whenever
main task (
On Mon, Mar 14, 2022 at 7:37 AM Dariusz.sabala wrote:
> Hello
>
> I am developing SAMRH71 BSP in RTEMS 4.11, I started editing atsam BSP and
> accomplished some success, but the decision was made to support both BSP
> (atsam and samrh71) in separate folders. I reverted my changes, copied and
> re
On Mon, Mar 14, 2022 at 6:44 AM Jerzy J wrote:
> Hi,
>
> I've been developing some tests and observed some task behaviour that i
> can't understand and couldn't find any documentation about it.
>
> I have tests where I create 2 extra tasks (Workers) and then those tasks
> are blocked and unlocked
Hi Joel,
Thanks for the explanation! It was in the context of Classic API.
All the best,
Jerzy
pon., 14 mar 2022 o 13:12 Joel Sherrill napisaĆ(a):
>
>
> On Mon, Mar 14, 2022 at 6:44 AM Jerzy J wrote:
>
>> Hi,
>>
>> I've been developing some tests and observed some task behaviour that i
>> can
On 14/03/2022 15:12, dsa93 wrote:
I tried to change it to "rtems-c-src-lib-libbsp-arm-samrh71" (same as bsp root
folder), but doing this kind of autotools voodo didnt helped. The result is still the
same: Make does not see any target inside BSP folder. I guess I will continue work on two
GIT b