2009/6/23 Audrius Urmanavičius <didele.d...@gmail.com>: > Also, since I have working build environment for OpenOCD, it makes no > problem now to build OpenOCD myself, I do not need prebuilt binary. I > just afraid that OpenOCD would drop libft2xx support altogether to > settle the dust down.
I hope not. At least 64bit Windows user will need that. > >> By the way, the serial port situation is not exactly clearly to me. >> Maybe there is a solution. I just do not have the hardware to test >> right now. > > AFAIK the current open source FT2232 drivers/libs lack dual-port'ness > support (I would be more than glad if I am mistaken here). Maybe they > will in some future, but I do need to do my job now, and I do with > libft2xx quite successfully. > I hope there is a solution for the serial port. I agree with the practical side of the solution -- to use FDT2xx private build if you can do that. It is a more optimum solution for now for Windows users and may remain so for the foreseeable future. In fact for work, my colleagues use IAR+J-Link for ARM MCU development. The cost of the firmware development tools are not that significant compared to other cost (labor, mechanical tooling, CE/UL/etc certification and other testing, etc). And others are using Keil, Rowley, etc. Both the commercial tools and open source solutions have their places. That is the good thing of choices. -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
