Studio5 AVR ISP MK2 Programming Problem

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

Hey Guy's

i'm new in this forum so please be patient with my first entry here.

I'm programming on avr's since a while. Till now always on win xp, with my avr isp mk2 (factory firmware - 20080211). Every device was working fine, no problems.

Now i upgraded to win7 x64, avr studio 5 and also did a firmware upgrade (with the avr studio 5) at my avr isp mk2.
The installation of the avr studio and the isp happend without any errors. But when i try to programm my devices (2x ATMega32, 1x ATMega128) i got this error message:

Programming session setup failed: TCF command: Device:startSession failed: Code:1 ,Service: ,Message from peer:Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00

what can this mean? the isp and the devices worked well till the update came? did i miss any config parameter?

Thanks for your help!
charly

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

forgotten to say, when i connect the isp to the atmega the led switches from red to green.

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

I have the same exact problem. I'm using the ATtiny2312. The system recongnizes the device just fine. it can read the voltage but when i try to do anything with the device it gives that same error:

Programming session setup failed: TCF command: Device:startSession failed:  Code:1 ,Service: ,Message from peer:Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00

Any help would be great! Thanks!

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

I'm not alone, it doesn't solve the problem but it fine to see that others have this problem too.

the voltage reading is also no problem with my isp.

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

I also tested it with AVR Studio 4.18, Still could not enter programming mode. Installing on another system now to see if that helps.

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

I fixed my problem. It was a problem with the header i made, i had a pin shorted with another. Works fine now.

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

i'm using the example project's to test it ... nothing changed till now.

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

I have got the same error warning and can not read out the fuse setting, search for advise.

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

I've the same error too. First I though I messed up something in my Butterfly (ATmega169) so I got another exactly same unit that I didn't program at all, it still has factory demo code running. New unit shows the same error. Tried to search the Internet but nothing helped so far. May be somebody on this forum know how to fix it or diagnose further.

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

Brand new to this site, Brand new to these chipsets, Hello! I've got a similar problem. I bought two ATtiny85 chips, and a ATAVRISP2. I have 2 green LEDs, and am trying to program a hex code to one of them, for a SD card reader project I saw online (Reads wav file from SDcard and plays it through speaker).

-ATtiny85
-AVR Studio 5
-ATAVRISP2

In AVR studio 5 I setproper tool, device, interface, hit apply, and it takes me to the clock speed screen. I have tried every clock speed in this list down to 2.152KHz, but when I hit 'Read' on either device ID or Voltage, I get an error.

Quote:

Unable to enter programming mode. Please verify that the programmer is correctly attached to the target and that target power has been switched on. Also verify that the correct device and interface settings have been specified.
Timestamp: 2011-10-29 11:22:42.733
Severity: ERROR
ComponentId: 20100
StatusCode: 0

Programming session setup failed: TCF command: Device:startSession failed: Code:1 ,Service: ,Message from peer:Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00

Wiring is correct, and I have verified it 4 times myself and had others check. I've tried inserting an external CLK @ 1MHz. i've used both power sources from the USB and from a DC power supply. I am completely stuck and frustrated for the last 3 weeks.

PLEASE HELP!!

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

try using AS4

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

Just got done trying that. Getting the same type of error, cannot program. And with AS4 i can't even get both green LEDs. In re-installing AS5 right now, so i can compare things.

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

From what i'm finding online, I cant use an ISP unit to program these on the first go. Is this correct?

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

Quote:

I cant use an ISP unit to program these on the first go. Is this correct?

No not correct - AVRISPmkII will happily ISP mega32 and mega128 from AS4.

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

HI, I HAVE THE SAME PROBLEM, BUT I KNOW WHAT IS THE REASON, [ERROR] TCF command: Device:startSession failed: Code:1 ,Service: ,Message from peer:Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00, IT IS BECAUSE WE HAVE TO PROGRAM THE FUSES OF THE MICROCONTOLLER, IF YOU WANT YOU CAN SEND ME AN E-MAIL, mikenutp@hotmail.com

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

