Dragon not recognized by Studio 7

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

Just got the Dragon but I cannot get ATMEL Studio 7 to recognize the Dragon.

Running Windows 10 (new computer).  Latest Studio 7-when it was installing it indicated the USB drivers were installed.

I want to use the JTAG to debug a BC Micro MARVIC-1B development board  (Atmega128).   The connections look correct.

I had been programming it over ISP with a STK500.

 

The Led next to the USB connector is lit green, indicating that the USB is connected (I think).  The other LED is red indicating that the Atmel Studio is not recognizing the Dragon (I think).

 

Any ideas about what to try?

 

*Moved by moderator*

Last Edited: Wed. Dec 16, 2015 - 07:10 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Welcome to AVR Freaks. 

 

You are not the first with this problem. See this thread (toward the end): 

 

https://www.avrfreaks.net/forum/s...

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

Last Edited: Wed. Dec 16, 2015 - 02:35 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have a similar issue, without the W10 "feature". Running W7/64 SP1, AS 7.0.634, Visual Micro 1511.21.0, Jungo atmelwindrvr v12.0 & WinDriver v11.5, and an AVR Dragon 17/7.2.7.

 

Trying to work with a Sparkfun Pro Micro 3.3V/8MHz with an ATmega32U4. Enabled JTAGEN and OCDEN fuses via SPI.

 

When all wired together, either SPI or JTAG, and AS running but nothing attempted, the Dragon's status LED is red, indicating "Idle, not connected to the software front-end"

 

Using AS Tools/Device Programming, the Dragon appears and will connect with the target. While connected, the LED is dark, indicating "Idle, connected to the software front-end". Using either interface, the target can be read and fuses toggled. When the Device Programming is closed, the LED returns to red.

 

Dragon is listed and selected in project properties. After starting a debug session, the LED remains red, the additional items do not appear in the Debug/Windows sub-window and breakpoints not-in-the-main-program are not honored.

 

I have found nothing that tells me how or where to install the BSDL file that supposedly tells the Dragon about the 32U4 or for that matter, a BSDL file for a QFN pkg 32U4.

 

The reinstall-everything fix described by Jim and Bernd had no effect.

 

Any ideas ?

 

Mike

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

The fact is that AT St 7 is a pathetic program and it is full of issues. I would suggest to down grade to lower version of ATS and try to get the dragon to work.