From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29406 invoked by alias); 6 Jul 2007 21:14:23 -0000 Received: (qmail 29394 invoked by uid 22791); 6 Jul 2007 21:14:22 -0000 X-Spam-Check-By: sourceware.org Received: from stelecom.gomel.by (HELO stelecom.gomel.by) (82.209.213.61) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 06 Jul 2007 21:14:16 +0000 Received: from localhost (localhost [127.0.0.1]) by stelecom.gomel.by (Postfix) with ESMTP id 1707CB01D4A7; Sat, 7 Jul 2007 00:14:14 +0300 (EEST) Received: from stelecom.gomel.by ([127.0.0.1]) by localhost (stelecom.gomel.by [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06230-06; Sat, 7 Jul 2007 00:14:12 +0300 (EEST) Received: from localhost (unknown [82.209.209.41]) by stelecom.gomel.by (Postfix) with ESMTP id 42A17B001369; Sat, 7 Jul 2007 00:14:12 +0300 (EEST) Date: Fri, 06 Jul 2007 21:14:00 -0000 From: Sergei Gavrikov To: Tales Toledo Cc: ecos-discuss@ecos.sourceware.org Message-ID: <20070706211314.GA12393@ubuntu> References: <2308fb0f0707061132x678e5b47t772bf866104090a7@mail.gmail.com> <20070706191055.GA10570@ubuntu> <2308fb0f0707061237k630fdea4y7e3c148aa213f16c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2308fb0f0707061237k630fdea4y7e3c148aa213f16c@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] How to enable diag_printf at Redboot X-SW-Source: 2007-07/txt/msg00070.txt.bz2 On Fri, Jul 06, 2007 at 04:37:47PM -0300, Tales Toledo wrote: > On 7/6/07, Sergei Gavrikov 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... Ah, I did pass your vis-a-vis dialog with Gary. I'm seeing now what is your issue. That is a flash config issue, isn't that? I look at some RedBoot options/semaphores and found this one cdl_option CYGSEM_REDBOOT_FLASH_CONFIG_READONLY_FALLBACK {user_value 1}; Perhaps, some fail(s) protected itself by such a way? But, you told that fconfig copy in RAM is good. Did you tried to change the default flash config block number (cdl_option CYGNUM_REDBOOT_FLASH_CONFIG_BLOCK) ? Execuse me that my useless suggest about DEBUG* options. I would play with a set of the CYG*REDBOOT*FLASH*CONFIG defaults at the end: editing `ecos.ecc' and re-building RedBoot. But that can take your whole weekend. Regards, Sergei -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss