EmbeddedRelated.com
Forums
Memfault Beyond the Launch

CrossWorks and eZ430

Started by leon_heller August 15, 2006
I just tried CrossWorks with the eZ430 and my F2001 board, using the
MSP-FET430UIF target. I was slightly surprised to find that it worked
OK, as TI doesn't seem to state anywhere that the eZ430 is compatible
with the USB FET.

Leon

Beginning Microcontrollers with the MSP430

I've wondered too Leon.
I just simply assumed that the EZ430 "clones" a FET430UIF target ?
Debugging works perfect - but then again, debugging always has been painless on CrossWorks :-)
(V1.3 & V1.4)

I looked in the USB details properties of the EZ430 and indeed DEVCAP_UNIQUE_ID &
DEVCAP_SURPRISE_REMOVAL_OK is present.
I've tried unplugging the EZ430 (w/o using safe HW removal), replugged it in and it works fine, as
expected.
This came up in a thread a while ago.

73s & best regards,
Kris

-----Original Message-----
From: m... [mailto:m...] On Behalf Of leon_heller
Sent: Wednesday, 16 August 2006 5:49 AM
To: m...
Subject: [msp430] CrossWorks and eZ430

I just tried CrossWorks with the eZ430 and my F2001 board, using the
MSP-FET430UIF target. I was slightly surprised to find that it worked
OK, as TI doesn't seem to state anywhere that the eZ430 is compatible
with the USB FET.

Leon
--- In m..., "Microbit" wrote:

> I just simply assumed that the EZ430 "clones" a FET430UIF target ?

I am guessing that the EZ430 uses SpyBiWire and the msp430.dll is able
to support that, and abstract the differences so the PC-side debuggers
will work unmodified. That assumes CrossWorks is using that DLL. I'm
not sure if this is the case?

Does anyone know if the gdbproxy will be modified to support USB
debugging on linux? I read somewhere that there was an effort underway
but I haven't heard whether this was ever completed. We can't use
msp430.dll on the linux side so the job is much harder.

Eric
Eric,

> I am guessing that the EZ430 uses SpyBiWire and the
> msp430.dll is able to support that, and abstract the
> differences so the PC-side debuggers will work unmodified.
> That assumes CrossWorks is using that DLL. I'm not sure if
> this is the case?

CrossWorks supports the MSP430 DLL interface, of course. However, TI
have muddied the water somewhat with SBW support, releasing a couple of
DLLs that you would think had identical functionality but don't.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
CrossWorks for ARM, MSP430, AVR, MAXQ, and now Cortex-M3 processors

Memfault Beyond the Launch