The Original Serial AVRISP

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

I have used the serial AVRSIP for many years now. It finally went to AVR heaven. i tried to get another one at digi key but no good. in fact i cannot seem to find anyone still selling these serial version AVRISP's anymore.
they seem to replaced my the newer USB version, which my compiler CodeVision, does not support yet.

https://www.avrfreaks.net/index.php?module=FreaksTools&func=viewItem&item_id=204

Does anyone know of someone who got a few of these new still laying around ?

Thanks
Jim

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

How about using AVR Studio (which does support the mkII) for program uploading instead?

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

Thanks, but then i would need to run two programs instead of one. My Compiler has the programer solutions built in except for this new verison ISP.

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

Hmmm. Sorry, I am operating in an environment where I write all kinds of code, but I very rarely get the chance to actually ISP-program anything.

OTOH, I work with folks who ISP-program things on a regular basis, but who've never even seen the source code.

In this set-up, it really doesn't matter if I'm using different software than my colleagues. Personally, I don't mind opening AVR Studio when I need to "get my hands dirty", even though I can also get the same functionality through WinAVR's integration of avrdude with Programmer's Notepad through the makefile system.

So it hadn't occurred to me that it might be a problem for somebody else.

You could add a link to AVR Studio using CodeVision's Tools menu. That way, at the very least, you could get into AVR Studio using an automatic hotkey from within the IDE instead of having to navigate to it through the Start Menu.

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

again, thanks for the help. My situation is more complicated.
we write mission critical software. having said that, there are all kinds of writeup for every step of the way even how to flash program the AVR. all that paperwork is checked and certified and approved. from that point on nothing can be changed without having go through the whole process over again. this is why i just want to get a handful of these AVRISP MKI's and keep on going with my work and not create more work for me right now. I know this will catch up with me later, but right now i need to keep on trucken...

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

How hard a compromise would it be to use one of the AVRISP "clones" within the existing processes?

(ie. hardware "inspired" by looking at the original AVRISP schematics, and running either the original AVRISP firmware as provided by Atmel for the original equipment, or "patched" firmware unique to the particular host MCU selected)

Such a "clone" would appear identical to the original as far as your host PC software is concerned, so programming procedures could remain the same.

I have seen clones on the Web that range from direct piece-by-piece copies of the Atmel-provided equipment (right down to the ATmega8535 host and ATtiny2313 upgrader chip), through to ATmega8-based solutions with customized firmware.

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

it has to be the same thing. I found a company that has 6 of them left. i am buying them all ;)

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

You could write a .bat file that runs the cmd line version of stk500.exe and call the .bat file from the cv ide? (iccavr lets you add cmd lines to be executed after the build)

Imagecraft compiler user

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

Same prob, Bob -- His organization has established procedures how how every AVR firmware upload has to go.

The procedure specifies exactly which software needs to be used -- it probably even specifies exactly what sequence of mouse-clicks need to be followed.

Judging from what has been stated so far, selecting to use a different piece of hardware would require a change in the procedures, even if it didn't require modifications in the software used or the individual keystrokes involved.

So I'll bet that using a mkII would not have been regarded as an acceptable "qualification-free" migration, even if CodeVision already had built-in support.

As I see it, the point of this post is that absolutely nothing can be allowed to change (in either hardware or software) or else the whole product qualification process will have to start over right from the beginning...

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

1) Pavel said at it is working to implant the USB AVRISP.
2) To day I open AVRstudio + AVRISP (USB) with link to my *hex & *eep directory. And after to have compile I just use AVRstudio to program with USB.
Work nice.
Thierry

Thierry Pottier

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

jimparisi wrote:
I have used the serial AVRSIP for many years now. It finally went to AVR heaven.

What happened to the original programmer? No status LED? stays red, won't see target???

I'd be willing to take it off your hands if you don't want it anymore.

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

Quote:
What happened to the original programmer?

Does the programmer have a Mega8535 or an AT90S8535?
Quote:
absolutely nothing can be allowed to change (in either hardware or software)

Would not a change from an RS232 type to a USB type programmer (which Jim was looking at but not supported by codevision yet) be deemed as a change requiring at least an operation manual change?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Quote:

Would not a change from an RS232 type to a USB type programmer (which Jim was looking at but not supported by codevision yet) be deemed as a change requiring at least an operation manual change?

I would think so. In fact, that was the point I was trying to make...

The OP has essentially stated that substituting a totally software-compatible clone of the mkI would be considered unacceptable, so IMHO, transitioning to the mkII would never have been a viable option in the first place.

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

see olimex there is good progs schematics you can also buy

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

hi guys, i found one in my old junk cabinet. Hopefully this one will make it until Pavel gets the USB support. ;)