AVRJTAGICE_MKII revision B problem

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

Hi there,

I am using the JTagIce mkII (revision B) for debuging the AT90CAN32-16AU. The current version of the tools I am using is:

    AVR Studio 4.14.589
    GUI Version 4, 14, 0, 589
    JTAGICE mkII 1, 0, 1, 150
    AT90CAN32 53

    Operating System
    Major 5
    Minor 1
    PlatformID 2
    Build 2600
    Service Pack 3

    Plugins:

    VDMAvrGUI
    AvrPluginAvrAsmObject 1, 0, 0, 46
    AvrPluginavrgccplugin 1, 0, 0, 9
    Stk500Dll 1, 0, 1, 10

An unexpected error has occured for two times now, that's why I am posting it. The problem is: After trying to get on debuging mode using a saved AVRStudio project, althought everything seem to be fine the device cannot be connected with my mkII via JTAG interface. After checking out my circuits for problems and realized that everything is fine, I tried to Tools/Jtag ICE mkII Upgrate, and after this the problem fixed.

As I told you before this problem has occured two time now using the same debugger and diferent devices (both AT90CAN32-16AU).

Do you have any idea or experiense on this???

Michael.

User of:
IAR Embedded Workbench C/C++ Compiler
Altium Designer

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

I'd start by getting an up to date Studio (4.16.628)

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

Ok, I'll install the newest revision of AVRStudio and I will check it again. The problem is that this is a stochastic phenomenon and cannot guess when it will be happen again or if it is fixed.

Thanks anyway.

Michael.

User of:
IAR Embedded Workbench C/C++ Compiler
Altium Designer

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

I feel for ya man.. My FAE is coming in today because of similar issues here. I'm hoping that there isn't an inverse correlation between his distance from me and how the ice behaves.

So far this morning, things have been good, but I've recently lost entire days to "can't connect to target", or "we just decided to always have the WDT on no matter how you set it", or "I don't like the value you loaded in this register, I think I'll change it", or "I just don't feel like executing this part of your code today"....