|Date Added:||24 August 2016|
|File Size:||58.41 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
The trouble with this device is that it is just a generic set of USB endpoints until the driver does something specific with it for device initialization. Sure, I would certainly be willing to work with you to try and identify this.
As I suspected, it doesn’t offer any clues as to what went wrong: Let me know if I can send you anything to help diagnose the problem. No, Bus Powered 7: But it would be really good to know the USB endpoint types on the device bulk, interrupt, etc. Sorry about that, the formatting on that output did not translate to HTML well. Now I know it’s a high-speed USB device, which is important. So far I’m not aware of other complains re USB regressions in 3.
ACTEL FLASHPRO3 JTAG FPGA Device Programmer USB Interface
Feel free to contact me at michaln at sun dot com. Bus Device Changed 9 years ago by jhodapp attachment Windows XP Any ideas where to find it? Now when I use the software in Windows that utilizes the FlashPro3 device for programming a hex file onto a flash device for an embedded microprocessor, I get an error stating that the software cannot communicate with the device.
Please e-mail me at the address I have in the previous comment; I don’t have access to your e-mail address.
Thanks for the lsusb output. I just upgraded to VB 3.
Connect the Flashpro3 device to virtualbox click the usb icon in the bottom right of the virtualbox window and check “Actel Flashpro3 Programmer” Open the flashpro software and load a project. Description I just upgraded to VB 3.
Actel FlashPro JTAG
The broken formatting is not a real problem, and at any rate it’s the same information that lsusb -v printed. Reserved set to one. I noticed that Flashpro software finds device but when I try to rescan programmers, device stops responding. Reserved set to one bus-powered for 1. There may be other OS X utilities which show this information, or perhaps you have access to a Linux machine.
So without knowing how the device uses them, that doesn’t help much: Without such information, we don’t even know what to start looking at. Can you make any sense of that or do you need it in a text file as an attachment? So inserting it into Linux without a proper driver is meaningless for getting endpoint information. I don’t currently have XCode on my Macbook Pro because it’s rather large, so this was the best I could do.