Not able to read device signature

Log in or register to post comments
Go To Last Post
15 posts / 0 new
Author
Message
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
#1
Posted by yogendra1: Tue. Feb 28, 2017 - 12:07 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi All,

While programming I getting this error.

 

Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)

Unable to enter programming mode. Verify device selection, interface settings, target power, security bit, and connections to the target device

 

Timestamp:    2017-02-28 17:32:56.227
Severity:        ERROR
ComponentId:    20100
StatusCode:    1
ModuleName:    TCF (TCF command: Device:startSession failed.)

Failed to enter programming mode. ispEnterProgMode: Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)

 

I am using Atmel ICE and Atmel studio 7.0, with Atmega8515

Any solution to this, because from six months it was working fine and I have changed many IC.

Tags:

Tools, Evaluation and Development Kits (AVR-related)
Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Tue. Feb 28, 2017 - 12:47 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Any Help?

 

Top
Gold Markclawson
clawson's picture
Level: Moderator
Joined: Mon. Jul 18, 2005
Posts: 102300 View posts
Location: (using avr-gcc in) Finchingfield, Essex, England
Posted by clawson: Tue. Feb 28, 2017 - 01:01 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you changed AS7 recently (upgrade) or is it the same version that was working previously?

Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Tue. Feb 28, 2017 - 01:04 PM (Reply to #3)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It is the same version working earlier

Top
sparrow2
sparrow2's picture
Level: Raving Lunatic
Joined: Mon. Oct 7, 2002
Posts: 7394 View posts
Location: Denmark
Posted by sparrow2: Tue. Feb 28, 2017 - 01:08 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

does it work on a board you have programmed in the past?

Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Tue. Feb 28, 2017 - 01:12 PM (Reply to #5)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes it was working on board.

Today when I again tried to program, It is not reading the device signature.

So I changed many boards, but same issue.

I doubt that programmer has gone bad of Programmer firmware corrupted 

Top
jgmdesign
jgmdesign's picture
Level: Moderator
Joined: Mon. Mar 19, 2007
Posts: 18090 View posts
Location: Long Island New York
Posted by jgmdesign: Tue. Feb 28, 2017 - 01:37 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The cable/connector that comes with the Atmel-ICE is very delicate and breaks easily.  I would use an ohmmeter/continuity tester and check the connections to see that they are still sound.

 

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

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"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, RSLogix user

Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Tue. Feb 28, 2017 - 02:00 PM (Reply to #7)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I checked the cable, its good

 

Top
jgmdesign
jgmdesign's picture
Level: Moderator
Joined: Mon. Mar 19, 2007
Posts: 18090 View posts
Location: Long Island New York
Posted by jgmdesign: Tue. Feb 28, 2017 - 02:18 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well SOMETHING has changed.

 

Do you have another ICE available to see if the problem shows up?

 

 

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

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"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, RSLogix user

Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Tue. Feb 28, 2017 - 02:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

No other programmer

that is the problem

Top
jgmdesign
jgmdesign's picture
Level: Moderator
Joined: Mon. Mar 19, 2007
Posts: 18090 View posts
Location: Long Island New York
Posted by jgmdesign: Tue. Feb 28, 2017 - 03:19 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The only thing I can suggest is to either install Studio 6_2 on your machine, or use a machine that already has it and connect the ICE to it.  I should require a firmware upgrade/downgrade.  perform the action, then reconnect it to AS7 and it should again want to do the Upgrade/Downgrade.  Perform the action and see if the issue resolves.

 

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

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"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, RSLogix user

Top
yogendra1
yogendra1's picture
Level: Rookie
Joined: Mon. Jan 2, 2017
Posts: 22 View posts
Posted by yogendra1: Fri. Mar 3, 2017 - 01:28 PM (Reply to #11)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Jim,

I tried the above process, but still no luck

Top
Mike Bocovich
Mike Bocovich's picture
Level: New Member
Joined: Sat. Apr 8, 2017
Posts: 2 View posts
Posted by Mike Bocovich: Mon. Apr 16, 2018 - 11:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm programming an ATmega162 using an AVR Dragon with the ISP interface, AtmelStudio 7(Version 7.0.1417).  I'm using an old computer power supply that delivers 5.2V, I read 5.23V with a multimeter.  The processors have external crystals running at 8MHz, fuse "LOW.CKDIV8" is not set.  It was working, I was programming and things were going along happy.  I Locked my computer down from any changes, like I said things were going well.  I added a small electrolytic capacitor across the voltage supply to stabilize the voltage, and now I can't program the processors.  I receive "Failed to launch program ... Error status received: Got 0xc0, expected 0x00 (Command has failed to execute on the tool)".  The cables are good, and debug is not possible with this Dragon and processor.

I tried poking around some, this is interesting:  

When I go to device programming apply AVR Dragon, ATmega162, ISP then try to read the device signature I get the same error.  However, if I drive the reset pin low while reading, the correct device signature is returned 0x1E9404.  From here:

If I let the reset pin float and try to re-read the device signature, I get the same error

If I keep the reset pin low and re-read the device signature, I receive a signature of 0x000102, and a window indicating unable to enter program mode. ... Unexpected signature 0x00000102 (expected 0x01e9404)

If I let the reset pin float, then force it low, when I re-read the device signature, I receive the correct device signature, 0x1E9404.

If I let the reset pin float, and go to Fuses, I get an error.

If I enter the Fuses page from a different page (Device Information), then go to the Fuses with the reset pin driven low, then I can read the fuses.  I have not been able to change the fuses!

The system appears to read some items of the processor correctly if I let the reset pin float, then drive it low, then read information.  

 

I thought maybe Dragon was having difficulty sinking the voltage with the pull up resistor I was using 20kOhm.  I replaced it with 47kOhm with no luck, then removed the pull up resistor, again with no luck.  Is there something I need to do with the reset pin control in the dragon to make this system work again?

 

I've gone on line to investigate this, it appears the problem is out there regardless of the programming tool or the processor.

 

Is there some way of bypassing the need to read the device signature?  Will that help me get past this problem?

 

Top
meslomp
meslomp's picture
Level: Raving Lunatic
Joined: Wed. May 2, 2007
Posts: 6469 View posts
Location: Nieuwegein, Netherlands
Posted by meslomp: Tue. Apr 17, 2018 - 05:46 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If the device signature cannot be read, there is no point in trying anything else, so you can stop trying to program and first get the programmer to successfully read the device signature.

 

first of all, what happens when you remove the capacitor again?

You state that ll you did was add a capacitor and then all stopped working. Does removing the capacitor make programming work again (despite the vd stability then being less)

 

Is there a capacitor connected to the reset line?

When that is to high in value it might give problems.

 

what is the set programming speed?

If it is set at 125KHz or below you should always be fine. if by accident you run at the internal RC oscillator instead of the 8MHz external crystal, and the clk/div8 fuse is still set. Then 125Khz is the maximum safe programming clock.

 

 

Top
Mike Bocovich
Mike Bocovich's picture
Level: New Member
Joined: Sat. Apr 8, 2017
Posts: 2 View posts
Posted by Mike Bocovich: Thu. Apr 19, 2018 - 12:31 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the quick reply.

 

No capacitor on the reset pin!

 

I removed the capacitors and I was not able to go through the normal mode of access / programming like I was able to do before.  This appears fickle.  I get: Got 0xc0, expected 0x00 (Command has failed to execute on the tool).  Something else must be different!

 

However,

In the device programming (control shift P) Memories, I was able to force the reset pin low (as stated above) then erase the processor.  I let the reset pin go high, then forced it down again and read the processor flash, it was erased.  I cycled the reset pin high then low again and was able to load the hex file into the processor with the program button (removed check marks from erase and verify selections first.  The program worked.  Second check, again I was able to read the processor flash by cycling the reset pin (high low) and read.  

 

Again, I'm using an external crystal, the manual programming was done at 125kHz

 

Something goofy is going on with the reset line out of the dragon.  Is there a known or common failure mode with programmers or the dragon?  This weekend, I will probably hook a scope to the four active lines and see what is going on.

 

Any other advice would be greatly appreciated.

 

Top