Hello All,
I just wanted to clarify that Signalyzer-H2 is also USB 2.0 high-speed
device with RTCK support just like any other FT2232H based devices. As
original Signalyzer it features two ports, both of these can be used
for JTAG interfacing if needed. Some other, currently unrelated to
OpenOCD f
Tue, Oct 27, 2009 at 12:41 PM, David Brownell wrote:
> On Tuesday 27 October 2009, Signalyzer ( www.signalyzer.com ) wrote:
>> Please find attached a subset of the Signalyzer H support that will
>> compile with released version of libftdi and not require proposed
>> libftdi mo
onfig files to ./tcl/interface .
Files are attached to this message.
Many thanks,
Oleg
---
www.signalyzer.com
On Tue, Oct 27, 2009 at 6:53 AM, Signalyzer ( www.signalyzer.com )
wrote:
> Hello David,
>
> Please find attached a subset of the Signalyzer H support that will
> comp
Hello David,
Please find attached a subset of the Signalyzer H support that will
compile with released version of libftdi and not require proposed
libftdi mods.
I sincerely hope they will make into 0.3.0 release.
Best regards,
(I apologize for duplicate message)
Oleg
On Sun, Oct 25, 2009 at
Hello,
Thank you for your valuable feedback. I certainly understand your
concerns and recommendations.
I will revisit the code and make it to function without new libftdi
functions, at least for the time being, until these functions
propagate into libftdi.
Many thank
Oleg
www.signalyzer.com
PM, David Brownell wrote:
> On Friday 23 October 2009, Signalyzer ( www.signalyzer.com ) wrote:
>>
>> This patch adds support for Signalyzer H2 (FT2232H) and Signalyzer H4
>> (FT4232H) to OpenOCD using D2XX and/or libftdi drivers.
>
> Great ... but could you spin a versi
This patch adds support for Signalyzer H2 (FT2232H) and Signalyzer H4
(FT4232H) to
OpenOCD using D2XX and/or libftdi drivers.
Signalyzer H relies on FTDI eeprom location read/write calls for the
extra functionality
built into the product, therefore patched version of libftdi must be
used implement
