Debugger Failure

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

I am using an ATmega168 Xplained development board.  I am able to compile and program my code onto this PCB, however, when I try to use the built in debugger, I get an error.

 

First it says, "Failed to launch debug session with debugWIRE.  This could be caused by reset line circuitry or disable debugWIRE interface.  Make sure that the reset line is free before continuing.  Do you want to use SPI to enable the DWEN fuse."

 

If I click yes, then I get the error, "Failed to enable DW: Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (command has failed to execute on the tool)"

 

This is an off the shelf dev board, with no mods, so I don't think there is a hardware issue.  I've looked at all of the other forum threads by other people who have had this problem, but none of the ideas in those threads worked for me.

 

Any help is greatly appreciated.

 

Brent

Last Edited: Thu. Mar 14, 2019 - 02:16 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

From the manual:

 

JIm

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB user

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

Thank you for taking the time to read my question and respond.  However, the instructions you posted only deal with the first error code I receive.

 

The error code that seems to be the problem is "Failed to enable DW: Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (command has failed to execute on the tool)"

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

Follow the numbered steps.
With a pencil, tick each number on paper as you perform it.
If a step fails, write down exactly what happpens and which number.
.
If you don't own a pencil, BUY one. It is the best value and cheapest tool you can ever own.
The ones with an eraser are the most convenient.
.
David.

Last Edited: Tue. Mar 19, 2019 - 07:50 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

David,

  I have tried following those instructions multiple times.  Your tone was very condescending in your last post and does not meet the Code of Conduct that is expected on these forums.  Please do not create a hostile environment.  Let's make this be a place where we encourage others and not bring them down.

 

Brent

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

I am being realistic.    It is a very practical strategy.

 

Why do you think Airline Pilots have checklists?

Do you think that Boeing is condescending?

 

Seriously.   If you make notes on paper,  you can present important information for your readers.

When I see meticulous notes,   I follow them.    And can either reproduce the problem or offer the solution.

 

You will be surprised by the time and effort that readers often contribute to help a user.

A thread with 50-60 messages over days and weeks probably gets there in the end.

It takes the OP 10-20 minutes from his / her life to document "numbered steps"

However the problem is answered within ONE reply.

 

David.