Mukund,
You should be aware that if you take this approach, you are
essentially committing yourself to a particular compiler vendor, as
the approach is non-portable.
It's fine if this isn't an issue for you, or if the advantage of
being closer to your current code is more important to you.
See recent message posts on the topic for more details.
Brendan
--- In lpc2000@yahoogroups.com, Mukund Deshmukh <betacomp_ngp@...>
wrote:
>
> Thanks.
> Yes this is what I was looking for.
>
> Can you send me header files for LPC2138, 2148, or link.
> Could you care to explain in details, with disadvantage.
>
> Best Regards,
>
> Mukund Deshmukh.
> Beta Computronics Pvt Ltd,
> 10/1, IT Park, Parsodi,
> Nagpur-440022
> Cell - 9422113746
> ----- Original Message -----
> From: "Steve Franks" <stevefranks@...>
> To: <lpc2000@yahoogroups.com>
> Sent: Wednesday, March 01, 2006 10:07 PM
> Subject: [lpc2000] Re: Bit addressing
>
>
> > Hi,
> >
> > First, I think this topic was hashed over a bit awhile back, you
might
> > do a search of the archives for more info.
> >
> > IAR uses the following in their include files that shipped with
my
> > 2148 demo board:
> >
> > /* GPIO registers */
> > typedef struct {
> > __REG32 P0_0 :1;
> > __REG32 P0_1 :1;
> > __REG32 P0_2 :1;
> > __REG32 P0_3 :1;
>Message
Re: Bit addressing
2006-03-02 by brendanmurphy37
Attachments
- No local attachments were found for this message.