Hi all,

The problems mentioned before with "slow" printfs *could* be because
of stepping, but then it'd be a problem anywhere there's code to chew
through.

The workaround in general is to - if you do hit a breakpoint, and want to
step/stop
a little further down - to NOT single-step (it'll take/took forever).
Remove the last hit breakpoint should you be out of them, and
point'n'right click to the
C line further down where you wanna go (eg. "jumping over" a printf()
) and
select "Run To Cursor".

I don't have IAR experiences anymore, but I recall times with C-spy even
where,
if you didn't click on *exactly* the right column you couldn't even
set a breakpoint 
at all. (V1.25 and/or V1.26 IIRC) (had to constantly go to ASM to set BREAK)
Admittedly, that might have been due to TAB use, but still, it was the pits.

EW430 might be tip-top nowadays, I can't opiniate either way.
But whatever, no worries here - on CrossWorks I fly through these things like a
knife
through melted butter :-)
(Even the stepping/breakpoint business)

Long live CrossWorks ! :-)

-- Kris


----- Original Message ----- 
From: "Paul Curtis" 
To: <msp430@msp4...>
Sent: Friday, February 18, 2005 1:18 PM
Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger


> Al, 
> 
> > You could probably write your 
> > own JTAG routines to stream other data over the port
> 
> This requires an understanding of how MSP430 JTAG works--not that
> difficult, TI publish an app note on it.
> 
> > but I 
> > believe that IAR only does this when stopped. This is NOT a 
> > full JTAG implentation.
> 
> True.
> 
> > I believe that Paul has posted to 
> > this effect in the past. 
> 
> The trick is not to impose a burden on the micro by starting/stopping it
> all the time (intrusion).  Some vendors do this with a breakpoint and
> stealing a breakpoint from a processor with only two breakpoints nukes
> the usefulness somewhat.  CrossWorks doesn't require a breakpoint and
> nor is it intrusive.  We don't publish how we achieve this; perhaps
> somebody can actually work it out.
> 
> (Has anynody noticed that posts from JK are rather rare to non-existent
> these days?  Has our knowledgeable poster jumped ship to another
> processor?)
> 
> --
> Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
> 
> 
> .
> 
> 
> 
> 
> 
> --------
> . 
> 
> 

ENOUGH ALREADY, THEY DON'T DO ASSEMBLERS WITHOUT THE INFLATIONARY
PARTS!!

O:-)

microbit wrote:

>Hi all,
>
>The problems mentioned before with "slow" printfs *could* be
because
>of stepping, but then it'd be a problem anywhere there's code to
chew through.
>
>The workaround in general is to - if you do hit a breakpoint, and want to
step/stop
>a little further down - to NOT single-step (it'll take/took forever).
>Remove the last hit breakpoint should you be out of them, and
point'n'right click to the
>C line further down where you wanna go (eg. "jumping over" a
printf() ) and
>select "Run To Cursor".
>
>I don't have IAR experiences anymore, but I recall times with C-spy
even where,
>if you didn't click on *exactly* the right column you couldn't
even set a breakpoint 
>at all. (V1.25 and/or V1.26 IIRC) (had to constantly go to ASM to set BREAK)
>Admittedly, that might have been due to TAB use, but still, it was the pits.
>
>EW430 might be tip-top nowadays, I can't opiniate either way.
>But whatever, no worries here - on CrossWorks I fly through these things
like a knife
>through melted butter :-)
>(Even the stepping/breakpoint business)
>
>Long live CrossWorks ! :-)
>
>-- Kris
>
>
>----- Original Message ----- 
>From: "Paul Curtis" 
>To: <msp430@msp4...>
>Sent: Friday, February 18, 2005 1:18 PM
>Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger
>
>
>  
>
>>Al, 
>>
>>    
>>
>>>You could probably write your 
>>>own JTAG routines to stream other data over the port
>>>      
>>>
>>This requires an understanding of how MSP430 JTAG works--not that
>>difficult, TI publish an app note on it.
>>
>>    
>>
>>>but I 
>>>believe that IAR only does this when stopped. This is NOT a 
>>>full JTAG implentation.
>>>      
>>>
>>True.
>>
>>    
>>
>>>I believe that Paul has posted to 
>>>this effect in the past. 
>>>      
>>>
>>The trick is not to impose a burden on the micro by starting/stopping it
>>all the time (intrusion).  Some vendors do this with a breakpoint and
>>stealing a breakpoint from a processor with only two breakpoints nukes
>>the usefulness somewhat.  CrossWorks doesn't require a breakpoint
and
>>nor is it intrusive.  We don't publish how we achieve this; perhaps
>>somebody can actually work it out.
>>
>>(Has anynody noticed that posts from JK are rather rare to non-existent
>>these days?  Has our knowledgeable poster jumped ship to another
>>processor?)
>>
>>--
>>Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
>>CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors
>>
>>
>>.
>>
>>
>>
>>
>>
>>--------
>>. 
>>
>>
>>    
>>
>
>
>
>
>
>.
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>  
>

