I just realized something. I compiled and uploaded my .hex file from the Digisage firmware, but take a look:
How is that possible? I successfully uploaded it, the clock runs fine, but an ATMega168 with 16KB of RAM somehow accepted a 43.3KB .hex file. Indeed, even the stock firmware .hex file occupies 25.0KB. Neither should fit. Obviously it did, but since I'm working on another firmware file, I figure it'd be nice to know where the real limit is, and why it isn't at 16KB.
Oh, and no, the file sizes I quoted are not the size on disk, they're the actual sizes.
How did this work?
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- stinkbutt
- Posts: 593
- Joined: Wed Feb 17, 2010 2:40 am
Re: How did this work?
Wait, never mind. I just found avr-size:
Code: Select all
C:\Users\XXX\Desktop\firmware09-30-09-multipack-digisage>avr-size iv.hex
text data bss dec hex filename
0 15770 0 15770 3d9a iv.hex
C:\Users\XXX\Desktop\firmware09-30-09-multipack-digisage>
Please be positive and constructive with your questions and comments.