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

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…

When Is Software Done?

I have some very exciting news.  A piece of software I've been working on for over 2 years is released to the general public!  This is a little exciting if it were software I'd been working on for some big company.  It's very exciting because it's software I have been working on for my company.  That's right!  My company is ready to start selling software and start making money!

I'm not gonna use this blog post to talk about my company and what it does.  You can read about that in our press release.  Instead, I'm going to talk about the software industry and the concept of done.  Because, as with everything, it's more complicated than it seems.

Software is never really done
Actually that's a misnomer.  Software can really be done.  But done is sort of a quantum state--there and not there at the same time.  First and foremost, anyone can understand that software that works is complete.  If the software's purpose is to process a credit card, if th…

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 …