Can't Program/Read! Dragon & STK500 - ATMega88V

Go To Last Post
10 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

After testing for most of the day, all of a sudden I find myself unable to read or program my ATMega88V's, either using the Dragon with ISP to my project board, or by plugging an 88V into the STK500 board (green socket) and using either high voltage or ISP mode. Both of these worked earlier.

Any idea what could be causing this?

I am using the latest AVR Studio 4.13 with GCC, a (USB) Dragon, an STK500 configured for HV programming, and a 13.6VDC/1A power supply for the project board or STK500.

I have verified that the project board works okay with an early, already programmed part (a 90S4433 - pin compatible).

When I try to read anything using either device, I get either an error or all FF's (except for the flags, which come in non-FF on the STK500 even with no part plugged in!). Programming appears to work on the STK500, but verify fails because it reads FF.

I have tried 4 different 88V's.

HELP!

Tiny Vital Systems, LLC
http://www.tinyvital.com
Embedded solutions
-------------
Microsoft Vista needs over 1GB of memory to work. We get our job done in 8KB!

Harvard architectures suck, but what the heck.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

IIRC there were some gyrations & special hookups to do a Mega8 HV programming in an STK500. I don't know if exactly the same setup is used for an '88; perhaps others who have done it can chime in. Double-check the setup in the AVRStudio Help.

We've dropped Mega8s & 88s into '4433 designs as well. ADC6 & ADC7 are NC on '4433, but a connection to them wouldn't hurt anything on the 8/88 AFAICT.

If you never breathe fire onto a new chip with the Dragon do the symptoms still appear?

Have you tried doing ISP reeeallll ssssllllow? Hmmmm--HV shouldn't care.

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just a thought, are you using the STK500 with a real serial port or via a USB to Serial adapter?

I have coded for about 2 dozen architectures, and they all have their place.
Don't get too religious about them (but AVR is excellent!)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
already programmed part (a 90S4433 - pin compatible).
For the larger chip you need to install the BSEL2 ?? jumper to PC2?? check the latest info on the stk500 docs.Also remember that V version of the chip can only run at a max of 8MHz.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the responses...

First.. a thought... Do I ever need the high voltage programming mode of the STK500? For that matter, do I ever need the STK500?

1) Everything was working earlier. I didn't change the hookups on the STK500 (which include various jumper settings, two big ribbon cables, and the one-wire mentioned by js.. I also double-checked against the book after things started to fail.

2) I am using a USB to serial adapter, which worked okay for the STK500 and still works for other purposes, so I don't think it is the problem.

3) The dragon is also *no longer* able to do anything with this

4) I don't remember the order of tinkering for all the parts.

My current (weak) hypothesis is that all the chips got some *can't ever touch me again* flag/lock set. Is there a way to fix that? Is that consistent with the symptoms (unable to enter programming mode message, for example)?

Tks!

Tiny Vital Systems, LLC
http://www.tinyvital.com
Embedded solutions
-------------
Microsoft Vista needs over 1GB of memory to work. We get our job done in 8KB!

Harvard architectures suck, but what the heck.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Do I ever need the high voltage programming mode of the STK500?
Well I have used it twice in the past few weeks after about 7 years of gathering dust! (it happened while using GCC BUT it MAY just be a coincindence :) )The STK500 is quite handy to do HVPP as everthing you need is already supplied unlike the Dragon.
HVPP is the final frontier when trying to recover chips.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
..The STK500 is quite handy to do HVPP as everthing you need is already supplied unlike the Dragon.
HVPP is the final frontier when trying to recover chips.

Thanks!

Is there any condition under which the STK500 should not be able to program a chip, other than the chip being actually damaged?

I ask since I can't seem to program any of my chips, so either:
1) All the chips are fried
2) All the chips are in some mode that can't be recovered
3) The STK500 is fried
4) I have it set up wrong or something, which is unlikely because it *was* working just before everything stopped working, and I didn't change it.

Also, I presume that if I get a brand new ATmega88V, I can use the Dragon ISP to program and debug it without having to resort to the STK500 first. Correct?

Tiny Vital Systems, LLC
http://www.tinyvital.com
Embedded solutions
-------------
Microsoft Vista needs over 1GB of memory to work. We get our job done in 8KB!

Harvard architectures suck, but what the heck.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I am in exactly the same black hole with a mega88 design (and it may also be happening on a Tiny44 as well). I have a proven design with 5 prototype boards working. I made a new layout and using SKT500 and also JTAGmkII in ISP mode I programmed the board once, but the program seemed corrupted. In particular the internal pull-ups did not seem to work. Trying to reprogram just failed. It seems the RESET line is dead as shoring to 0v does nothing. I even built a board with nothing but the mega, decoupling and ISP header. That did the same. Then after a few minutes the chip fried itself for no obvious reason. I could go on. Its been a week since I blew a working system.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My above posting contained 2 problems, 1 solved, 1 not. The frying and no-pull ups turns out to be the new flux which is highly acidic & aqueous. Small amounts trapped under the chip shorts out the pins (over-riding the pull-ups) and then electrolysis burns up tracks. Great this chemistry...think Ill stick to electronics. But the JTAGmkII suddenly burning the disable RESET fuse all on its own seems to be a real issue.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
But the JTAGmkII suddenly burning the disable RESET fuse all on its own seems to be a real issue.
I notice above that you are using GCC. >>>>WITHOUT<<< any prejudice, I had to resort to HVPP with one of my chips twice whilst using GCC and never before using asm in the past 7 years, Coincidence?? I can't really see how using GCC could be causing a problem but I'm keekping this at the back of my mind.

Of course I was also using the Dragon, when I would use AVRISP and AVR910 programmers in the past, perhaps the USB driver is really JUNKO!

Nice to have a half working computer again after battling with suspected BIOS virus infection :cry: for almost a week :cry:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly