Crazy compiler bugs, AVR Studio’s avr-gcc commands explained, and makefiles

[Edit: solved, the error was in the fab hello world makefile line
$(OBJCOPY) -j .text -O ihex $(PROJECT).out $(PROJECT).hex
To fix, add -j data or drop the -j option altogether)
See also, man avr-objcopy.
What was actually happening was in one example the compiler replaces the code with the array data and then loads it into the microcontroller, while for the other example it loads the compiled code into the micro, and in both cases the constant array never makes it into the microcontroller.]

The surface symptoms of crazy compiler bug which appears to eat variables (NOT an optimization issue! — check out this awesome thread for more about that )

Me: I’m getting bugs where the exact symptom in simplest form is

void light_led(char led_num) {
   DDRB = led_dir[2];
   PORTB = led_out[2];
void main(void) {
   while (1) {
      light_led(2); //obviously I am ignoring the argument given here
works as expected but
void light_led(char led_num) {
   DDRB = led_dir[led_num];
   PORTB = led_out[2];
void main(void) {
   while (1) {

doesn’t. (tested and doesn’t work: char, volatile char, int and now int8_t and uint8_t).

Based on this code:
(full file here:

Yes, I tried int instead if char in case C arrays wanted int indices. And volatile char in case the compiler was like “You, variable! You are a useless waste of memory. OPTIMIZED.” (sfx notes: that should sound like RECTIFIED in Tron).

Okay, so why doesn’t AVR Studio 5 Debugger work?

Turned out AVR Studio debugger is straightforward, but it doesn’t work if you have a

void main (void) {}
function instead of a
int main … (return 0; )

Also, AVR Studio 5 is amazing. I can peer at all the DDRB and PORTB and all the pins — even with an oscilloscope I would need like 8 arms to do this.

Oh right, back from worshiping AVR for making AVR Studio freely available (the Gobsmacking Glory of which is only slightly diminished by my sadness that it’s not open-source / doesn’t run on linux (haven’t tried WINE yet)) and on to compiler issues.

Re: linux avr toolchains, Pranjal Vachaspati, hallmate and 2014, in yet-another-spam-thread-I-started, writes:

If you’re using AVR eclipse (and I strongly recommend you do, as AVR development has way too many steps to comfortably manage manually), make sure you change the build target from “Debug” to “Release” or else it won’t create the appropriate binary. Also if you’re not using AVR eclipse it’s awesome!

In the meantime, I will continue my terrifying toolchain of Desktop > AVR Studio > Compile > attach *.hex file to email > Netbook > download file > run avrdude > Debug in AVR studio > … =/ Maybe AVR Studio works with Wine.

I grabbed the avr-gcc commands from the terminal output at the bottom of AVR Studio 5, edited the filenames, and used it to compile C code on ubuntu. (Note that choosing “Release” uses -Os, full optimization, while choosing “Debug” uses -O0, no optimization. For my code this results in 3 kilobytes flashed versus 150 bytes! — 3kb = almost 90% of available mem on attiny45)

I’m writing some C code for the attiny45 microcontroller for how to make anything,  and I’m debugging a problem where for the exact same C code,  AVR Studio creates a happy .hex file but the class-derived makefile creates a “I’m-going-to-half-work-and-drive-you-crazy-debugging” .hex file (see C code above for the symptoms).

 ~~~AVR Studio commands
avr-gcc -funsigned-char -funsigned-bitfields -Os -fpack-struct -fshort-enums -g2 -Wall -c -std=gnu99  -mmcu=attiny45   -MD -MP -MF”v0.1.45.d” -MT”v0.1.45.d” -o”v0.1.45.o” “v0.1.45.c”
avr-gcc -mmcu=attiny45  -Wl, -o v0.1.45.elf  v0.1.45.o
avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature  “v0.1.45.elf” “v0.1.45.hex”
avr-objdump -h -S “v0.1.45.elf” > “v0.1.45.lss”
avr-objcopy -j .eeprom –set-section-flags=.eeprom=alloc,load –change-section-lma .eeprom=0 –no-change-warnings -O ihex “v0.1.45.elf” “v0.1.45.eep” || exit 0
avrdude -p t45  -c usbtiny -U flash:w:v01.45.hex
~Results  as run on Ubuntu 11.10 in 435 bytes .hex file / 146 bytes flashed. And results in a bunch of magical files.

~~~Class-derived Makefile
avr-gcc -mmcu=attiny45 -Wall -Os -DF_CPU=8000000 -I./ -o ./v0.1.45.out ./v0.1.45.c
avr-objcopy -j .text -O ihex ./v0.1.45.out ./v0.1.45.c.hex;
avr-size –mcu=attiny45 –format=avr ./v0.1.45.out
avrdude -p t45  -c usbtiny -U flash:w:v0.1.45.c.hex

~Results as run on Ubuntu 11.10 in 443 bytes .hex file / 150 bytes flashed. (it takes up more memory and it doesn’t work right! :/)

So, I emailed out to the MAS.863 and one of the TAs promptly spent almost an hour writing an essay in reply. o__o Yay awesome people. Directly copied:

Brian Mayton (bmayton):

Here’s what some of this means.  First, starting with the compiler command (avr-gcc).

> avr-gcc   -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums

The -f options change the behavior of the compiler.  -funsigned-char tells it that the ‘char’ type is by default unsigned (that is, cannot represent negative numbers, but can store numbers twice as large.)  Normally in C ‘char’ is signed, and if you want an unsigned one you have to say ‘unsigned char’.  This flag swaps it around, so that ‘char’ is unsigned by default and you have to say ‘signed char’ if you want a signed one.  Generally, when writing microcontroller code, I very much prefer to be explicit, never assuming what the compiler is going to do.  <stdint.h> is part of the C standard library and defines types like ‘uint8_t’ (an unsigned 8-bit integer, same as ‘unsigned char’) and ‘int8_t’ (a signed 8-bit integer, same as ‘signed char.’)  I prefer these over the char, short, int, long types because I know exactly what I’m getting.

-funsigned-bitfields says that bitfields are also unsigned.  If you don’t know what bitfields are, you’re probably not using them.  (Most code for avr-gcc doesn’t use them.)

-fpack-struct says that all structs should be packed.  (Look up C structs if you’re not sure what these are.)  On some processor architectures, memory is addressed a ‘word’ at a timeβ€”on a 32-bit x86 processor, for example, a word is 32 bits (or four bytes) long.  The instructions for accessing a word of memory tend to be faster when the word being accessed is ‘aligned’ to a word boundary, i.e. its address in memory is a multiple of four bytes.  In a struct, if you were to have, for example, three fields that were each one byte long (uint8_t), and then one field that was four bytes long (uint32_t), and the beginning of the struct is aligned to a word boundary, then the 32-bit variable won’t be, and accessing it will be slower than if it were.  So sometimes the compiler will insert ‘padding’ to make sure that all multi-byte fields in a struct are aligned to word boundaries; in this case, it might insert one byte of padding in between our three single-byte variables and the four-byte variable to push it over onto the word boundary.  Telling the compiler that a struct should be ‘packed’ tells it *not* to insert this padding.  On a microcontroller with limited memory, you might prefer the slower access to unaligned fields to the ‘wasted’ memory that padding creates, or if you’re implementing a network protocol that needs the fields to be at specific locations.

-fshort-enums tells the compiler that enums (again, look this up if you don’t know what they are) should be stored as a ‘short’ rather than an ‘int’.

My guess is that it’s likely one of the above flags that makes your code work, but without seeing your code I couldn’t say for sure.

>   -Os

This sets the optimization level.  -Os means that the compiler should optimize to make things faster, but try to produce the smallest program possible.  -O0 means don’t optimize, -O1 means some optimizations, -O2 enables more optimizations, and -O3 turns on optimizations that might also result in a larger program.
>   -g2

This tells the compiler to include debugging information in the code it generates; if you use a debugger later, it uses this information to map between which instruction in the compiled program corresponds to which line of the C files.

>   -Wall

This tells the compiler to enable all warnings.  There are some warnings that aren’t enabled by default (such as you defined a variable but didn’t use it, there’s nothing wrong with that, but it might be a mistake.)  This can sometimes help point out programming bugs that compile fine but might not be what you meant to write.

>   -c

This tells the compiler that it’s going to build an object file instead of a complete program.  Object files contain compiled functions, but they’re not yet ‘linked’ together into a complete program.  When you use a C compiler, one way to do it is to just give it all of your C files at once and have it produce a complete program all in one go (this is how Neil’s example Makefiles do it).  In more complex programs, it’s often useful to produce the intermediate object files first, and then link them together into the complete program at the end.  If you have lots of .c files, and only change one, then you only need to rebuild the .o object file corresponding to the .c file that changed.  For a big project with lots of code, that can be faster.

You can read more about what ‘compiling’ and ‘linking’ mean (lots of info online) if you want to get a better understanding of what’s happening.

>   -std=gnu99

This tells the compiler to use the GNU99 standard.  There are a couple of different variants of C.  There’s ‘ANSI C’ or C89 (the ’89’ corresponds to 1989, the year the standard was ratified.)  C99 is a newer revision to the standard that adds some extra features to the language (like being able to declare varaibles at other places than the top of a block.)  GNU99 adds in a handful of GCC-specific extensions.

>   -mmcu=attiny45

This, of course, tells the compiler what processor to produce code for.

>   -MD -MP -MF”v0.1.45.d” -MT”v0.1.45.d”

These are all dependency-tracking options, that tell the compiler to save information about which header files are used by each .c file, which can be used later to determine, if a header changes, which source files need to be rebuilt.  This is useful for large projects, but not terribly useful for small microcontroller stuff.

>   -o”v0.1.45.o”

This specifies the output filename.  Usually the convention for object files is whatever the name of the .c file was, but with .o instead.

>   “v0.1.45.c”

And finally, this is the .c file to compile.  And that’s it for the compilation step.  If you had multiple .c files in the program, this would be repeated for each one.

Now, the linking step:

> avr-gcc -mmcu=attiny45  -Wl, -o v0.1.45.elf  v0.1.45.o

This also uses the avr-gcc command, but since there’s no -c flag, it’s going to build a complete program instead.  The linker will take all of the object files (in this case, only one) and assemble them together into a complete program, figuring out where everything fits in memory.  The object files have ‘notes’ in them that say things like ‘here I want to call function foo()’; it’s the linker’s job to decide where function ‘foo()’ is actually going to be in memory, and replace that ‘note’ with the actual address for the program to jump to.  The -Wl,-Map= flag tells the linker to also produce a file that says where it’s putting things, which can be helpful to reference when debugging sometimes.

The -o flag, like before, specifies the output file; for a complete program, this will be in ‘elf’ format.  (This is a standard format for executable programs, you can read more about it if you want.)  Finally, a list of all of the .o files to include in the program follows (in this case, again, we only have the one.)

Now some objcopy/objdump stuff:

> avr-objcopy -O ihex -R .eeprom -R .fuse -R .lock -R .signature  “v0.1.45.elf” “v0.1.45.hex”

Mostly for historical reasons, a lot of programming tools won’t read an elf file directly.  Customarily, the file format that’s used is Intel HEX (ihex, or simply .hex.)  (Some embedded systems also use Motorola S-record or srec files).  The objcopy command here is basically copying the compiled code from the elf file into a hex file.  It’s told (via the -R flags) to ignore the .eeprom, .fuse, .lock, and .signature sections (so this hex file will basically only contain the program code, or the .text (in executable parlance, ‘text’ often means compiled code) section.)

> avr-objdump -h -S “v0.1.45.elf” > “v0.1.45.lss”

objdump here is generating a file with the disassembly listing of the compiled program.  This is completely unnecessary to generating working code, but sometimes looking at the disassembled program to see what instructions the compiler generated can be a useful debugging tool.

> avr-objcopy -j .eeprom –set-section-flags=.eeprom=alloc,load –change-section-lma .eeprom=0 –no-change-warnings -O ihex “v0.1.45.elf” “v0.1.45.eep” || exit 0

Finally, this is creating another hex file that would contain any ‘.eeprom’ section you defined in your program.  You’re quite likely not using the EEPROM on the chip, and don’t need this.

That ended up being a bit long-winded and I went off on a few tangents, but maybe that helps a little?

Also, perhaps the reason why avr-gcc install with neither manpages nor info files is the length of the avr-gcc manual:

Then my email to my hall course-6 list sidetracked into a rant about makefiles. The main takeaway was that to learn about makefiles I should read the GNU Make manual.

Here’s the gist of the email thread, if it’s interesting to others:

Marti Bolivar (of leaflabs! yay open source hardware startups):

if at any point, you find the experience of writing a nontrivial
makefile akin to swimming upstream in a river of tepid molasses, don’t
despair. that is the expected behavior. make sucks, that’s life :(.

if your class requirements don’t forbid it, you may wish to try scons
( out.

RJ Ryan (of open-source DJ software mixxx and mobile health Sana Mobile says:

SCons is good for projects where everyone knows Python. If nobody knows Python, it’s a really terrible idea. πŸ™‚ Just look at Mixxx’s SConstructs. I’ve attempted to bring some sanity to them, but they’re mostly crap.

And that’s only like 70% of the SCons files we have. After dealing with this long enough, I coined this addage: Give a person a turing-complete build system and they will find a way to club a baby seal.

In my experience, you have two options if you are stuck with make:

1) Spend years learning by example and eventually understand most of what is going on but still be utterly confused 10% of the time (e.g. dealing with autoconf-generated makefiles).

2) Spend a couple hours reading the GNU make manual straight through. Everything will make a lot more sense.

Reid Kleckner writes:

Build systems are like the ultimate doomed project area.  There are so many systems that reinvent the wheel in slightly different ways and don’t provide a bulletproof solution for everyone.

Every user has completely different requirements and is always migrating from some other system where xyz was easy, and so they just grow and grow features that make them incomprehensible at the end of the day.

Projects in this area that haven’t solved all your problems yet:

  • make
  • autoconf/automake
  • cmake (we use this for DynamoRIO and DrMemory)
  • Boost’s jam
  • jom
  • eclipse
  • visual studio
  • ninja
  • scons
  • rake
  • BSD make
  • Ant
  • Maven and all the *other* Java build systems
  • gyp (we use this for Chrome, go NIH)
  • the new LLVM build system ddunbar proposed

It’s just…  I ** hate build systems.  They all suck.  They’re too slow, don’t run on platform x, can’t crosscompile, mess up the deps so you have to do a clean build…

Maybe we ask too much of them. 

marti picks up on the topic of turing complete baby seal clubbers:



that second one reminds me of duff’s quote about his device (with respect to whether fall-through was ok), “This code forms some sort of argument in that debate, but I’m not sure whether it’s for or against.”

 then perry huang, some hall alum I have never met I think:

from the creator of make:

“Why the tab in column 1? Yacc was new, Lex was brand new. I hadn’t tried either, so I figured this would be a good excuse to learn. After getting myself snarled up with my first stab at Lex, I just did something simple with the pattern newline-tab. It worked, it stayed.  And then a few weeks later I had a user population of about a dozen, most of them friends, and I didn’t want to screw up my embedded base. The rest, sadly, is history.”– Stuart Feldman

So yea. I’m waiting for when microcontrollers get so powerful and cheap that I can run python on them. >__> <__<

How to design pcbs to fit CAD models (not solved well)

How to fit design pcbs to fit CAD models, specifically how to interchange between eagle and solidworks in 2d (copy pasting from my email b/c I’m too lazy to reformat):

Me: if I want to make a board in eagle which fits inside a shape that I have a solidworks model of (I only care about 2d for now). It’s pretty straightforward, so I can do the oldskool from x1 to x2 thing, but what if it were more complicated? Is the only way to do this export an image in solidworks and make a library part of it, or use some import_bmp script and trace over it in eagle, or something crazy? I guess the opposite is easier, show only the board, export image, import into solidworks, and trace it… What if I cared about 3d? Is eagle just have zero support for this?

Charles Guan:
Also, if you want to make a board of a certain shape in Eagle, it’s a terrible pain. I was in fact just messing with this tool yesterday:
What I did was make a solid model of the plan of the board (sketch > extrude), then laid it out in a DXF drawing as if I were waterjetting it. If you just export a sketch as a DXF you have to exclude things like dimensions. The tool just imports every DXF entity into the .brd file on the Dimension layer.
Example board outline:

If your board has internal slotting and stuff it will import that too.

John David Cranor:
cross platform one:

In 3d, I have no idea, but check out this post:
If only Sketchup were parametric…

You can poke the eagle file on github ( > eagle-board > .brd) and see that I simply drew a rectangle starting at the origin and then set the x2 and y2 coordinates according to the 2d solidworks measurements. For my prototype, I didn’t even end up using that board outline — I sheared off the excess copperclad and sanded* the pcb where my shearing was file until the pcb fit inside, and then used rolled up masking tape to keep it in ‘cos I sanding failed past pressfit tolerances.

* I was using FR1, not FR4, so sanding was fine.
FR1 versus FR4 copperclad:
The copper-clad we use in MAS.863 is FR1 Phenolic Paper, instead of the standard FR4 Epoxy Glass which is what you’ll probably find on ebay if you search “pcb copperclad”. Tiny particles of glass in the air make your lungs sad and result in increased cancer risk over time, so if you’re milling boards or sanding them a lot you want to go with FR1. There are disadvantages which make FR4 preferred for Real Boards which are fine for DIY boards — fr4 has less heat tolerance, delaminates easier, and cracks more easily — see
(For more info, see;
for our fr4 supplier, see

Yes, I’m splitting my giant!update for today into 3 posts.
(p.s. if you don’t know what eagle is, it’s free pcb layout software,  older version layout tutorial:
schematic tutorial:
more resources (including eagle libraries) here:,
and the list of parts for fab.lbr:

Thanks to Bayley Wang for being the first to show me how to use Eagle.

PoV Yoyo, charlieplex+pov (attiny45, 6 LEDs/3 pins) research

[edit, 6 dec 2011, see update for semi-working-ness:]

board layout

mmm, fab’d a terribly board together for persistence of vision yoyo so now I can start on code.

charlieplex and basic hello world rgb led, c, attiny44 and 45 respectively

C cheat sheet

eagle brd and sch on github
charlieplexing with arduino libraries
hello world
olopede code (not charlieplexed)
tom’s nanopov code (charlieplexed, in assembly)
ladyada code
gui gode, attin2313, has gui
assembly: avr instruction sets
led documentation
mmm instructables (attiny85, charlieplexing)
my own notes on make commands
real time clocks (for hat alarm clock)

more pov yoyo cost research

scale of 50 yoyos. project will be working on over the next month by dan fourie, laura shumaker, and I as a for-fun project spawned out of an idea my for-grades 2.008 team passed over.

functional parameters:
yoyo with integrated persistence-of-vision display

design parameters:
as of right now, for each side:

  • 5 LED display, similar to (josh gordonson and zach banks, fellow mit students) earlier work:
  • Goals: user-friendly and mod-friendly
  • Two buttons, high enough that can be accessed by pressing down on the clear thermoformed plastic cover over the circuitboard (similar to plastic water bottle in feel)
    • on/off power button(decided against the centrifugal switch designed by paulina mustafa, another classsmate, for their iron man arc reactor yoyo, because gives user option to operate pov-display without spinning the yoyo for a more stable display)
    • “change text displayed” button, and you can change the display by holding it up to your monitor ala This method means the user doesn’t need to have special cables to change the displayed text, and we don’t need a complicated / non-intuitive button interface.
    • 8pin: $14, 14pin: $17
      • if we order pcbs, can have holes for people to stick FTDI or ISP headers in, so people don’t need to solder little wires straight to the microcontroller if they want to edit or update the firmware on the ucontroller (or make a clamp breadboard) or buy one of the clamp programmers 
      • can have another mode (hold down button longer?) to change the flicker rate, since we’ll be using internal microcontroller clock which is RC and due to manufacturing variability only accurate to +- 10%
      • discarded option: right-angle button which sticks out side of yoyo. more complicated injection molds and I was worried if it’d be structural enough, since solder joints would be taking the strain. Seemed most likely to fail after repeated use.
  • PCB should snap fit in, so people can mill their own pcb’s and swap out the pcb if wanted
  • Rectangular PCB should fit, so it’s easier to panelize and easier for people to make their own board (can etch and shear off one side instead of having to have a mill and mill a circular board, although circular boards look cool .___.)
  • Ideally PCB is single-sided
  • run off a 3v button cell and contain a spare so people can go longer without ordering their own.
    • pcb serves as cell-holder, batteries should snap fit in to further simplify mechanical design
    • TODO not sure how batteries will be electrically connected to the board
  • for changing the battery / updating the firmware, top half of each side will be removable via a notch on the side
  • assembly: teach a microcontroller series and have people assemble two and keep one?

–maybe have a fourth state changing the flicker rate, in case a specific microcontroller’s clock is off (on/off/text programming/flickr rate programming)

cost estimate: 
$4.30 for two attiny85’s off of digikey, + shipping. || $2.96 for each attiny88 ($6).
cheap power-hungry LED, well.

Circuit: Shane’s interior-routed circuitboard

( cost ~$50 + shipping for 12 of them off of myropcb. Ladyada has a cost calculator for multiple suppliers and comments for each supplier:
That’s like $12 for each yoyo.

So uh… Maybe instead I will sink $80 into buying my own 1/64” and 1/32” spindles for the modela (each good for ~50 boards).
$2 per yoyo
ebay: $25 for 3x 9” by 12” FR4 board. Est.: our boards max 2” diam, so 1.5” square is 6×8 = 48 boards. So maybe $50 for 96 boards, or about
$1 copperclad per yoyo

75c ea @ 100 off of digikey. (need 200). or ebay, 100 for $7 incl shipping. $14 / 50 = 30c per yoyo. but late shipping…! may be too late for the semester
$3 per yoyo.

phototransistor: 28c each @ 100.
$1.20 per yoyo.

10k resistor, 50kohm, 5x zero ohm, 4x 500 ohm, 1uF cap.
14c each @ 100, cap
0.017 @ 100, 10k, 50k
0.01292 @ 250, total 400 needed, 500ohm
total 500 needed
0.00676 @ 500, total 500 needed, zero ohm
(this is if pov circuit does NOT need any resistors etc. ala , these are all for voxel light-programming)
total = .14*2 + 0.017*6 + 0.013*4 + 0.007*5 = 0.469
About 50c per yoyo. these are all 1206 packaging!

CR927, 4 batteries each, 200 total: $22, 30 mAh, used in blinkies
44c ea. yoyo
(alternative: rechargeable ones, $1.44 ea 55 mAh TINY 6.8mm diam, with solder tabs: $1.29 ea 48mAh 12 mm diam, $1.71 550mAh 23 mm diam
octopart search:

accelerometers 0.67 ea @ 100,, as used by
Indeed mill-able on the modela — 0.5mm gap, 0.3mm pad — DFN package
25 mil pins (15.6 mil gap and 10 mil pad/trace) — for modella, can achieve. aka 0.398 mm gap / 0.254 mm pad

$1.40 per yoyo

unless I figure out how to make accelerometers — see, and the borked link is J. Doscher, Innovations in Acceleration Sensing Using Surface Micromachining
— I’ll just pre-program the flickr rate (and make it adjustable via the light-serial-programming protocol?)

total: $15 per yoyo + some digikey shipping costs, so close to $17 each if we count the aluminum molds and injection molding / thermoforming raw mats as free (due to 2.008). and of course free labor XD

Previous research:
If we use those super-efficient LEDs, they are 30c each if we buy 400 (50 yoyos * 8 = 400 LEDs).
( via
x8 = $3 (if we include shipping)
Total = $118 + $10 shipping (so upward bound of $130)
So, about $2.60 per yoyo

3V Batteries — batteries are somewhere around $15 / 100 on ebay w/ free shipping, so $0.30 per yoyo)
 if we want them (I don’t think we do, we should design this into our mold or PCB) holders would be $1.50 each

Microcontroller ~$1.50 each, maybe $10 for shipping, aka $1.70 per yoyo

Here is how the “spin-activation” would work:

So, at 50 yoyo’s, we’re looking at $6 each which is over our budget. However, I’m confident if we look a bit harder we can get the prices down to $5 each.



Thursday: [everyone] finish the CAD for the molds
Friday: [nancy] check the dims / tolerances with Pat and Dave
Then CAM over the weekend Saturday, say meet for dinner on putz @ 5pm and then CAM (putzgiving is Sunday). Order electrical parts.
Hopefully mill / turn the molds over Mon – Wed before thanksgiving.
Finish electrical design -> gerber and programming over thanksgiving break and order pcbs if ordering them. by 26th
And injection mold / thermoform the week after (done by Friday December 2nd).
Assembly done by Dec 9th.

PoV no accelerometer notes:
I got nanopov example working this weekend — no accelerometer indeed means there’s an optimum speed the display wants to be waved at. wave it too fast and the image gets stretched out, too slow and the whole image isn’t displayed or it’s super-squished.

Oh, Tom went over this in his blog post:

One downside of this design is that there is no synchronisation between movement of the display and the display output. So if e.g. you wave it left-right-left all output is mirror-inverted half the time. Also, there is no stable, repeating image as you would get from a constantly rotating POV.

Hardware sharing / versioning, recent startups

A good number of hardware (well, electrical) online version control / sharing startups have come up recently.

  • – thoughts on smarter diff for EE
    • (version control. has good snapshot features for both board and bill of materials. has embeddable schematics. has nets. based around github, so social) 
    • “Online electronics design. Includes schematic diagrams, design hosting, parts library, and GitHub integration. Free for public open-source projects”
    • (version control and online ee viewing, board and schematic embedding. less of a social feel) 
    • “SolderPad is a place to share, discover and collaborate on electronic projects.” 
    • based off of github, so integrated
  • — no updates since october 2011?
    • (for embedding boards/schematics)
    • “CircuitBee provides a platform for you to share live versions of your circuit schematics on your websites, blogs or forums.”
    • (includes full hardware, not just ee, part sourcing) 
    • “The place to post and contribute to open-source hardware projects”

No doubt some form of open-source biology version control software will come into play soon too. But meanwhile the mechanical engineering side of things is looking a little bit neglected.

For online 3d model viewing, there are a few implementations, namely Thingiverse and 3dCADBrowser: (has assemblies, it looks like) (no embedding) (parts only, not assembled projects) (CAN be embedded!)
and a community around CAD:
another one, solidworks oriented:

Tools / raw materials search: Maybe we should do our startup around this, for integrating into one of the hardware version control platforms. Octopart is doing it for EE; now lets get the meche side done too. Then we can really have full integrated open source products sharing+version control online, and then life will be awesome πŸ™‚
If open hardware hub got popular enough (they allow “links” when you submit parts for your project), that would be cool.
[Edit 6 Dec 2011: I found a few search engines. See]

Some more research on the subject: basically says “use all the normal software version control systems” (none of which are made for visual diffing)
For some snark on circuitbee: — so yea, circuitbee is not too useful
and some more snark on upverter / circuitbee for not making the extra effort to be open source themselves:
I think actually both circutibee and upverter are awesome and people are just being paranoid. -^-^- look at the long responses all the posts got from the founders o.o

to check out: another online circuits project: