On Jan 13, 3:08=A0pm, Grant Edwards <gra...@visi.com> wrote:

> You might try asking on the msp430 mailing list. =A0I know that
> one or more guys from Rowley reads the list.

Already in the side door on that one ;)

On 2008-01-13, Leon <leon355@btinternet.com> wrote:

>> I've tried copying msp430.dll from the IAR directory
>> (2.1.10.1) to the CrossWorks directory (was 2.1.7.0) with no
>> discernible effect.
>>
>> Has anyone got this working?
>
> I don't think that CrossWorks supports the ez430. It isn't
> shown in the list of targets.

You might try asking on the msp430 mailing list.  I know that
one or more guys from Rowley reads the list.

-- 
Grant Edwards                   grante             Yow!  I'm also against
                                  at               BODY-SURFING!!
                               visi.com            

On Jan 13, 2:21=A0pm, Leon <leon...@btinternet.com> wrote:

> > Has anyone got this working?
>
> I don't think that CrossWorks supports the ez430. It isn't shown in
> the list of targets.

It is supported, though (from an msp430.dll standpoint it's the same
as a USB-FET) - and it's one of those "but it used to work!" things.

I've just found that it works on another computer, and I'm up and
running, but I'd like to know why it no worky (suddenly) on my spare
PC.

On 13 Jan, 02:44, larwe <zwsdot...@gmail.com> wrote:
> I've got a strange problem. I'm trying to move some code over from IAR
> Kickstart (where I developed it) to Crossworks (where I need to show
> it working, for various reasons). The debugger I'm using is the ez430;
> the target is a TI MSP430F2012 target board soldered to a larger
> circuit. I can build fine, but if I click "build and debug" I get
> various problems; either it pretends to run but really just sits
> there, or it says it couldn't run to breakpoint (no breakpoints are
> set). Verify usually fails.
>
> I've tried it on a bare T2012 board with nothing attached, and using a
> trivial piece of code that just blinks the LED. It looks as if it
> can't even write the flash area reliably; very strange.
>
> Same computer, same everything works fine with IAR.
>
> I've tried copying msp430.dll from the IAR directory (2.1.10.1) to the
> CrossWorks directory (was 2.1.7.0) with no discernible effect.
>
> Has anyone got this working?

I don't think that CrossWorks supports the ez430. It isn't shown in
the list of targets.

Leon

I've got a strange problem. I'm trying to move some code over from IAR
Kickstart (where I developed it) to Crossworks (where I need to show
it working, for various reasons). The debugger I'm using is the ez430;
the target is a TI MSP430F2012 target board soldered to a larger
circuit. I can build fine, but if I click "build and debug" I get
various problems; either it pretends to run but really just sits
there, or it says it couldn't run to breakpoint (no breakpoints are
set). Verify usually fails.

I've tried it on a bare T2012 board with nothing attached, and using a
trivial piece of code that just blinks the LED. It looks as if it
can't even write the flash area reliably; very strange.

Same computer, same everything works fine with IAR.

I've tried copying msp430.dll from the IAR directory (2.1.10.1) to the
CrossWorks directory (was 2.1.7.0) with no discernible effect.

Has anyone got this working?