jtagice mkii failed programming......

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

Hello, I've got two jtagice mkii's that don't want to program or debug. I might have blown them up in some horiffic disaster but it could also be a result of upgrading my avr studio to 4.18 sp1 (coincidence?).

Has anyone else discovered their jtagice mkii programmer is now useless?

Has anyone dared fix a broken jtagice or shall I bin it and buy another? It connects to the pc ok, the lights come on and it talks to the program applet but it can't find my processors on jtag, pdi or isp.
My dragons work fine on the same processors, except the pdi option just tells me it failed to set emulator or something so i assume that's just a dodgy pdi implementation (have seen other posts). There are some multiplexer chips down by the fpc connector that may need replacing maybe? Any help appreciated.

Cheers.

John.

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

Quote:
it talks to the program applet
Not sure what you mean by "applet". It's unlikely that both have blown up unless you have a guilty conscience :). Have you tried a manual upgrade of the firmware?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

I power up the target board and the MKII. That may help.

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

Quote:

Not sure what you mean by "applet".

The applet is the dialog box that pops up when the programmer icon is pressed.

Quote:

Have you tried a manual upgrade of the firmware?

I have manually loaded firmware and also tried different versions of studio, replacing the firmware everytime.

Quote:

It's unlikely that both have blown up unless you have a guilty conscience

There was a minor incident involving a board, programmer and an incorrectly wired brushless motor but it seemed like the problem was resolved after replacing the hall effect sensors and the programmer still worked with the debug wire link. This might account for one of them being broken!

Quote:

I power up the target board and the MKII.

I don't think I have ever not!

I have previously had problems with the little flexi cable before and have replaced it on both programmers. It is now longer by about 20 or 30mm, I've been using the one programmer for a while (6 months) like this and it's been fine. The other has been in the cupboard, i'm sure it worked when it went in but it was a while ago though and my memory suffers from severe corruption and loss.

I've got other stuff I can get on with today so I might order another from farnell and go from there, thanks for the suggestions chaps.

John.

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

Turns out both are blown up!! I've identified the problem ic's, see attached. The 1st is a driver IC of some description that drives the TDI line and the 2nd looks like it's taken out a few of the interface chips which I now have on order.
The problem is the 1st which only has the marking BB on it so it could be anything... does anyone have any idea?
I've got a new one on order but it would be nice to get them working again.

Attachment(s): 

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

The 2nd is just a bunch of transorbs in the same package. It died in my JTAG, got some from Farnell and all is well. I would just remove it and see if it starts working...carefull no static protection without it.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly