Steve & Chris, thanks for the feedback.
So the TUSB3410 is getting bootstrapped with firmware from the OS
driver(Linux/Win), correct?
When I connected using gdbproxy the first time I was required to update
the FET firmware so that gdbproxy could talk to the FET. I'm guessing
this was static firmware in the "JTAG engine" inside the FET (another
msp430?) and nothing to do with the TUSB3410.
Is that a close approximation?
Dave L.
Chris Liechti wrote:
Stephen Glow schrieb:
I believe that the FET is first recognized as a generic device when it's
plugged in, then the driver downloads firmware to it and the device
disconnects & reconnects to the USB as a different device.
yup. i think it does this. thats the standard way to use a TUSB3410
which is used in the box.
hm. replacing teh EEPROM on the box it would be possible to store the
second stage firmware there. that might cure some problems.
chris
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
