Looking into it. The failure is on a really low level because the scan
chain discovery just finds garbage. I suspect a problem with the reset
signals because the I/O initialization seems to otherwise match the legacy
driver. Looking at the old driver it seems the adapter has fully
tristate-buffered reset signals even though they are not used as such. Not
sure why that should be a problem but can you anyway try the following
config file patch?
diff --git a/tcl/interface/ftdi/sheevaplug.cfg
b/tcl/interface/ftdi/sheevaplug.cfg
index f299f27..5e3f369 100644
--- a/tcl/interface/ftdi/sheevaplug.cfg
+++ b/tcl/interface/ftdi/sheevaplug.cfg
@@ -10,5 +10,5 @@ ftdi_vid_pid 0x9e88 0x9e8f
ftdi_channel 1
ftdi_layout_init 0x0608 0x0f1b
-ftdi_layout_signal nTRST -data 0x0200
-ftdi_layout_signal nSRST -noe 0x0400
+ftdi_layout_signal nTRST -data 0x0200 -noe 0x0100
+ftdi_layout_signal nSRST -data 0x0800 -noe 0x0400
On Wed, Aug 10, 2016 at 11:23 PM, Benjamin Rodgers <
[email protected]> wrote:
>
> On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson <andreas.
> [email protected]> wrote:
>>
>> On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers <benjamin.rodgers@veri
>> zondigitalmedia.com> wrote:
>>>
>>> On Thu, 23 Jul 2015 00:57:21 +0200 Andreas Fritiofson <
>>> [email protected]> wrote:
>>>
>>>> On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands <[email protected]> wrote:
>>>>
>>>>> 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.
>>>
>>>
>>> With the legacy driver "/dev/ttyUSB0" is no longer disappearing upon
>>> running OpenOCD. It was disappearing with the FTDI driver.
>>>
>>
>> Can you send the output of "lsusb -v -d 0x9e88:0x9e8f" and whatever adds
>> to "dmesg" after plugging in the adapter and starting openocd (beginning
>> with the line "new full-speed USB device number...")?
>>
>
> I've attached the output of both (lsusb.txt, dmesg.txt).
>
>
Nothing in dmesg when openocd starts and ttyUSB0 goes missing? I just want
to confirm that openocd actually opens the correct interface, otherwise
that could be the problem (talking JTAG with the serial port circuitry).
The "ftdi_channel 1" option is not used a lot and I've never tested it
myself. A disappearing serial port might indicate that the interface is
actually wrong, but it could also be some quirk of
libusb/ftdi_sio/virtualbox.
Regards,
Andreas Fritiofson
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
