On 7/3/06, Steve Underwood <ste...@coppice.org> wrote:
This rule certainly gets things started. When I plug in the FET tool the driver is loaded, but then I get "ti_download_firmware - error downloading firmware". The older rule create two phases - a boot load phase, and a running phase. I guess something like this is needed in the rules here to get the device up and running. Lots of USB devices need this kind of download operation. I found a couple of examples of downloading from a firmware file, but the TUSB3410 driver has the firmware inside it. I am still not clear how this works.
I do not know how the FET tool works but Microchip MPLAB ICD2 is similar. The initial USB product id is 0x8000 and after loading the firmware the product id becomes 0x8001. We just need to create two rules for it. http://piklab.sourceforge.net/support.php However, MPLAB ICD2 does not have a kernel driver associated and the firmware downloading is done in the libusb based application (piklab). So this is a bit different. Regards, Xiaofan
