This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: jffs2 missing files


On Thu, 2003-12-11 at 16:15, Brian Pomerantz wrote:
> On Thu, Dec 11, 2003 at 09:21:54AM -0800, Brian Pomerantz wrote:
> > 
> > Today I'll see if I can figure out why the size is being reported
> > wrong.  I would certainly appreciate some ideas on why when I hard
> > code the partition size to the size that it should be, I get this
> > illegal memory access.
> > 
> 
> Okay, I guess I'm just finding this whole configuration system a bit
> confusing.  Turns out I didn't have /dev/flash1 get configured via
> FIS.  When I changed CYGNUM_IO_FLASH_BLOCK_CFG_STATIC_1 from 1 to 0
> and CYGNUM_IO_FLASH_BLOCK_CFG_FIS_1 from 0 to 1, then mounting my
> partition works just fine and the whole thing is seen.
> 
> So, I guess most of my problems were configuration related.  Only the
> header file issue in compr.c remains though it sounds like it must be
> under control.
> 
> I just started looking at redboot this week and am not sure I
> understand the configuration model.  Is it generally accepted that the
> the default .cdl files get changed and subsequently merged when
> updating from cvs/tarballs?  Or is there some other less intrusive way
> of changing options via a config file or something else that overrides
> the defaults?

In general, there is no need to modify the .cdl files in the field.
The way that you control a configuration is  by using one of these:
  * the GUI ConfigTool
  * hand-editing the "ecos.ecc" database in your build directory
  * using .ecm scripts to manipulate data items
I normally use a combination of the last two.

For example, to build a version of RedBoot on a platform that needs some
tweaks/setup, one would follow these steps:
  % ecosconfig new target redboot
  % ecosconfig import target_special.ecm
  % ecosconfig tree
The 'import' step modifies the "ecos.ecc" database in place.  The 'tree'
step generates all of the files (Makefiles, headers, etc) for the build.
You could also:
  % edit ecos.ecc
  ... fiddle with some parameters
  % ecosconfig tree

-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]