Have you used it successfully? Helios has that too (since early 2011?),
but I've never got it running. I've just updated to indigo and still
can't make it work.
When trying to start a debug session, it eventually just hangs in the
openocd startup process after it's detected my device, regardle
Please give a warm welcome to Jean-Christophe as the release
manager.
He will be laying down some new ground rules for how we
treat the git repository and how we handle the release process.
As well as releases, we're looking forward to more the improved
discipline and structure, which will help i
On Wed, Jun 29, 2011 at 3:43 PM, Andreas Fritiofson
wrote:
>
>
> On Wed, Jun 29, 2011 at 9:17 PM, Rodrigo Rosa
> wrote:
>>
>> On Wed, Jun 29, 2011 at 12:44 AM, Øyvind Harboe
>> wrote:
>> > This is disturbing. Why switch to global variables?
>> >
>> > +static uint32_t data_read_dummy;
>> > stati
The warnings are gone.
I saw some more followup to your patches. Could you work over
that feedback and push a fix to a branch in your fork and post
a message when it's ready?
Thanks!
We may be moving to "pull requests" soon
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US t
On Wed, Jun 29, 2011 at 9:17 PM, Rodrigo Rosa wrote:
> On Wed, Jun 29, 2011 at 12:44 AM, Øyvind Harboe
> wrote:
> > This is disturbing. Why switch to global variables?
> >
> > +static uint32_t data_read_dummy;
> > static int jtag_data_write(struct target * target, uint32_t instr,int
> > num_bits
patches 1,2,3,4 get the target to the state it was before it was
disabled, but with the warnings fixed.
why were the warnings not showing up when i originally submitted the patch?
the dsp5680xx has been around for at least a month...
i'm worried about not being able to get the compiler to show me
Could you create a branch in your fork and post something when it's ready?
Thanks!
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/
___
Openocd-development
i messed something up during the last changes, this patch fixes it.
i'll be doing a lot of testing during the next days.
sorry for the trouble...
On Wed, Jun 29, 2011 at 1:13 PM, Rodrigo Rosa wrote:
> On Wed, Jun 29, 2011 at 12:20 PM, Øyvind Harboe
> wrote:
Seperate patch? Does this have
On Wed, Jun 29, 2011 at 12:20 PM, Øyvind Harboe wrote:
>>> Seperate patch? Does this have anything to do with fixing warnings?
>>>
>>> - counter = FLUSH_COUNT_FLASH;
>>> + counter = FLUSH_COUNT_READ_WRITE;
>>>
>>
>> nothing to do with warnings, but it doesn't really affect anything,
>> s
>> Seperate patch? Does this have anything to do with fixing warnings?
>>
>> - counter = FLUSH_COUNT_FLASH;
>> + counter = FLUSH_COUNT_READ_WRITE;
>>
>
> nothing to do with warnings, but it doesn't really affect anything,
> since both constants are defined to the same value (i'm was
> exp
On Wed, Jun 29, 2011 at 12:44 AM, Øyvind Harboe wrote:
> This is disturbing. Why switch to global variables?
>
> +static uint32_t data_read_dummy;
> static int jtag_data_write(struct target * target, uint32_t instr,int
> num_bits, uint32_t * data_read){
> int retval;
> - uint32_t data_read_dum
From: Spencer Oliver
The actual release is 411e92fea9621630eb350e0c2bb43543e553b84f as we
had a few issues relating to its use within openocd.
Signed-off-by: Spencer Oliver
---
jimtcl |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/jimtcl b/jimtcl
index 60dfb02..411e9
On Wed, Jun 29, 2011 at 4:32 PM, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 07:24 Wed 29 Jun , Øyvind Harboe wrote:
>> On Wed, Jun 29, 2011 at 2:30 AM, Jean-Christophe PLAGNIOL-VILLARD
>> wrote:
>> > On 20:20 Tue 28 Jun , Øyvind Harboe wrote:
>> >> Where is the plan?
>> > I'll write the
On Wed, Jun 29, 2011 at 4:25 PM, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 08:34 Wed 29 Jun , Øyvind Harboe wrote:
>> So when I send a pull request to you from my repository, would
>> you rebase or merge?
> merge never rebase the master repo
I was thinking about branches you pull from. If
On 07:21 Wed 29 Jun , Øyvind Harboe wrote:
> >> I'd have some reservations about only one person having write
> >> access, but not particularly the way of working. Call me old fashioned.
> > Does not mean you do not have the write access does just mean you dont use
> > it
> > As example if the
On 08:13 Wed 29 Jun , Øyvind Harboe wrote:
> On Wed, Jun 29, 2011 at 7:43 AM, simon qian
> wrote:
> > Is it possible to update Versaloon driver in 0.5.0 release?
> > Mail me if there is any problem with the driver patch.
>
> I don't have a problem with applying this patch as it only affects
On 07:24 Wed 29 Jun , Øyvind Harboe wrote:
> On Wed, Jun 29, 2011 at 2:30 AM, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > On 20:20 Tue 28 Jun , Øyvind Harboe wrote:
> >> Where is the plan?
> > I'll write the patch when we have finish the discussion about the workflow
> > now we just clos
On 08:34 Wed 29 Jun , Øyvind Harboe wrote:
> So when I send a pull request to you from my repository, would
> you rebase or merge?
merge never rebase the master repo
>
> We now have a nice linear history, which gives me a warm fuzzy
> feeling for a simple project like OpenOCD
>
> What wou
Hi all,
I have additional questions about target_read_memory() and
target_read_u32() used to set/unset breakpoints.
I can see that target_read_memory() simply calls
mips_m4k_write_memory() and since I have big endian MIPS target, bytes
are not swapped.
However, target_read_u32(), besides calling
This is disturbing. Why switch to global variables?
+static uint32_t data_read_dummy;
static int jtag_data_write(struct target * target, uint32_t instr,int
num_bits, uint32_t * data_read){
int retval;
- uint32_t data_read_dummy;
Seperate patch? Does this have anything to do with fixing warni
20 matches
Mail list logo
