Can't enable a dummy clock driver

[Denis Obrezkov]

2017-07-23 22:30 GMT+02:00 Joel Sherrill <joel at rtems.org>:

> Increasing the stack size effectively eliminated a data corruption issue.
> The memory corrupted likely was an RTEMS internal object structure.
>
> What is the stack frame size required by each subroutine call?
>
How can I determine it?

>
> How much stack to call printf()?
>
> The minimum is an educated guess by the porter that is large enough to run
> many/most small applications. You should be able to call RTEMS services and
> do a context switch.
>
> Hope that helps pick one. :)
>

As for now, I have increased the minimum stack size and get the following
output:

*** LOW MEMORY CLOCK TICK TEST ***

TA1 - rtems_clock_get_tod - 09:00:00 12/31/1988

TA2 - rtems_clock_get_tod - 09:00:00 12/31/1988
TA3 - rtems_clock_get_tod - 09:00:00 12/31/1988

I will try to determine how to proceed further.



-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170724/87ee9d4a/attachment-0002.html>