Yahoo Groups archive

Lpc2000

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

Message

Re: [??????????????][lpc2000] IAR and UCOS-ii

2005-10-14 by Mike Nelson

And it would be foolish to think it is not being
monitored by IAR.

--- Michael Rubitschka <rubitschka@...> wrote:

> Guys are you serious ???
> This is NOT a crack share list.
> 
> Cheers
> 
> 
> >From: "leomecma" <leomecma@...>
> >Reply-To: lpc2000@yahoogroups.com
> >To: "lpc2000" <lpc2000@yahoogroups.com>
> >Subject: Re: [??????????????][lpc2000] IAR and
> UCOS-ii
> >Date: Thu, 13 Oct 2005 12:05:42 -0300
> >
> >Can you send the crack for me too?
> >leomecma@...
> >
> >
> >
> >franco chalissery.
> >
> >       hello.can you give me a crack for IAR
> 4.5??very thanks.!!
> >
> > >
> > >Hi all,
> > >
> > >I am stuck with a situation nw, I am trying to
> port ucos-ii to 2138
> > >using IAR (v 4.5). The errors are because it is
> not taking the
> > >identifiers like INT16U, INT8U in the
> (ucos_ii.h)etc but which is
> > >already in the project file.
> > >
> > >Its around 39 errors for all the (.c) files in
> project file.
> > >
> > >Is the compiler version has something to do with
> it or rtos version is
> > >the problem.
> > >
> > >I find michaelanburaj's  port for gcc compiler
> but nw i hav no choice
> > >other than IAR nw.
> > >
> > >If anyone done porting ucos-ii to 2138 or 2129
> kindly help me out from
> > >this...
> > >
> > >regards
> > >franklin
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >YAHOO! GROUPS LINKS
> >
> >  Visit your group "lpc2000" on the web.
> >
> >  To unsubscribe from this group, send an email to:
> >  lpc2000-unsubscribe@yahoogroups.com
> >
> >  Your use of Yahoo! Groups is subject to the
> Yahoo! Terms of Service.
> >
> >
> >[Non-text portions of this message have been
> removed]
> >
> 
> 
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

Attachments

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.