On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands <p...@hands.com> wrote: > Package: openocd > Version: 0.9.0-1+b1
> I've added the " B" to the end of the ftdi_device_desc line in > interface/ftdi/openrd.cfg, thus: > > ftdi_device_desc "OpenRD JTAGKey FT2232D B" The device really has a B in its product string? I.e. "lsusb -v -d0403:9e90 | grep idProduct" shows the B? Is the device "original"? > > judging by the output from the working 0.5.0 package A lot has happened since 0.5.0 apart from the adapter driver change so the problem might lie somewhere else than ftdi vs ft2232. Can you try the latest release that included the ft2232 driver (0.8?), or even better, build from source and explicitly pass --enable-legacy-ft2232_libftdi to configure (make sure you have libusb-1.0 and libftdi dev packages installed). The feroceon target has AFAIK not been tested in a long time so there might be issues with that. Does the hardware allow you to connect other targets to the same debug adapter or vice versa (i.e. an external debug connector or such)? Just trying to reduce the number of unknowns. > the right number > is probably: > > adapter_khz 3000 > > (I've also tried various other frequencies without success) The result shouldn't be especially dependent on a specific frequency. Usually there's a max and lower than that shouldn't make a difference. If your log is complete there is no frequency issue. > > I notice that running openocd causes the /dev/ttyUSB0 device to disapear, > so it's certainly doing something, even if it's not very useful. OpenOCD detaches the kernel driver on the selected interface (FTDI channel) which might serve a serial port if so configured. Do you really have a tty on the same interface/channel as the JTAG circuitry? Channel A *should* be unaffected by OpenOCD if "ftdi_channel 1" is selected. > Attached is the output from running this with -d3 -- feel free to ask > me to run other tests, or try other options. Did you truncate the log or did it just freeze right there? Regards, Andreas
