public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: rob.wj.jansen@philips.com
To: sebastien.andre@sxb.bsf.alcatel.fr
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Question about Hello World eCos example
Date: Wed, 25 Jul 2001 07:52:00 -0000	[thread overview]
Message-ID: <OF7F3D9EBA.0A3AC39F-ONC1256A94.0050C994@diamond.philips.com> (raw)

Andre,

> i execute the program i receive on the HYPER-TERMINAL this :
> $O48656C6C6F2C2065436F7320776F726C64212035200A#BB

This is clearly GDB output.
During build it is decided that your output will always go via your GDB channel.
The reason why printf does not return is because you need to acknowledge this
packet (with a "+").

Same thing happened on my target. Try to remove the GDB stub and rebuild eCos.
If this fails, then search for the point where it is decided that your diagnostics output
has to be via GDB packets. I forgot where this was defined but I somewhere found
that GDB packetized output is done if you have either GDB stubs OR if you use
the RAM memory map (they forgot about JTAG debugging pods).

The diagnostics output is done from packages/hal/arm/pid/current/src/hal_diag.c.
Just place a breakpoint on the hal_diag_write_char() function and you will see.

Regards,

     Rob Jansen

Software Engineer
Competence Center Platforms
BU Mobile Communications
Meijhorst 60-10, 6537 KT Nijmegen, The Netherlands
Tel: +31-24-353-6329
Fax: +31-24-353-3613
mailto:Rob.WJ.Jansen@philips.com



             reply	other threads:[~2001-07-25  7:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25  7:52 rob.wj.jansen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-25  6:09 [ECOS] question about stack assign for interrupt service routine Tony Ko
2001-07-25  7:16 ` [ECOS] Question about Hello World eCos example Andre Sebastien
2001-07-25  7:38   ` Robin Farine
2001-07-25  8:14     ` Andre Sebastien
2001-07-25  8:45       ` Robin Farine
2001-07-25  9:11   ` David Airlie

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=OF7F3D9EBA.0A3AC39F-ONC1256A94.0050C994@diamond.philips.com \
    --to=rob.wj.jansen@philips.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=sebastien.andre@sxb.bsf.alcatel.fr \
    /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).