On Mon, Oct 29, 2018 at 12:53 PM The EMARD <[email protected]> wrote: > > HI Tim > > maybe easiest way is to get my (1-2 month old) openocd fork at github > where the patch is integrated and start modifying it to > support CBUS pins on the similar way as RS232 pins are supported > without breaking RS232 pins which already work :) > > https://github.com/emard/openocd > > Here is another JTAG bitbanger code perhaps a bit dirty written but it works > mixed RS232 and CBUS signaling for you to see how this is done > > https://github.com/emard/FleaFPGA-JTAG > > FT232R FT230X FT231X chips are all the same, they need to > switch modes between CBUS pins and RS232 pins therefore it's not > so straigtforward otherwise it would already been done
Davor, Ok I will take a look at those. Another thought I has is that I noticed the current linux-usb tree has added support for GPIO to the Linux ftdi-sio driver (https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/commit/drivers/usb/serial/ftdi_sio.c?id=ba93cc7da8965bd513a7393db0f030e51bff4b60). This means that one could use the generic sysfsgpio interface for OpenOCD with GPIO on any of the FTDI uart's. Would this be a cleaner path? I'm also completely unfamiliar with the generic sysfsgpio interface for OpenOCD. I've got another board coming my way in the next month that will attach an nRF52840 SWD to ARM GPIO's so perhaps that path makes more sense for me as the same method can be used for both the current board I have with FT231X CBUS GPIO SWD as well as the next board with ARM GPIO SWD. Regards, Tim _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
