From: "Lukas Riezler" <lukas.riezler@gmx.net>
To: "Ilija Kocho" <ilijak@siva.com.mk>
Cc: ecos-discuss@sourceware.org
Subject: Aw: Re: [ECOS] Debugging via JTAG - problems?
Date: Thu, 25 Apr 2013 13:00:00 -0000 [thread overview]
Message-ID: <trinity-92615307-1bf0-4eab-9851-bfc3f9d429d7-1366894837854@3capp-gmx-bs14> (raw)
In-Reply-To: <5178E338.3090307@siva.com.mk>
Hi Ilija!
> How do you get to main? by single stepping? Breakpoint?
> Put breakpoint on hal_system_init() . That's an early breakpoint and
> will give you chance to step through system booting.
Yes, I did it by single stepping. Like you advised I tried it now with a breakpoint at hal_system_init().
Eclipse shows me that this breakpoint exists and it also shows me that the breakpoint is located in the correct file! That's good.
Now I try to "run" (with "Resume" / F8) the program until the breakpoint should halt it. But unfortunately nothing happens?
With kind regards,
Lukas
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2013-04-25 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 0:13 Lukas Riezler
2013-04-25 8:03 ` Ilija Kocho
2013-04-25 13:00 ` Lukas Riezler [this message]
2013-04-25 13:03 ` Aw: " Lukas Riezler
[not found] ` <CAPrjMDBTTL3K=jw8bN=u0D3qL-K kbqraFgS4e2vL pTrN3mNw@mail.gmail.com>
[not found] ` <CAPrjMDBTTL3K=jw8bN=u0D3qL-K_kbqraFgS4e2vL_pTrN3mNw@mail.gmail.com>
2013-04-25 13:38 ` Edgar Grimberg
2013-04-25 14:19 ` Aw: " Lukas Riezler
2013-04-25 15:31 ` Ilija Kocho
2013-04-26 13:00 ` Aw: " Lukas Riezler
2013-05-02 19:36 ` Ilija Kocho
2013-05-07 19:16 ` Aw: " Lukas Riezler
2013-05-07 21:58 ` Lukas Riezler
2013-05-07 23:24 ` Lukas Riezler
2013-05-08 6:45 ` Ilija Kocho
2013-05-08 15:10 ` Aw: " Lukas Riezler
2013-05-02 19:05 ` Aw: " Lukas Riezler
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-92615307-1bf0-4eab-9851-bfc3f9d429d7-1366894837854@3capp-gmx-bs14 \
--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).