headers
Gary Thomas | 2 Oct 2003 14:44
Favicon

Targets with overrides

I'd like to add some targets to ecos.db which contain explicit CDL
overrides (e.g. to force a particular board configuration).  I know
in the past we avoided doing this because the public tools might not
handle it, but it's now many years on and the tools are all new enough.

Is there any dissension to my making such a change?

--

-- 
Gary Thomas <gary <at> mlbassoc.com>
MLB Associates
Permalink | Reply | 6 comments |
headers
John Dallaway | 2 Oct 2003 15:11
Favicon

Re: Targets with overrides

Hi Gary

One of the reasons we have avoided this technique in public sources is that 
the implementation is not fully integrated with the rest of the CDL 
library. For example, the values you provide for options you override do 
not become the CDL default values. The configtool therefore indicates that 
the options have been changed and allows you to restore the default value 
which would effectively change the target and confuse the "run tests" 
capability of the tool. Without improved integration, I would prefer to 
avoid the use of this technique in the public repository.

John Dallaway
eCosCentric Limited

-----Original Message-----
From: Gary Thomas
Date: Thursday 02 Oct 2003 13:44
Subject: Targets with overrides

> I'd like to add some targets to ecos.db which contain explicit CDL
> overrides (e.g. to force a particular board configuration).  I know
> in the past we avoided doing this because the public tools might not
> handle it, but it's now many years on and the tools are all new enough.
>
> Is there any dissension to my making such a change?
Permalink | Reply | 1 comment |
headers
Gary Thomas | 2 Oct 2003 15:27
Favicon

Re: Targets with overrides

On Thu, 2003-10-02 at 07:11, John Dallaway wrote:
> Hi Gary
> 
> One of the reasons we have avoided this technique in public sources is that 
> the implementation is not fully integrated with the rest of the CDL 
> library. For example, the values you provide for options you override do 
> not become the CDL default values. The configtool therefore indicates that 
> the options have been changed and allows you to restore the default value 
> which would effectively change the target and confuse the "run tests" 
> capability of the tool. Without improved integration, I would prefer to 
> avoid the use of this technique in the public repository.
> 

I understand, but I think that the potential benefits far outweigh the
problems.  If someone wants to mess with options that have been 
inferred, then he's asking for trouble anyway.  There are already many
other such inferences happening that are not part of target descriptions
anyway.

In the case I'm most interested in, I have a set of platforms which 
share the same HAL but which need very specific setups to run properly.
As is, we have to document the details of how to set this up which can
be sources of errors.  If I had a target which described the platform
explicitly, then this source of errors is mitigated.  I'd much rather
live with the potential that someone *could* mess up "run tests" in
the ConfigTool than a more serious situation where he can easily turn
his unit into a brick by missing a step in the setups.

> John Dallaway
> eCosCentric Limited
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ashwin Patwekar | 3 Oct 2003 07:27
Favicon

problems Porting to LPC2106

Hello All ,

I am trying to port ecos to the arm7 tdmi processor LPC2106 from philips on
the ashling eval board.

I am having problems defining the meory layout. In the reference guide it
says that the configuration tool can be used to generate the memory layout
files but I find no option to do this.

Can any one please help me with this
my ram starts at  0x40000000 and size is 0x10000
my flash starts at 0x0 and size is 0x20000

I tried editing the  header files but when i compile and link hello then I
get error
/ecos-c/PFARM/gnuarm/bin/../lib/gcc-lib/arm-elf/3.2.1/../../../../arm-elf/bi
n/ld
: address 0x160 of hello section .fixed_vectors is not within region ram
/ecos-c/PFARM/gnuarm/bin/../lib/gcc-lib/arm-elf/3.2.1/../../../../arm-elf/bi
n/ld
: address 0x10040 of hello section .rom_vectors is not within region ram

Am I forgetting something ?

Thanks,
Ashwin
Permalink | Reply | 3 comments |
headers
Andrew Lunn | 3 Oct 2003 13:29
Picon

Re: Targets with overrides

