Voting resources, early voting, and poll worker information - VOTE. ... Adafruit is open and shipping.
0

How did this work?
Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.

How did this work?

by stinkbutt on Fri Jun 11, 2010 11:32 pm

I just realized something. I compiled and uploaded my .hex file from the Digisage firmware, but take a look:

huh.png
huh.png (5.99 KiB) Viewed 937 times

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.
Red M&M, Blue M&M: They all wind up the same color

stinkbutt
 
Posts: 593
Joined: Wed Feb 17, 2010 2:40 am

Re: How did this work?

by stinkbutt on Fri Jun 11, 2010 11:48 pm

Wait, never mind. I just found avr-size:

Code: Select all | TOGGLE FULL SIZE
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>
Red M&M, Blue M&M: They all wind up the same color

stinkbutt
 
Posts: 593
Joined: Wed Feb 17, 2010 2:40 am

Please be positive and constructive with your questions and comments.