_ _ | \ | | | \| | | |\ | |_| \_|
##### ## ## ## ## ##### ## #####
____ | _ \ | | | | | |_| | |____/
_____ | __ \ | | \/ | | __ | |_\ \ \____/
## ## #### ## #### ## ##
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: Compiled using WinAVR. A few messages, but nothing scary so far. Hmm. What if I tried to make the footprint smaller to see if it would fit in another device? (I won't bother readers by explaining why unless you want to know. Ask if you do.) '''Why ?''' Which device ? Commenting out "# MY_CONF += -D LCD" makes it barf on missing functions. Someone forgot to #ENDIF <stub code>. I suggest either taking out the indication in my_make it can be done, or correcting code so it can. Obviously, it is possible to fix it to compile without LCD, and magicstr.h and varstr.h and lcd_display.c would free much space. Also, much inlining eats space. 64 kbyte flash would be possible, but 32kbyte would mean serious compromise. I'll better go have a sightseeing in the code and see if it may be too much other stuff making it difficult to fit in another device. I think (even if it's possible), it's a waste of time to fit in a smaller device. Also note that the code is covered by copyright (open != freeware). If you want to help making the code (more) portable, it's possible that you get SubVersionSvn access for the trunk (codetree that has been started to be ported for ARM), but signing a lightish NDA is necessary, and firmware developers must see your intentions clearly. Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.