<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hmm, maybe clock driver code has been changed during the years to
read or write some register bits that are illegal on the 3-chip
ERC32. This would cause a trap to error mode and most likely a
watchdog reset. I quickly looked through the ERC32 clock driver
code but could not see anything obvious. It could also be an ERC32
interrupt driver issue - enabling interrupts seems to trigger the
problem. I will try to run ticker on an old version of sis that
did some more checks for the 3-chip version ...<br>
</p>
<div class="moz-cite-prefix">On 9/3/19 12:57 AM, Joel Sherrill
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF9ehCW9OxQF2nxphq5Qidudrk9WaEVka=JQ1B65wFnw0bQHag@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Jiri does this ring a bell with the old Tharsys
board and 3 chip erc32?</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Sep 2, 2019, 5:09 PM
Michel Macena <<a href="mailto:mmacena.eng@gmail.com"
moz-do-not-send="true">mmacena.eng@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>It is the ERC 32 chipset version (TSC691, TSC692 and
TSC693 units), The Board was manufactured by Tharsys, a
french company, but it does not</div>
<div>exist anymore. The board manual dates from 2000.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Em sex, 30 de ago de 2019
às 17:53, Joel Sherrill <<a
href="mailto:joel@rtems.org" target="_blank"
rel="noreferrer" moz-do-not-send="true">joel@rtems.org</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Aug 30,
2019, 11:35 AM Michel Macena <<a
href="mailto:mmacena.eng@gmail.com"
target="_blank" rel="noreferrer"
moz-do-not-send="true">mmacena.eng@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Thanks for the answer, but the ticker
sample program</div>
<div>has this macro in his system.h header. I
can compile a program</div>
<div>with this macro but when I load it, the
board just ignores it an then reset. If I
change the</div>
<div>macro for the opposite one ("does not need
the clock driver") the program just works,
except that I can't</div>
<div>use any time related routine. Also without
the clock drive driver enabled I can't
communicate with the board (send and receive
data).</div>
<div>I understand that the Macro enables the
clock drive but how this happens ? It changes
a register value in the chip ?<br>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">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. </div>
<div dir="auto"><br>
</div>
<div dir="auto">Check that it survives initialising the
clock and gets the interrupt ok.</div>
<div dir="auto"><br>
</div>
<div dir="auto">This isn't something I have heard of
before. Is this a very early erc32? Just wondering
with nothing specific in mind. </div>
<div dir="auto"><br>
</div>
<div dir="auto">--joel</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Em sex, 30 de
ago de 2019 às 03:21, Sebastian Huber <<a
href="mailto:sebastian.huber@embedded-brains.de"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">sebastian.huber@embedded-brains.de</a>>
escreveu:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">On
30/08/2019 19:09, Michel Macena wrote:<br>
> I still have the issue with the macro
#define <br>
> CONFIGURE_APPLICATION_NEEDS_CLOCK_DRIVER.
I tried<br>
> a different version of RTEMS but It
didn't work. Can someone explain me <br>
> how this macro works? So I can<br>
> try to figure out some patch or fix for
my hardware.<br>
<br>
This configuration option enables the clock
driver.<br>
<br>
I would run first the RTEMS test suite on your
target. For example start <br>
with the ticker sample program.<br>
<br>
-- <br>
Sebastian Huber, embedded brains GmbH<br>
<br>
Address : Dornierstr. 4, D-82178 Puchheim,
Germany<br>
Phone : +49 89 189 47 41-16<br>
Fax : +49 89 189 47 41-09<br>
E-Mail : <a
href="mailto:sebastian.huber@embedded-brains.de"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true">sebastian.huber@embedded-brains.de</a><br>
PGP : Public key available on request.<br>
<br>
Diese Nachricht ist keine geschäftliche
Mitteilung im Sinne des EHUG.<br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>