>
> Hi at all,
>
> I'm currently planning the support for the FTDI FT2232H and FT4232H with
> OpenOCD. They have some new features and I would like to have some
> comments for the implementation.
>
> There are two main features:
>
> - Adaptive Clocking: For this feature I would like to introduce a new
> parameter for the interface file, e.g.
>
> ft2232_adaptive_clocking {0,1}
>
> - A TCK of 30 Mhz is now possible and that's my main problem. How to
> handle this. I thought about three options:
>
> * create a new parameter for the interface file, e.g.
> ft2232_device FT2232{C,D,L,H}
>
> * try to implement a sort of autodetect. I currently do not know if it
> is possible, just an idea.
>
> * Extend the table of the layouts in ft2232.c with a addional column,
> which chip is assembled.
>
> I prefer option 1. What do you think ?
>
> regards
> Joern
Use the
* try to implement a sort of autodetect. I currently do not know if it
is possible, just an idea.
When openning the device get-and-store a new var as deviceType
Device Type = 4 for FT2232C/D -> Amontec JTAGkey (USB2.0 full-speed)
Device Type = 6 for FT2232H -> Amontec JTAGkey2 (USB2.0 high-speed)
Then re-use the deviceType when modifying Frequency (30Mhz vs. 12Mhz ...) /
Adaptative-frequency (RTCK), and other supports for Texas OMAP Boundary Scan.
Note: I just did like that this morning on the new Amontec JTAGkey2 (USB2.0
high-speed) and that works great (in Amontec SVF Player).
Amontec JTAGkey2 (USB2.0 high-speed) is working very fast.
If I have time I will add support of Amontec JTAGkey2 in OpenOCD next week.
Laurent Gauch
http://www.amontec.com
Making JTAG a snap !
______________________________
*Amontec To Exhibit at Embedded World 2009
*Amontec Hi-Speed JTAGkey2
Compare JTAGkey and JTAGkey2 speeds yourself at
Embedded World 2009 <http://www.embedded-world.de/en/> in Nuremberg,
Germany from 3rd - 5th March 2009
FTDI Hall 12 Stand 442
______________________________
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
