Re: [ECOS] create eCos on Linux

[Gary Thomas <gthomas at redhat dot com>]

On 10-Aug-2000 Guillermo GARCIA wrote:
>>     Gary> On 10-Aug-2000 Guillermo GARCIA wrote:
>>     >> Hi there,
>>     >>
>>     >> I'm lost with ecosconfig.
>>     >>
>>     >> [root@localhost ecos-work]# ecosconfig new edb7209
>>     >> ecosconfig: Symbol `__vt_9bad_alloc' has different size in shared
>>     >> object, consider re-linking
>>     >> ecosconfig: Symbol `__vt_9exception' has different size in shared
>>     >> object, consider re-linking
>>     >> Unknown target edb7209
>>     >>
>>     >> what did i forget ?
>>     >>
>>     >> the install of gcc, gdb and insight was done without problems.
>>     >> the ecos's rpm was installed without problems too.
>>     >> i set the ECOS_REPOSITORY=/opt/ecos/ecos-1.3.1/packages.
>>     >> i set the
>>     >> PATH=/opt/ecos/ecos-1.3.1/tools/bin:/tools/H-i686-pc-linux-gnu/bin:/sbin:/usr/sbin:/bin:/u
>>     >> sr/bin:/
>>     >> usr/X11R6/bin
>>
>>     Gary> This looks like an issue with 'ecosconfig' itself.
>>     Gary> What version of Linux are you running?
> 
> i'm using Mandrake 7.0
> 

I would be nice to know where the problem with the shared libraries is.
Can you send the output from:
  % ldd `which ecosconfig`

>> Bart>More accurately, it is a problem with the C++ runtime support that is
>> Bart>installed. There are complications here depending on which Linux
>> Bart>distribution you are using, whether or not you have upgraded the gcc
>> Bart>installation yourself, ... I have not seen the symbol size warnings
>> Bart>before but I suspect that they are harmless. If ecosconfig starts
>> Bart>SEGV'ing on you than that is an indication that C++ exception handling
>> Bart>is not working and that you need to rebuild ecosconfig from source.
> 
> i use gcc provided by Mandrake 7.0
> [root@localhost /]# gcc -v
> Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/specs
> gcc version 2.95.2 19991024 (release)
> what are the steps involved in order to rebuild ecosconfig ?
> 
>>     Gary> However, it doesn't seem to have affected the output. I
>>     Gary> think you need to tell ecosconfig where to find your source
>>     Gary> repository. In my case:
>>     Gary>   % ECOS_REPOSITORY=/work2/ecc/ecc
> 
> what is the source repository because on the docs the ECOS_REPOSITORY is
> /opt/ecos/ecos-1.3.1/packages.
> 

What you've chosen is just fine (sorry I missed it during my first reading).

> 
>>     Gary> The other thing, you probably want to use 'edb7212', not
>>     Gary> 'edb7209'. The 7209 has no DRAM controller and thus no
>>     Gary> memory. Not much use for anything but ROM based
>>     Gary> applications.
> 
> but i have the CIRRUS LOGIC EP7209 Development Kit, do i really have to use
> 'edb7212' instead of 'edb7209' ?
> 

Yes.  Even if your board and chip are labelled 7209, you really have a 7212
if the board has any DRAM :-)  Of course if you don't have any DRAM that 
would be a whole other consideration :-)

Based on the information you sent (ecosconfig list) and the fact that you're
working from the 1.3.1 version (very old, that), you'll need to do this
instead:

  % ecosconfig new edb7xxx 
  % ecosconfig import config.edb7212
  % ecosconfig tree

Where 'config.edb7212' looks like this:

======= cut here - config.edb7212 ===========================================
cdl_option CYGHWR_HAL_ARM_EDB7XXX_VARIANT {
    user_value EP7212
};
======= cut here - config.edb7212 ===========================================

Of course, since I know you're wanting to get the GoAhead web server working,
you probably really want to use this:

  % ecosconfig new edb7xxx net
  % ecosconfig import config.edb7212
  % ecosconfig tree

Where 'config.edb7212' looks like this:

======= cut here - config.edb7212 ===========================================
cdl_option CYGHWR_HAL_ARM_EDB7XXX_VARIANT {
    user_value EP7212
};

cdl_option CYGNUM_LIBC_MALLOC_MEMPOOL_SIZE {
    user_value 1638400
};
======= cut here - config.edb7212 ===========================================


Let me/us know if this helps.