EDBG tool not available in AS6, driver seems to be wrong

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

I bought a G53 Xplained Pro eval kit a while ago and everything worked fine. I sent it to a guy who works for me and bought another one for myself. When I plugged in the new one, nothing happened. By that I mean AS6 didn't do what it did with the old one - recognize it and offer to immediately let me work with the eval kit.

I've tried everything: reinstalling AS6.2, updating the ASF (I know this has nothing to do with it, but still), reinstalling Atmel USB drivers (I downloaded the installer from the Atmel Gallery), and trying it on various USB ports. I have no idea what to do next.

In device manager, the dev kit device is listed as "AT32UC3A3" under "Atmel USB Devices." I never looked at it when I had the first dev kit, so I don't know if this is different than it was before, but I did search the forums and it appears that the device should be bifurcated into an EDBG device and something else.

I tried updating the driver by pointing specifically to the Atmel USB driver directory, but it said it found the most recent driver, which identified the device as AT32UC3A3 again.

I'm at the end of my rope and I don't know what to do. This is halting progress on a product release and Atmel support hasn't responded yet. Please let me know if you have any ideas.

Attachment(s): 

Last Edited: Fri. Jun 27, 2014 - 06:24 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

IIRC, AT32UC3A3 is the actual microcontroller of the EDBG.

If it's showing up as that, maybe they forgot to load the EDBG firmware into it in the first place :?:

I'd have a word with your supplier...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

awneil wrote:
IIRC, AT32UC3A3 is the actual microcontroller of the EDBG.

If it's showing up as that, maybe they forgot to load the EDBG firmware into it in the first place :?:

I'd have a word with your supplier...

I got it from Mouser. Do they actually program it? I figured Atmel did that because the EDBG IC isn't externally available (or is it?).

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

Small update: Mouser told me to contact vikings.avr@atmel.com to see if they can help. I sent an email with a link to this thread, so we'll see what happens.

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

bandtank wrote:
I got it from Mouser. Do they actually program it?

No, they don't - but, as your supplier, they should be your first port-of-call.

Also, if this is the problem, it could well be a batch problem - so they would probably be aware of it by now...

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bandtank wrote:
I figured Atmel did that because the EDBG IC isn't externally available (or is it?).
Proprietary and only in Atmel's tools IIRC; likely for Atmel firmware signing, encrypting, securing.
Firmware upgrade (Atmel, webdoc, Atmel Studio) (I hope for I don't know by that experience that you're enduring)

O.T.
Another use of an AVR32 UC3A3 for signing, encrypting, and securing is Crypto Stick Storage.
First batch of Crypto Stick Storage beta (German Privacy Foundation, 2014-06-13)

"Dare to be naïve." - Buckminster Fuller

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

It's horked - you've only got the raw bootloader and not the actual EBDG stack. It's not a normal UC3A3 part but is based on it, and you won't be able to load the firmware yourself (this must be done at the factory).

Contact Mouser for a RMA.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

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

abcminiuser wrote:
It's horked - you've only got the raw bootloader and not the actual EBDG stack. It's not a normal UC3A3 part but is based on it, and you won't be able to load the firmware yourself (this must be done at the factory).

Contact Mouser for a RMA.

- Dean :twisted:

Thanks. Working on that now...

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

The replacement wouldn't enumerate properly until I reinstalled the Atmel USB driver package again. It's working as expected at this point. Thanks for the help everyone.