On Mon, Jun 20, 2011 at 9:19 PM, amotec-laurent_gauch <[email protected]> wrote: > Your TCL bitbang will control the port of the FTDI from an higher level than > FT2232.c. OK but you TCL bitbang is specific to the layout used. How do you > accept or not the use of the TCL procedure, if you do not have the notion of > layout in this function ???
Let's assume we want to use our specific interface to quickly flash the SPI memory because we have no time to get familiar with source code and complex program internals... some_very_specific_interface.cfg: (..) interface_signal MOSI 0x01 interface_signal MISO 0x02 interface_signal SCK 0x04 interface_signal EN 0x08 interface_signal SPI 0 TCL script then can check if signal SPI is defined (no mask value, so no pin is driven, it is only informational), if so check if other signals are defined and proper value, if so work the SPI operation, if not return error because interface does not define/support necessary signals. If no such signals are defined by interface configuration file, there is no option to drive those signals on that specific interface, so there is no worry anything get broken. Again - signals are to be defined inside interface configuration file, so the signals are also layout specific. This is far more better solution than hardcoding them into source code... Btw. I have to add signal check interface to TCL command :-) How to make tcl command return some value that can be used for later calculation (i.e. "interface_signal mask" returns 0 for SPI signal, 1 for MOSI, 2 for MISO, ...) ? > How does the ADC controlled from K T ? It is connected somehow to free IO pinf on the FT2232H port. Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
