CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER macro issue

[Joel Sherrill]

On Fri, Aug 30, 2019, 11:35 AM Michel Macena <mmacena.eng at gmail.com> wrote:

> Thanks for the answer, but the ticker sample program
> has this macro in his system.h header. I can compile a program
> with this macro but when  I load it, the board just ignores it an then
> reset. If I change the
> macro for the opposite one ("does not need the clock driver") the program
> just works, except that I can't
> use any time related routine. Also without the clock drive driver enabled
> I can't communicate with the board (send and receive data).
> I understand that the Macro enables the clock drive but how this happens ?
> It changes a register value  in the chip ?
>

Setting that macro adds the clock driver to the set of statically installed
device drivers. The code is in bsps/sparc/erc32/clock. It uses a timer on
the erc32.

Check that it survives initialising the clock and gets the interrupt ok.

This isn't something I have heard of before. Is this a very early erc32?
Just wondering with nothing specific in mind.

--joel



> Em sex, 30 de ago de 2019 às 03:21, Sebastian Huber <
> sebastian.huber at embedded-brains.de> escreveu:
>
>> On 30/08/2019 19:09, Michel Macena wrote:
>> > I still have the issue with the macro #define
>> > CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER. I tried
>> > a different version of RTEMS but It didn't work. Can someone explain me
>> > how this macro works? So I can
>> > try to figure out some patch or fix for my hardware.
>>
>> This configuration option enables the clock driver.
>>
>> I would run first the RTEMS test suite on your target. For example start
>> with the ticker sample program.
>>
>> --
>> Sebastian Huber, embedded brains GmbH
>>
>> Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> Phone   : +49 89 189 47 41-16
>> Fax     : +49 89 189 47 41-09
>> E-Mail  : sebastian.huber at embedded-brains.de
>> PGP     : Public key available on request.
>>
>> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20190830/17bc7057/attachment-0002.html>