Lpc2000

--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@...> wrote:
>
> At 06:25 PM 4/8/06 +0000, ocnek1 wrote:
> >Hi Robert,
> >
> >Thanks for the help.
> >
> >The codes is actually your TEST1.c program from the ibutton download.
> >  Thats why I'm pretty sure it is my problem...  Do you still have the
> >makefile from when you compiled the test1.c? (there is a hex file but
> >no make)
> 
> There is a makefile but I doubt it would be of much use, it's pretty 
> localized to the setup I use.  If this next little bit doesn't get you 
> going I'll send it along though.
> 
> I think I have an idea as to what's going on.  A question
> 
>          Are you using a recent release of newlib-lpc?
> 
> I think you are from other questions you asked.  If so GCC should be
giving 
> you complaints about prototype mismatches if you have been using
test1.c 
> without modifications.
> 
> Also what crystal speed have you been using?
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always
restrictions,   be 
> they legal, genetic, or physical.  If you don't believe me, try to
chew a 
> radio signal. "  -- Kelvin Throop, III
> http://www.aeolusdevelopment.com/
>

Yes I'm using the new (5a) newlib-lpc and I am getting the prototype
warnings.  The dev board has a 14.746Mhz crystal on it.

I must say that I am having fun with this though.  Learning about
makefiles/ linker scripts and build libraries is actually quite
interesting.

Maybe you could answer this question:  Building Libraries...When
building a library file for the ownet do I need to include the
newlib-lpc.c and .h files with all the ownet files when building the
library?  If not how do I ownet.a to link with newlib-lpc.a ?  Is this
in the linker script / make file?  

Thanks for the help Robert...sorry to be a pain asking these dumb
quesitons.

J.