Led test help needed please with USBTiny

[cornz]

Ok, repaired the power supply section of the board, tested and have 3, 5,12 and 26v.
So, CPU is soldered in place with res and LED.
The downloaded firmware file is unpacked in c:\bubble

So, i run (as admin) a CMD , do the test: avrdude -c usbtiny -p m8 and the reponse is as it should be.
So then, clutching at straws, i tried avrdude -c usbtiny -p atmega88
Which gave:


So, then i tried make burn-fuse and as you can see, it didnt program. I think its the com4 part but how do i change it???

Thanks for any help..

[cornz]

Well, i decided to open the "makefile" file and look for the string com4, which i found and changed to com3, needless to say it still fails.
I feel pretty sure this is half the fault, how do i select the com port for programming it.
Cant understand how i can probe the chip though..

[Chankster]

Looks like you installed an atmega88p but are specifying an atmega88

part
id = "m88p";
desc = "ATMEGA88P";
has_debugwire = yes;
flash_instr = 0xB6, 0x01, 0x11;
eeprom_instr = 0xBD, 0xF2, 0xBD, 0xE1, 0xBB, 0xCF, 0xB4, 0x00,
0xBE, 0x01, 0xB6, 0x01, 0xBC, 0x00, 0xBB, 0xBF,
0x99, 0xF9, 0xBB, 0xAF;
stk500_devcode = 0x73;
# avr910_devcode = 0x;
signature = 0x1e 0x93 0x0f;

part
id = "m88";
desc = "ATMEGA88";
has_debugwire = yes;
flash_instr = 0xB6, 0x01, 0x11;
eeprom_instr = 0xBD, 0xF2, 0xBD, 0xE1, 0xBB, 0xCF, 0xB4, 0x00,
0xBE, 0x01, 0xB6, 0x01, 0xBC, 0x00, 0xBB, 0xBF,
0x99, 0xF9, 0xBB, 0xAF;
stk500_devcode = 0x73;
# avr910_devcode = 0x;
signature = 0x1e 0x93 0x0a;

http://svn.savannah.nongnu.org/viewvc/t ... iew=markup

[cornz]

Thanks for the bone..
Sadly, still doesnt seem to want to play.
I copied the conf files from the link into my avrdude directory, ran the make burn-fuse command and got an error about a "@" being an unknown charater at 595. So then i just copied the device id code from the at88p to the at88, which still gave an error...
Stuck and its getting late...
Any suggestions?

its passingt he connection test , thats whats odd...

[Chankster]

What is the full string you are using to program and the full error that you are receiving?

[cornz]

Ok, here are the steps taken so far and the results.


Right,Win7 ULT x64
USBtiny with 5.5 from here.

http://www.ladyada.net/make/usbtinyisp/download.html
I have used my USBtiny before to program my ice clock so im pretty sure its ok.

Download latest WinAVR from:
http://sourceforge.net/projects/winavr/ ... /20100110/

So, using the test procedure.
http://www.ladyada.net/make/usbtinyisp/avrdude.html


Suggests all works well.
Then, as an experiment i tried:


So, then i wondered what wouldhappen if i used -F, well, still suggests the programmer is working, but it still doesn't help.


So, back to the "make section of the WB website and programming the chip.
I've unzipped the firmware files for the WB and placed them into a folder.
C:\bubble

I then navigate to this directory and type make burn-fuse. The result is below:




Now, after having slept and had a think, i have a better grasp of what the problem is. Its that AVRDUDE (or "makefile") isnt configured properly to use a USBTiny...So, it means messing with something in AVRDUDE to make it realise that im using a USBTiny programmer. But i'm stuck now as im reading about compiling and source code and i havent got a clue.
Advice???
Thanks....

[cornz]

UPDATE:

After using this string:
C:\bubble>avrdude -c usbtiny -p atmega88 -F avrisp -u -U lfuse:w:0xe2:m -U hfuse
:w:0xd7:m

It appears i have been succsesful.



So....We shall see.....

[Chankster]

Good troubleshooting!

I would be cautious about overriding the Device Signature checks unless you are super sure. What I was referring to earlier was the message "Device signature = 0x1e930f" "Expected signature for ATMEGA88 is 1E 93 0A". Instead of specifying atmega88 you should use atmega88p which matches the device signature.

For future reference here's what you would need to change in the makefile:

Line 2: Change atmega88 to atmega88p (to match the part you selected)
Line 101: Change avrisp to usbtiny
Line 105: Change com4 to whatever com port your device is on