public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Tales Toledo" <toledo.tales@gmail.com>
To: "Sergei Gavrikov" <w3sg@softhome.net>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] How to enable diag_printf at Redboot
Date: Fri, 06 Jul 2007 19:37:00 -0000	[thread overview]
Message-ID: <2308fb0f0707061237k630fdea4y7e3c148aa213f16c@mail.gmail.com> (raw)
In-Reply-To: <20070706191055.GA10570@ubuntu>

On 7/6/07, Sergei Gavrikov <w3sg@softhome.net> wrote:
> On Fri, Jul 06, 2007 at 03:32:01PM -0300, Tales Toledo wrote:
> > Hi,
> >
> > I would like to enable all diag_printf messages at Redboot.
> > How can I do this?
> > Which cdl option should I have to enable to make it works?
>
> There are a lot of debug messages in RedBoot. That depends on packages
> are used to build RedBoot (RedBoot is a closely target related stuff).
> You can see that, U.T.S.L.
>
> find $ECOS_REPOSITORY/redboot/current/src | xargs grep DEBUG
>
> You can meet ZM_DEBUG, DEBUG_TCP, etc., etc., etc.
>
> but it seems, that more suitable way is to look at any CYGDBG_REDBOOT_*
> options in your `ecos.ecc' is prepared to build RedBoot
>

I enable CYGDBG_REDBOOT_NET_DEBUG that is the most important for me
right now. Unfortunately  I am having some problems with flash
configuration at boot that override it with 0.
I can't see any messages until now...

Thx anyway,
TT

> ecosconfig new <target> redboot
> ecosconfig import <redboot_{ROM|RAM|ROMRAM}.ecm>
> grep CYGDBG_REDBOOT ecos.ecc
>
> Sergei
>
> >
> > Thx,
> > TT
> >
> > --
> > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> > and search the list archive: 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:[~2007-07-06 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 18:32 Tales Toledo
2007-07-06 19:12 ` Sergei Gavrikov
2007-07-06 19:37   ` Tales Toledo [this message]
2007-07-06 21:14     ` Sergei Gavrikov
2007-07-09 15:45       ` Tales Toledo
2007-07-09 17:29         ` Sergei Gavrikov
2007-07-09 19:11           ` Tales Toledo
2007-07-09 21:48             ` Sergei Gavrikov
2007-07-10 19:24               ` Tales Toledo
2007-07-10 22:04                 ` Sergei Gavrikov
2007-07-12 21:00                   ` Tales Toledo
2007-07-12 21:37                     ` Sergei Gavrikov

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=2308fb0f0707061237k630fdea4y7e3c148aa213f16c@mail.gmail.com \
    --to=toledo.tales@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=w3sg@softhome.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).