NerdKits - electronics education for a digital generation

You are not logged in. [log in]

NEW: Learning electronics? Ask your questions on the new Electronics Questions & Answers site hosted by CircuitLab.

Support Forum » Newest irritation No longer can program MCU

June 24, 2010
by Ralphxyz
Ralphxyz's Avatar

I tried to program a ATmega168 that I have not used in a while.

The compiler ran through everything and said Thank You.

So I believe it compiled but now I cannot set the MCU to run mode.

All I get are the two bars.

So I tried another MCU which had a working program loaded and it gets the same results:

Two black bars.

Then I tried using a different breadboard and loading the program.

Now the compiler hangs at:

miniMac:tempsensor Me$ make
avrdude -c avr109 -p m168 -F -b 115200 -P /dev/cu.PL2303-0000101D -U flash:w:tempsensor.hex:a

I get the same hung results with the original breadboard also.

Both MCUs hand when trying to load a program and show two black bars when trying to run.

Any idea about how to reset the MCUs?

Ralph

June 27, 2010
by Ralphxyz
Ralphxyz's Avatar

Anyone have any idea about what I should do or look for?

When in programming mode it just hangs at:

miniMac:tempsensor Me$ make avrdude -c avr109 -p m168 -F -b 115200 -P /dev/cu.PL2303-0000101D -U flash:w:tempsensor.hex:a

Ralph

June 29, 2010
by Ralphxyz
Ralphxyz's Avatar

Duh, I "forgot" to switch back to the 168 makefile in the libnerkits folder.

For the past month I have been programing a ATmega328p MCU and had tried to program a ATmega168 forgetting to switch back

to the 168 makefile. Gee imagine once I used the correct makefile it works.

Ralph

June 29, 2010
by hevans
(NerdKits Staff)

hevans's Avatar

Hi Ralph,

Glad you got it working, it is always the little things!

Humberto

Post a Reply

Please log in to post a reply.

Did you know that first-order systems have a exponentially decaying response to step inputs? Learn more...