Hans Nieuwenhuis writes:
> I have been playing tonight with mspdebug (git) and a USB FET but I can't
> seem to get them to work together. I used mspdebug before with an
> eZ430-2013 stick and they work together great, thanks for that.
>
> The MSP-FET430UIF is a whole different beast to get working though. I
> know I have had it working once with an old version of mspdebug and
> unknown firmware, but lately I just cannot get it to work anymore.
>
> So far I tried FET versions 20401004 (the one delivered with CCS4) and
> 20402000 and an MSP-EXP430F5438 experimenter board as target. On windows
> it all works perfectly.
> Mspdebug bombs out with the following error:
>
> fet: FET returned error code 4 (Could not find device (or device not
> supported)) fet: command 0x28 failed
> fet: identify failed
>
> I am wondering which firmware is working. What I have seen also is that
> under windows the FET is responding with a 0x28 byte length message on a
> 0x28 command and in the case of mspdebug the response is 0x24 bytes
> length. I have snoppy logs available for anyone interested.
Hi Hans,
I (the author) would be interested in the Snoopy logs :).
There is a change you might like to try. I has worked for some people
but I haven't committed it yet as I'm still trying to figure out if it's
going to break things for others:
diff --git a/fet.c b/fet.c
index 0907f87..1c745fd 100644
--- a/fet.c
+++ b/fet.c
@@ -812,7 +812,7 @@ device_t fet_open(transport_t transport, int proto_flags,
int vcc_mv,
/* configure: Spy-Bi-Wire or JTAG */
if (xfer(dev, C_CONFIGURE, NULL, 0,
2, FET_CONFIG_PROTOCOL,
- (proto_flags & FET_PROTO_SPYBIWIRE) ? 1 : 0) < 0) {
+ (proto_flags & FET_PROTO_SPYBIWIRE) ? 1 : 2) < 0) {
fprintf(stderr, "fet: configure failed\n");
goto fail;
}
This appears to be a slightly different JTAG mode, and apparently it's
used by the new IAR software when querying devices on startup.
- Daniel
