Picc

[abollegala]

I used PICC software to write a program for PIC18F452 and used IC prog with a JDM programmer to program the device. Iwas simuleted correctly in Proteus7 software. But when it is programmed to the PIC it does not work. Assembly programs are working in this pic. is there a bug in this PICC?

 

[Nigel Goodwin]

More likely it's either a hardware problem, or a software problem, but why use PICC when there's a free C compiler from MicroChip?.

 

[Funny NYPD]

PICC and PICC18 is so pupolar in the industry, all Microchip FAE here in the new england area recommend it.

Couple of years ago, Some of them even told me privately to avoid using C18 for product development since they thought Microchip C18 was a piece of junk and a trouble-maker for them.

My personal experience about the C18 is, once you got use to other C compilor, like the PICC or Turbo C, you won't like the C18.

And I don't recommend the C18 for beginners even though it is almost free.

The PICC lite is free and support some popular PICs. It will save lot of time for beginner, so they can concentrate on the C language, not the compiler itself.

 

[Funny NYPD]

By the way, you cannot use a PICC for PIC18F chips, which require a PICC18 c compiler.

PICC is target on PIC12F and PIC16F family not the PIC18Fs.
Here is some projects we have done with PICC for PIC12F508 chip(which only got 512 bytes of Flash, 25 bytes of RAM):

One example is the LED runner which only consume 21% of flash and 68% of RAM, web link and user manual are here:
**broken link removed**
**broken link removed**

Another example is a dual-door bell project (only use 59% of flash, 84% of RAM), web link and user manual are here:
**broken link removed**
**broken link removed**

Hope this will clear the confuse.

 

[Pommie]

I have had no problems with the C18 compiler.

Can you post your running light code so I can compare the two?

Mike.

 

[Funny NYPD]

Hi, Mike,
It is good to hear that.
Since both project are commercial product now, I don't have the authority to post the code here, but I can help post the build result with PICC, please see below.
It was amazing when I was first told it was written in C language for the 12F508 chip with so little Flash and RAM.

By the way, PICC cannot compare with C18 since the PICC is target to the PIC12Fs and PIC16Fs.

Regards,
Funny N.

Build Y:\HT-PIC\12F508\LEDRunner\LEDRunner for device 12F508
Using driver C:\Program Files\HI-TECH Software\PICC\std\9.60\bin\picc.exe

main.obj is up-to-date
Executing: "C:\Program Files\HI-TECH Software\PICC\std\9.60\bin\picc.exe" -q -g --asmlist --chip=12F508 "--errformat=Error [%n] %f; %l.%c %s" "--msgformat=Advisory[%n] %s" "--warnformat=Warning [%n] %f; %l.%c %s" -P --char=unsigned -oLEDRunner.cof -mLEDRunner.map --runtime=default,-clear main.obj

Memory Usage Map:

Program space:
CODE used 64h ( 100) of 1FFh words ( 19.6%)
ENTRY used 6h ( 6) of 1FFh words ( 1.2%)

Data space:
BANK0 used 11h ( 17) of 19h bytes ( 68.0%)

EEPROM space:
None available

Configuration bits:
CONFIG used 1h ( 1) of 1h word (100.0%)

ID Location space:
IDLOC used 0h ( 0) of 4h bytes ( 0.0%)

Summary:
Program space used 6Ch ( 108) of 200h words ( 21.1%)
Data space used 11h ( 17) of 19h bytes ( 68.0%)
EEPROM space None available
Configuration bits used 1h ( 1) of 1h word (100.0%)
ID Location space used 0h ( 0) of 4h bytes ( 0.0%)

Loaded Y:\HT-PIC\12F508\LEDRunner\LEDRunner.cof.