PICC-Lite and 16F648/88

[bsodmike]

The above mentioned PICs are currently 'unsupported' by PICC-Lite and I suspect all one needs to get 'em to work is the 'device' info file - i.e. the device library.

Does any one here have the libs for the two PICs, as that would really come in handy - seems like I'll be using a 16F877 to perform a job that the 16F88 could EASILY manage - Going from 18 pin to 40 pin, just for the extra ROM space too...

Thanks, Mike

 

[bsodmike]

Another oddity I've come across is that when I compiled the code with the 16F84A, it exceeded the 1K ROM space (it gave some queer errors) so on a hunch I compiled as a 16f877, it compiled! If I disable the code for lcd control, it uses 50% of the 16f84, if I disable code for ps2 coms also 50%, so I know it's not vastly over 1K...

Rather than saying 1/8th of the space is used it says 50% ...

If I remember correctly, a 16f84 = 1K, 16f877 = 8K, um am I missing something here?

I'm thinking what it means is that 50% of the 2K bank, and it has four of these banks (i.e. 4 x 2k = 8K) - I just find that this is quite a strange way for the compiler to report how much space has been used ?!?

--Mike

 

[bsodmike]

PICC-Lite restricts ROM usage as follows:

Processor Limitations
12F629 No Limitations
12F675 No Limitations
16C84 No Limitations
16F627 2 RAM banks supported
16F627A 2 RAM banks supported
16F684 1 RAM banks, 1K program memory supported
16F690 New! 2 RAM banks, 2K program memory supported
16F84A No Limitations
16F877 2 RAM banks, 2K program memory supported
16F877A 2 RAM banks, 2K program memory supported

This sucks

--Mike

 

[Nigel Goodwin]

PICC-Lite restricts ROM usage as follows:

Processor Limitations
12F629 No Limitations
12F675 No Limitations
16C84 No Limitations
16F627 2 RAM banks supported
16F627A 2 RAM banks supported
16F684 1 RAM banks, 1K program memory supported
16F690 New! 2 RAM banks, 2K program memory supported
16F84A No Limitations
16F877 2 RAM banks, 2K program memory supported
16F877A 2 RAM banks, 2K program memory supported

This sucks

That's why it's a free DEMO version! - buy the full version if you don't like it!.

 

[bsodmike]

Yea I might just have to do just that

--Mike

 

[evandude]

and what a steal it is, at only $950! :lol:

 

[Joel Rainville]

You've got to give BoostC/SourceBoost a try. The full version is only $69 or so, and the free version itself is quite capable...

Edit : a single user, non-commercial license is only $59.95 while a commercial single user license is a very reasonable $149.95!

 

[evandude]

also, boostC is constantly improving. they respond quickly to any issues you have with it on their forum... this summer I requested that they add the method of bit accessing that was available in CC5x (ie - var.3 = 0 would clear bit 3 of variable 'var') and that was one of the first things they added after they finished 32-bit variable support.

Just today they emailed me asking me to try out their newest revision compiler on a program that I had previously spoken with them about.

here's the breakdown:
CC5x (free edition): 300 code words
CC5x (full version): 224 code words
BoostC (outdated free edition): 264 code words
BoostC (version 6.20 free edition): 234 code words

So even the free edition of BoostC is less than 1% larger than the $250 CC5x compiler, and significantly more optimized than the free edition of CC5x. That's one of the great things, even with the free edition you still get full optimization capability.

 

[bsodmike]

Lo there Evan,

Thanks for your many emails and support (I'll be starting another thread soon).

BoostC eh? Sounds nice, and yea I will get around to it at some point

Right now I'm being tortured by PS/2, bleh

--Mike