| Author |
Message |
|
|
 Posted: Jan 29, 2012 - 12:09 AM |
|
Joined: Aug 03, 2009
Posts: 162
|
|
Using JTAGICE mkII and Studio 4.18/716 to program/debug target board. Everything worked yesterday but today after entering debug mode twice subsequent entries led to error message:
"A device with ID 0xfb18003f was detected. This device is unknown or unsupported by this version of AVR Studio."
Signature Bytes can be read and seem reasonable (get 3 non-zero bytes but not sure if they are correct).
Also tried the JTAGICE mkII Upgrade but that did not change anything. Same results.
Tried another target board and get the same error message. JTAGICE gone bad or something else? |
|
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 01:15 AM |
|
Joined: Nov 22, 2002
Posts: 12197
Location: Tangent, OR, USA
|
|
Reduce the ISP clock frequency. This is a common symptom with the frequency is too high. It must be no higher than 1/4 of the CPU clock frequency.
Jim |
_________________
Jim Wagner
Oregon Research Electronics, Consulting Div.
Tangent, OR, USA
"The only thing standing between us and victory is defeat" P.G.Wodhouse in Wooster & Jeeves series
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 01:32 AM |
|
Joined: Nov 02, 2009
Posts: 3239
Location: Zelenograd, Russia
|
|
| The JTAG mode is not affected by the ISP frequency setting. |
_________________
Warning: Grumpy Old Chuff. Reading this post may severely damage your mental health.
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 02:10 AM |
|
Joined: Jun 22, 2004
Posts: 3849
Location: South West Utah, USA
|
|
What AVR are you attempting to connect with? Is it supported in AVRstudio 4.18/716?
Search your AVR data sheet for "signature" too see what your AVR signature should look like.
Did you select the correct AVR chip for your JTAG? |
|
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 02:13 AM |
|
Joined: Nov 22, 2002
Posts: 12197
Location: Tangent, OR, USA
|
|
Has the OP always used JTAG (as in previously, when it did work)?
Is the programmer connected to the proper JTAG port of the MCU? It seems likely that it is, since some kind of response is generated.
Has any hardware been added to the TDO pin (PortF.6)
Jim |
_________________
Jim Wagner
Oregon Research Electronics, Consulting Div.
Tangent, OR, USA
"The only thing standing between us and victory is defeat" P.G.Wodhouse in Wooster & Jeeves series
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 12:40 PM |
|
Joined: Jul 18, 2005
Posts: 62944
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
| I have a feeling the device ID it's referring to here is the USB ID of the JTAG interface, not the signature of the AVR. |
_________________
|
| |
|
|
|
|
|
|
Posted: Jan 29, 2012 - 05:43 PM |
|
Joined: Aug 03, 2009
Posts: 162
|
|
| As mentioned in my original post
Quote:
Everything worked yesterday.
Mega128 is supported, always used JTAG, signature matches spec. There were NO hardware or configuration changes whatsoever. Did not edit or recomplie sources. Just turned the PC off at night, back on the next morning and tried to enter Debug Mode.
Reinstalled Studio on same PC and also another PC. Still the same results. Sounding more and more like JTAGICE failure?
I have a Dragon and STK500. Will try connecting with them. |
|
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 01:04 AM |
|
Joined: Aug 03, 2009
Posts: 162
|
|
Some new information:
I am able to program/verify the Mega128 with the JTAGICE mkII by selecting Connect to Selected AVR Programmer > Program tab > Program (and Verify). I think this means there is no reason to try the Dragon or STK500. The problem remains that I cannot enter Debug Mode.
1 The link from the PC to the JTAGICE must be working
2 The link from the JTAGICE to the Mega128 Flash must be OK
3 The JTAGICE firmware upgrade worked so the firmware has been reloaded (in case it had been corrupted)
One other input:
When this first started I was able to enter Debug Mode 2 times and then failed every time after that. I tried another target board and it worked 1 time and then failed every time after that. I have not been able to get to Debug Mode at all since then.
What is different about Debug Mode? |
|
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 01:32 AM |
|
Joined: Jun 22, 2004
Posts: 3849
Location: South West Utah, USA
|
|
| In the past with older versions of AVRstudio, I sometimes found completely un-installing, then re-installing it solved sudden unreasonable problems that cropped up. With your version I think you need to re-install all the service packs in sequence? |
|
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 09:14 AM |
|
Joined: Jul 18, 2005
Posts: 62944
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
With your version I think you need to re-install all the service packs in sequence?
Why bother now that 4.19 is available? |
_________________
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 02:02 PM |
|
Joined: Jun 22, 2004
Posts: 3849
Location: South West Utah, USA
|
|
|
clawson wrote:
Why bother now that 4.19 is available?
But 4.19 has its own problem outlined in several previous threads. I would consider "fixing" the current problem to be separate from changing to the next version. If 418 SP3 is reinstalled and the JTAG debug still fails at least you clearly "know" your problem is not solved. If the problem is solved, take a few more minutes to move to 4.19. |
|
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 02:22 PM |
|
Joined: Jul 18, 2005
Posts: 62944
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
But 4.19 has its own problem outlined in several previous threads.
There have been two issues of 4.19. The first had several serious problems. All fixed in the second. |
_________________
|
| |
|
|
|
|
|
|
Posted: Jan 30, 2012 - 06:01 PM |
|
Joined: Aug 03, 2009
Posts: 162
|
|
I installed Studio 4.19, then uninstalled it and went back to 4.18. I was able to get into Debug Mode 3 times and the code ran as expected. But after that all subsequent Debug Mode entries failed with the same error message.
I tried my old JTAGICE1 and it gave the messege below. Maybe this is the JTAGICE1 version of the original mkII error message?
Connected the JTAGEICE mkII to an AT90USBKEY and it entered Debug Mode and ran every time. Connected to a board from an older Mega128 project and it worked every time, also.
I think all this confirms that the mkII is OK but the original Mega128 has an intermittent problem. Some times it works and sometimes it does not. I tried chilling it but that didn't help. Being SMT it is not easy to replace but that is the next step. (Had it been a DIP in a socket that would have been the first thing I tried.)
This is a strange failure. Especially since I can connect and program/verify the MCU reliably from the Connect menu and then the code runs as expected. Have never seen an MCU fail intermittantly this way (just a signature error). Has anyone else seen this? |
|
|
| |
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
