codevision doesn't see AVRISP MkII

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

I've just installed CodevisionAVR Eval ( 2.04.8 ).
I have an AVRISP MkII (with latest firmware) that works just fine with AVR Studio 4.18. But WinAVR-20100110 doesn't contain libraries for the Tiny10. So I thought I'd try CodevisionAVR.
However, Codevision doesn't seem to be able to communicate with the AVRISP MkII.
In Programmer settings, I've selected "Atmel AVRISP MkII (USB)". But when I try to read the Chip Signature or the Programmers Firmware Version I get an AVRISP MkII Error that it can't read the Chip Signature or Firmware Version.
I'm sure I can't be the only person the have had this problem.
Any help, guys?

Jim M., Rank amateur AVR guy.

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

Do you still have Studio open at that point?

Did you heed the note about ensuring the latest firmware version?

What are the status of the LEDs? What does the help in AVRStudio say about what that indicates? Are you providing Vcc to the ISP?

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

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

theusch wrote:
Do you still have Studio open at that point?

Did you heed the note about ensuring the latest firmware version?

What are the status of the LEDs? What does the help in AVRStudio say about what that indicates? Are you providing Vcc to the ISP?


Thanks for the reply.
Studio is not open at the time.
The AVRISP MkII has the latest firmware.
The AVRISP power LED is green, the status LED is green when connected to the chip which has 5V supplied.

Again. If I open Studio everything works. If I then close Studio, and open Codevision, it does not.

Jim M., Rank amateur AVR guy.

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

I have CodeVisionAVR and also the MKII. You may need to lower the frequency choice in the programming dialog box. My target has a 7.6MHz crystal but I have to set the frequency to under 2MHZ for good programming. I think there is a rule about it needing to be 1/4 of target. Setting lower just takes longer to program.

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

alwelch wrote:
I have CodeVisionAVR and also the MKII. You may need to lower the frequency choice in the programming dialog box. My target has a 7.6MHz crystal but I have to set the frequency to under 2MHZ for good programming. I think there is a rule about it needing to be 1/4 of target. Setting lower just takes longer to program.

The frequency option is there if I select a chip like the ATTiny13. Then I can read the firmware version; Major: 1 Minor: 13 with an SCK frequency all the way up to 500kHz. However, there is no SCK frequency selection for the ATTiny10 (or the ATTiny4 either).

Jim M., Rank amateur AVR guy.

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

Is it possible to write/compile the code with CodevisionAVR and then use AVR Studio to write the generated hex file to the Tiny10?

Jim M., Rank amateur AVR guy.

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

It works.

I'm not sure exactly what did it. I was on AS 4.18SP1 (thought I was on SP2). Upgraded to SP2. Upgraded AVRISP MkII firmware. No change, still at 1.13.

Opened CV, tried to read chip sig. Didn't work. Switched to ATTiny13, tried to read sig. Didn't work. Switched back to Tiny10, read sig worked. I've uploaded the flash and the chip is running as expected.

Hmmph. Go figure.

Jim M., Rank amateur AVR guy.

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

I was having the exact same issue with AVR Studio 4.18 and SP2 not working with AVRISP MK II. It used to work and then it no longer can be detected by AVR Studio 4.

I downloaded AVR Studio 5 beta and it recognizes AVRISP mkII with no issues at all. I tried JTAGICE mkII and no problem. JTAGICE 3 also works just fine.

I like the new interfaces and design on Studio 5 a lot. I highly recommend using it.

I guess if you wait long enough, AVR will deliver something better. Although there's no excuse for crippling tools with a new revision of software. On the side note, AVR Studio 5 is programmed with VS C++ 2010 and it is using .NET Framework 4.0. I hope Microsoft doesn't get the idea of acquiring Atmel altogether. That would be annoying.