adafruit industries

The_Don125 · Post by **The_Don125** » Mon Feb 25, 2008 8:05 pm

Just curious, but how small does the source code compile down to? I ask because I want to try to build one of these, and I have a few ATTiny45 chips laying around. I'm guessing the code would be nearly 100% compatible, but it might be somewhat too big.

magician13134 · Post by **magician13134** » Mon Feb 25, 2008 8:20 pm

The typical firmware is 23kb
The EHP custom firmware is: 14.1kb for EU 14.2kb for NA 22.4kb for World
The compressed code it: 9kb

The_Don125 · Post by **The_Don125** » Mon Feb 25, 2008 8:23 pm

Thats what has me somewhat confused, the compressed code is 9k, but even the Tiny85 used in the actual kit only has 8k of storage.

magician13134 · Post by **magician13134** » Mon Feb 25, 2008 8:27 pm

You're absolutely right, I was thinking about that right after I posted...

I'm not the person to answer this then. I do remember mention that the compressed code would even fit on a 2313 with only 2kb, so you should be fine.

caitsith2 · Post by **caitsith2** » Mon Feb 25, 2008 9:45 pm

The file sizes posted, are of the intel hex format sizes. My custom firmware has these specs.

Hardware Version 1.0, Simple version
North America/Asia - 5282 bytes
Europe - 5180 bytes

Hardware Version 1.1, Simple version
North America/Asia - 5232 bytes
Europe - 5130 bytes.

Hardware Version 1.0, double click feature version
North America/Asia - 5652 bytes
Europe - 5550 bytes
World - 8134 bytes

Hardware Version 1.1, double click feature version
North America/Asia - 5608 bytes
Europe - 5506 bytes
World - 8090 bytes

All of these versions require some modifications to fit inside an ATtiny45/25. (specifically, a reduction in the number of available codes. for that, I would start from the end of the code list, (least common shut off codes.))

The_Don125 · Post by **The_Don125** » Mon Feb 25, 2008 10:03 pm

Awesome, thanks for the info BANNED.

magician13134 · Post by **magician13134** » Mon Feb 25, 2008 10:47 pm

Just curious, how did you get those sizes and why does Windows insist otherwise?

caitsith2 · Post by **caitsith2** » Mon Feb 25, 2008 11:33 pm

Several ways.

1. If you have hex workshop, you can import intel hex files, and it translates them into .bin files.

2. Program them to an AVR, or at least fake the process. With AVRdude, you can do

AVRDUDE -p [AVR_PART] -P [PROGRAMMER_PORT] -c [PROGRAMMER] -V -F -U flash:w:[intel hex file to determine size of]

The -F flag specifies to ignore the device type identifier, and proceed anyways. The -V flag specifies to not verify what is written, since verification WILL fail. the -P flag is absolutely required if the programmer is a COM or LPT port programmer.

Windows insists otherwise, because an Intel Hex format file contains information other than binary data itself. Specifically, it contains information on where to load each byte of binary data.

Code: Select all

A typical line of Intel Hex format data.

Number of bytes to write,  Address to write to,  Data record type, Data to write, row checksum
:10 0000 00 73C88DC88CC88BC88AC889C888C887C8 77

The second last line may not have as many bytes to write, depending on where the data aligned to. The very last row is always :00000001FF

koolkat · Post by **koolkat** » Wed May 07, 2008 6:32 pm

The "Hardware Version 1.1, Simple version " new download link is

http://www.BANNED.net/projects/tvbgo ... simple.rar

koolkat · Post by **koolkat** » Thu May 08, 2008 7:14 pm

will avrdude automatically compress it when you burn it to the chip?

Lede · Post by **Lede** » Tue May 13, 2008 1:23 pm

Is this double click feature version same as the 1.1b version where the "always on" bug is fixed?

adafruit industries

Size of source?

Size of source?