On 10/24/2010 02:14, David Brownell wrote:
Why not assume a mismatch between its
custom firmware (for MSP430 debug??) and
your expectations?
That TUSB chip is just a fairly
generic programmable USB+serial
beast, which has been used for years. In
such cases, I assume the hardware is fine,
and any issue is software expectations.
You are after all not using it with the
intended software application, which has
key information embedded in it (ISTR there
are no docs for the MSP430 debug protocols,
at least generally available ones (TI must
clearly have internal docs).
To be honest the device does present two interfaces, one that is meant
for debug, and one that appears as CDC_ACM.
The issue at hand here is not programming/accessing the device using the
debug interface, which works fairly well, but actually communicating
with an already programmed device(which then communicates through the
serial interface).
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
