Go Down

Topic: usbasp and zombie arduino uno : "cannot set sck period" error of death (Read 3314 times) previous topic - next topic

bperrybap

Lets take a step back.
What is your exact h/w?
I'm assuming you are trying to replace an AVR chip in an UNO board with a new virgin one?

The signature I get when reading a m328P-PU is 0x1e950f
(I attached the avrdude output using a USBASP device connecting to a m328P-PU AVR)

The signature you first read back in post #6 looked correct.
What changed since then?
Since the signature is changing there must be some wiring/connection issue or perhaps a SCK clock rate issue.

I'd stick with the UNO board as it should have everything in place including bypass caps, and a crystal which will be needed once the fuses are changed by burning the bootloader by the IDE.
Using the Arduino PCB instead of the breadboad helps eliminate some potential issues.

Are you using a 10 pin to 6 pin adapter or just running your own wires?


chaosbc

Yes I am indeed trying to replace my chip with a virgin one (actually I ordered 10 chips so I have some spares)
I don't have the  10 pin to 6 pin adapter  (not received yet) so I do with my own wires.
In post #6, I tried to find out the signature through Extreme burner using the "chip info" menu
but I am VERY unexperimented with extreme burner, I suspect this "chip info" to only read what is inside the chips.xml file

Well regarding the arduino uno, I have no problem to go back and test with this board...
I'll wire it back with the usbasp and test this command to see what this dudes gives:
avrdude -c usbasp -p m328p -v -v -v

DrAzzy

0.1uf ceramic right next to chip. You may want another larger cap (any type)


That's really strange - that suggests either a bad connection, or that something fundamental is wrong with the chip.

How is it all wired, exactly?
ATTinyCore for x4/x5/x61/x7/x8/x41/1634/828/x313 megaTinyCore for the megaavr ATtinies - Board Manager:
http://drazzy.com/package_drazzy.com_index.json
ATtiny breakouts, mosfets, awesome prototyping board in my store http://tindie.com/stores/DrAzzy

chaosbc

I quickly tested my uno board and I believe it is dead because of my stupidity.
I initially removed the chip to put a ZIF socket instead because I hoped to bootload chips one to one on the uno.
But the problem is ZIF socket probably destroyed the uno chip socket because I cannot insert the chip on it anymore.
With or without the zif socket (so with the atmega directly on the uno the least worst I can or with the zif socket, it is the same result :
avrdude: usbasp_program_enable()
avrdude: error: programm enable: target doesn't answer. 1
avrdude: initialization failed, rc=-1
         Double check connections and try again, or use -F to override
         this check.

So my uno is not really reliable anymore.
I will by another one but still I have those 10 chips I cannot bootload properly...
my my my... :smiley-roll-blue:

DrAzzy

You should be able to bootload them on breadboard no problem though...

I don't really understand why it's not working...
ATTinyCore for x4/x5/x61/x7/x8/x41/1634/828/x313 megaTinyCore for the megaavr ATtinies - Board Manager:
http://drazzy.com/package_drazzy.com_index.json
ATtiny breakouts, mosfets, awesome prototyping board in my store http://tindie.com/stores/DrAzzy

chaosbc

well...I replugged my usbasp to the breadboard and I ran several time the command.
This is my results...puzzling!
0xfe958f
0x1e958f
0x1e958f
0x1e958f
0x9e958f
0x1e958f
0x1e958f
0x9e958f
0x1e958f


And I find always thoses values 0x1e958f or 0x9e958f or 0xfe95ff

DrAzzy

Can you please post exactly how the breadboard is wired so we can doublecheck it?

Have you tried with different chips, since you say you have several? That would let you rule out a problem with the specific chip...
ATTinyCore for x4/x5/x61/x7/x8/x41/1634/828/x313 megaTinyCore for the megaavr ATtinies - Board Manager:
http://drazzy.com/package_drazzy.com_index.json
ATtiny breakouts, mosfets, awesome prototyping board in my store http://tindie.com/stores/DrAzzy

chaosbc

This is really kind from you...Yes I tested other chips but it is the same.
I tried to get the whole picture but if necessary I can photography a detail



DrAzzy

Where is the 0.1uf ceramic cap that you should have between power and ground as close to the chip as possible? Is it that blue one that you've placed as far away from the chip as possible? Put it right between the chip's power and ground connections (bypassing is the first and most frequent place where you encounter things that are sensitive to the layout - but luckily it's simple; just like crystals, they care very much about being close to the chip. That's why you'll see on circuit boards how every chip often has it's own bypass cap across power and ground right next to it).
ATTinyCore for x4/x5/x61/x7/x8/x41/1634/828/x313 megaTinyCore for the megaavr ATtinies - Board Manager:
http://drazzy.com/package_drazzy.com_index.json
ATtiny breakouts, mosfets, awesome prototyping board in my store http://tindie.com/stores/DrAzzy

chaosbc

Ok fixed but so far same results

Go Up