Rolf Meeser pisze:
> How would you write a board file for a board with two LPC2103 in the
> chain? A simple source [find target/lpc2103.cfg] source [find
> target/lpc2103.cfg] wouldn't work because it would try to declare two
> targets with the same name (lpc2103.cpu).
>
> Previously it was possib
Hi Freddie,
I didn't find the time yet to write a few comments. But here they are:
They are all meant to be constructive and friendly! :-)
How would you write a board file for a board with two LPC2103 in the chain?
A simple
source [find target/lpc2103.cfg]
source [find target/lpc2103.cfg]
wouldn
Tittle: Fix for STR9 Hitex comStick(REV A2) evaluation board JTAG lockup.
under openocd, and FTDI libftd2xx V 4.16(maybe other versions to)
The Symptom:
Comstick on board JTAG interface fail's, requiring the board to be
unplugged and reinserted, to gain control. (even this will fa
Be it your way...
4\/3!!
Index: tcl/target/lpc2103.cfg
===
--- tcl/target/lpc2103.cfg (revision 2744)
+++ tcl/target/lpc2103.cfg (working copy)
@@ -1,38 +1,19 @@
-# NXP LPC2103 ARM7TDMI-S with 32kB Flash and 8kB SRAM, clock
David Brownell pisze:
> Not sure; did it fail the same way with that set in
> an "openocd.cfg" file?
>
> There's a bunch of code that works today and uses
> variables set in previous files. If you're doing
> that the same way that code does, I'd expect it
> to "just work".
>
> If it doesn't ...
On Sun, Sep 27, 2009 at 7:28 PM, David Brownell wrote:
> On Sunday 27 September 2009, Ųyvind Harboe wrote:
>> I can't find the place in the ft2232 code where the state is set
>> to TAP_RESET when srst pulls trst under a reset...
>
> I'd have expected that to be in common jtag/core.c code ...
>
>
>
On Sunday 27 September 2009, Freddie Chopin wrote:
> David Brownell pisze:
> >> -f interface/sth.cfg -f target/sth.cfg
> >
> > That's the same as a "wrapper script".
> >
> > Just stick "-c set CRYSTAL_SPEED 3579545" in there, same effect.
>
> I tried the same yesterday (-c "set CRYSTAL_FREQ xxx"
On Sunday 27 September 2009, Øyvind Harboe wrote:
> I can't find the place in the ft2232 code where the state is set
> to TAP_RESET when srst pulls trst under a reset...
I'd have expected that to be in common jtag/core.c code ...
> How does the attached patch look?
>
> rlink.c, bitbang.c, bitq
On Sunday 27 September 2009, Øyvind Harboe wrote:
> I think we should list the broken drivers in TODO and
> leave it at that.
Done
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openo
I can't find the place in the ft2232 code where the state is set
to TAP_RESET when srst pulls trst under a reset...
How does the attached patch look?
rlink.c, bitbang.c, bitq.c and zy1000 all have this code
path right.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cor
> Fixing around a dozen driver seems messy, but perhaps
> unavoidable. Do you think I should check in $SUBJECT
> and have us seek patches and testing for all of the
> other drivers?
I think we should list the broken drivers in TODO and
leave it at that.
There are lots of known bugs/problems in O
On Sunday 27 September 2009, Øyvind Harboe wrote:
> > Comments?
>
> TAP_RESET is special. Navigating to this state
> can only be done via jtag_add_tlr().
Or equivalently jtag_add_statemove(TAP_RESET), which
calls jtag_add_tlr() in turn.
There's bit of a maze at the intermediate levels, which
to
Has anyone looked at adding coredump file support
to OpenOCD?
I don't know what the format is, but core dump files
could be quite small for many targets(a few megabytes
at most).
If OpenOCD grows coredump support and the
coredump files are small, then perhaps OpenOCD
could be modified to save off
> Comments?
TAP_RESET is special. Navigating to this state
can only be done via jtag_add_tlr(). No assumptions
should be made about the JTAG TAP state as
jtag_add_tlr() supports being invoked when the state has
been modified by some external event.
--
Øyvind Harboe
http://www.zylin.com/zy1000.htm
David Brownell wrote:
> So this one's nasty, because of the root cause: OpenOCD init
> state is incorrect, so "shortest path" through the JTAG state
> machine wrongly short-circuits. Fix is either:
>
> (a) update every interface driver (!) like this
> (b) or else find some core fix
>
> Expedi
David Brownell pisze:
>> -f interface/sth.cfg -f target/sth.cfg
>
> That's the same as a "wrapper script".
>
> Just stick "-c set CRYSTAL_SPEED 3579545" in there, same effect.
I tried the same yesterday (-c "set CRYSTAL_FREQ xxx") but... it doesn't
work...
> c:\>openocd -c "set CRYSTAL_FREQ 12
16 matches
Mail list logo
