Please add these files instead the previous ones.
The 'A' is still a trouble for ft2232 based emulators.
Amontec Team is working on ft2232.c and the jtagkey layout. Also, we
will resolve the specific ' A' on Windows in the same time.
After resolving the ' A', the specific 'Windows OS' lines will be
removed from the amontec-jtagkey.cfg and amontec-jtagkey-hispeed.cfg
Laurent
http://www.amontec.com
JTAGkey / JTAGkey-Tiny / JTAGkey-HiSpeed maker
## NOTE : Windows OS still needs the 'A' at the end of the Device Description
as
## "Amontec JTAGkey A"
##
## Amontec JTAGkey
## http://www.amontec.com
##
## interface reference: http://www.amontec.com/jtagkey.shtml
## openocd location : ./src/target/interface/amontec-jtagkey.cfg
interface ft2232
#ft2232_device_desc "Amontec JTAGkey"
## Windows OS (see NOTE)
ft2232_device_desc "Amontec JTAGkey A"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0xcff8
## NOTE : Windows OS still needs the 'A' at the end of the Device Description
as
## "Amontec JTAGkey-HiSpeed A"
##
## Amontec JTAGkey-HiSpeed
## http://www.amontec.com
##
## interface reference: http://www.amontec.com/jtagkey-hispeed.shtml
## openocd location: ./src/target/interface/amontec-jtagkey-hispeed.cfg
interface ft2232
#ft2232_device_desc "Amontec JTAGkey-HiSpeed"
## Windows OS (see NOTE)
ft2232_device_desc "Amontec JTAGkey-HiSpeed A"
ft2232_layout jtagkey
ft2232_vid_pid 0x0FBB 0x1000
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
