So...yeah, that's pretty much the problem.
It was working fine a month or so ago, but yesterday, I've tried uploading a new code to this micro controller, and this happened.
The program says "Binary sketch size: whatever bytes (of a 14,336 byte maximum)" and the loading bar gets stuck at 90%
The TX led on micro controller turns solid yellow, and pretty much nothing else happens.
I've tried a few things already, like reinstalling the usb driver, restarting the chip (in this case the upload completes, but the chip still has old code on it), shorting GND to RST, nothing helped.
The code now is complete bare minimum, so it's not that exclamation mark issue.
All the options in the programmer are set right, (at least, to my understanding, though I can't change Serial Port to anything else, as COM5 is the only choice.)
So, yeah, any help would be appreciated, as this chip doesn't make a good paperweight.
Yep, tried different USB sockets, result always the same.
Board correct.
Edit:
One more thing. I used to use OP-COM for car diagnostics on this computer as well. It worked fine, until one day for some reason it started giving BSOD every time I plugged the device into my computer. No matter which socket, 2 seconds and BSOD. I reinstalled usb drivers and it helped, but quickly went back to the same state. I kinda shrugged it off, but when I plugged ATmega168 in, the same thing started happening. I reinstalled USB drivers again, and it worked after that, though I didn't try to modify the code on the chip until yesterday, so dunno, maybe it's related.
Well, screw it. I'll be reinstalling my windows tomorrow, we'll see how it works after that.
Edit (again):
Nope
Same sh*t as before, getting stuck at 90%, so I suppose it might be a problem with chip itself.
Anything can be done about that?
Edit (like, realy....)
I've read around the web a bit, and, well...
The current code on the chip keeps giving readings on few things continuously (a compass and 5 buttons (even though they are unplugged). I was wondering that maybe that could be causing the problem ( like keep shoving data through the port so upload cannot make through or something)?
Edit (...seriously)
MOTHERF*^&<G S+# NUGGETS
...so, apparently, one of the solutions in this kind of problem is changing the brand of the chip to something else in the programmer, and hitting reset button just before the upload stage takes place. Not sure why the programmer is so eager to work now that the wrong brand is selected, but whatever, I'm happy enough that I can finally get back to building my motion controlled game controller.
So...yeah, sorry I didn't try that earlier, and thanks for helping. Ciao.