Skip to main content

Mintduino Programming Error

As I occasionally do, today I'm using this blog to post about a specific issue that I encountered, where I had a very hard time finding the answer on the internet.

Some Background

As of late, I've been spending a lot of time learning about microcontrollers, specifically the Arduino kind.  Soon, I suspect I'll be putting together a larger post on this adventure.

The Problem

I decided to test my skill and build a Mintduino from Minitronics.  This was a true test of my skill at building circuits thusfar, and it was very rewarding (I even got an extra microcontroller to build stuff with at the end).

However, after the build, I hooked up the obligatory FTDI Friend from Adafruit and could not get the Mintduino to accept the new program.  To be specific, I was getting this error:

avrdude: stk500_getsync(): not in sync: resp=0x00
Unfortunately, this error has many causes.  Here are a few of the common ones.  Per the instructions at that link, I verified all of my drivers and checked the connections.  But my FTDI Friend has LEDs on it, that blink as it does it's job, so I was seeing the reset trigger on my mintduino by the LED on Pin 13 flashing, and I was seeing the FTDI Friend attempt to transmit data and fail (by it's LED).  So I went through the instructions again and verified my build.  Everything was fine.  I spent quite some time searching for the solution.  I tried holding down the reset button per this old article, but that didn't work.  Even Stack Exchange didn't have a decent answer.  I was almost to the point of buying a different USB to Serial Converter per this guy's advice.

The Solution

Deep in the bowels of the arduino forums, I found this post.  It turns out that the Mintduino needs to be programmed not as an Uno, but as a:
Duemilanove w/ ATmega328
I don't know if this is always the case, but it worked for me and for the guy on the forums.  The Mintduino doesn't always work as the Uno it seems.  Happy Coding.


Popular posts from this blog

Teams and Complexity

Let's pretend you're a car mechanic (I don't know, maybe you are).  But you don't work at some shop in town, you work at a bigtime auto-maker onsite at the factory.  You help build cars from scratch.  You work with a lot of other car mechanics, and various engineers of different levels.  If we were looking at the 1910s, you might be working for Henry Ford on one of the first ever assembly lines.  Either way, you have a specific part of the car you're responsible for.  Your skills probably extend beyond that, and you might work on a different part of the car each day as your manager moves you around to keep the factory efficient.

One of your coworkers, Bob, is a superb engineer.  He is very good at building cars, far better than you, and he does it faster than everyone else.  Your boss really likes him.  You often get stuck after him in the assembly line, so you know exactly what sorts of things he does.  He's not sloppy, but he likes to do things his way.  He w…

Managing Programmers

Working with other programmers is tricky.  That said, it's nothing compared to the job of managing programmers.  One of my favorite quotes about Perl is that (paraphrased) "a Perl developer is like a rockstar.  Now imaging having a bunch of rockstars in one room together and you will understand why you don't want an entire team of Perl developers."  It's not about Perl here though. What's important to understand is that any developer worth his salt is going to be like a rockstar.  And yes, there are a lot of professional developers out there who aren't worth their salt, but that's for another post another day.  Rockstar may not be the right term here, but think of it this way.  These guys are smart.  They may not be geniuses, but there's going to be things that they know that you don't and probably never will.

I've seen it more than once and it's not going to make some Product Managers happy, but I'm going to state a fact, an eleph…

Managing Developers is HARD

I've been a software dev for a long time.  I've also been running my own software company for a few years now.  This is important information because of why I do these things.  I am a sofware developer because I love learning.  I slack off when doing a job that bores me, and software development always has something new to experience which keeps me excited and interested.  Why start a software company then?  That puts me in the role of manager rather than developer.  The truth is simple.  I've worked for a lot of companies, and I don't see any of them doing a great job of managing their software development.  That's not to say none of them have done a good job, but no one out there seems to be doing a great job.

How are they different?
A lot of companies get this part right.  Software developers are different from other employees.  The distinction is important in the same way it's important to acknowledge that an insurance agent is different from a construction…