On Feb 22, 2009, at 1:50 PM, Joern Kaipf wrote:
Hi at all,I'm currently planning the support for the FTDI FT2232H and FT4232H withOpenOCD. 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}
You should be able to handle this like all the other chips that have RTCK. They use 'jtag_khz 0'.
- 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 ?
I don't know anything about MSSPE, but I assume that either it tells you what chip you are talking to or when you set the speed, it will refuse the value for 30MHz if it isn't supported. I really don't like introducing new interface-specific commands and making the layout include which chip is used seems like a bad idea for maintenance. Some form of intelligence in the driver about what device it is talking to and what it is capable of is much nicer for the user.
regards Joern _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