Maybe that's because TI didn't pay them a shitload of money :-)

-- Kris

----- Original Message -----
From: "Onestone"
To: <msp430@msp4...>
Sent: Friday, February 18, 2005 8:29 PM
Subject: Re: [msp430] printf using terminal I/O in C-SPY FET debugger


> ENOUGH ALREADY, THEY DON'T DO ASSEMBLERS
WITHOUT THE INFLATIONARY PARTS!!
>
> O:-)
>
> microbit wrote:
>
> >Hi all,
> >
> >The problems mentioned before with "slow" printfs *could* be
because
> >of stepping, but then it'd be a problem anywhere there's code
to chew
through.
> >
> >The workaround in general is to - if you do hit a breakpoint, and want
to
step/stop
> >a little further down - to NOT single-step
(it'll take/took forever).
> >Remove the last hit breakpoint should you be out of them, and
point'n'right click to the
> >C line further down where you wanna go (eg.
"jumping over" a printf() )
and
> >select "Run To Cursor".
> >
> >I don't have IAR experiences anymore, but I recall times with
C-spy even
where,
> >if you didn't click on *exactly* the
right column you couldn't even set a
breakpoint
> >at all. (V1.25 and/or V1.26 IIRC) (had to
constantly go to ASM to set
BREAK)
> >Admittedly, that might have been due to TAB
use, but still, it was the
pits.
> >
> >EW430 might be tip-top nowadays, I can't opiniate either way.
> >But whatever, no worries here - on CrossWorks I fly through these
things
like a knife
> >through melted butter :-)
> >(Even the stepping/breakpoint business)
> >
> >Long live CrossWorks ! :-)
> >
> >-- Kris
> >

Jaromir, 

> Isn't this the main cause of problems with
singlestepping and 
> programming small MSP's with CrossWorks & CrossConnect Lite?

No.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

Al,

ADuC development tools (assembler and so on) with adequate support might
actually cost; MAX-IDE is free and being improved.  I don't know,
perhaps some of the other ARM guys give away free tool for assembly-only
development.

Rgds,

-- Paul. 

> -----Original Message-----
> From: Onestone [mailto:onestone@ones...] 
> Sent: 18 February 2005 07:22
> To: msp430@msp4...
> Subject: Re: [msp430] printf using terminal I/O in C-SPY FET debugger
> 
> 
> I 'm oscillating between MAXQ and ADuC at the moment. 32 bit 
> ARM ASM is NICE! YUM! and I've only just started playing with 
> it. I did finally find MAXQ-IDE, but by then was engrossed in 
> arming myself. I have some didly bits, but it is obvious that 
> you can make this thing do circus tricks with a bit of 
> friendly persuasion. Spoiled for choice right now ;@}
> 
> Al
> 
> Paul Curtis wrote:
> 
> >Hi Al,
> >
> >  
> >
> >>All these high level languages and debug devolves to blinky 
> LEDs. ;@} 
> >>Oh the joys of asm.
> >>    
> >>
> >
> >Man, have you got yourself into MAXQ yet?  Learning how to 
> get the best 
> >out of that puppy is a real experience!
> >
> >--
> >Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk 
> CrossWorks 
> >for MSP430, ARM, AVR and (soon) MAXQ processors
> >
> >
> >.
> >
> > 
> >Yahoo! Groups Links
> >
> >
> >
> > 
> >
> >
> >
> >
> >
> >  
> >
> 
> 
> 
> .
> 
>  
> Yahoo! Groups Links
> 
> 
> 
>  
> 
> 
> 
> 
> 

WHat's best in your humble opinions Cross(Dressing)Studio or IAR
compiler?
 
 

-----Original Message-----
From: Paul Curtis [mailto:plc@plc@...]
Sent: 18 February 2005 12:16
To: msp430@msp4...
Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger


Jaromir, 

> Isn't this the main cause of problems with
singlestepping and 
> programming small MSP's with CrossWorks & CrossConnect Lite?

No.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors


.





  _____  

> . 

ive bin using IAR for aBOUT a year now but this mornin' had a look at
CrossDressingStudio and the IDE knocks spots off IAR
(I use DOT NET so it was nice to see a similar IDE)

