From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5599 invoked by alias); 10 Jul 2007 19:24:07 -0000 Received: (qmail 5588 invoked by uid 22791); 10 Jul 2007 19:24:06 -0000 X-Spam-Check-By: sourceware.org Received: from wr-out-0506.google.com (HELO wr-out-0506.google.com) (64.233.184.231) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 10 Jul 2007 19:24:02 +0000 Received: by wr-out-0506.google.com with SMTP id 55so650537wri for ; Tue, 10 Jul 2007 12:23:59 -0700 (PDT) Received: by 10.90.94.2 with SMTP id r2mr3428533agb.1184095439261; Tue, 10 Jul 2007 12:23:59 -0700 (PDT) Received: by 10.90.65.12 with HTTP; Tue, 10 Jul 2007 12:23:59 -0700 (PDT) Message-ID: <2308fb0f0707101223k78efbaa0t1a809824859be2b5@mail.gmail.com> Date: Tue, 10 Jul 2007 19:24:00 -0000 From: "Tales Toledo" To: "Sergei Gavrikov" Cc: ecos-discuss@ecos.sourceware.org In-Reply-To: <20070709214653.GA16045@ubuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2308fb0f0707061132x678e5b47t772bf866104090a7@mail.gmail.com> <20070706191055.GA10570@ubuntu> <2308fb0f0707061237k630fdea4y7e3c148aa213f16c@mail.gmail.com> <20070706211314.GA12393@ubuntu> <2308fb0f0707090845i122a5131v7a307e3969b79ed7@mail.gmail.com> <20070709172751.GA10396@ubuntu> <2308fb0f0707091211w2c6b0fb0xc1f4354e0eda9b65@mail.gmail.com> <20070709214653.GA16045@ubuntu> 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/msg00097.txt.bz2 On 7/9/07, Sergei Gavrikov wrote: > On Mon, Jul 09, 2007 at 04:11:52PM -0300, Tales Toledo wrote: > > On 7/9/07, Sergei Gavrikov wrote: > > >On Mon, Jul 09, 2007 at 12:45:16PM -0300, Tales Toledo wrote: > > >> On 7/6/07, Sergei Gavrikov wrote: > > >> >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}; > > >> > > >> Yes, I believe it could be a flash config problem. I have tried it but > > >> with no success. I am still having the same behavior. The flash was > > >> written (I'm sure because i can dump and see the ip address > > >> server/mask/gateway) but seems that Redboot don't take this > > >> configuration from flash at boot up. > > >> > > >> > > > >> >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) ? > > >> > > >> I also change it. Should I see the differences at fis list command? I > > >> choose -4 as example and the Redboot config remains at 0x407FF000. It > > >> should be at 0x407FA000. Did i understand the cdl_option right? > > > > > >That has an effect, if this option is turnned off: > > > > > >cdl_option CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG {user_falue 0}; > > > ^^^^^^^^^^^^ > > >So, try such an import before make > > > > > You were right. I was using > > CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG {user_value 1};. > > > > >... > > >cat <<_EOF | ecosconfig import /dev/stdin > > >cdl_option CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG {user_value 0}; > > >cdl_option CYGNUM_REDBOOT_FLASH_CONFIG_BLOCK {user_value -4}; > > >_EOF > > > > > >Then fulfil `fconf -i', `fis init -f' as you do it as well and compare > > >the `fis list' results. I get the expected changes on my target. > > > > > With cdl_option CYGNUM_REDBOOT_FLASH_CONFIG_BLOCK {user_value -3}; I got > > RedBoot> fis list > > Name FLASH addr Mem addr Length Entry point > > RedBoot 0x40000000 0x40000000 0x00030000 0x00000000 > > RedBoot config 0x407D0000 0x407D0000 0x00001000 0x00000000 > > FIS directory 0x407F0000 0x407F0000 0x00010000 0x00000000 > > > > It works BUT... the problem is still present. Redboot doesn't seem to > > read boot configuration from flash. > > I again did review your previous RedBoot dumps. You known/sure that is > 1) RAM copy of `fconfig' is correct, 2) Written flash copy of `fconfig' > seems or is correct too, there are a valid human readable chunks at the > least, Just checking ... 1) and 2) Ok. You can see as follow RedBoot> fconfig -i Initialize non-volatile configuration - continue (y/n)? y Run script at boot: false Use BOOTP for network configuration: false Gateway IP address: 192.168.1.1 Local IP address: 192.168.1.100 Local IP address mask: 255.255.255.0 Default server IP address: 192.168.1.1 DNS domain name: DNS server IP address: 192.168.1.1 Network hardware address [MAC]: 0x7C:0x71:0x43:0xA6:0x7C:0x92 GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Update RedBoot non-volatile configuration - continue (y/n)? y ... Erase from 0x407d0000-0x407d1000: . ... Program from 0x01fe3000-0x01fe4000 at 0x407d0000: . RedBoot> ck RedBoot> cksum usage: cksum -b -l RedBoot> cksum -b 0x01fe3000 -l 0x1000 POSIX cksum = 2836439824 4096 (0xa910a310 0x00001000) RedBoot> cksum -b 0x407d0000 -l 0x1000 POSIX cksum = 2836439824 4096 (0xa910a310 0x00001000) RedBoot> >3) you don't see the BAD magic values in your dumps (0x0BADFACE > or 0xDEADDEAD). RedBoot> dump -b 0x407d0000 -l 0x1000 407D0000: 00 00 10 00 0B AD FA CE 01 0C 01 00 62 6F 6F 74 |............boot| 407D0010: 5F 73 63 72 69 70 74 00 00 00 00 00 04 11 01 0C |_script.........| 407D0020: 62 6F 6F 74 5F 73 63 72 69 70 74 5F 64 61 74 61 |boot_script_data| 407D0030: 00 62 6F 6F 74 5F 73 63 72 69 70 74 00 00 00 00 |.boot_script....| I can see 0x0BADFACE... I miss this point, what is wrong with that? >4) You did disable a caching. Is it right? But you get > these lines on every reboot: If I disable caching with "Redboot>cache off" my console stays to slow and loose some characters every time I type ;-( . This is the next step. Why did it happen? > > **Warning** FLASH configuration checksum error or invalid key > "Use 'fconfig -i' to [re]initialize database > > That stop point is placed here (you saw): fconfig.c:load_flash_config(). > > if ((flash_crc(config) != config->cksum) || > (config->key1 != CONFIG_KEY1)|| (config->key2 != CONFIG_KEY2)) { > > and, if you sure that you don't meet that magic cookies in your dumps, > therefore, it's needed look at flash_crc(), isn't it? > > There is a stone in that proc, this is REDBOOT_FLASH_REVERSE_BYTEORDER > (look on the flash_crc(), please). And I wonder about your settings in > your ecos.ecc too. I believe that cyg_crc32 calculates all okay :) but > what do you think about those lines: > > if (swabbed) > conf_endian_fixup(conf); > > it's possible that is wrong set of the REDBOOT_FLASH_REVERSE_BYTEORDER > value is your issue. Check that, please. Insert your own additional diag > prints into flash_crc to print direct and endian fixed values. And use > RedBoot's `cksum' command to calculate the check sums for RAM fconfig > copy and FLASH fconfig copy. > I will check this but I think it can't be wrong since my environment is based on viper that works fine for all. > > 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