On 28/09/2021 21:39, Joel Sherrill wrote:
Sebastian is there any guidance in the Classic API or Users Guide
about static systems?
Not yet, but it is on my TODO list.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phon
On Tue, Sep 28, 2021 at 11:21 AM Петр Борисенко wrote:
>
> > By wanting static allocation only, you need to use the special task and
> queue create APIs for that and avoid services which do dynamic allocation
>
> Are we talking about some existing API? Can you
> By wanting static allocation only, you need to use the special task and
queue create APIs for that and avoid services which do dynamic allocation
Are we talking about some existing API? Can you provide a link for
documentation?
On Tue, Sep 28, 2021, 6:33 PM Joel Sherrill wrote:
>
&g
mically extend the number of objects until
you run out of memory.
Combine it with unified work area and you can allocate until all memory on
your board is consumed.
By wanting static allocation only, you need to use the special task and
queue create APIs for that and avoid services which do
Seems pretty obvious, but I mean kernel. When I define a queue or a task,
will it compile statically or it will get memory from heap during the
initialization? @Sebastian Huber mentioned
that it depends on using of UNLIMITED_OBJECTS configuration option.
On Tue, Sep 28, 2021, 5:26 PM Joel Sherril
On Tue, Sep 28, 2021, 6:43 AM Петр Борисенко wrote:
> Hello!
> Is it possible to compile Rtems statically and disable memory allocation
> routines and heap?
>
No. You have to restrict your application use of APIs and services to those
which do not use dynamic allocation.
--joel
> _
Hello!
Is it possible to compile Rtems statically and disable memory allocation
routines and heap?
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
