[ECOS] Redboot rebuild problem

[ECOS] Redboot rebuild problem

[Wang, Liu (Liu)]

The following command "ecosconfig new se7751 reboot" in cygwin gives
the following warnings.

...............
ecos.db, package CYGPKG_HAL: warning
    Version subdirectory `common' does not have a CDL script `hal.cdl'.
ecos.db, package CYGPKG_HAL: warning
    This package does not have any valid version subdirectories.
ecos.db, package CYGPKG_INFRA: warning
    Version subdirectory `infra' does not have a CDL script `infra.cdl'.
...............
Hardware selection: warning
    The target specification lists a package `CYGPKG_HAL_SH' which is
not presen
t in the component repository.
Hardware selection: warning
    The target specification lists a package `CYGPKG_HAL_SH_SH4' which
is not pr
esent in the component repository.
Hardware selection: warning
    The target specification lists a package
`CYGPKG_HAL_SH_SH7751_SE7751' which
 is not present in the component repository.
...............

File 'ecos.db" has been changed by adding "/v2_0/cdl" to all the
directories of all packages. The first portion of the above warnings
gone. The second portion of the above warning are still there.

Your help will be highly appreciated in fixing the above warnings.

Regards,

Liu Wang
Software/Firmware Engineer
10C-359B LVC
1110 American Pkwy, Allentown
PA 18109, USA
(610)712-3472(o)
liuwang@agere.com




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

Re: [ECOS] Redboot rebuild problem

[Gary Thomas]

On Tue, 2005-10-25 at 17:41 -0400, Wang, Liu (Liu) wrote:
> The following command "ecosconfig new se7751 reboot" in cygwin gives
> the following warnings.
> 
> ...............
> ecos.db, package CYGPKG_HAL: warning
>     Version subdirectory `common' does not have a CDL script `hal.cdl'.
> ecos.db, package CYGPKG_HAL: warning
>     This package does not have any valid version subdirectories.
> ecos.db, package CYGPKG_INFRA: warning
>     Version subdirectory `infra' does not have a CDL script `infra.cdl'.
> ...............
> Hardware selection: warning
>     The target specification lists a package `CYGPKG_HAL_SH' which is
> not presen
> t in the component repository.
> Hardware selection: warning
>     The target specification lists a package `CYGPKG_HAL_SH_SH4' which
> is not pr
> esent in the component repository.
> Hardware selection: warning
>     The target specification lists a package
> `CYGPKG_HAL_SH_SH7751_SE7751' which
>  is not present in the component repository.
> ...............
> 
> File 'ecos.db" has been changed by adding "/v2_0/cdl" to all the
> directories of all packages. The first portion of the above warnings
> gone. The second portion of the above warning are still there.
> 
> Your help will be highly appreciated in fixing the above warnings.

Why are you messing with the paths (as you mention above)?

I'd suggest that you just start by downloading the latest CVS tree
and everything will just work.
  http://ecos.sourceware.org/anoncvs.html

-- 
------------------------------------------------------------
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

[ECOS] Byte array address alignement

[Michael Anburaj]

Hi,

I have very general compiler question. Since, there are a lot of experts 
here, I am sure I will get an answer :)

I see that most compiler follow this alignment rule for byte arrays (I guess 
structures too), that they get aligned at least on a 4byte boundary on a 
32bit machine (like ARM or MIPS32 & so on).

I donÂ’t know if this alignment is an artifact of something else or the 
tool-chain has a rule as such for doing so.

Can anyone who is familiar with this, throw some light on this subject?
1.	I am curious to know if such a rule exists in C compilers?
2.	If so, what is it called? It will be great if you could point me to some 
matrial.

Thanks a lot,
-Mike.

Sample code:

Char C1;
Char C2[8];
Char C3;

&C1 is equal to 0x800001
&C2 is equal to 0x800004
&C3 is equal to 0x800002



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

RE: [ECOS] Byte array address alignement

[Paul D. DeRocco]

> From: Michael Anburaj
>
> I have very general compiler question. Since, there are a lot of experts
> here, I am sure I will get an answer :)
>
> I see that most compiler follow this alignment rule for byte
> arrays (I guess
> structures too), that they get aligned at least on a 4byte boundary on a
> 32bit machine (like ARM or MIPS32 & so on).
>
> I donÂ’t know if this alignment is an artifact of something else or the
> tool-chain has a rule as such for doing so.
>
> Can anyone who is familiar with this, throw some light on this subject?
> 1.	I am curious to know if such a rule exists in C compilers?
> 2.	If so, what is it called? It will be great if you could
> point me to some
> matrial.
>
> Thanks a lot,
> -Mike.
>
> Sample code:
>
> Char C1;
> Char C2[8];
> Char C3;
>
> &C1 is equal to 0x800001
> &C2 is equal to 0x800004
> &C3 is equal to 0x800002

I don't think all compilers do that. I don't recall the old Borland x86
compiler doing that, and I used it for years. My guess is that this version
does that in order to work better with functions like memset and memcpy,
which generally play tricks to use full word memory accesses rather than
byte accesses.

--

Ciao,               Paul D. DeRocco
Paul                mailto:pderocco@ix.netcom.com


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