AVR ISP MKII won't connect on XP systems

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

I've been using the MkII on my Win2k systems for a long time, no problems. I just connected it to an XP Pro system (with Studio 4 already installed), let the system do its install thing when it saw the MkII, and then tried to connect from Studio - Connect Failed! Plugged it back into my Win2k system, all ok. Go to a second XP system (also with Studio installed), again I can't connect.

It's the same version of Studio on all machines (4.13 build 528). Is there something special about XP???

Thanks,

Roger

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

Sorry, too much of a hurry.... It's a JTAGICE MkII, not an AVR ICE

Roger

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

Try to connect the MKII via serial port.

If it's working you will know, the error is in the USB com/driver.

Gergo

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

Have you found the cause for the problem yet?

I have similar problems with JTAGICE MkII, but on a Win 2k system.
I used AVR Studio 4.12 and mostly everything was ok, but in the debugger it ignored the memory locations I defined in my project (WinAVR). The HEX output is ok, so there is no big problem. When I installed 4.13 it showed the memory correctly, but the JTAGICE stopped working.

Now I removed 4.13 and installed 4.12 again.
Who else has similar problems,or better - a solution?

Dirk

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

wero_ee3 wrote:
but in the debugger it ignored the memory locations I defined in my project (WinAVR).

Can you add more detail to what you mean by that? - just sounds a LOT like optimisation to me.

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

I am using a Tiny13 and wanted to store some Information (Software version defined in the software, serial number generated by the device programmer, and so on).
I defined a memory segment beginning at 0x3f0 (the last 16 Bytes in the program memory)
This is done in the memory settings by:
LDFLAGS += -Wl,-section-start=.Ser_Num=0x3f0

In the software:
const unsigned char Data[16] __attribute__ ((section (".Ser_Num"))) = "123456789 112233";

In the Hex-output the version number appears as it should, but in the debugger I dont see it in the memory window (all Bytes FF). But when I read these bytes in my programm the information is there.

This was the reason for installing 4.13, because this was solved (at least in the simulator, because debugging is not possible).

At the moment im using 4.12 again and manage to live with the problem that the information is not displayed correctly.

Hope this helps to understand the problem.
But still, with 4.13 the JTAGICE is not working?

Dirk

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

Oh right, I understand now - that ELF parsing problem in 4.12 is actually something I reported to Atmel and that they then fixed for 4.13

I'm not sure what your problem with JTAGICEmkII and 4.13 in W2K can be as that's EXACTLY the combination I use and it works just fine here. I can only assume it's something to do with USB driver installation?

As Gergo suggested to the OP above - a way to isolate whether it's a USB issue is to connect the ICE via RS232 instead - how does that work for you?

Cliff