David E. Lotton @ Tue, 24 Jun 2008 18:16:36 -0600: > So the TUSB3410 is getting bootstrapped with firmware from the OS > driver(Linux/Win), correct?
Yes, it boots by its own bootloader to load application firmware: * from the OS it's usb connect, usb load fimware, usb reconnect, choose usb_config (usually udev). * from EEPROM it must run right away, but its speed is too small to pass USB standard plug/run tests. Thus all dances with firmware, ugly linux udev etc. are in due. > 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. Yes, FET itself has a msp430 chip implementing JTAG. This application is updated by proprietary TI's JTAG driver dll in case of newer devices support. > Is that a close approximation? Yes. The question is why people can't update JTAG application in uC under MS Windows and happily use it under Linux/OS afterwards, living out obvious stuff like 20-bit address space support in toolchain. -- sed 'sed && sh + olecom = love' << '' -o--=O`C #oo'L O <___=E M
