On Monday 28 September 2009, Brian Hutchinson wrote:
> I have a BeagleBoard now :)
>
> It was a good but busy week!
Thanks for the report. ESC can be fun.
TI didn't happen to have XDS100 v2 prototypes did they?
http://wiki.davincidsp.com/index.php/XDS100
It's an oversight that OpenOCD doesn
On Monday 12 October 2009, Jiří Kubias wrote:
> Im using Amontec JTAGkey2 with FT2232H with LPC2364. The Openocd often
> reports me this error:
> Error: couldn't read the requested number of bytes from FT2232 device (76 <
> 81)
> Error: couldn't read from FT2232
>
> Im using libftdi. Usually I g
On Monday 12 October 2009, Henry Margies wrote:
> By the way, I just found the BSDL file for the NS9360 CPU.
> Not sure if that is helping, but it says (things like):
>
> -- Specifies the number of bits in the instruction register.
>
> attribute INSTRUCTION_LENGTH of cooper: entity is 3;
On Tuesday 13 October 2009, simon qian wrote:
> Any comments or suggestions?
I don't follow. Maybe if you showed the proposed change
to src/jtag/interface.h and sketched how it would be used
in higher level code, that would help...
- Dave
___
Openocd
On Tuesday 13 October 2009, Redirect "Slash" NIL wrote:
> Sorry about the inline patch. Please find the original diff file as a text
> attachment.
See appended comments. As is usual with this type of port, some
of the type warnings are real issues that need fixing. But a lot
of them seem to be
This makes the documentation a closer match to "help" output:
- "pathmove" somehow was not documented in the User's Guide
- "jtag_nsrst_assert_width" and "jtag_ntrst_assert_width"
are new; both needed descriptions.
- Removed two undocumented and fairly useless script mechanisms:
* prod
David Brownell wrote:
> On Wednesday 14 October 2009, Michael Schwingen wrote:
>
>> Have you setup correct Mini-IC entries using the "xscale vector_table"
>> command?
>>
>> Without that, the kernel crashes on the first exception, since the
>> mini-IC does not match ram contents.
>>
>
> We s
On Wednesday 14 October 2009, Michael Schwingen wrote:
>
> Have you setup correct Mini-IC entries using the "xscale vector_table"
> command?
>
> Without that, the kernel crashes on the first exception, since the
> mini-IC does not match ram contents.
We should start collecting hints for Linux de
Wookey wrote:
> I haven't tested new code yet (will do next week), but certainly
> with existing code we find that on pxa270, the kernel does not boot if
> openocd has left the CPU running in debug mode. i.e. to reboot and run
> the kernel we have to do 'jtag_reset 0 1' (to just waggle the reset
>
Well, that won't really work since history is nonlinear.
You can "git log --oneline -- path/to/file" to list out the last commit to
modify that file.
Then "git describe " and it'll give
you something like:
tagname--g
which is a valid way to specify a revision.
> -Original Message-
> Fro
On Wednesday 14 October 2009, Johannes Stezenbach wrote:
>
> > I was thinking about something like "0.2 + N versions".
>
> How about 'git describe'?
On one recent tree it says: "0.2.0-367-g4bc3132"
where the 367 ~= N ... good answer!
That also pretty much matches what "openocd --version" says:
On Wed, Oct 14, 2009 at 04:11:33PM +0200, Øyvind Harboe wrote:
> What's the most reasonable way to refer to a git version
> for human beings?
>
> In svn it's a small integer("only" in the thousands).
>
> I was thinking about something like "0.2 + N versions".
How about 'git describe'?
Johannes
On Wednesday 14 October 2009, Wookey wrote:
> +++ Michael Schwingen [2009-10-13 19:41 +0200]:
> > David Brownell wrote:
> > Looks quite stable to me. I use it regularly at home on IXP42x (I have a
> > BDI2000 at work), mostly in the mode of "reset halt / erase & program
> > flash / reset run", plus
On Tuesday 13 October 2009, Øyvind Harboe wrote:
> > So I'd think the current code is behaving, modulo issues
> > you might have with iMX31 ...
>
> The currrent code target/arm11* code doesn't assert srst,
> it just issues a halt during assert.
A quick skim of the docs suggests the right way to g
Øyvind Harboe wrote:
> What's the most reasonable way to refer to a git version
> for human beings?
>
> In svn it's a small integer("only" in the thousands).
>
> I was thinking about something like "0.2 + N versions".
>
>
Actually you can checkout things like
$ git checkout master~2 Makefile
S
Hi!
On Wed, Oct 14, 2009 at 6:11 PM, Øyvind Harboe wrote:
> What's the most reasonable way to refer to a git version
> for human beings?
>
> In svn it's a small integer("only" in the thousands).
>
> I was thinking about something like "0.2 + N versions".
Most git-using people are happy with commi
On Wed, Oct 14, 2009 at 10:11 AM, Øyvind Harboe wrote:
> What's the most reasonable way to refer to a git version
> for human beings?
>
> In svn it's a small integer("only" in the thousands).
>
> I was thinking about something like "0.2 + N versions".
Tags are cheap in git, you can make as many a
Øyvind Harboe ha scritto:
> What's the most reasonable way to refer to a git version
> for human beings?
>
> In svn it's a small integer("only" in the thousands).
>
> I was thinking about something like "0.2 + N versions".
You can't. Just use the relevant SHA-1 id (which you can easily find by
What's the most reasonable way to refer to a git version
for human beings?
In svn it's a small integer("only" in the thousands).
I was thinking about something like "0.2 + N versions".
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash progra
Committed.
Thanks!
--
Ø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/mailman/listinfo/ope
Ofrwarded from Ron, who's not subscribed.
- Forwarded message from Ron -
From: Ron
Date: Wed, 14 Oct 2009 04:50:17 +1030
To: woo...@debian.org
Subject: [PATCH] OpenRD board configuration
X-Spam-Status: No, score=-3.6 required=4.5 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham ve
+++ Michael Schwingen [2009-10-13 19:41 +0200]:
> David Brownell wrote:
> Looks quite stable to me. I use it regularly at home on IXP42x (I have a
> BDI2000 at work), mostly in the mode of "reset halt / erase & program
> flash / reset run", plus from time to time some gdb-based debugging. I
> had s
Worked. Committed.
--
Ø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/mailman/listinfo/
23 matches
Mail list logo
