| Author |
Message |
|
|
 Posted: Mar 21, 2011 - 07:37 PM |
|
Joined: Apr 10, 2007
Posts: 5
|
|
Hello,
when I want to start the simulator in AVRStudio 5
there appears a error message:
Timestamp: 2011-03-21 20:30:43.897
Severity: ERROR
ComponentId: 20100
StatusCode: 0
TCF command: Processes:launch failed: Code:131101 ,Service:Processes ,Message from peer:Device ATxmega256A3: Expected signature 0x1e9843, got signature 0x1e9842
Is there a posibility to switch off this message?
Thanks
Stefan |
|
|
| |
|
|
|
|
|
|
Posted: Mar 22, 2011 - 10:07 AM |
|
Joined: Jan 19, 2005
Posts: 166
Location: Atmel Norway
|
|
|
stefanju wrote:
TCF command: Processes:launch failed: Code:131101 ,Service:Processes ,Message from peer:Device ATxmega256A3: Expected signature 0x1e9843, got signature 0x1e9842
Is there a posibility to switch off this message?
No, it is not possible to switch off the signature check.
However, we are not able to reproduce this problem. ATxmega256A3 has signature 0x1e9842 and we don't understand how you manage to launch a session that requests 0x1e9843 for this device. The expected signature is retrieved from the device description file in the AVR Studio installation (...\Program Files\Atmel\AVR Studio 5.0\devices\ATxmega256A3.xml). Do you have any more details on this? Anything unusual with your AS5 installation or your project?
- roland |
|
|
| |
|
|
|
|
|
|
Posted: Mar 22, 2011 - 10:31 AM |
|
Joined: Jul 18, 2005
Posts: 62922
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
avrdude.conf wrote:
Code:
#------------------------------------------------------------
# ATXMEGA256A3B
#------------------------------------------------------------
part
id = "x256a3b";
desc = "ATXMEGA256A3B";
signature = 0x1e 0x98 0x43;
So it looks like it's launched expecting 256A3B rather than 256A3 |
_________________
|
| |
|
|
|
|
|
|
Posted: Mar 22, 2011 - 11:16 AM |
|
Joined: Jan 19, 2005
Posts: 166
Location: Atmel Norway
|
|
|
clawson wrote:
avrdude.conf wrote:
Code:
#------------------------------------------------------------
# ATXMEGA256A3B
#------------------------------------------------------------
part
id = "x256a3b";
desc = "ATXMEGA256A3B";
signature = 0x1e 0x98 0x43;
So it looks like it's launched expecting 256A3B rather than 256A3
The 256A3B support has been withdrawn in AS5 (I don't know why. I see it is supported in AS4). For now, the only way to make it work in AS5 it is to rebuild the project for the "regular" 256A3.
- roland |
|
|
| |
|
|
|
|
|
|
Posted: Mar 22, 2011 - 11:27 AM |
|
Joined: Jul 18, 2005
Posts: 62922
Location: (using avr-gcc in) Finchingfield, Essex, England
|
|
|
Quote:
The 256A3B support has been withdrawn in AS5
Looks like some part of the software stack didn't get the memo!  |
_________________
|
| |
|
|
|
|
|
|
Posted: Mar 23, 2011 - 04:58 AM |
|
Joined: Jan 14, 2011
Posts: 156
|
|
Excuse me for jumping in here, but I have a similar problem that I posted shortly after the beta release and never got a comment.
When I try to debug an Atmega 168 with a Dragon, I get the following in the S5 Output window:
Quote:
09:00:28.628: [ERROR] TCF command: Processes:launch failed: Code:1 ,Service: ,Message from peer:Unexpected signature 0x001e940b (expected 0x001e9406)
No issues debugging in S4 with this setup after downgrading the Dragon firmware.
Same problem or different? |
|
|
| |
|
|
|
|
|
|
Posted: Mar 23, 2011 - 08:58 AM |
|
Joined: Jan 19, 2005
Posts: 166
Location: Atmel Norway
|
|
|
MurMan wrote:
Excuse me for jumping in here, but I have a similar problem that I posted shortly after the beta release and never got a comment.
When I try to debug an Atmega 168 with a Dragon, I get the following in the S5 Output window:
Quote:
09:00:28.628: [ERROR] TCF command: Processes:launch failed: Code:1 ,Service: ,Message from peer:Unexpected signature 0x001e940b (expected 0x001e9406)
No issues debugging in S4 with this setup after downgrading the Dragon firmware.
Same problem or different?
Related but different, since there is actual hardware involved here...
The signature 1e940b indicates an ATmega168P, while 1e9406 is the older ATmega168 (without the P (PicoPower) suffix). The 168P is supposed to be a drop-in replacement for the 168 so you should be all set if you change your device to ATmega168P in your project.
- roland |
|
|
| |
|
|
|
|
|
|
Posted: Mar 23, 2011 - 09:42 AM |
|
Joined: Jan 19, 2005
Posts: 166
Location: Atmel Norway
|
|
The error messages in these situations leave a lot to be desired, I have posted a bug report on this (Bug 13933).
- roland |
|
|
| |
|
|
|
|
|
|
Posted: Mar 23, 2011 - 03:27 PM |
|
Joined: Jan 14, 2011
Posts: 156
|
|
|
|
|
|
|
FAQ
Search
Register
Log in to check your private messages
Log in
Maximize
RSS
