AVR-Chat

Still working on this one, but I have a critical delivery to do, and 
need other eyes.

Jtag ice connected to a project, but there's nothing on the Jtag pins 
other than the M128 itself.

Jtag is seen by studio, but can't debug, and can't be opened as a chip 
programmer to check fuses etc.   The chips are raw M128's so they will 
have the M103 fuse set wrong.

So far, I can't get any of them talking, and unfortunately, I don't 
have any other platforms handy with Jtag ice ports to test against.

Pinout and connections seem ok, VCC, /Reset etc.
Chips are new, so should be running on internal 1MHz osc.

Ok, it gets better.

Ripped out and reinstalled studio.
Changed to STK-500/501 combo, still same problem.

Dave VanHorn wrote:
> Still working on this one, but I have a critical delivery to do, and 
> need other eyes.
> 
> Jtag ice connected to a project, but there's nothing on the Jtag pins 
> other than the M128 itself.
> 
> Jtag is seen by studio, but can't debug, and can't be opened as a chip 
> programmer to check fuses etc.   The chips are raw M128's so they will 
> have the M103 fuse set wrong.
> 
> So far, I can't get any of them talking, and unfortunately, I don't 
> have any other platforms handy with Jtag ice ports to test against.
> 
> Pinout and connections seem ok, VCC, /Reset etc.
> Chips are new, so should be running on internal 1MHz osc.

Remember that the output buffer of the jtag ice is powered
from the target pcb. See if there's any pulses on the jtag
pins with a cro when you open the programming dialog in avr studio.

> Ripped out and reinstalled studio.
> Changed to STK-500/501 combo, still same problem.

Cable length ?

I found that I got nowhere with a Duo-ICE until I shortened the IDC cable.

Steve.


==========================================
Steve Baldwin                          Electronic Product Design
TLA Microsystems Ltd             Microcontroller Specialists
PO Box 15-680, New Lynn                http://www.tla.co.nz
Auckland, New Zealand                     ph  +64 9 820-2221
email: steve@tla.co.nz                      fax +64 9 820-1929
=========================================

At 01:22 AM 8/08/2006, you wrote:
>So far, I can't get any of them talking, and unfortunately, I don't
>have any other platforms handy with Jtag ice ports to test against.

Can you try and hook up the STK500 as an ISP programmer to the board?
May have to connect some flying leads if you don't have the ISP pins
available to a connector.
If you need it I have a M64/M128 (CONT3) circuit diagram on the download
page of my website to double check JTAG and ISP pins connection.....I know
that you know how it all should be hooked up but....:-)

Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

Is it an Atmel JtagIce I have had trouble with MkII after using 1 wire debug
and not closing Studio properly the MkI still worked but the MkII would not,
The fix was a complete uninstall of Studio saving NO settings 'clear the
registry' reboot the computer then reinstall Studio.
Owen.

Still working on this one, but I have a critical delivery to do, and 
need other eyes.

Jtag ice connected to a project, but there's nothing on the Jtag pins 
other than the M128 itself.

Jtag is seen by studio, but can't debug, and can't be opened as a chip 
programmer to check fuses etc.   The chips are raw M128's so they will 
have the M103 fuse set wrong.

So far, I can't get any of them talking, and unfortunately, I don't 
have any other platforms handy with Jtag ice ports to test against.

Pinout and connections seem ok, VCC, /Reset etc.
Chips are new, so should be running on internal 1MHz osc.







 
Yahoo! Groups Links

It's been an interesting day.

The root of the problem seems to be AVR studio.
I was able to visit PRLLC  (now Priio) and use their non-studio programmer
which worked just fine.
Those same boards would not program here, nothing worked. And on one PC I
did a full strip and reinstall of studio without repairing the problem.

Very interesting.


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

>
> Can you try and hook up the STK500 as an ISP programmer to the board?
> May have to connect some flying leads if you don't have the ISP pins
> available to a connector.
> If you need it I have a M64/M128 (CONT3) circuit diagram on the download
> page of my website to double check JTAG and ISP pins connection.....I know
> that you know how it all should be hooked up but....:-)


By the time I gave up this AM, I'd tried the STK-500, AVRISP, Official jtag
ice, and a sparkfun jtag ice, across three pcs, different cables, and into
three different M128 target systems, one an STK-500.

The problem is studio.


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

