This is normal. Burning the EE fuse value tells the chip to disable the internal RC oscillator and use an external crystal. The chip needs a clock signal to be programmed, so the chip won't work while in the AVR programmer, since it has no crystal or other clock source. I should have thought of this before recommending that fuse value, given that I saw your AVR programmer. (If you had programmed the flash memory and high fuse first, the chip would be usable now.)
The quick'n'dirty way to solve this would be to add a crystal between the same two pins as in the actual circuit. The value shouldn't be too critical for just programming the chip. Any crystal >=1 MHz that doesn't exceed the rating for the chip should work well enough for the purpose.
You MAY be able to program the chip adding the -B 1.0 switch to avrdude, but if it works it will be slow as a dog's butt.
The less quick'n'dirty way of solving this is to add some form of programming header to the board, so the AVR chip can be programmed in circuit. If you had sent it to me, I probably would have done this just for my own convenience.
However, with this in mind you should be able to plug the chip back in to the GB programmer and notice an improvement. There's no code on the chip, so it won't work as a flasher, but now that the crystal should be oscillating at 6 MHz, the FTDI chip should be identified since it should be able to communicate over USB.
Last edited by nitro2k01 (Dec 19, 2013 12:41 am)
