I'm using PIC for my tech project, right, and it's really annoying me...I had five proceedures but that was 270% of the memory...i got rid of the only two I can (also the largest two) so my project still kinda works as I want but it's 112% of the effing memory...girl in serious need of help here...
I'm using PIC for my tech project, right, and it's really annoying me...I had five proceedures but that was 270% of the memory...i got rid of the only two I can (also the largest two) so my project still kinda works as I want but it's 112% of the effing memory...girl in serious need of help here...
In the many years I've been using PICs I've found that almost without exception (and always read the Microchip Errata sheets) that anytime a PIC program crashed or was simply unreliable was because of some I did wrong.
A well designed PIC device will pretty much run forever, I had an old 16C54 running continuously for years.
Hanxa:
Microcontroller Code overflow is no different than the overflow of anything else in the world. Its not a leakage. Its a spill. Leakages are the fault of the container. Spills are the fault of the fillers. If 4K, 8K, 16K, 32K, or 64K does not suffice, time to break down an communicate with your chip at the chip level which is magnitudes of order and ever increasingly more efficient and compact than the programmers level.
Speaking in the collective conscious of the PIC spirit:
"I wish these humans would stop and look before just haphazardly dumping crap down our throats" - Collective PIC Spirit.