Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Thread

Re: Efsl-devel digest, Vol 1 #33 - 1 msg

Re: Efsl-devel digest, Vol 1 #33 - 1 msg

2006-02-08 by Steve Franks

Yea Efsl!  I downloaded, read the manual, compiled on GCC for arm and
tested inside an hour, no problems.  That's what I call smooth code.

Efsl tested on IAR/Olimex LPC2148 Kickstart board built with current
GCC-Arm (4.0.2) and old SanDisk 32MB SD with FAT16; status: no
problems encountered.  Only edits were to rename LPC2138-ROM.ld to
LPC2148-ROM.ld, change processor from lpc2138 to lpc2148 in makefile,
and rename lpc-config.h to config.h.

Steve

Re: [lpc2000] Re: Efsl-devel digest, Vol 1 #33 - 1 msg

2006-02-15 by Jim Parziale

On 2/8/06, Steve Franks <stevefranks@...> wrote:
>
>  Yea Efsl!  I downloaded, read the manual, compiled on GCC for arm and
> tested inside an hour, no problems.  That's what I call smooth code.
>
> Efsl tested on IAR/Olimex LPC2148 Kickstart board built with current
> GCC-Arm (4.0.2) and old SanDisk 32MB SD with FAT16; status: no
> problems encountered.  Only edits were to rename LPC2138-ROM.ld to
> LPC2148-ROM.ld, change processor from lpc2138 to lpc2148 in makefile,
> and rename lpc-config.h to config.h.
>
> Steve
>
>
Sounds excellent!
Just for info, which version are you using?
Latest stable = 0.2.6
Latest development = 0.3.5
They seem to be very different from each other.

--
Jim Parziale
nuncio.bitis@...
Malden, MA


[Non-text portions of this message have been removed]

Re: Re: Efsl-devel digest, Vol 1 #33 - 1 msg

2006-02-16 by Steve Franks

Re Efsl: I was using the stable branch.  There was a warning somewhere
that the devel branch was not for use and some things were
unimplemented.

Steve

Re: Efsl-devel digest, Vol 1 #33 - 1 msg

2006-04-16 by darcyw@satlan.co.nz

>  Yea Efsl!  I downloaded, read the manual, compiled on GCC for arm and
>tested inside an hour, no problems.  That's what I call smooth code.
>
>Efsl tested on IAR/Olimex LPC2148 Kickstart board built with current
>GCC-Arm (4.0.2) and old SanDisk 32MB SD with FAT16; status: no
>problems encountered.  Only edits were to rename LPC2138-ROM.ld to
>LPC2148-ROM.ld, change processor from lpc2138 to lpc2148 in makefile,
>and rename lpc-config.h to config.h.
>
>Steve

Hi Steve,

Could you please post this somewhere for newbies such as myself to get a better understanding of how this all works?  :)  I've used IDEs for so many years and am now trying to use GCC but have very little understanding of makefiles.  I've tried porting EFSL over but just end up with so many make errors I give up in frustration.

Kind Regards
Darcy

Re: Efsl-devel digest, Vol 1 #33 - 1 msg

2006-04-16 by rtstofer

--- In lpc2000@yahoogroups.com, darcyw@... wrote:
>
> >  Yea Efsl!  I downloaded, read the manual, compiled on GCC for arm and
> >tested inside an hour, no problems.  That's what I call smooth code.
> >
> >Efsl tested on IAR/Olimex LPC2148 Kickstart board built with current
> >GCC-Arm (4.0.2) and old SanDisk 32MB SD with FAT16; status: no
> >problems encountered.  Only edits were to rename LPC2138-ROM.ld to
> >LPC2148-ROM.ld, change processor from lpc2138 to lpc2148 in makefile,
> >and rename lpc-config.h to config.h.
> >
> >Steve
> 
> Hi Steve,
> 
> Could you please post this somewhere for newbies such as myself to
get a better understanding of how this all works?  :)  I've used IDEs
for so many years and am now trying to use GCC but have very little
understanding of makefiles.  I've tried porting EFSL over but just end
up with so many make errors I give up in frustration.
> 
> Kind Regards
> Darcy
>

Just for fun, I downloaded EFSL and compiled it to create an AVR
library and an ARM library using the respective GNU toolchains.  No
warnings or errors.  The instructions for the AVR target apply to the
LPC target where no build instructions are given.  The only real issue
is creating config.h from one of the prototypes in the 'conf' directory.

Download the file to a directory, say ~/EFSL. Then:

[rstofer@DellPWS EFSL]$ ls
efsl-0.2.7.tar.bz2  manual-0.2.7.pdf <= source files and manual

[rstofer@DellPWS EFSL]$ bunzip2 efsl-0.2.7.tar.bz2

[rstofer@DellPWS EFSL]$ tar -xvf efsl-0.2.7.tar
...
tar output omitted
...
[rstofer@DellPWS EFSL]$ ls
efsl-0.2.7  efsl-0.2.7.tar  manual-0.2.7.pdf <= efsl directory created

[rstofer@DellPWS EFSL]$ cd efsl-0.2.7/conf

[rstofer@DellPWS conf]$ ls
config-sample-avr.h    config-sample-lpc2000.h
config-sample-linux.h  config-sample-nios2.h

[rstofer@DellPWS conf]$ cp config-sample-lpc2000.h config.h

[rstofer@DellPWS conf]$ cd ..

[rstofer@DellPWS efsl-0.2.7]$ ls
conf  examples  linuxutils    Makefile-LINUX    src
docs  inc       Makefile-AVR  Makefile-LPC2000  testfiles

[rstofer@DellPWS efsl-0.2.7]$ make -f Makefile-LPC2000
...
compiler output omitted -- no errors, no warnings
...

[rstofer@DellPWS efsl-0.2.7]$ ls
conf  examples  libefsl.a   Makefile-AVR    Makefile-LPC2000  testfiles
docs  inc       linuxutils  Makefile-LINUX  src
[rstofer@DellPWS efsl-0.2.7]$

libefsl.a (the efsl library) was created.

Richard

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.