On Sat, Nov 5, 2016 at 11:49 AM, Andreas Fritiofson <
andreas.fritiof...@gmail.com> wrote:
>
> Well, I assume other people have successfully used that config file before
>
Specifically https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751372#40
On Thu, Oct 27, 2016 at 2:35 PM, Arnaud Patard
wrote:
> Hi,
> I've modified the
> /usr/share/openocd/scripts/interface/ftdi/sheevaplug.cfg file to use
> ftdi_channel 0 and not 1. With that change, I was able to use openocd,
>
Well, I assume other people have successfully used that config file be
0x0800 -noe 0x0400
On Wed, Aug 10, 2016 at 11:23 PM, Benjamin Rodgers <
benjamin.rodg...@verizondigitalmedia.com> wrote:
>
> On Wed, Aug 10, 2016 at 3:24 AM, Andreas Fritiofson fritiof...@gmail.com> wrote:
>>
>> On Wed, Aug 10, 2016 at 4:55 AM, Benjamin Rodgers &
part of the motivation for the full rewrite. We will not
fix issues with the deprecated ft2232 driver upstream, in fact we have a
patch pending to purge it completely. Now that we know that the same setup
works with ft2232 but not with ftdi, let's focus on getting the latter
working.
>
> On
On Wed, 22 Jul 2015 14:17:31 +0100 Philip Hands 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
5 matches
Mail list logo
