This is an automated email from Gerrit.
Mateusz Manowiecki (segmentat...@fault.pl) just uploaded a new patch set to
Gerrit, which you can find at http://openocd.zylin.com/2563
-- gerrit
commit 0a868a73635c7f11057a6768c441637761af
Author: Mateusz Manowiecki
Date: Thu Feb 26 22:06:46 2015
On Thu, Feb 26, 2015 at 07:38:30PM +0100, Uwe Bonnes wrote:
> Does perhaps LPC provide a signed replacement firmware with docs? Any other
> way to use the LPC Link?
https://www.segger.com/lpc-link-2.html ?
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer.
Hello,
it seems that the LPC Link as used on the LPCXpresso LPC11c24 has no open
documentation and the chip ist cryptographic protected and so can't be
reused.
Does perhaps LPC provide a signed replacement firmware with docs? Any other
way to use the LPC Link?
Thanks
--
Uwe Bonnes
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/2560
-- gerrit
commit 1e220c94b3bbee0ac94cb88b51f5e3a985d48c03
Author: Paul Fertser
Date: Thu Feb 26 19:42:08 2015 +0300
fla
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/2562
-- gerrit
commit 461c3a67773648a20eb1539a60387d70b9a25292
Author: Paul Fertser
Date: Thu Feb 26 20:18:38 2015 +0300
jta
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/2561
-- gerrit
commit ff8d775ad0b7e1b48449f0904a2ffa6ab32d7bf6
Author: Paul Fertser
Date: Thu Feb 26 19:48:08 2015 +0300
tar
This is an automated email from Gerrit.
Paul Fertser (fercer...@gmail.com) just uploaded a new patch set to Gerrit,
which you can find at http://openocd.zylin.com/2559
-- gerrit
commit a5bc07f8db2cda2b490c08e062010e34ea72d79f
Author: Paul Fertser
Date: Thu Feb 26 19:39:50 2015 +0300
fla
Paul Fertser wrote:
> > 1. Do all developers (contributors and core developers) have to
> > submit a code review for every change? I’m asking because many
> > projects only review changes made by contributors.
>
> Every (except for the two special "new release" and "restore normal
> development")
Thanks for answering Paul and Jens, I appreciate it.
- Radjino
From: Paul Fertser [fercer...@gmail.com]
Sent: Thursday, February 26, 2015 12:41 PM
To: Radjino Bholanath
Cc: openocd-devel@lists.sourceforge.net
Subject: Re: [OpenOCD-devel] Questions about cod
On Thu, Feb 26, 2015 at 2:22 PM, Tomas Vanek
wrote:
> HI,
>
> thanks for reporting.
> Can you please test and review
>
> http://openocd.zylin.com/2558
Thanks. I've tested it and the patch is okay.
Reviewed with +1 as well.
--
Xiaofan
--
Hi Jens :)
On Thu, Feb 26, 2015 at 12:36:44PM +0100, Jens Bauer wrote:
> On Thu, 26 Feb 2015 14:26:26 +0300, Paul Fertser wrote:
> > On Thu, Feb 26, 2015 at 10:12:58AM +0100, Jens Bauer wrote:
> >> Eh... It seems I have to issue that lpc2000 part_id 0 command,
> >> before the bank is updated ?
>
Hi,
Please feel free to announce the paper here with the results of the
research once it's ready.
On Thu, Feb 26, 2015 at 09:34:09AM +, Radjino Bholanath wrote:
> 1. Do all developers (contributors and core developers) have to
> submit a code review for every change? I’m asking because many
>
Hi Paul.
On Thu, 26 Feb 2015 14:26:26 +0300, Paul Fertser wrote:
> On Thu, Feb 26, 2015 at 10:12:58AM +0100, Jens Bauer wrote:
>> Eh... It seems I have to issue that lpc2000 part_id 0 command,
>> before the bank is updated ?
>
> [...] once you try to write to the bank, it'll get auto-probed and
On Thu, Feb 26, 2015 at 10:12:58AM +0100, Jens Bauer wrote:
> Eh... It seems I have to issue that lpc2000 part_id 0 command, before the
> bank is updated ?
> -So in fact, Nemui's patch must be working for me as well, but do I have a
> problem somewhere else, perhaps ?
Probably there's no issue a
Hi Radjino.
Questions 2 and 3 are best answered by those who knows the setup in details. ;)
On Thu, 26 Feb 2015 09:34:09 +, Radjino Bholanath wrote:
> 1. Do all developers (contributors and core developers) have to
> submit a code review for every change?
Nope, the rules are not so strict h
Hey Paul,
Il 26/feb/2015 08:27 "Paul Fertser" ha scritto:
>
> Hey Rodrigo,
>
> Thank you for the interest in OpenOCD.
>
> On Thu, Feb 26, 2015 at 12:22:56AM +, Rodrigo Santos wrote:
> > Giving this scenario, IMHO, it looks like I need to implement a
> > ptm.c file based on etm.c. Do you agree
Hi everyone,
I'm doing research on code reviews and static analysis tools at the SERG group
(http://swerl.tudelft.nl/bin/view/Main/WebHome) of the Delft University of
Technology. Currently, we want to give an overview of the usage of code review
and static analysis tools in open source projects
Hi Paul.
On Thu, 26 Feb 2015 11:03:59 +0300, Paul Fertser wrote:
> On Thu, Feb 26, 2015 at 01:22:53AM +0100, Jens Bauer wrote:
> It seems you're using an outdated target config (even though the
> binary is new), the current code has no lpc1788.cfg file at all,
> please retry with the recent versio
Hey Jens,
On Thu, Feb 26, 2015 at 01:22:53AM +0100, Jens Bauer wrote:
> I tested with LPC1788, but I'm not sure the auto-detection is working on my
> chip revision.
>
> ---8<-8<-8<-
> $ openocd -c 'telnet_port ' -f interface/ftdi/jtag-lock-pick_tiny_2.cfg
> -c "transport select
19 matches
Mail list logo
