I have a free running MSP430F2618 with no JTAG attached that stopped working
(some kind of crash I think). I want to see where it is running now - is it
still in my mainloop or is it running somewhere in the memory - (not in my
code).
I want to connect the JTAG - attach it - and just jump into the current
running code to the current PC. I tried it with Crossworks; I know this is
not possible...
Any idea how I can attach to a running MSP430 with no reset?
Matthias
Attach Debugger with no reset?
Started by ●November 11, 2010
Reply by ●November 11, 20102010-11-11
Matthias Weingart :
> Any idea how I can attach to a running MSP430 with no reset?
So well, my code was not running at all; the 32kHz crystal was off (as in
LPM4, however there is no LPM4 instruction at all in my code ;-(, and no
setting of the XTS, LFXT1Sx or toher bits is done in my code.
Applying RESET works just fine and it is working again. The question is - how
can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
Matthias
> Any idea how I can attach to a running MSP430 with no reset?
So well, my code was not running at all; the 32kHz crystal was off (as in
LPM4, however there is no LPM4 instruction at all in my code ;-(, and no
setting of the XTS, LFXT1Sx or toher bits is done in my code.
Applying RESET works just fine and it is working again. The question is - how
can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
Matthias
Reply by ●November 11, 20102010-11-11
On 11.11.2010 19:10, Matthias Weingart wrote:
:
> Applying RESET works just fine and it is working again. The question is - how
> can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
:
Your application crashed... Use the watchdog to get out of that
situation (I guess you already know).
Hardy
:
> Applying RESET works just fine and it is working again. The question is - how
> can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
:
Your application crashed... Use the watchdog to get out of that
situation (I guess you already know).
Hardy
Reply by ●November 11, 20102010-11-11
I have yet to see any jtag debugger too this stunt.
My understanding is that its not possible in the hardware.
And a logic analyzer is not possible either :-).
don
--- In m..., Matthias Weingart wrote:
>
> I have a free running MSP430F2618 with no JTAG attached that stopped working
> (some kind of crash I think). I want to see where it is running now - is it
> still in my mainloop or is it running somewhere in the memory - (not in my
> code).
> I want to connect the JTAG - attach it - and just jump into the current
> running code to the current PC. I tried it with Crossworks; I know this is
> not possible...
> Any idea how I can attach to a running MSP430 with no reset?
>
> Matthias
>
My understanding is that its not possible in the hardware.
And a logic analyzer is not possible either :-).
don
--- In m..., Matthias Weingart wrote:
>
> I have a free running MSP430F2618 with no JTAG attached that stopped working
> (some kind of crash I think). I want to see where it is running now - is it
> still in my mainloop or is it running somewhere in the memory - (not in my
> code).
> I want to connect the JTAG - attach it - and just jump into the current
> running code to the current PC. I tried it with Crossworks; I know this is
> not possible...
> Any idea how I can attach to a running MSP430 with no reset?
>
> Matthias
>
Reply by ●November 11, 20102010-11-11
Based on my very limited knowledge of the JTAG interface and EEM on the chip, I
think it should be possible.
From JTAG, one should be able to stop the MCLK, single cycle it, and watch the activities of the internal address bus, data bus, and control signals (such as fetch/read/write, byte/word, etc.) cycle by cycle.
Not a stunt. It is only a matter of who is motivated to do so.
--- In m..., "Donald H" wrote:
> I have yet to see any jtag debugger too this stunt.
>
> My understanding is that its not possible in the hardware.
>
> And a logic analyzer is not possible either :-).
>
> don
>
> --- In m..., Matthias Weingart wrote:
> >
> > I have a free running MSP430F2618 with no JTAG attached that stopped working
> > (some kind of crash I think). I want to see where it is running now - is it
> > still in my mainloop or is it running somewhere in the memory - (not in my
> > code).
> > I want to connect the JTAG - attach it - and just jump into the current
> > running code to the current PC. I tried it with Crossworks; I know this is
> > not possible...
> > Any idea how I can attach to a running MSP430 with no reset?
> >
> > Matthias
>
From JTAG, one should be able to stop the MCLK, single cycle it, and watch the activities of the internal address bus, data bus, and control signals (such as fetch/read/write, byte/word, etc.) cycle by cycle.
Not a stunt. It is only a matter of who is motivated to do so.
--- In m..., "Donald H" wrote:
> I have yet to see any jtag debugger too this stunt.
>
> My understanding is that its not possible in the hardware.
>
> And a logic analyzer is not possible either :-).
>
> don
>
> --- In m..., Matthias Weingart wrote:
> >
> > I have a free running MSP430F2618 with no JTAG attached that stopped working
> > (some kind of crash I think). I want to see where it is running now - is it
> > still in my mainloop or is it running somewhere in the memory - (not in my
> > code).
> > I want to connect the JTAG - attach it - and just jump into the current
> > running code to the current PC. I tried it with Crossworks; I know this is
> > not possible...
> > Any idea how I can attach to a running MSP430 with no reset?
> >
> > Matthias
>
Reply by ●November 12, 20102010-11-12
Hardy Griech :
> On 11.11.2010 19:10, Matthias Weingart wrote:
>:
>> Applying RESET works just fine and it is working again. The question is
>> - how can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
>:
>
> Your application crashed... Use the watchdog to get out of that
> situation (I guess you already know).
No application crash, the 32kHz crystal oscillator crashed: XOUT is at DC-
level of 500mV - but no 32kHz waves visible. With LPM4 XOUT would be 0V.
The MSP430 watchdog is stopped in this case also. After downloading of the
lastest errata it seems I got hit by the XOSC8 fault of the 2x series.
However; it would be nice to be able to attach the debugger without applying
reset...
M.
> On 11.11.2010 19:10, Matthias Weingart wrote:
>:
>> Applying RESET works just fine and it is working again. The question is
>> - how can LPM4 (or maybe any LFXT1 bits) get enabled by itself?
>:
>
> Your application crashed... Use the watchdog to get out of that
> situation (I guess you already know).
No application crash, the 32kHz crystal oscillator crashed: XOUT is at DC-
level of 500mV - but no 32kHz waves visible. With LPM4 XOUT would be 0V.
The MSP430 watchdog is stopped in this case also. After downloading of the
lastest errata it seems I got hit by the XOSC8 fault of the 2x series.
However; it would be nice to be able to attach the debugger without applying
reset...
M.
Reply by ●November 12, 20102010-11-12
--- In m..., Matthias Weingart wrote:
>
> I have a free running MSP430F2618 with no JTAG attached that stopped working
> (some kind of crash I think). I want to see where it is running now - is it
> still in my mainloop or is it running somewhere in the memory - (not in my
> code).
> I want to connect the JTAG - attach it - and just jump into the current
> running code to the current PC. I tried it with Crossworks; I know this is
> not possible...
> Any idea how I can attach to a running MSP430 with no reset?
>
> Matthias
>
This should work on JTAG only parts - not on parts with a TEST pin/SBW - but it may have rotted. Which version of CrossWorks are you using?
Did you turn off the "Identify Target" target property when you connected using CrossWorks?
Which JTAG cable are you using?
Regards
Michael
>
> I have a free running MSP430F2618 with no JTAG attached that stopped working
> (some kind of crash I think). I want to see where it is running now - is it
> still in my mainloop or is it running somewhere in the memory - (not in my
> code).
> I want to connect the JTAG - attach it - and just jump into the current
> running code to the current PC. I tried it with Crossworks; I know this is
> not possible...
> Any idea how I can attach to a running MSP430 with no reset?
>
> Matthias
>
This should work on JTAG only parts - not on parts with a TEST pin/SBW - but it may have rotted. Which version of CrossWorks are you using?
Did you turn off the "Identify Target" target property when you connected using CrossWorks?
Which JTAG cable are you using?
Regards
Michael
Reply by ●November 12, 20102010-11-12
"nutleycottage" :
> This should work on JTAG only parts - not on parts with a TEST pin/SBW -
> but it may have rotted. Which version of CrossWorks are you using?
>
> Did you turn off the "Identify Target" target property when you
> connected using CrossWorks?
>
> Which JTAG cable are you using?
I am using 2.0.3 4251; JTAG is "Olimex JTAG iso" or "Elprotronic". It is
identifying the target; where can I disable this? (maybe I can just remove
the reset wire from the connector to avoid reseting?)
"release jtag" = false (what will happen when I enable this?),
SpyByWire/JTag support = True (what will happen when I disable this?)
Use SpyByWire = False
Software breakpoints = false
Matthias
> This should work on JTAG only parts - not on parts with a TEST pin/SBW -
> but it may have rotted. Which version of CrossWorks are you using?
>
> Did you turn off the "Identify Target" target property when you
> connected using CrossWorks?
>
> Which JTAG cable are you using?
I am using 2.0.3 4251; JTAG is "Olimex JTAG iso" or "Elprotronic". It is
identifying the target; where can I disable this? (maybe I can just remove
the reset wire from the connector to avoid reseting?)
"release jtag" = false (what will happen when I enable this?),
SpyByWire/JTag support = True (what will happen when I disable this?)
Use SpyByWire = False
Software breakpoints = false
Matthias
Reply by ●November 13, 20102010-11-13
--- In m..., Matthias Weingart wrote:
>
> "nutleycottage" :
>
> > This should work on JTAG only parts - not on parts with a TEST pin/SBW -
> > but it may have rotted. Which version of CrossWorks are you using?
> >
> > Did you turn off the "Identify Target" target property when you
> > connected using CrossWorks?
> >
> > Which JTAG cable are you using?
>
> I am using 2.0.3 4251; JTAG is "Olimex JTAG iso" or "Elprotronic". It is
> identifying the target; where can I disable this? (maybe I can just remove
> the reset wire from the connector to avoid reseting?)
> "release jtag" = false (what will happen when I enable this?),
> SpyByWire/JTag support = True (what will happen when I disable this?)
> Use SpyByWire = False
> Software breakpoints = false
>
> Matthias
>
Hi Matthias
If you show the targets window on the right hand edge of the toolbar there's an options drop down (vv). Click on this and then uncheck the box "Identify Target On Connect". You can then connect (which hopefully shouldn't do anything to the target processor) and then use the debug icon that looks like a paper clip to attach the debugger.
Regards
Michael
>
> "nutleycottage" :
>
> > This should work on JTAG only parts - not on parts with a TEST pin/SBW -
> > but it may have rotted. Which version of CrossWorks are you using?
> >
> > Did you turn off the "Identify Target" target property when you
> > connected using CrossWorks?
> >
> > Which JTAG cable are you using?
>
> I am using 2.0.3 4251; JTAG is "Olimex JTAG iso" or "Elprotronic". It is
> identifying the target; where can I disable this? (maybe I can just remove
> the reset wire from the connector to avoid reseting?)
> "release jtag" = false (what will happen when I enable this?),
> SpyByWire/JTag support = True (what will happen when I disable this?)
> Use SpyByWire = False
> Software breakpoints = false
>
> Matthias
>
Hi Matthias
If you show the targets window on the right hand edge of the toolbar there's an options drop down (vv). Click on this and then uncheck the box "Identify Target On Connect". You can then connect (which hopefully shouldn't do anything to the target processor) and then use the debug icon that looks like a paper clip to attach the debugger.
Regards
Michael
Reply by ●November 17, 20102010-11-17
Hello group
I have a some questions that I hope this group can help me with.
I have an:
AVR JTAGICE mkII, H/W version: 0x0000, S/W version: 0x0426 0x0426,
Device id: 0x978103F
JTAG clock (approx): 98 KHz, Target voltage: 3.294 V, CPU: AT90CAN128
I am using IAR version 430F
I want to set 1 breakpoint in my program, but after loading the program
I get:
Iar Ide Pm
One or more breakpoints could not be set and have been disabled
The fuse flags are set to:
On-Chip Debug Enabled
JTAG Interface Enabled
My questions are:
* How can I set a breakpoint?
* After loading the program, and being told that my breakpoint has
been disabled, I then click on "Next Statement" expecting the program to
go to the next statement and stop, but instead it runs the entire
program at 1/120 speed. By the way the clock speed is 8MHz.
Can someone shed some light on this?
Thank you
I have a some questions that I hope this group can help me with.
I have an:
AVR JTAGICE mkII, H/W version: 0x0000, S/W version: 0x0426 0x0426,
Device id: 0x978103F
JTAG clock (approx): 98 KHz, Target voltage: 3.294 V, CPU: AT90CAN128
I am using IAR version 430F
I want to set 1 breakpoint in my program, but after loading the program
I get:
Iar Ide Pm
One or more breakpoints could not be set and have been disabled
The fuse flags are set to:
On-Chip Debug Enabled
JTAG Interface Enabled
My questions are:
* How can I set a breakpoint?
* After loading the program, and being told that my breakpoint has
been disabled, I then click on "Next Statement" expecting the program to
go to the next statement and stop, but instead it runs the entire
program at 1/120 speed. By the way the clock speed is 8MHz.
Can someone shed some light on this?
Thank you