On Thu, Oct 02, 2003 at 06:44:41AM -0600, Gary Thomas wrote:
> I'd like to add some targets to ecos.db which contain explicit CDL
> overrides (e.g. to force a particular board configuration).  I know
> in the past we avoided doing this because the public tools might not
> handle it, but it's now many years on and the tools are all new enough.

".. in the past..", was before my time and im not sure i understand
what you mean. Could you give a concrete example.

     Thanks
        Andrew
Permalink | Reply | 3 comments |
headers
Gary Thomas | 3 Oct 2003 14:20
Favicon

Re: Targets with overrides

On Fri, 2003-10-03 at 05:29, Andrew Lunn wrote:
> On Thu, Oct 02, 2003 at 06:44:41AM -0600, Gary Thomas wrote:
> > I'd like to add some targets to ecos.db which contain explicit CDL
> > overrides (e.g. to force a particular board configuration).  I know
> > in the past we avoided doing this because the public tools might not
> > handle it, but it's now many years on and the tools are all new enough.
> 
> ".. in the past..", was before my time and im not sure i understand
> what you mean. Could you give a concrete example.
> 

Yes, long ago, we had some internal work that supported targets with
additional "configury".  It would look something like this:

        target viper2_866 {
                alias		{ "A&M Viper PPC866T board" viper866 }
        	packages        { CYGPKG_HAL_POWERPC
                                  CYGPKG_HAL_POWERPC_MPC8xx
                                  CYGPKG_HAL_POWERPC_VIPER
                                  CYGPKG_HAL_QUICC 
                                  CYGPKG_IO_SERIAL_POWERPC_QUICC_SMC
                                  CYGPKG_DEVS_ETH_POWERPC_FEC
                                  CYGPKG_DEVS_ETH_POWERPC_VIPER
                                  CYGPKG_DEVS_FLASH_VIPER
                                  CYGPKG_DEVS_FLASH_AMD_AM29XXXXX
                }
                set_value CYGHWR_HAL_POWERPC_MPC8XX "866T"
                set_value CYGHWR_HAL_POWERPC_VIPER_I  0 
                set_value CYGHWR_HAL_POWERPC_VIPER_II 1
                set_value CYGHWR_HAL_POWERPC_BOARD_SPEED 133
(Continue reading)

Permalink | Reply | 2 comments |
headers
Jani Monoses | 3 Oct 2003 14:09
Picon

Re: Targets with overrides

>                     This target provides the packages needed to run
>                     eCos on a A&M Viper PPC866 board."
>         }
>         
> The point would be that "ecosconfig new viper2_866" would create a 
> configuration with the model 866T and it's supporting options set
> properly.

Why can't this be done with an appropriate ecosconfig import after new ?

Jani
Permalink | Reply | 1 comment |
headers
Gary Thomas | 3 Oct 2003 14:27
Favicon

Re: Targets with overrides

On Fri, 2003-10-03 at 06:09, Jani Monoses wrote:
> >                     This target provides the packages needed to run
> >                     eCos on a A&M Viper PPC866 board."
> >         }
> >         
> > The point would be that "ecosconfig new viper2_866" would create a 
> > configuration with the model 866T and it's supporting options set
> > properly.
> 
> Why can't this be done with an appropriate ecosconfig import after new ?
> 

Absolutely.  It would just be nice to not have to use a separate step.

--

-- 
Gary Thomas <gary <at> mlbassoc.com>
MLB Associates
Permalink | Reply | 0 comments |
headers
Jonathan Larmour | 9 Oct 2003 05:06
Favicon

test mail - ignore

test
--

-- 
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine
Permalink | Reply | 0 comments |
headers
Hadi Dewan | 9 Oct 2003 15:37
Picon
Favicon

Help enquiring thread info in ecos

Hi,

I am running ecos on a sparc platform. I am using
insight 5.3 to do my debuging. Everything is fine
except when I do "thread info" I get the following 

RMT ERROR : failed to get remote thread list\n

I am not sure what I am doing wrong. I have enabled 
"gdb_multithreading_debug_support" what else do I need
.

              Hadi 

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
Permalink | Reply | 1 comment |

Gmane