-----Original Message-----
From: Paul Curtis [mailto:plc@plc@...]
Sent: 18 February 2005 12:19
To: msp430@msp4...
Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger


Al,

ADuC development tools (assembler and so on) with adequate support might
actually cost; MAX-IDE is free and being improved.  I don't know,
perhaps some of the other ARM guys give away free tool for assembly-only
development.

Rgds,

-- Paul. 

> -----Original Message-----
> From: Onestone [mailto:onestone@ones...] 
> Sent: 18 February 2005 07:22
> To: msp430@msp4...
> Subject: Re: [msp430] printf using terminal I/O in C-SPY FET debugger
> 
> 
> I 'm oscillating between MAXQ and ADuC at the moment. 32 bit 
> ARM ASM is NICE! YUM! and I've only just started playing with 
> it. I did finally find MAXQ-IDE, but by then was engrossed in 
> arming myself. I have some didly bits, but it is obvious that 
> you can make this thing do circus tricks with a bit of 
> friendly persuasion. Spoiled for choice right now ;@}
> 
> Al
> 
> Paul Curtis wrote:
> 
> >Hi Al,
> >
> >  
> >
> >>All these high level languages and debug devolves to blinky 
> LEDs. ;@} 
> >>Oh the joys of asm.
> >>    
> >>
> >
> >Man, have you got yourself into MAXQ yet?  Learning how to 
> get the best 
> >out of that puppy is a real experience!
> >
> >--
> >Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk 
> CrossWorks 
> >for MSP430, ARM, AVR and (soon) MAXQ processors
> >
> >
> >.
> >
> > 
> >> . 

by the way im using a J-LINK... when i launch C-SPy for the first time
every day more often than not my PC resets
 
duz Enny-1 else have this problem?
 
 

-----Original Message-----
From: Darren Logan [mailto:darrenl@darr...]
Sent: 18 February 2005 12:26
To: msp430@msp4...
Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger


ive bin using IAR for aBOUT a year now but this mornin' had a look at
CrossDressingStudio and the IDE knocks spots off IAR
(I use DOT NET so it was nice to see a similar IDE)

-----Original Message-----
From: Paul Curtis [mailto:plc@plc@...]
Sent: 18 February 2005 12:19
To: msp430@msp4...
Subject: RE: [msp430] printf using terminal I/O in C-SPY FET debugger


Al,

ADuC development tools (assembler and so on) with adequate support might
actually cost; MAX-IDE is free and being improved.  I don't know,
perhaps some of the other ARM guys give away free tool for assembly-only
development.

Rgds,

-- Paul. 

> -----Original Message-----
> From: Onestone [mailto:onestone@ones...] 
> Sent: 18 February 2005 07:22
> To: msp430@msp4...
> Subject: Re: [msp430] printf using terminal I/O in C-SPY FET debugger
> 
> 
> I 'm oscillating between MAXQ and ADuC at the moment. 32 bit 
> ARM ASM is NICE! YUM! and I've only just started playing with 
> it. I did finally find MAXQ-IDE, but by then was engrossed in 
> arming myself. I have some didly bits, but it is obvious that 
> you can make this thing do circus tricks with a bit of 
> friendly persuasion. Spoiled for choice right now ;@}
> 
> Al
> 
> Paul Curtis wrote:
> 
> >Hi Al,
> >
> >  
> >
> >>All these high level languages and debug devolves to blinky 
> LEDs. ;@} 
> >>Oh the joys of asm.
> >>    
> >>
> >
> >Man, have you got yourself into MAXQ yet?  Learning how to 
> get the best 
> >out of that puppy is a real experience!
> >
> >--
> >Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk 
> CrossWorks 
> >for MSP430, ARM, AVR and (soon) MAXQ processors
> >
> >
> >.
> >
> > 
> >> . 








.





  _____  

> . 

Hi Al, 

> ENOUGH ALREADY, THEY DON'T DO ASSEMBLERS
WITHOUT THE 
> INFLATIONARY PARTS!!

Did you forget to turn off CAPS LOCK today?  Usually from you we get
mixed-case posts with the initial letter in lower rest in caps, but this
one isn't.  It's hard to tell whether you're just too darned
tired to do
hit the CAPS LOCK as it's just one more keystroke and adds no value or
whether you're really shouting from the rooftop.  ;-)

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors

Hi Darren, 

> ive bin using IAR for aBOUT a year now but this
mornin' had a 
> look at CrossDressingStudio and the IDE knocks spots off IAR 
> (I use DOT NET so it was nice to see a similar IDE)

I glad to see we're providing affordable haute couture for the masses!
Perhaps the cross dressing community is an untapped market... :-)

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors