Hi,

I would suggest you get some higher-level language development
environment, such as PicBasic, PicBasic Pro or CCS. The prices are $99,
$249 and $99, respectively. Why I suggest them? Because of all of them
have a native RS232 and I2C support, so an appropriate access is one
single statement. No project files, no linking stuff etc. Your project
will consist of a single source file.

The compiled file can be burned using Picstart + (it is not a big deal for
it as the Tait's programmer is available for free - you need only build it
for less than $10).

The links:
http://www.melabs.com/mel/home.htm
http://www.ccsinfo.com/picc.html

I hope it can help you.

Imre

On Thu, 13 Aug 1998, Michael van der Zee wrote:

> hi,
>
> I'm new at this pic programming. I belive I need a push in the right direction
.
>
> I've got a pic 16c84 and a "picstart plus" programmer from microchip with mpas
m.
>
> I'm lost in all kinds of project files linkers and *.asm.
>
> What I like to do is the following,
>
> I need a I2C or UART (or any other) communication, and olso my own code ( I ne
ed to count inputs only). My own code is not the problem but compiling it with t
he I2C. Some AN*** directory's on the cd shiped with the programmer contain asm
files and other, but the files are all for different pic divices...??
>
> can I use these files on a 16c84 ..?
> do I need template's ..?
>
> I belive that it must be verry simple (couse thats what a read everywere) but
I'm lost.
>
> I olso keep getting the same error like this:
>
> *************
> (Lots of errors)
> Error[147]   C:\PROGRA~1\MPLAB\EXAMPLE\I2CBUS.ASM 391 : Directive not allowed
when generating an object file (ORG)
> Error[152]   C:\PROGRA~1\MPLAB\EXAMPLE\I2CBUS.ASM 392 : Executable code and da
ta must be defined in an appropriate section
> (but alway's unable to find output file)
> MPLAB is unable to find output file "I2CBUS.O".
>
> Build failed.
> *************
> What am I doeing wrong here...??
>
>
> please help
>
> thanx
>
> Michael.
>
>