SAME70 error: Could not activate interface, but found DAP with ID 0xbd11477.

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

Hello I am designing my own board for SAME70 and using ATMEL ICE to detect the target. the following error I am facing 

Could not activate interface, but found DAP with ID 0xbd11477. No external crystals stuffed. Please help me getting it solved. Thanks in advance. Waiting.

Last Edited: Fri. Jan 20, 2017 - 06:03 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What kind of interface you are using?

I had this issues only by using the JTAG Interface. With SWD this never happened

 

Maybe you have to reset your µC. This is to be done by pulling up the erase pin (PB12) to 3V3. See the manual at "7.5 ERASE Pin"

 

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

Using SWD interface. I rechecked my connections, programming jumper was faulty. I am having same issue on SAM E70 Xplained Evaluation Kit, i have 2 boards both having same behavior. Microcontroller goes to deep sleep after a few seconds. What is the issue? 

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

In this case i would suspect an issue in the clock settings, but this difficult to find out. What says the debugging function of Atmel Studio? In which section of code stops the software?

 

Or in General is the software flashed correctly? When i am programming a new "fresh" ATSAME70 sometimes the µC hangs up in look a like deep sleep. I solved this by flashing an simple example project of asf studio.

 

 

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

Thanks Horn, I tried asf example code and yes it doesnot go into deep sleep. What is the reason for this deep sleep when i run my code? 

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

Good question,

in your position i would check the clock settings.

If this doesn't work, go step by step with Atmel Studio Debugger along your code. Then you will see where it hangs up.

In my projects i often found empty while loops in asf source code, when something couldn't get started or Hardware modules are requested.

 

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

It happens to me always on the first time the flash is blank. The second access with the same command (doesn't matter what is the command) works fine. It's easy to see this with Atmel Studio or Atmel Command Prompt.

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

SOLVED (sort of):  I've developed my own board around the ATSAMD21G18A and programming with Atmel Studio 7.0.122.  From the Device Programming menu I'm programming via the SWD using a JTAGICE3.  SWD clock set to 2MHz.  I can read the device signature and target voltage (3.0V), set fuses, security bit, and erase the flash.  The one thing it wouldn't do was program.  When I tried it always came up with the "Could not activate interface, but found DAP with ID..." error message.  To fix, I unchecked the "Erase Flash before programming" and Verify Flash after programming" options.  Then clicked "Erase Chip" and "Erase now", then "Program".  It fails the first time, but clicking the "Program" button again allows it to program.  Then I can press "Verify" and it passes.  Go figure.

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

Thank you. I had the same Problem with an ATSAML21E18B and your soloution saves the day.

 

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

Same problem only with the ATSAMD20E14A. And unchecking Erase and Verify allowed me to program from the that window However, I can't programming using stdio debug button, so I can't debug. Any clues? Thanks in Advance.

Stay Calm and Listen to the Grateful Dead

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

Same problem. Working from Device Programming window but impossible to debug the board. Did you find a solution?

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

Trying looking at the Reset pin on the debug header. That was my problem.

Stay Calm and Listen to the Grateful Dead