I am looking for a version of LPC2129.h done by Phillips. I would like
to include the file with some source for the GNU ARM tools and figure
it's not a good idea to use a header file with IAR or Keil copyrights.
Right now I am using LPC214x.h from Phillips. Anyone know where I can
get this file with the basic #defines for the I/O registers of the 2129?
David
-----
uC Hobby - Microcontrollers for Hobbyist
www.uCHobby.com i...@uchobby.com
-----
Where can I find LPC2129.h?
Started by ●June 28, 2006
Reply by ●June 28, 20062006-06-28
At 12:29 AM 6/28/2006 -0500, David Fowler wrote:
>I am looking for a version of LPC2129.h done by Phillips. I would like
>to include the file with some source for the GNU ARM tools and figure
>it's not a good idea to use a header file with IAR or Keil copyrights.
>Right now I am using LPC214x.h from Phillips. Anyone know where I can
>get this file with the basic #defines for the I/O registers of the 2129?
I don't believe Philips has released any headers for the LPC2000
family. Like many (most?) vendors they rely on the compiler vendors and
end users to read the documentation and develop as they see fit.
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/
>I am looking for a version of LPC2129.h done by Phillips. I would like
>to include the file with some source for the GNU ARM tools and figure
>it's not a good idea to use a header file with IAR or Keil copyrights.
>Right now I am using LPC214x.h from Phillips. Anyone know where I can
>get this file with the basic #defines for the I/O registers of the 2129?
I don't believe Philips has released any headers for the LPC2000
family. Like many (most?) vendors they rely on the compiler vendors and
end users to read the documentation and develop as they see fit.
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/
Reply by ●June 28, 20062006-06-28
--- In l..., Robert Adsett wrote:
>
> At 12:29 AM 6/28/2006 -0500, David Fowler wrote:
> >I am looking for a version of LPC2129.h done by Phillips. I would like
> >to include the file with some source for the GNU ARM tools and figure
> >it's not a good idea to use a header file with IAR or Keil copyrights.
> >Right now I am using LPC214x.h from Phillips. Anyone know where I can
> >get this file with the basic #defines for the I/O registers of the
2129?
>
> I don't believe Philips has released any headers for the LPC2000
> family. Like many (most?) vendors they rely on the compiler vendors
and
> end users to read the documentation and develop as they see fit.
>
> 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/
>
There is a file of sample LPC2148 code in the Files section that has a
header file for the LPC2148. It talks about Keil but the code was
submitted by Philips. At least the header was.
For the header, it would seem to me (as a non-lawyer) that copyright
was meaningless. You can't copyright an idea, only an implementation.
The #define's have two major components: a register name and a memory
address. Both of these are specified by Philips and the information
is in the User Manual for everyone to use. In fact, if they didn't
provide the original definitions, nobody could use their chips.
Then there is the manner in which the #define is formulated. There
are probably alternatives.
Richard
>
> At 12:29 AM 6/28/2006 -0500, David Fowler wrote:
> >I am looking for a version of LPC2129.h done by Phillips. I would like
> >to include the file with some source for the GNU ARM tools and figure
> >it's not a good idea to use a header file with IAR or Keil copyrights.
> >Right now I am using LPC214x.h from Phillips. Anyone know where I can
> >get this file with the basic #defines for the I/O registers of the
2129?
>
> I don't believe Philips has released any headers for the LPC2000
> family. Like many (most?) vendors they rely on the compiler vendors
and
> end users to read the documentation and develop as they see fit.
>
> 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/
>
There is a file of sample LPC2148 code in the Files section that has a
header file for the LPC2148. It talks about Keil but the code was
submitted by Philips. At least the header was.
For the header, it would seem to me (as a non-lawyer) that copyright
was meaningless. You can't copyright an idea, only an implementation.
The #define's have two major components: a register name and a memory
address. Both of these are specified by Philips and the information
is in the User Manual for everyone to use. In fact, if they didn't
provide the original definitions, nobody could use their chips.
Then there is the manner in which the #define is formulated. There
are probably alternatives.
Richard
Reply by ●June 29, 20062006-06-29
At 01:20 AM 6/29/2006 +0000, rtstofer wrote:
>The #define's have two major components: a register name and a memory
>address. Both of these are specified by Philips and the information
>is in the User Manual for everyone to use. In fact, if they didn't
>provide the original definitions, nobody could use their chips.
Well, yes. But I can understand why someone would want something without a
vendors copyright notice on it (even if not enforceable it still carries
some threat of suit). Even if the OP is comfortable using a header with a
copyright on it from a compiler vendor, corporate policy may not allow
it. I can also understand wanting something Philips had written as being a
definitive source.
There may be headers around that meet the first criteria. I know there are
for some members of the LPC since I wrote some of them.
>Then there is the manner in which the #define is formulated. There
>are probably alternatives.
It's not as if they are hard to write. Tedious maybe but not difficult.
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/
>The #define's have two major components: a register name and a memory
>address. Both of these are specified by Philips and the information
>is in the User Manual for everyone to use. In fact, if they didn't
>provide the original definitions, nobody could use their chips.
Well, yes. But I can understand why someone would want something without a
vendors copyright notice on it (even if not enforceable it still carries
some threat of suit). Even if the OP is comfortable using a header with a
copyright on it from a compiler vendor, corporate policy may not allow
it. I can also understand wanting something Philips had written as being a
definitive source.
There may be headers around that meet the first criteria. I know there are
for some members of the LPC since I wrote some of them.
>Then there is the manner in which the #define is formulated. There
>are probably alternatives.
It's not as if they are hard to write. Tedious maybe but not difficult.
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/
Reply by ●June 29, 20062006-06-29
--- In l..., Robert Adsett wrote:
>
> At 01:20 AM 6/29/2006 +0000, rtstofer wrote:
> >The #define's have two major components: a register name and a memory
> >address. Both of these are specified by Philips and the information
> >is in the User Manual for everyone to use. In fact, if they didn't
> >provide the original definitions, nobody could use their chips.
>
> Well, yes. But I can understand why someone would want something
without a
> vendors copyright notice on it (even if not enforceable it still
carries
> some threat of suit). Even if the OP is comfortable using a header
with a
> copyright on it from a compiler vendor, corporate policy may not allow
> it. I can also understand wanting something Philips had written as
being a
> definitive source.
>
> There may be headers around that meet the first criteria. I know
there are
> for some members of the LPC since I wrote some of them.
The referenced Keil demo code has the header for the LPC2148 and it
was copyrighted by Philips, not Keil.
I didn't look at the other files, just the header.
> >Then there is the manner in which the #define is formulated. There
> >are probably alternatives.
>
> It's not as if they are hard to write. Tedious maybe but not difficult.
Right! Just print out the document you find and start typing,
referring at every opportunity to the LPC User Manual. Or even start
typing from scratch without an existing header. Not a big deal unless
you want to define every bit in every register.
Then too, projects may not use anywhere near all of the registers.
Why bother typing an unused definition?
Richard
>
> At 01:20 AM 6/29/2006 +0000, rtstofer wrote:
> >The #define's have two major components: a register name and a memory
> >address. Both of these are specified by Philips and the information
> >is in the User Manual for everyone to use. In fact, if they didn't
> >provide the original definitions, nobody could use their chips.
>
> Well, yes. But I can understand why someone would want something
without a
> vendors copyright notice on it (even if not enforceable it still
carries
> some threat of suit). Even if the OP is comfortable using a header
with a
> copyright on it from a compiler vendor, corporate policy may not allow
> it. I can also understand wanting something Philips had written as
being a
> definitive source.
>
> There may be headers around that meet the first criteria. I know
there are
> for some members of the LPC since I wrote some of them.
The referenced Keil demo code has the header for the LPC2148 and it
was copyrighted by Philips, not Keil.
I didn't look at the other files, just the header.
> >Then there is the manner in which the #define is formulated. There
> >are probably alternatives.
>
> It's not as if they are hard to write. Tedious maybe but not difficult.
Right! Just print out the document you find and start typing,
referring at every opportunity to the LPC User Manual. Or even start
typing from scratch without an existing header. Not a big deal unless
you want to define every bit in every register.
Then too, projects may not use anywhere near all of the registers.
Why bother typing an unused definition?
Richard
