I'm in the quest learning gcbasic on different Pics.
What I discovered in only 2 days is deeply impressive.
A small example program using PWM and LCD Output uses only about 1 Kbyte in the PIC. (Programs Name LottoGen, described here elsewhere in the Forum)
What should I say, I feared a bit using Basic would produce overhead. But if any, it's really small, congratulations for this fine Compiler!
(Please be generous with my English written nonsense, I'm still trying :-) )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was shocked to find that my code was larger than native GCBASIC produced with the added benefit that the GCBASIC code was portable and mine was not.
Great news!
Last edit: bed 2017-08-30
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are several reasons why I would not bother with a 16F1818. First it is an 18-Pin device with odd power pin locations and therefore not compatible with Curiousity LCP Dev Board (and others.)
Next, it is short on both Program Memory and RAM and therefore pretty much worthless for driving most displays, using Arrays, etc unless you like jumping through hoops trying to optimize code.
Finally, it costs more ($1.56) than superior chips with more features and more memory... Example: 16F1826,1827,1847. ( All less than $1.10)
If I had a bagful of 16F818 Chips I would probably give them to someone I did not like very much. :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm in the quest learning gcbasic on different Pics.
What I discovered in only 2 days is deeply impressive.
A small example program using PWM and LCD Output uses only about 1 Kbyte in the PIC. (Programs Name LottoGen, described here elsewhere in the Forum)
What should I say, I feared a bit using Basic would produce overhead. But if any, it's really small, congratulations for this fine Compiler!
(Please be generous with my English written nonsense, I'm still trying :-) )
I found that too.
I tried to optimise my first GCBASIC program by replacing some calls with inline assembler.
I was shocked to find that my code was larger than native GCBASIC produced with the added benefit that the GCBASIC code was portable and mine was not.
I do still use assembler, bot only rarely and only when GCBASIC has no native library for the function I need.
EDIT: Spelling
Last edit: Chris Roper 2017-07-30
Last edit: bed 2017-08-30
I do have some 16F818 (Prog=1024 EEPROM=128 RAM=128)
I wonder and hope to use them in some mini applications.
Plentyo of RAM for GLCD in Text Mode!!!
Yeah, but 1024 Bytes Code is not very much, maybe simple Applications like a counter of something or so
16F818?
There are several reasons why I would not bother with a 16F1818. First it is an 18-Pin device with odd power pin locations and therefore not compatible with Curiousity LCP Dev Board (and others.)
Next, it is short on both Program Memory and RAM and therefore pretty much worthless for driving most displays, using Arrays, etc unless you like jumping through hoops trying to optimize code.
Finally, it costs more ($1.56) than superior chips with more features and more memory... Example: 16F1826,1827,1847. ( All less than $1.10)
If I had a bagful of 16F818 Chips I would probably give them to someone I did not like very much. :)