Whats the studio version and service pack, maybe it needs a firmware update. I know that on the very latest up to date version you do need one.

  ----- Original Message ----- 
  From: David VanHorn 
  To: AVR-Chat@yahoogroups.com 
  Sent: Tuesday, August 08, 2006 5:12 AM
  Subject: Re: [AVR-Chat] jtag ice problem


  >
  > Can you try and hook up the STK500 as an ISP programmer to the board?
  > May have to connect some flying leads if you don't have the ISP pins
  > available to a connector.
  > If you need it I have a M64/M128 (CONT3) circuit diagram on the download
  > page of my website to double check JTAG and ISP pins connection.....I know
  > that you know how it all should be hooked up but....:-)

  By the time I gave up this AM, I'd tried the STK-500, AVRISP, Official jtag
  ice, and a sparkfun jtag ice, across three pcs, different cables, and into
  three different M128 target systems, one an STK-500.

  The problem is studio.

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



   

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

David,
My problem was also caused by studio, I was using 4.12 - 472 sp2 at the time
are you using sp2 or sp3.
Owen.

-----Original Message-----
From: AVR-Chat@yahoogroups.com [mailto:AVR-Chat@yahoogroups.com] On Behalf
Of David VanHorn
Sent: Tuesday, August 08, 2006 2:12 PM
To: AVR-Chat@yahoogroups.com
Subject: Re: [AVR-Chat] jtag ice problem

>
> Can you try and hook up the STK500 as an ISP programmer to the board?
> May have to connect some flying leads if you don't have the ISP pins
> available to a connector.
> If you need it I have a M64/M128 (CONT3) circuit diagram on the download
> page of my website to double check JTAG and ISP pins connection.....I know
> that you know how it all should be hooked up but....:-)


By the time I gave up this AM, I'd tried the STK-500, AVRISP, Official jtag
ice, and a sparkfun jtag ice, across three pcs, different cables, and into
three different M128 target systems, one an STK-500.

The problem is studio.


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



 
Yahoo! Groups Links

On 8/8/06, OWEN-A <oldboot@bigpond.com> wrote:
>
> David,
> My problem was also caused by studio, I was using 4.12 - 472 sp2 at the
> time
> are you using sp2 or sp3.
> Owen.



SP3.


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

On 8/8/06, BryanW <purpenuk@yahoo.co.uk> wrote:
>
> Whats the studio version and service pack, maybe it needs a firmware
> update. I know that on the very latest up to date version you do need one.


Been there, done that.  No, studio is CRAP, I'm sorry to say.
I've had problems like this for several years now, and been reluctant to say
it like this, but STUDIO IS CRAP.

I've had major problems with ICE-50 (2), Atmel Jtags(3), Sparkfun jtags(2),
AVRISP(many) on many different platforms and chips, including STK-500/501
boards.

Sometimes uninstalling studio (rip all settings) and reinstalling will fix,
sometimes not.

The pain, frustration, and money that studio has cost me is frightening.


I just got a CableISP from Priio, (nee PRLLC) and it works just fine on two
platforms here that studio still refuses to program with anything I've got.


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

At 04:44 AM 9/08/2006, you wrote:
>studio still refuses to program with anything I've got.

OK I think I know what's happening and should have
thought of it before. :( The latest versions on SP3
both B488 and B490 seem to forget the ISP frequency
settings and reverts back to a high frequency that would
cause havoc especially with new chips.

Even if you change the settings and write it sometimes it will
just change back as you flick the tabs in the programming
windows. May have to do it a couple of times before it
sticks FOR THAT SESSION. Most likely it will be wrong the next
session and may have to do it again.

It seems to be an offshoot of the new Dragon interface and
we have reported it to Atmel (on Avrfreaks). I have been using
JTAG in the past few days both JTAG1 and Dragon JTAG and it
works very well otherwise, but my chips are already set up
correctly and I remember having the same problem with new chips.

Give it a try, what have you got to lose? Your sanity? Too late
for that :-D

Regards

John Samperi

********************************************************
Ampertronics Pty. Ltd.
11 Brokenwood Place Baulkham Hills, NSW 2153 AUSTRALIA
Tel. (02) 9674-6495       Fax (02) 9674-8745
Email: john@ampertronics.com.au
Website  http://www.ampertronics.com.au
*Electronic Design * Custom Products * Contract Assembly
********************************************************

>
>
> Give it a try, what have you got to lose? Your sanity? Too late
> for that :-D


Well, it's deeper than just that..
The ices have big problems too.  They come and go without any apparent
correlation, so there's no way to prevent them or deal with them.. I've had
it go as far as to torpedo a business trip where I went there to load
firmware, and ended up unable to get anything done at all.
Very embarrasing.

Same computer/jtag/cable etc worked fine the day before, nothing was
installed or removed.


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