AVR-JTAG-USB and new AVR-Studio

Development Boards MicroMod
1

Hy!

We bought two AVR-JTAG-USB, and let AVR-Studio download the new Firmware. Now we have the problem, that we can’t use them for the same reasons the normal AVR-JTAG didn’t worked. We also tried to reprogramm the flags as described here: http://www.olimex.com/dev/avr-jtag-upgrade.html

But writing the device was not possible, because PonyProg was not able to find a device (the parallel port ISP was configured correctly).

What do we have to do, to get them working correctly?

Regards,

Andreas Wallner

2

AVR-JTAG-USB needs to take power fromt he target circuit, what power supply did you apply to your target when you wanted to program/upgrade etc?

how AVR-JTAG-USB was connected to target?

Tsvetan

3

Hello!

The problem is not progamming the target (not yet), but upgrading the JTAG. We first tried to auto-upgrade from AVR-Studio, but we got an error while upgrading, and after this, the JTAG is not found by AVR-Studio any more.

While Upgrading the JTAG, we had connected it to a AVR development board, it was connected to 5V supply, and the JTAG was recognized by AVR-Studio. My development board has 5V supply on JTAG Pin 4 and 7, so everything should be fine.

Any Sollutions?

Regards

Andreas Wallner

4

if your upgrade is not finished this means your power supply is weak or have noise

during upgrade flash write AVR needs about 50mA so your target should be able to provide 70-100mA to AVR-JTAG

if your upgrade fail you can manually enable the bootloader in AVR-JTAG as explained on our web and re-flash your memory

Tsvetan

5

Can we reflash the device with a normal parallel port ISP programmer?

6

Hy!

I tried with our second JTAG Adapter after updating to AVR Studio Service Pack 4.

The second isn’t defect after updating.

So we connected the first one. After trying to connect to the target we get the error message on the attached screenshot. Any Idea for a sollution?

http://mbox.htl-kapfenberg.ac.at/user/u … n_jtag.jpg

Regards,

Andreas Wallner

7

I have the same issue. AVR STUdio tried to upgrade my JTAG-USB-UCE and failed. Now It won’t even see the device. I’ve forced it to COM1 but joy.

what the freak do I do now?

DFR

8

Hi,

I have much the same problems:

I have one of the Olimex USB JTAG debugging boards, and have used it successfully for some time with AVR Atmega16, 32 and 64 processors, using AVR Studio as the debugger. A great gadget !

But now I have some new boards fitted with ATMega644 chips, and the selections in AVR Studio do not allow to get to this processor.

I can use the existing JTAG board to read the signature of the AtMega 644, so I know the JTAG interface etc still works, just cant select the correct processor from the available list - the selection for the AtMega644 is greyed out as not available.

I tried an upgrade to the JTAG board using the AVRProg utility, but it complains that “No supported board found” when started, either from within AVR Studio, or when run as a standalone program.

Running Windows 2000

AVR Studio 4.12 service pack 4

AVRProg 1.40

I saw the note about upgrades not being successful unless using Comport 1 or 2, and disabled both hardware comports in the BIOS and in Windows, then set the USB port to Com1, but still could not connect to the JTAG board with AVRProg.

Apart from the problems with not being able to upgrade the JTAG, does anyone know whether this model JTAG supports the AtMega644 ? The help file with AVR Studio suggests not, and that you need a MkII JTAG, ant cost $$$

9

hmmmmmmmmmmm

I had the same problem

10

Just had a reply from Olimex to say that as far as they know, Atmel only support the later chips, eg AtMega644, with their JTAG MkII. So even if the upgrade works, its no go for these anyway. Bummer. Guess we fork out US$300 or so for their device.

Seems to me its ‘only’ a matter of incorporating the different control codes in whatever JTAG adapter you have… are you listening Olimex ?

11

I should have read this before upgrading, now here’s another dead AVR-JTAG-USB. Any news on this issue?