public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lukas Riezler" <lukas.riezler@gmx.net>
To: "Ilija Kocho" <ilijak@siva.com.mk>
Cc: ecos-discuss@sourceware.org
Subject: Aw: Re:  Re: [ECOS] eCos application crashes
Date: Mon, 03 Jun 2013 23:35:00 -0000	[thread overview]
Message-ID: <trinity-c0093909-ece3-47c8-91bb-37d3d4f8d7f5-1370302503001@3capp-gmx-bs21> (raw)
In-Reply-To: <51AD13BF.3090408@siva.com.mk>

Hi Ilja,
 
I think you are right!!!
It seems that the situation for FM3 is the same like for kinetis!
==> I forgot to disable the hardware watchdog!
Now it seems to run! :-)

Thank you very very much for this hint!

Lukas
 
 

Gesendet: Dienstag, 04. Juni 2013 um 00:07 Uhr
Von: "Ilija Kocho" <ilijak@siva.com.mk>
An: "Lukas Riezler" <lukas.riezler@gmx.net>
Cc: ecos-discuss@sourceware.org
Betreff: Re: Aw: Re: [ECOS] eCos application crashes
On 03.06.2013 22:14, Lukas Riezler wrote:
> Hi Ilja,
>
> I think it's the port which crashes...because the application contains only a simple counter.
> I did the clocking and hal_diag.c - are there any traps causing me stumble?The clocking I did is on the same way like it is described in examples of FM3 (where the clocks also get initialized). So I can't imagine that my fault depends on clocking.

Try to imagine... Check whether your code tries access on some illegal
location.

Is your hardware properly initialized? Some devices like Kinetis have
watchdog that is enabled after reset so you must disable it before u do
anything. Does FM3 have one?

Ilija

>
> Lukas
>
>
>
> Gesendet: Montag, 03. Juni 2013 um 21:49 Uhr
> Von: "Ilija Kocho" <ilijak@siva.com.mk>
> An: "Lukas Riezler" <lukas.riezler@gmx.net>
> Cc: ecos-discuss@sourceware.org
> Betreff: Re: [ECOS] eCos application crashes
> On 03.06.2013 21:31, Lukas Riezler wrote:
>> Hi eCos-guys!
>>
>> I have a problem with my fm3 port.
>> When I start an eCos application first it seems to run fine...but after ~1 second it crashes and restarts.
>> Do you have any idea what could be the reason for this behaviour?
>> I've tried to compile eCos without optimization ==> the first running was okay! The application did run fine!!!
>> But when I started it a few minutes later it crashed again...
> Is it the application or the port that chrashes? Have you tried the
> application on some mature port?
>
> HTH
> Ilija
>
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss[http://ecos.sourceware.org/ml/ecos-discuss][http://ecos.sourceware.org/ml/ecos-discuss[http://ecos.sourceware.org/ml/ecos-discuss]]
>
>


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos[http://ecos.sourceware.org/fom/ecos]
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss[http://ecos.sourceware.org/ml/ecos-discuss]
 

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2013-06-03 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03 19:31 Lukas Riezler
2013-06-03 19:49 ` Ilija Kocho
2013-06-03 20:14   ` Aw: " Lukas Riezler
2013-06-03 22:09     ` Ilija Kocho
2013-06-03 23:35       ` Lukas Riezler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-c0093909-ece3-47c8-91bb-37d3d4f8d7f5-1370302503001@3capp-gmx-bs21 \
    --to=lukas.riezler@gmx.net \
    --cc=ecos-discuss@sourceware.org \
    --cc=ilijak@siva.com.mk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).