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.

Comments

Popular posts from this blog

How to identify a skilled programmer during an interview

How does one identify a skilled programmer?  No company that has interviewed me could tell the difference between myself and other programmers they'd interview.  The interview process is truly a game of luck in this industry--on both sides.  Both the programmer and the company are basing their actions entirely on luck.

Companies have come up with numerous methods to attempt to discern a good programmer from a bad one.  The best tricks they have include a series of math problems, algorithms, problem solving technique tests, and even obscure programming questions, some without definitive answers.  As an example: Is there an authoritative source of information on the core principles that define object oriented programming?  I've heard everywhere from 3 to 7.  In a field of research about a synthetic concept, an authoritative answer is almost impossible to obtain.

Programmers were then forced to study to the interview.  Careercup is one of my favorite sites for this.  This almost …

Dependency Injection - You're doing it wrong!

So I have worked at a lot of places and seen a lot of different styles of programming.  Early on in my career, I became acquainted with the concept of dependency injection.  It was a hard topic to grasp, but I have learned understand it deeply.  Now, when I step into a new application that uses it, I can very quickly see the flaws in the implementation, and there's a common one I want to talk about today: global singletons.  But we'll get to that in a minute.

What is Dependency Injection?
Dependency Injection is exactly what it sounds like.  You use it to inject your dependencies. The unique part about Dependency Injection though, is that you can do this at runtime.  Now this sounds fancier than it is.  By inject we don't mean they're downloaded for you.  You still have to have all of the parts installed where you want to run your app.

Dependency Injection is somewhat of a complicated topic to a newbie.  Let's start with defining the word dependency here.  Specific…

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…