Hello everyone !
I'm pretty new to arduino but i aam trying to learn.
I faced an issue with a cheap chinese clone of a nano arduino (Mega 168PA chipset). When I try to upload a sketch through regular usb i get:
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x00
for info: i got a bunch of other nanos and whithout changing anything in the arduino ide, i can upload a sketch without issue. so it's not an ide configuration issue.
So i guess it has to do with the bootloader, so i got myself a usbasp from amazon with the 10 to 6 ribbon cable, plugged it in and now i get:
avrdude: auto set sck period (because given equals null)
avrdude: error: program enable: target doesn't answer. 1
avrdude: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check
I tryed to upload a sketch with the usbasp on both nanos (the one i can't flash throught usb and one i can) and no change. And same result if i try to burn the bootloader.
Any idea on what am i doing wrong ?
Small addition:
I have added the -F option to see what happens and i get this:
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000 (retrying)
avrdude: Device signature = 0x000000 (retrying)
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATmega168 is 1E 94 06
So conclusion, i'm still lost and still don't understand what i'm doing wrong
Do not use -F, it does not help is such cases. First of all you have to realize what 0x00 in all "received" bytes means. There is no response at all from the target so "double check connections".
Let focus to USBasp programming first. If it is raw chip, never programmed, then the USBasp will probably need to set slow SCK. It is usually by closing JP2 but it depends on your model.
Thanks for the help, I closed the JP2 bridge with a jumper.
I was able to flash one nano with the usbasp just right now. But on my faulty one still no luck...
So I'm unable to upload a sketch throught usb on this one, unable to burn a sketch nor the bootloader with the usbasp.
But i'm able to do so on all other nanos now. So the faulty one seems to be the cause.
When i plug it with usb, the port is correctly detected and it powers on, when i connect it to the usbasp, i powers on and the rx led flash quickly.
I wouldn't take assumptions too quickly but it seems that i killed that nano. Is there any way to make it work again correctly ?
Post whole log from uploading via ISP include the command, not just a snippet.
As I wrote be sure you closed correct jumper. There are many clones of USBasp on market and it can be JP1 or JP3. Normally
it is JP1 - 5V/3.3V, JP2 - slow SCK, JP3 - self programming as original.
But maybe it is time to check Nano's HW. You can do something with any cheap DMM (multimeter). VCC on chip and regulator.
Oscillator check - XTAL1 pin on ATmega against GND, there should be some voltage about 1V and XTAL1-XTAL2 about 0.7V.
It is square 50/50 signal but DMM it shows like some DC voltage, half of real amplitude.
Reset pin have to be equal to VCC just it the reset button is pressed it is equal to GND - 0V. When uploading attempt starts there is generated reset pulse and it should be visible on DMM as voltage drop to 0V. It is short but observable.
So these 3 things are mandatory: VCC, oscillator and reset circuit, and MCU is prepared for ISP programming and it should work.