public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Robin Farine <acnrf@dial.eunet.ch>
To: Andre Sebastien <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:38:00 -0000	[thread overview]
Message-ID: <86y9pd9iq7.fsf@halftrack.hq.acn-group.ch> (raw)
In-Reply-To: <3B5ED469.4A25761B@sxb.bsf.alcatel.fr>

Andre Sebastien <sebastien.andre@sxb.bsf.alcatel.fr> writes:

[...]

> It s exactly that i try to print : printf("Hello, eCos world! %d \n",5);
> 
> PS: what is $0 and #BB at the beginning and the end of output ?

Not $0, but $O (O packet). The GDB protocol uses such packets to output text
non-related to GDB itself (e.g. your printf). The protocol also appends a
checksum to every packet, the #BB in your case.

> But never the program go out the function "printf", it seems to go in a
> infinite loop !!!!!  What does it wrong ?

It's waiting for an ack from the remote side of a GDB connection !!!!!

Try to set the option below in your ecos.ecc:

    cdl_component CYGDBG_HAL_DIAG_TO_DEBUG_CHAN {
        user_value 0
    };

[...]

Robin

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2001-07-25  8:14     ` Andre Sebastien
2001-07-25  8:45       ` Robin Farine
2001-07-25  9:11   ` David Airlie
2001-07-25 11:26 ` [ECOS] question about stack assign for interrupt service routine Jonathan Larmour
2001-07-25 13:59   ` [ECOS] question about GCC for Arm Installation Grant Whitacre
2001-07-25 14:53     ` Jonathan Larmour
2001-07-25  7:52 [ECOS] Question about Hello World eCos example rob.wj.jansen

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=86y9pd9iq7.fsf@halftrack.hq.acn-group.ch \
    --to=acnrf@dial.eunet.ch \
    --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).