Matthias,

> How can I supress, that crossworks is deleting the
Info-flash 
> everytime I reprogramm my device?

In the target interface you're using to download your application, set
Erase All to No.

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

On Thu, May 12, 2005 at 11:32:01AM +0100, Paul Curtis wrote:
> Matthias,
> 
> > How can I supress, that crossworks is deleting the Info-flash 
> > everytime I reprogramm my device?
> 
> In the target interface you're using to download your application, set
> Erase All to No.

Paul, thank you. It is well hidden (or at least I was not clever enough to
find it ;:-). Btw. what can I do with the "ModuleClockControl". Some
of them
are enabled, some not, what happend when I e.g. enable the clk for uart0?
One example: when I sending a character and I got into a breakpoint
during sending, that character is garbled. Can I cure it with that clk-flag?

"Verify Flash Writes" is disabled; but it is doing verify (well I get
a
verify error sometimes, if my voltage is to weak).

        Matthias

Hi Matthias, 

> > > How can I supress, that crossworks is
deleting the Info-flash 
> > > everytime I reprogramm my device?
> > 
> > In the target interface you're using to download your 
> application, set 
> > Erase All to No.
> 
> Paul, thank you. It is well hidden (or at least I was not 
> clever enough to find it ;:-). 

That's the problem: too much stuff.  :-(

> Btw. what can I do with the 
> "ModuleClockControl". Some of them are enabled, some not, 
> what happend when I e.g. enable the clk for uart0?
> One example: when I sending a character and I got into a 
> breakpoint during sending, that character is garbled. Can I 
> cure it with that clk-flag?

All that serious black magic is Mike's domain.

> "Verify Flash Writes" is disabled; but
it is doing verify 
> (well I get a verify error sometimes, if my voltage is to weak).

I think Michael moved this out to a global option and forgot to nuke it
in the presented target interface properties.

Rgds,

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

--- In msp430@msp4..., "Paul Curtis" <plc@r...> wrote:
> Hi Matthias, 
> 
> > > > How can I supress, that crossworks is deleting the
Info-flash 
> > > > everytime I reprogramm my device?
> > > 
> > > In the target interface you're using to download your 
> > application, set 
> > > Erase All to No.
> > 
> > Paul, thank you. It is well hidden (or at least I was not 
> > clever enough to find it ;:-). 
> 
> That's the problem: too much stuff.  :-(
> 
> > Btw. what can I do with the 
> > "ModuleClockControl". Some of them are enabled, some not, 
> > what happend when I e.g. enable the clk for uart0?
> > One example: when I sending a character and I got into a 
> > breakpoint during sending, that character is garbled. Can I 
> > cure it with that clk-flag?
> 
> All that serious black magic is Mike's domain.

The ModuleClockControl properties are enabled for parts that have a
full EEM e.g. 169, 449. These properties can be used to specify which
clocks are stopped/left running on breakpoint.

Regards
Michael

> 
> > "Verify Flash Writes" is disabled; but it is doing verify 
> > (well I get a verify error sometimes, if my voltage is to weak).
> 
> I think Michael moved this out to a global option and forgot to nuke it
> in the presented target interface properties.
> 
> Rgds,
> 
> --
> Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
> CrossWorks for MSP430, ARM, AVR and (soon) MAXQ processors