Dead JTAGICE MkII needs factory bootloader

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

After many years of fine service, I managed to erase the Atmel proprietary bootloader (AVRBLDR) on my JTAGICE mkII. I know for a fact the hardware itself is perfectly fine.

My attempts to contact Atmel customer support for help culminated in a loop of being asked to contact the group where I started after about a month of back-and-forth. They were all very un-helpful at best.

I found a couple of other posts from people with the same problem, but no one ever posted back with any solution.

In the meantime, to get on with work I purchased another mkII, but it seems a shame to toss the old one in the trash just because the bootloader is gone.

Does anyone know a way to get this back to "factory fresh" condition?

Thanks...

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

As Atmel provide main firmware images for devices like ICEmkII as encrypted binary file (.ebn) and it's the bootloader that decrypts the image using some hidden secret I guess your question to Atmel is like asking them for the key to the cupboard where they hold the family silver, hence their reluctance to help (even though ICEmkII is now effectively a dead product).

It does seem a shame that for a $300 product (with about $50 of components) that Atmel don't offer a return-to-base refurbishing service.

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

How did you manage to erase the bootloader?
and why did you get the fancy idea of doing that?

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

Ironically, you may be able to snarf it out of one of the Chinese kmII clones that they were trying to prevent by this very situation :)

Mike Adams
ADI Development, Inc.
http://www.adidev.com

... When it has to actually work.

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

cooluser wrote:
How did you manage to erase the bootloader?
and why did you get the fancy idea of doing that?

By connecting to the internal 10-pin JTAG port with a dragon. I was exploring with avrdude and the erasure was accidental.

And why? The mkII operating firmware had locked up again, as it has done a half-dozen times in the past. Reloading the firmware brings it back but at the time I didn't have a running copy of AVR studio.

I use linux and I was looking for alternative ways to reload the firmware without having to install AVR studio yet again just for this task.

Was it my fault? Absolutely.

Should standalone tools+firmware be available for windows and linux to deal with the programmer devices (aka atfw.exe/avrfwupgrade)? I think so. That's all I really needed in the first place.

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

dr.mike wrote:
Ironically, you may be able to snarf it out of one of the Chinese kmII clones that they were trying to prevent by this very situation :)

Yes, I thought of that too and went looking for firmware, but I was unable to clearly identify which one of the clones runs the original Atmel firmware.

Do you know which one?

I'll try anything on the dead unit. I can't make it any worse.

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

clawson wrote:
As Atmel provide main firmware images for devices like ICEmkII as encrypted binary file (.ebn) and it's the bootloader that decrypts the image using some hidden secret I guess your question to Atmel is like asking them for the key to the cupboard where they hold the family silver, hence their reluctance to help (even though ICEmkII is now effectively a dead product).

It does seem a shame that for a $300 product (with about $50 of components) that Atmel don't offer a return-to-base refurbishing service.


Knowing the sensitivity of the decrypting bootloader, I had actually asked Atmel to allow me to return the unit for service and I would gladly pay for the restoration.

They wanted nothing to do with such a support request, apart from "buy a new one".

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

Quote:

Yes, I thought of that too and went looking for firmware, but I was unable to clearly identify which one of the clones runs the original Atmel firmware.

Do you know which one?

I'll try anything on the dead unit. I can't make it any worse.

Not off-hand. But, I assume it would be one of the ones that say that they accept the Atmel firmware updates ?

Mike Adams
ADI Development, Inc.
http://www.adidev.com

... When it has to actually work.

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

Quote:
They wanted nothing to do with such a support request, apart from "buy a new one".

They are in effect saying they don't want your business and you should use dspics instead.

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

dr.mike wrote:
Quote:

Yes, I thought of that too and went looking for firmware, but I was unable to clearly identify which one of the clones runs the original Atmel firmware.

Do you know which one?

I'll try anything on the dead unit. I can't make it any worse.

Not off-hand. But, I assume it would be one of the ones that say that they accept the Atmel firmware updates ?


For the record, I think it's this one here:

http://www.pic16.com/en/wzcapi/avrjtagicemkii.htm

There doesn't seem to be any bootloaders around for it either. After all, how dare anyone try to take their bootloader when they worked so hard to steal it from Atmel.

But I give up. I've used up enough time on this and it's not the first time Atmel support has demonstrated their helpful attitude. We're probably moving away from Atmel anyway for future products.

If anyone has one of those clones and wants to post or PM me the bootloader (if it can be extracted, that is), I'll give it one last try. Thanks...