public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: Lukas Riezler <lukas.riezler@gmx.net>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Debugging via JTAG - problems?
Date: Thu, 25 Apr 2013 08:03:00 -0000	[thread overview]
Message-ID: <5178E338.3090307@siva.com.mk> (raw)
In-Reply-To: <trinity-f282db46-eac2-47d3-8bb1-13e21542ba72-1366848816388@3capp-gmx-bs55>

On 25.04.2013 02:13, Lukas Riezler wrote:
> Hello ecos-guys!
>
[snip]
> 8) I am able to start debugging --> the debugger starts at vectors.S and after some steps I get into the main() of Hello World. What makes me a little
>    perplex is that I don't leave vectors.S until I reach the main() of Hello World.
>    I expected that I should run through the different files of the HAL to see among other things the steps of my clock initialisation.

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.

> 9) like I said I arrive at main() of Hello World...but exactly the line of code which should cause the LED to switch on is ignored by the debugger!

It is possible that your code has been optimised by GCC. Did you get
some warnings for unused variables from GCC? I assume you are writing to
some port, try to declare the port (variable) as volatile.

>    A few steps later I get with the debugger to serial.c
> Do you know what I'm doing wrong? If there are some passages you don't really understand because of my english --> please tell ;)
>
> ---
>
> By the way - can you tell me what I have to do for answering in the mailing-list? I think I still don't understand how that works ;)
> With kind regards, Lukas

You simply reply to the e-mail (I assume that you do so). If you click
reply to all recipients than the mailing list address should appear as
either To or Cc. One thing that you should take care is to send only
plain text (no HTML).

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

  reply	other threads:[~2013-04-25  8:03 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 [this message]
2013-04-25 13:00   ` Aw: " Lukas Riezler
2013-04-25 13:03   ` 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=5178E338.3090307@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@sourceware.org \
    --cc=lukas.riezler@gmx.net \
    /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).