public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "André-John Mas" <ajmas@sympatico.ca>
To: Gary Thomas <gary@mlbassoc.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Reading flash config value from application
Date: Sun, 18 Jun 2006 03:28:00 -0000	[thread overview]
Message-ID: <654C0418-990F-4C1E-8636-99447A050A55@sympatico.ca> (raw)
In-Reply-To: <1150579533.8940.26.camel@hermes>

Oops, sorry for that. Thanks for the help.

Andre

On 17-Jun-06, at 17:25 , Gary Thomas wrote:

> On Fri, 2006-06-16 at 22:43 -0400, André-John Mas wrote:
>> Which package do I need to include in my ECC for this?
>
> Please keep your replies on the list so that all may benefit.
>
> No special packages are required;  just include <cyg/hal/hal_if.h>
>
>> Andre
>>
>> On 16-Jun-06, at 21:41 , Gary Thomas wrote:
>>
>>> On Fri, 2006-06-16 at 19:22 -0400, André-John Mas wrote:
>>>> Hi,
>>>>
>>>> I use fconfig in my redboot to set an IP address for my card.  
>>>> What is
>>>> the
>>>> best way to read this IP address from my application, since
>>>> flash_config.h
>>>> seems to be part of the Redboot package.
>>>
>>> You can do this using the Virtual Vectors interface into RedBoot.
>>> The call:
>>>   CYGACC_CALL_IF_FLASH_CFG_OP(CYGNUM_CALL_IF_FLASH_CFG_GET,
>>>                               <fconfig_name>,
>>>                               &result,
>>>                               <type>)
>>>
>>> Where <fconfig_name> is a string containing the 'fconfig' short
>>> name for
>>> the data item (use 'fc -l -n' to see what the names are).  The
>>> variable
>>> <type> defines the type of data.  You can find the #define's for  
>>> these
>>> in the include file "flash_config.h".
>>>
>>> Note: the result of this call is a boolean - true if the data was
>>> found, false if not.
>>>
>>> -- 
>>> ------------------------------------------------------------
>>> Gary Thomas                 |  Consulting for the
>>> MLB Associates              |    Embedded world
>>> ------------------------------------------------------------
>>>
>>>
>>> -- 
>>> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/
>>> ecos
>>> and search the list archive: http://ecos.sourceware.org/ml/ecos-
>>> discuss
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------


--
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:[~2006-06-18  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 23:23 André-John Mas
2006-06-17  1:41 ` Gary Thomas
     [not found]   ` <FAE7AB22-59C4-4C01-8C7E-AC3C86F6E3F1@sympatico.ca>
2006-06-17 21:25     ` Gary Thomas
2006-06-18  3:28       ` André-John Mas [this message]
2006-06-20 22:26 Andre-John Mas
2006-06-21  2:15 ` Gary Thomas

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=654C0418-990F-4C1E-8636-99447A050A55@sympatico.ca \
    --to=ajmas@sympatico.ca \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).