AVR-Chat

No used BASCOM so not sure how they do it, but try slowing the programmer down. If You have the Kanda AVRISP software in the setup box select slowest for the speed and then see if the device is detected. You'll need v4 and above to do this.

Bryan (Kanda)


  ----- Original Message ----- 
  From: Behrooz Hariri 
  To: AVR-Chat@yahoogroups.com 
  Sent: Thursday, July 20, 2006 12:41 PM
  Subject: RE: [AVR-Chat] Waking up dead AVR??


  I tried 4.194304 MHz external crystal, with and without caps; then tried 32,768 xtal, with and without caps, also CRO for around 1Mhz, and the 'dead' didn't even blink to me! 
  The problem exactly is, the programmer (STK200/300) under BASCOM environment can NOT recognize any chip out there. In last, OSC fuse mess solved by a CRO, but not this time! Am almost sure OSC is responsible for the 'death', for I was manipulating that fues bit.

  Now, can another AVR provide a '1MHz clock signal' for the dead one? A hint on how to make this clock and what might be its characteristics? (peak to peak voltage, wave form, etc)

  Matthew Cook <matthew.cook@iinet.net.au> wrote: At 21:34 17/07/2006, Tim wrote:
  >If it is dead because of wrong oscillator fuse settings, you just need
  >to put a 1MHz clock signal into the XTAL1 pin, then set the fuse bits
  >for internal 1MHz oscillator (the factory default). Then you will be
  >able to remove the clock and program it ok.

  I've certainly messed up the osc fuse settings a few times. I have usually 
  recovered by sticking dip parts back into my STK200 and reprogramming. I 
  think you'll find the STK300 has its own external oscillator that drives 
  the XTAL1 pin, the same as the STK200.

  So Tim's method above should work. If not I'd be looking somewhere 
  else. Any chance of checking the XTAL1 input with a CRO ? What program 
  are you using to drive the STK programmer ? Can you elaborate more on "not 
  waking up ?".

  Cheers

  Matthew





  ---------------------------------
  See the all-new, redesigned Yahoo.com. Check it out.

  [Non-text portions of this message have been removed]



   

[Non-text portions of this message have been removed]