ftd2xx) and a small hardware mistake on my part.
#Byteblaster Altera Driver drivers#
Turns out I had issues with drivers (namely open source libftdi vs. Hope someone can shed some light on this,Īpologies for the late reply,I haven't done much work with ARM or CPLD's until a few days ago, when this saga started againīefore I made the first post in this topic I had managed to successfully use openocd 0.3.1, with a jtagkey-like interface to debug my At91SAM7256 board from omilex. I would love to get this working, as I'm still having 'issues' with my FT2232 programer (JTAGkey based clone) - which could be hardware, or software,I don't know.
#Byteblaster Altera Driver how to#
I realise there is a patch for a 'USB blaster clone' on this page:īut I do'nt know how to use it with either version of OpenOCD. I have only ever successfully used the latter version, it is the same one used in Jim Lynch's wonderful tutorial. I have tried the bove commands but it is not recognised as an interface. The following VID/PID is for Kolja Waschk's USB JTAG: Currently, only one vid, pid pair may be given, e.g. If not specified, default values are used. The vendor ID and product ID of the FTDI FT245 device. Config Command: usb_blaster_vid_pid vid pid
This setting is only valid if compiled with FTD2XX support. If not specified, the FTDI default value is used. Provides the USB device description (the iProduct string) of the FTDI FT245 device. Config Command: usb_blaster_device_desc description These interfaces have several commands, used to configure the driver before initializing the JTAG scan chain: USB JTAG/USB-Blaster compatibles over one of the userspace libraries for FTDI chips. Does anyone know if the Amtera USB blaster is supported by openOCD? It is mentioned (along with the config commands) on this page:
0 kommentar(er)
