Thanks for taking charge on this one.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/m
On Saturday 07 November 2009, simon qian wrote:
>
> Try attached patch.
> Turn default_mmu back to original version.
I committed a patch that just reverts everything added in
the patch which changed that. More to come ... but current
GIT should thus resolve this problem.
_
On Monday 09 November 2009, Øyvind Harboe wrote:
> > My issue with that patch is that it should not be needed!
> >
> > If there is no mmu() method ... that's sufficient to
> > know that has_mmu() == false. Etc.
>
> So all CPUs that have an MMU should implement this fn?
>
> OK.
Yes.
> That wo
On Monday 09 November 2009, Øyvind Harboe wrote:
> > I don't follow. Disregarding all non-MMU stuff,
> > and presuming the above commit gets reverted, what
> > are the "no-ops" you refer to?
>
> Lets say we define a polymorphic cache flushing fn.
That's non-MMU stuff. You don't have an MMU-rela
On Mon, Nov 9, 2009 at 10:12 PM, David Brownell wrote:
> On Monday 09 November 2009, Řyvind Harboe wrote:
>> On Mon, Nov 9, 2009 at 8:23 PM, David Brownell wrote:
>> > On Monday 09 November 2009, Thomas Kindler wrote:
>> >> btw: the current git-master still has the problem.
>> >
>> > Does it work
On Monday 09 November 2009, Øyvind Harboe wrote:
> On Mon, Nov 9, 2009 at 8:23 PM, David Brownell wrote:
> > On Monday 09 November 2009, Thomas Kindler wrote:
> >> btw: the current git-master still has the problem.
> >
> > Does it work if you replace that patch with
> >
> > git show d269122f91efa
On Mon, Nov 9, 2009 at 8:23 PM, David Brownell wrote:
> On Monday 09 November 2009, Thomas Kindler wrote:
>> btw: the current git-master still has the problem.
>
> Does it work if you replace that patch with
>
> git show d269122f91efaf2f745424c215fabb758b7e7ea0 |patch -p1 -R
>
> I don't like that
On Monday 09 November 2009, Thomas Kindler wrote:
> btw: the current git-master still has the problem.
Does it work if you replace that patch with
git show d269122f91efaf2f745424c215fabb758b7e7ea0 |patch -p1 -R
I don't like that patch at all. It adds needless clutter;
the same effect can be h
simon qian wrote:
> Try attached patch.
Works for me!
btw: the current git-master still has the problem.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Saturday 07 November 2009, simon qian wrote:
> 0.3.0 has a bug in target_alloc_working_area, and fixed in 0.3.1.
> But head version has a problem with default_mmu, which will return
> ERROR_FAIL, stm32 doesn't implement mmu, so it uses default_mmu, and will
> cause target_alloc_working_area retu
simon qian pisze:
> Try attached patch.
> Turn default_mmu back to original version.
This patch fixes the issue with master's head ( [; ) for me (on both
chips that I've tried).
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berl
David Brownell pisze:
> I'd suspect a bad build. On the other hand, no matter what's
> causing the problem, THIS
Me too, but I've built that 3 times, from snapshot and directly with git
clone... The build is fine.
>>> Error: Not implemented.
>
> is a really *horrible* diagnostic. *WHAT* is no
Try attached patch.
Turn default_mmu back to original version.
2009/11/8 David Brownell
> On Saturday 07 November 2009, Freddie Chopin wrote:
> > But... The current master in main branch still fails the same way...
> > This is extremely strange, because I open the target.c file and it HAS
> > th
On Saturday 07 November 2009, Freddie Chopin wrote:
> But... The current master in main branch still fails the same way...
> This is extremely strange, because I open the target.c file and it HAS
> the fix ( (!enabled) ), but still doesn't work...
I'd suspect a bad build. On the other hand, no m
0.3.0 has a bug in target_alloc_working_area, and fixed in 0.3.1.
But head version has a problem with default_mmu, which will return
ERROR_FAIL, stm32 doesn't implement mmu, so it uses default_mmu, and will
cause target_alloc_working_area return ERROR_FAIL.
2009/11/7 Freddie Chopin
> I've just ch
I've just checked the 0.3.1-dev branch and I confirm that it works for
me - I can flash STM32 and LPC2103 normally. I've tried this:
http://openocd.git.sourceforge.net/git/gitweb.cgi?p=openocd/openocd;a=commit;h=c6ac97cf3b95ad5a9582ad6e6ea159d9d2aa9e1b
But... The current master in main branch sti
16 matches
Mail list logo