On Mon, Feb 24, 2014 at 3:05 PM, Paul Fertser wrote:
> ajkroll on IRC asks for some feedback on jlink adapters, suspecting a
> bug in OpenOCD code. Can anyone please state if jlink driver works
> properly with the current code?
Seems to work fine for me on an IAR STM32-SK starter kit. I just
buil
On Mon, Feb 24, 2014 at 8:53 PM,
wrote:
> > "Alain" == Alain Mouette writes:
>
> Alain> Looking forward for that to become official...
>
> Alain> Thanks to whoever is working on it :-)
>
> Thanks from here too!
>
You're welcome!
>
> Does anybody have speed fort SWD on such a FTDI
> "Alain" == Alain Mouette writes:
Alain> Looking forward for that to become official...
Alain> Thanks to whoever is working on it :-)
Thanks from here too!
Does anybody have speed fort SWD on such a FTDI adapter?
Bye
--
Uwe Bonnesb...@elektron.ikp.physik.tu-darms
Hi Jörg.
Thanks for the pointer. :)
I'll check out the patch, probably tomorrow (it's too late for me to start a
build right now).
Love
Jens
On Mon, 24 Feb 2014 17:35:50 +0100, Jörg Fischer wrote:
> Hi,
> Am 24.02.2014 08:15, schrieb Jens Bauer:
>> The LPC812 datasheet does not mention a TAP I
This is an automated email from Gerrit.
Andreas Fritiofson (andreas.fritiof...@gmail.com) just uploaded a new patch set
to Gerrit, which you can find at http://openocd.zylin.com/1969
-- gerrit
commit 019c562f5c21e92a92b035da8c61571ea69109ed
Author: Andreas Fritiofson
Date: Mon Feb 24 20:44:5
Em 24-02-2014 13:35, Jörg Fischer escreveu:
> Hi,
> Am 24.02.2014 08:15, schrieb Jens Bauer:
> Note that there is a new SWD pacth in gerrit for SWD with FTDI
> adapters. -- Jörg Fischer
Looking forward for that to become official...
Thanks to whoever is working on it :-)
Alain
--
Hi,
Am 24.02.2014 08:15, schrieb Jens Bauer:
> The LPC812 datasheet does not mention a TAP ID for the LPC8xx devices.
> So I asked NXP for the TAP ID, and they replied that 0x0BC11477 should work.
> But I have not been able to communicate with my device using JTAG-lock-pick
> Tiny 2 or any of my O
Hi Andreas.
On Mon, 24 Feb 2014 09:13:18 +0100, Andreas Fritiofson wrote:
> On Mon, Feb 24, 2014 at 8:15 AM, Jens Bauer wrote:
>> The LPC812 datasheet does not mention a TAP ID for the LPC8xx devices.
>> So I asked NXP for the TAP ID, and they replied that 0x0BC11477 should work.
>
> Does auto-p
On Mon, Feb 24, 2014 at 11:05:31AM +0400, Paul Fertser wrote:
> Hi,
>
> ajkroll on IRC asks for some feedback on jlink adapters, suspecting a
> bug in OpenOCD code. Can anyone please state if jlink driver works
> properly with the current code?
Best I can say is that a Micrium (STM32F107) worked
On 23.02.2014 06:25, Paul Fertser wrote:
> Hi,
>
> On Sat, Feb 22, 2014 at 11:02:14PM +0100, Andreas Ortmann wrote:
>> I'm playing around with the TCL RPC (default port ) atm. The problem
>> is that I cannot get the output of commands like:
>> 'mem2array outputArray 8 0x023223 1\x1a'
>> in a co
On 23.02.2014 05:47, Duane Ellis wrote:
> What are you expecting the ‘mem2array’ to do?
>
> As the name implies, the function reads memory and places it into an array
> variable, there would be no output from that.
>
> If I remember the syntax of this command:
>
>mem2array outputArray 8 0x02
On Mon, Feb 24, 2014 at 8:15 AM, Jens Bauer wrote:
> Hi all.
>
> The LPC812 datasheet does not mention a TAP ID for the LPC8xx devices.
> So I asked NXP for the TAP ID, and they replied that 0x0BC11477 should
> work.
>
Does auto-probing give anything at all? Try openocd -f interface.cfg -c
"adap
12 matches
Mail list logo
