Getting uisp to work in cygwin?

Jun 04, 2005 7 Replies

Has anyone encountered problems getting uisp to run in cygwin? I'm using 20040311, and savannah.nongnu.org seems to be down so I can't check for a newer version.


20040311 works fine inside Linux and MacOS, but when I try to use it in cygwin the STK500 doesn't respond at all. I see some activity on the serial port with a scope, but nothing coming back.

I haven't tried either one, but WinAVR (at least the July 2004 version) comes with MinGW versions of both uisp and avrdude that seem to work.

I've also heard you may want to transition to avrdude, as uisp support is drying up.

HTH, -=Dave

-=Dave

Change is inevitable, progress is not.

What do you use? AVR Studio? I need an open-source commandline programmer because I need to be able to embed fuse and program memory writes in a single-step make process, AND it has to run on Linux.

Hmm, thanks for that latter point. It wouldn't be much work for me to convert the makefiles over.

Have you guys tried the latest AVRStudio 411b406SP2 with the SP2 patch? Same with latest WinAVR 20050214? I recently purchased an STK500 DevKit and am trying out some C development with WinAVR. I noticed when using the previous AVRStudio WinAVR combo that avrdude worked fine. Not any more. I now have to always program the board through AVRStudio. It seems that the firmware upgrade that AVRStudio always does when used for the first time broke something with WinAVR. (Also tried BASCAVR and it seems that their programmer does not work anymore either.)

Does anyone have similar experiences? Or is it just my system?

*S*it!!*

I didn't think of that at all. I have been using my STK500 happily on other systems (mostly under Linux) for a long time. I had not "upgraded" it via AVR Studio for a year or more. A couple of days ago, I installed Windows temporarily because I want to run a Micro-Cap simulation while working on my code. Of course I downloaded the latest AVR Studio and of COURSE it broke my STK500 with its stupid firmware "upgrade".

Ulf, if you're reading this: Please go across to the office of the idiot SOB who did this and kill him, as slowly and painfully as possible. Post pictures. You should not be breaking programmers silently like this. If it is necessary to upgrade the protocol for a new micro, then tell the user that he needs to upgrade ONLY IF THE NEW MICRO IS SELECTED AS TARGET!

*steaming*

Lewin,

my vote for avrdude, too.

Tauno Voipio tauno voipio (at) iki fi

Atmel dramatically changed the communication protocol of the STK500 starting with Firmware revision 2.x. This broke most third party tool support.

But things are looking up - we have STK500 V2 support now in the new beta release. You can find AVRDUDE 5.0-BETA on the savannah download page for the project (no Windows binary yet, sorry).

formatting link

Remember, this is beta and there are still a few rough spots.

Another much anticipated feature of this new release is JTAGICE MkII support. We support programming only, not debug, of course, since AVRDUDE doesn't know anything about debugging.

-Brian

Brian Dean bsd@bsdhome.com http://www.bsdhome.com/ http://www.bdmicro.com/

We've got Windoze boxes for development, so we use CodeVisionAVR and PonyProg. Both work reasonably well.

Though we haven't upgraded AVR Studio in quite some time. ;-) Even if we had, we use the STK200-style serial programmer.

FWIW, PonyProg is under the GNU license and runs under Linux.

formatting link

For production, we have in-house software for our bed-of-nails tester.

Regards,

-=Dave

Change is inevitable, progress is not.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required