ECOS

Started by Billy September 6, 2004
I saw some months ago a patch for ecos but then it was withdrawn
Has any1 taken this further?
regards Billy



An Engineer's Guide to the LPC2100 Series

--- In , "Billy" <billygadget@y...> wrote:
> I saw some months ago a patch for ecos but then it was withdrawn
> Has any1 taken this further?
> regards Billy

Hello,

That patch is working. However many configuration options are not
implemented, and some part of the assembly startup is absolutly
unnecessary (Some IT enable part and other absolutly board specific
code).

Writing such a port also not a too comlicated method, only a few line
of code is required.

Are you sure it is not downloadable? (I think i have the original
patch, and some modification, but I also not implemented the
configuration related part of it)

Bals




I found the patch (I suppose your are talking about) here:
http://bugs.ecos.sourceware.org/show_bug.cgi?id00068
I'm having some install problems so if anyone could let me know how
to properly apply the patch and then build ecos that would be very
much appreciated.

Teun

--- In , "balazs_scherer" <scheba@f...> wrote:
> --- In , "Billy" <billygadget@y...> wrote:
> > I saw some months ago a patch for ecos but then it was withdrawn
> > Has any1 taken this further?
> > regards Billy
>
> Hello,
>
> That patch is working. However many configuration options are not
> implemented, and some part of the assembly startup is absolutly
> unnecessary (Some IT enable part and other absolutly board specific
> code).
>
> Writing such a port also not a too comlicated method, only a few
line
> of code is required.
>
> Are you sure it is not downloadable? (I think i have the original
> patch, and some modification, but I also not implemented the
> configuration related part of it)
>
> Bals





Hello,

If you have run the patch it created some sub directory.
(I suppose you have run it under the ecosxxx/packages subdirectory)

These directories are practically useless, because the patch is for
an old ecos version, but you have the platform specific c, and header
files.
So create an ashling library under the packages/hal/arm/ and
copy the contains of the current directory to it.

After this you have to modify the ecos.db file containing the package
descriptions. Use the pach created ecos.db file and copy its ashling
board related content to the original ecos.db file. Don not forget to
modify the directories part of the package descriptions. You could do
the same things to the serial driver part of the pach too.

After the modification of the ecos.db use the ecos configuration tool
and try to use the new ashlig packages.

If you have different platform than the ashlig board do not forget,
that the startup part enables one interrupt, and makes the PLL init,
therefore some modification could be needed in this part
hal_platfor_setup.h.

Good luck for using the port. If you unable to make it work write me
an e-mail and I will send you my version of the port. It also not
100%, because some of the ecos configuration part option is not
realized, but it is working fine).

Bals
--- In , "teunvandeberg"
<teun.van.de.berg@p...> wrote:
> I found the patch (I suppose your are talking about) here:
> http://bugs.ecos.sourceware.org/show_bug.cgi?id00068
> I'm having some install problems so if anyone could let me know how
> to properly apply the patch and then build ecos that would be very
> much appreciated.
>
> Teun
>
> --- In , "balazs_scherer" <scheba@f...>
wrote:
> > --- In , "Billy" <billygadget@y...> wrote:
> > > I saw some months ago a patch for ecos but then it was withdrawn
> > > Has any1 taken this further?
> > > regards Billy
> >
> > Hello,
> >
> > That patch is working. However many configuration options are not
> > implemented, and some part of the assembly startup is absolutly
> > unnecessary (Some IT enable part and other absolutly board
specific
> > code).
> >
> > Writing such a port also not a too comlicated method, only a few
> line
> > of code is required.
> >
> > Are you sure it is not downloadable? (I think i have the original
> > patch, and some modification, but I also not implemented the
> > configuration related part of it)
> >
> > Bals





Thanks! Installing works fine now. Running is a different thing
though :(
I'm trying to get the hello example running. I have a recent version
of eCos and patched it. Then I build eCos, which goes fine, though if
I run the tests I get:

/opt/ecos/gnutools/arm-elf/bin/../lib/gcc-lib/arm-
elf/3.2.1/../../../../arm-elf/bin/ld: address 0x400144e4 of /ecos-
c/cygwin/opt/ecos/ecos-2.0/ecos-
work/testashling_install/tests/infra/current/tests/cxxsupp
section .bss is not within region ram
collect2: ld returned 1 exit status

I guess that's not important because the test is just to big for the
memory. After that, I build the hello example (with the supplied
Makefile) and I get two files. hello (86k) and hello.o (1k). I needed
to convert the files to hex for the flasher to work. Both are
converted to hex using arm-elf-objcopy, but if I convert hello to hex
I cannot flash it (the file is to big). Hello can be converted to hex
and flashed but the board stays dead. I looked into both (bin) files
with a hex editor and found the following.
Hello.o is very small and only contains the Hello World sample code,
no OS (I think). Hello contains a lot of data but I guess it contains
a lot of useless stuff. The first half of the file (except for the
very beginning) is filled with zero's. I believe we used to open this
file in GDB -> insight but that doesn't work anymore.
My guess is that I am compiling / linking it wrong or that I
completely misunderstand something here. Do you have a clue?
Thank you in advance!

Also I am interested in your port, so if you would be willing to send
it to me I would appreciate it very much!

Teun van de Berg --- In , "balazs_scherer" <scheba@f...> wrote:
> Hello,
>
> If you have run the patch it created some sub directory.
> (I suppose you have run it under the ecosxxx/packages subdirectory)
>
> These directories are practically useless, because the patch is for
> an old ecos version, but you have the platform specific c, and
header
> files.
> So create an ashling library under the packages/hal/arm/ and
> copy the contains of the current directory to it.
>
> After this you have to modify the ecos.db file containing the
package
> descriptions. Use the pach created ecos.db file and copy its
ashling
> board related content to the original ecos.db file. Don not forget
to
> modify the directories part of the package descriptions. You could
do
> the same things to the serial driver part of the pach too.
>
> After the modification of the ecos.db use the ecos configuration
tool
> and try to use the new ashlig packages.
>
> If you have different platform than the ashlig board do not forget,
> that the startup part enables one interrupt, and makes the PLL
init,
> therefore some modification could be needed in this part
> hal_platfor_setup.h.
>
> Good luck for using the port. If you unable to make it work write
me
> an e-mail and I will send you my version of the port. It also not
> 100%, because some of the ecos configuration part option is not
> realized, but it is working fine).
>
> Bals >
> --- In , "teunvandeberg"
> <teun.van.de.berg@p...> wrote:
> > I found the patch (I suppose your are talking about) here:
> > http://bugs.ecos.sourceware.org/show_bug.cgi?id00068
> > I'm having some install problems so if anyone could let me know
how
> > to properly apply the patch and then build ecos that would be
very
> > much appreciated.
> >
> > Teun
> >
> > --- In , "balazs_scherer" <scheba@f...>
> wrote:
> > > --- In , "Billy" <billygadget@y...>
wrote:
> > > > I saw some months ago a patch for ecos but then it was
withdrawn
> > > > Has any1 taken this further?
> > > > regards Billy
> > >
> > > Hello,
> > >
> > > That patch is working. However many configuration options are
not
> > > implemented, and some part of the assembly startup is absolutly
> > > unnecessary (Some IT enable part and other absolutly board
> specific
> > > code).
> > >
> > > Writing such a port also not a too comlicated method, only a
few
> > line
> > > of code is required.
> > >
> > > Are you sure it is not downloadable? (I think i have the
original
> > > patch, and some modification, but I also not implemented the
> > > configuration related part of it)
> > >
> > > Bals