From: "St. Zarifakis" <stz@swistec.de>
To: ajmas@bigfoot.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] re: Reading flash config value from application
Date: Wed, 21 Jun 2006 16:04:00 -0000 [thread overview]
Message-ID: <44996DF7.1090605@swistec.de> (raw)
In-Reply-To: <20060621153425.EFDW10262.tomts22-srv.bellnexxia.net@smtp1.sympatico.ca>
Hi,
Andre-John Mas wrote:
>Hi,
>
>Just tried the code below and the 'CYGACC_CALL_IF_FLASH_CFG_OP' call returns false, just as in the code I had.
>
>Its possible as Thomas suggests that maybe I have code which does not match what Gary has. I am currrently using 2.0.51, I believe.
>
>
Could you try the following code ? It should display all available
variables. It works on my system which is eCosCentric's v2.0.50:
HTH
Stamatis
#include <stdio.h>
#include <pkgconf/hal.h>
#include <cyg/hal/hal_if.h>
#include <cyg/infra/diag.h>
void test_func(void)
{
// Testfunktion 1: Ausgabe der fconfig-Variablen
struct cyg_fconfig fc;
char key[64];
diag_printf("fconfig test started\n");
fc.offset = 0;
fc.key = key;
fc.keylen = sizeof(key);
while (CYGACC_CALL_IF_FLASH_CFG_OP2(CYGNUM_CALL_IF_FLASH_CFG_NEXT,
&fc)) {
diag_printf(" Offset: %d, key: '%s', type: %d\n", fc.offset,
fc.key, fc.type);
fc.keylen = sizeof(key);
}
// zurück
diag_printf("... done\n");
return;
}
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-06-21 16:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 15:34 Andre-John Mas
2006-06-21 15:40 ` Gary Thomas
2006-06-21 16:04 ` St. Zarifakis [this message]
2006-06-22 12:58 ` [ECOS] " John Dallaway
2006-06-21 18:11 Re: [ECOS] " Andre-John Mas
2006-06-22 9:21 ` St. Zarifakis
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=44996DF7.1090605@swistec.de \
--to=stz@swistec.de \
--cc=ajmas@bigfoot.com \
--cc=ecos-discuss@sources.redhat.com \
/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).