On Sat, May 30, 2009 at 10:08 PM, David Brownell wrote:
> On Saturday 30 May 2009, David Brownell wrote:
>> On Saturday 30 May 2009, Øyvind Harboe wrote:
>> > Why do I need to understand what this does?
>>
>> You don't. You just need to accept that since you're
>> working as a "maintainer", you n
git has the advantage of having more infrastructure (GUIs for example).
But some of the stuff that quilt was designed for is buried in exotic
commands in git.
'git help ' brings up the docs, 'git help git' lists all commands.
'git svn clone' creates a local git clone of an svn repo
'git svn rebas
On Sun, May 31, 2009 at 3:25 AM, Peter Denison wrote:
> Many thanks! Somehow in my testing (probably to try to replicate XC's
> config) I had put jtag_rclk in my .cfg file.
>
> I've replaced it with jtag_khz 30, and I can at least initialise now. Sorry
> for the misdirection.
I am guilty here.
>
On Saturday 30 May 2009, Peter Denison wrote:
> Quilt. It's exactly the tool to do this.
Exactly. You're working with a series of patches all
the time, so there's no special step to create one.
It's also a good way to work with semi-stable snapshots
while you finish stabilizing your work. You d
On Saturday 30 May 2009, Øyvind Harboe wrote:
> > This would work well with a "disable_rtck" ... when
> > a board doesn't support it, it shouldn't be possible
> > to try using it even if the adapter does.
>
> rtck is handled differently: if rtck is not supported, then
> setting rtck fails. The tcl
On Wed, May 27, 2009 at 2:33 AM, Krzysztof Dziuba
wrote:
> I attached my cfg file, I think it needs to be polished before including it
> to the official configurations, however it works for me.
> There is also patch which fix big endian issue. It was created by some other
> person and is some kind
On Sat, 2009-05-30 at 23:15 +0100, Peter Denison wrote:
> The debugging code in jlink_tap_execute() called when
> _DEBUG_USB_COMMS_ is
> defined was using the entire cached scan length to print the results
> buffers, and not the correct length of each individual buffer.
Committed, r1955.
--Z
__
On Fri, 2009-05-29 at 11:38 -0300, Alan Carvalho de Assis wrote:
> Hi all,
>
> Follow below links to some BSDL files:
>
> NXP LPC:
> http://www.standardics.nxp.com/support/models/lpc2000/
>
> Freescale PowerPC:
> http://www.freescale.com/webapp/sps/site/overview.jsp?code=DRPPCBSDLFLS
>
> Freesc
The debugging code in jlink_tap_execute() called when _DEBUG_USB_COMMS_ is
defined was using the entire cached scan length to print the results
buffers, and not the correct length of each individual buffer.
Index: src/jtag/jlink.c
On Sat, May 30, 2009 at 10:36 PM, David Brownell wrote:
> On Saturday 30 May 2009, Ųyvind Harboe wrote:
>> >> So these are *targets* that don't need or want
>> >> TRST?
>> >
>> > In the Atmel case, yes.
>> >
>> > In the TI case, no. TI boards often come with
>> > both "TI-14" and "ARM-20" JTAG co
On Sat, 30 May 2009, Duane Ellis wrote:
> All,
> (especially david & zach, you seem to do this very well).
>
> Yes, this is some what "off-topic" for this list, but it is on topic
> because the list wants "small more reviewable patches". To that end, I'm
> looking for a better way to deal with pat
All,
(especially david & zach, you seem to do this very well).
Yes, this is some what "off-topic" for this list, but it is on topic
because the list wants "small more reviewable patches". To that end, I'm
looking for a better way to deal with patch sets, etc.
I've noticed that for example some
(oops, sent this to the svn-mail list Doh!)
This commit earlier - exposes a now unused function,
Patch attached.
Modified: trunk/src/jtag/jlink.c
===
--- trunk/src/jtag/jlink.c 2009-05-30 07:56:14 UTC (rev 1948)
+++ trunk/src
On Saturday 30 May 2009, Øyvind Harboe wrote:
> >> So these are *targets* that don't need or want
> >> TRST?
> >
> > In the Atmel case, yes.
> >
> > In the TI case, no. TI boards often come with
> > both "TI-14" and "ARM-20" JTAG connectors.
> > So whether you have SRST depends on which kind
> > o
On Saturday 30 May 2009, David Brownell wrote:
> On Saturday 30 May 2009, Øyvind Harboe wrote:
> > Why do I need to understand what this does?
>
> You don't. You just need to accept that since you're
> working as a "maintainer", you need to enable that mode.
>
> The alternative is ugly: requiri
On Saturday 30 May 2009, Xiaofan Chen wrote:
> Do you know how to remove the warning?
> "Warn : DBGACK set while target was in unknown state. Reset or
> initialize target."
I consider that to be an initialization bug in the OpenOCD code.
One of several, actually ... sorting them all out will take
On Saturday 30 May 2009, Øyvind Harboe wrote:
> Why do I need to understand what this does?
You don't. You just need to accept that since you're
working as a "maintainer", you need to enable that mode.
The alternative is ugly: requiring everyone who builds
from source to have the *right* versio
Why is svf.c modifying cmd_queue_cur_state and
cmd_queue_cur_end_state?
This must end in tears as that state information belongs to
the private parts of jtag.c layer and modifying only the
JTAG layer doesn't take the driver into account.
Magnus explains a bit below a situation that I *believe* is
On Sat, 30 May 2009, Magnus Lundin wrote:
> Xiaofan Chen wrote:
>> On Sat, May 30, 2009 at 1:01 AM, Peter Denison
>> wrote:
>>
>>> Unfortunately not mine... I still get a 1 returned (instead of a zero) as
>>> the error code from EMU_CMD_HW_JTAG3, when I send 8 bits:
>>>
>>> Debug: 192 667 jlin
On Sat, May 30, 2009 at 5:10 PM, Michael Bruck wrote:
> My understanding is that usually projects provide pre-generated
> configure files so that users who want to build the package on their
> system don't need the autotools. A non-maintainer in this context is
> someone who just wants to compile
On Fri, May 29, 2009 at 4:51 PM, Zach Welch wrote:
>>
>> What about the J-Link issues with various target in the thread "TMS470
>> Scripts"?
>> TMS470:
>> https://lists.berlios.de/pipermail/openocd-development/2009-May/007391.html
Sorry this is a false alarm. The script I got has a problem of no
Hello Alan,
Friday, May 29, 2009, 4:38:55 PM, you wrote:
ACdA> Did I forget other BSDL links? Show me the link ;-)
http://www.freelabs.com/~whitis/electronics/jtag/
under "Semiconductor Manufacturer's BSDL files"
--
WBR,
Igormailto:skochin...@mail.ru
_
On Sat, May 30, 2009 at 11:39 PM, Magnus Lundin wrote:
> It looks like you are using jtag_khz 0, this means adaptive clocking with
> the RTCK signal. This work for LPC3148 that has a RTCK signal, but as far as
> I can find there is no RTCK singal on the TMS470R1A256.
>
> For testing interface
Xiaofan Chen wrote:
> On Sat, May 30, 2009 at 1:01 AM, Peter Denison wrote:
>
>> Unfortunately not mine... I still get a 1 returned (instead of a zero) as
>> the error code from EMU_CMD_HW_JTAG3, when I send 8 bits:
>>
>> Debug: 191 667 jlink.c:1032 jlink_usb_write(): jlink_usb_write, out_lengt
My understanding is that usually projects provide pre-generated
configure files so that users who want to build the package on their
system don't need the autotools. A non-maintainer in this context is
someone who just wants to compile the package rather than modify any
code (which would then poten
On Sat, May 30, 2009 at 1:01 AM, Peter Denison wrote:
> Unfortunately not mine... I still get a 1 returned (instead of a zero) as
> the error code from EMU_CMD_HW_JTAG3, when I send 8 bits:
>
> Debug: 191 667 jlink.c:1032 jlink_usb_write(): jlink_usb_write, out_length =
> 6, result = 6
> Debug: 1
2009/5/30 Igor Skochinsky :
> Hello Øyvind,
>
> Saturday, May 30, 2009, 9:40:54 AM, you wrote:
>
>>> than just "conform to JTAG spec". No problem when
>>> docs are available ... but sometimes they aren't.
> ØH> XScale is under Marvell NDA for instance :-)
> Really? What's this then?
OK, so *some*
remove unused check on TAP_INVALID. This value is never passed to drivers.
Comments?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Index: C:/workspace/openocd/src/jtag/ft2232.c
===
-
Hello Øyvind,
Saturday, May 30, 2009, 9:40:54 AM, you wrote:
>> than just "conform to JTAG spec". No problem when
>> docs are available ... but sometimes they aren't.
ØH> XScale is under Marvell NDA for instance :-)
Really? What's this then?
http://www.marvell.com/products/cellular/application/P
On Sat, May 30, 2009 at 2:01 PM, David Brownell wrote:
> On Saturday 30 May 2009, Řyvind Harboe wrote:
>> I see that I've jumped into a discussion where you are much
>> more up to date on the overall reset_config, how to write
>> quality documentation, etc. Below are some comments
>> where I had a
On Sat, May 30, 2009 at 8:01 PM, David Brownell wrote:
>> >> +If you have an interface that does not support SRST and
>> >> +TRST(unlikely),
>> >
>> > Not unlikely at all. The 14-pin JTAG connectors
>> > that TI uses don't pass SRST. The 10-pin JTAG
>> > connectors that Atmel uses with AVR8 (and
On Saturday 30 May 2009, Øyvind Harboe wrote:
> I see that I've jumped into a discussion where you are much
> more up to date on the overall reset_config, how to write
> quality documentation, etc. Below are some comments
> where I had any.
>
> Q: What's a "system configuration file"?
>
> I can t
Committed 1950
Remove JTAG_END_STATE entirely.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Index: C:/workspace/openocd/src/jtag/ft2232.c
===
--- C:/workspace/openocd/src/jtag/ft22
Committed 1949.
Splitting the patch into two. Next I'll look into removing this
from jtag.h and ft2232.c
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-develo
Oh and obviously if you have patches on this
to correct any mistakes I made then I'll be happy
to apply them. :-)
I just wanted to get something into the docs about
that we can not actually know what TRST and SRST
does and whether or not the interface supports it
is really a problem that OpenOCD
I see that I've jumped into a discussion where you are much
more up to date on the overall reset_config, how to write
quality documentation, etc. Below are some comments
where I had any.
Q: What's a "system configuration file"?
I can think of interface config files, target config files, board
con
On Saturday 30 May 2009, Øyvind Harboe wrote:
> Committed.
>
> Some more comments on reset_config and why it has the options
> it has.
>
>
> Index: C:/workspace/openocd/doc/openocd.texi
> ===
> --- C:/workspace/openocd/doc/openocd.t
I need to look into details, but I believe that this breaks
synchronous execution of JTAG calls (for hardware
implementations of JTAG FIFOs).
I believe this is what Dick was trying to point out, but I need
more time to look into this.
--
Øyvind Harboe
Embedded software and hardware consulting s
On Tue, May 26, 2009 at 12:21 AM, Magnus Lundin wrote:
> To move the discussion onto something that miqht require a bit o f real
> analysis:
>
> Why does some targets work better during "reset halt" when the
> TAP_RESET-> IR_SHIFT is B8(0011000,7) instead of B8(0011011,7) .
>
> And the hard
> You need to pass --enable-maintainer-mode to configure.
Why isn't enable-maintainer-mode the default?
I don't know what this option does really, but this should only be disabled
when making releases, right?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.
Committed.
Some more comments on reset_config and why it has the options
it has.
Index: C:/workspace/openocd/doc/openocd.texi
===
--- C:/workspace/openocd/doc/openocd.texi (revision 1946)
+++ C:/workspace/openocd/doc/openocd.t
This looks good to me. I'm not sure what a good long term solution
might be.
A requirement/goal of OpenOCD is that it should "just work"
with the default settings when using "monitor" commands w/GDB.
Really this warning is a reminder to OpenOCD developers to fix the code so
"monitor XXX" commands
On Fri, May 29, 2009 at 12:14 AM, David Brownell wrote:
> On Thursday 28 May 2009, Ųyvind Harboe wrote:
>> In the mists of time SRST & TRST probably had some
>> well defined function and meaning.
>
> I think they still *do* ... but it seems vendors
> have felt free to play with at least TAP resets
43 matches
Mail list logo