I have just started having the same problem. It happened to me with ATtiny13A. Starting from the virgin chip, I've selected a 128kHz internal clock fusebits in AVR Studio 5.1. Ever since the chip won't talk and I'm getting the same error as mentioned before.
By the way, the same error is issued when there is no target device, or fusebits are misconfigured (In my case it was either SPIEN or RSTDISBL, so ultimately the chip acted as if it was not present). Otherwise my setup (win 7 x64, AVR Studio 5.1, USB AVR ISP STK-500 fake) works okay.
Oh, and the only properly read property is the voltage, just like mentioned before.
:roll:

EDIT: Yay, I've made it! Since the chip operated at 128kHz I had to slow down the ISP clock in Interface settings screen (I've turned that down to 1,747kHz). To make things work, I have reduced the baud rate of virtual COM port (the one used by my programming kit), to comparable value (that is, 1800). It was not good enough to program the chip (I think the transmission got busted because of the frequencies mismatch), but I was able to restore the 9.4MHz fusebits setting. yay!
By the way, something fishy is going on about ISP programming. Anyways the producer of my USB "dongle" recommends using 115200 kbps which matches an option in AVR Studio, so I'll just stick to it. Perhaps the others struggled with similar mismatch too, hm?

ANOTHER EDIT: It seems that one is able to type in the individual ISP clock value in interface settings (forget about the slider thingie) after all. It keeps on "rounding" my 1.8k value down to 1.798k for some reason, but works like a charm now. Flash verification is successful on all occasions.

Not entirely familiar with AVR thingies... yet.

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

Just wondering if any of the posters had this problem with Avrisp mkII in PDI mode?

I can't get mine to program or erase an Xmega (Xplained board) but it will read intermittently!

See this thread for more info: https://www.avrfreaks.net/index.p...

Avrisp mk ii
Xplained Atxmega128A1
ATTiny13, Mega328, Mega8 etc.
Pololu USB AVR Programmer
Open Workbench Logic Sniffer
AVR Studio 4 & 5

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

Hi there
I have the same problem (ispEnterProgMode: Error status received: Got 0xc0, expected 0x00)
Can´t read the procesor info.
Have someone find the solution for this?
---------
MKII, AVR6, win7x64

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

what is your programming speed set to?
is it a virgin device or have the fuse bits been set to other values?

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

Hi everybody,

I had the exact same problem. After hours of trying to solve it, I've found THE solution: you simply have to connect a Xtal to your controller. It obviously has to be the exact same value that you specified in your config.
That is really stupid but it worked for me. I guess this is a feature of the atmel chips.

I hope this will help the following ones!

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

Quote:

you simply have to connect a Xtal to your controller.

Only if you have changed the clock selection fuses from the default internal RC oscillator to 'external crystal'.

Quote:

It obviously has to be the exact same value that you specified in your config.

For programming, actually no.

Quote:
That is really stupid but it worked for me. I guess this is a feature of the atmel chips.

The stupid thing here is the guessing. Don't guess. Read the documentation. For programming, any AVR needs a valid clock source. The default from factory is to use the internal RC oscillator - for all AVRs in production this means the AVR is running at 1 MHz. If you've changed the clock selection fuses to 'external crystal' then you need to have one attached.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

Hi Guys, I've managed to solve this.

If you are able to program fuses - and as I've noticed you are, set your clock to 8mhz internal oscilator.

Now go to IPS frequency, change it to 1Mhz.

And go, will work.

[If you have other frequnce, set ISP freq it to 1/4, 1/8 of it and try if it works]

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

hi!

 

I had the same issue on the AS7.0 + Atmel-ICE.

 

thanks to MECAMIKEN I resolved the issue. In my case I have in the code fuses configuration and from some reason the Atmel-ICe cant program the fuses by debugwire.

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

Uh it's much more crazy than expected, if you get this code but you can debug chances are you have to turn off debug wire to get back to the fuses. The only way that you seem to be able to do this is start debugging your code, hit pause, then go Debug->Disable debug wire and close. This option won't show up if you don't pause it. Seems like a rather silly feature to me.