Spen wrote:
> Hi,
>
> I think its about time openocd made a release 1.0.
> I propose we create a openocd_rel_1_0 branch that will be frozen (except for
> major bugs) after a month we make a release.
>
> Any objections/comments?
It would be good to gather a list of devices which will be tested /
rick> Do they need to specify the chip and tap as two separate arguments?
duane> Good question. What about this: Put a "dot" between the two -
it is sort of like TK path names.
duane> It would become:"--chain-position CHIP.TAP"
rick> How about we change it to --jtag-tap CHIP.TAP? --c
On Nov 22, 2008, at 4:14 PM, Duane Ellis wrote:
duane> # Example: Declare a chip, for example some Xilinx FPGA
duane> jtag newtap xilinx -chip xilinx -ir-length 6 -ir-
capture -ir-mask
rick> [I don't like chip]
duane> I prefer "chip" for one reason. Physically that
duane> # Example: Declare a chip, for example some Xilinx FPGA
duane> jtag newtap xilinx -chip xilinx -ir-length 6 -ir-capture
-ir-mask
rick> [I don't like chip]
duane> I prefer "chip" for one reason. Physically that is what is
present on the board.
rick> That's a pre
On Nov 22, 2008, at 1:09 PM, Duane Ellis wrote:
==
duane> # Example: Declare a chip, for example some Xilinx FPGA
duane> jtag newtap xilinx -chip xilinx -ir-length 6 -ir-
capture -ir-mask
rick> [I don't like chip]
I prefer "chip" for one reason. Physical
==
duane> # Example: Declare a chip, for example some Xilinx FPGA
duane> jtag newtap xilinx -chip xilinx -ir-length 6 -ir-capture
-ir-mask
rick> [I don't like chip]
I prefer "chip" for one reason. Physically that is what is present on
the board.
However, ba
On Nov 22, 2008, at 3:54 AM, Spen wrote:
Hi,
I think its about time openocd made a release 1.0.
I propose we create a openocd_rel_1_0 branch that will be frozen
(except for
major bugs) after a month we make a release.
Any objections/comments?
release will be for both x86 win32 (mingw) and
On Nov 22, 2008, at 9:36 AM, Duane Ellis wrote:
# Example: Declare a chip, for example some Xilinx FPGA
jtag newtap xilinx -chip xilinx -ir-length 6 -ir-capture -
ir-mask
This looks fine other than my personal preference to not use "chip"
here. In theory you could have a
All -
I'm doing some work that with a new "jtag" tcl command to help support
beagle board.
I need to deal a little bit with how taps are ordered. This also effects
the target command stuff some what.
I have a general idea sort of worked out - and need some input/feed back
if the scheme des
Rick Altherr wrote:
>> I start OpenOCD with the command:
>>
>> openocd -f interface/flyswatter.cfg -f target/hammer.cfg -c "init" -c
>> "reset"
>>
>
> Hurray! Someone uses the built-in configs.
By the way, there appears to be a bug/typo inside the hammer.cfg file.
Instead of "arm7_9 fast_memory
Carlos,
you need to issue an erase command first before writing to the flash.
the current svn trunk is not officially supported by TinCanTools. the latest
officially supported release is available at:
http://www.elinux.org/Hammer_Board_Software_System#OpenOCD
dave
--- On Fri, 11/21/08, C
duane> [long description of how to do this]
kees> The kind of changes you are talking about seams very far away from
anything I could help with.
That's ok - feed back & testing is also very helpful.
-Duane.
___
Openocd-development mailing list
Ope
> spen> release will be for both x86 win32 (mingw) and linux
>
> I would add a Cygwin build.
>
> Only because - often some development environments are
> _cygwin_ in addition to mingw
>
Fair enough - easily done.
Spen
___
Openocd-development mailin
spen> release will be for both x86 win32 (mingw) and linux
I would add a Cygwin build.
Only because - often some development environments are _cygwin_ in
addition to mingw
-Duane.
___
Openocd-development mailing list
Openocd-development@lists.berlios.
Hi,
I think its about time openocd made a release 1.0.
I propose we create a openocd_rel_1_0 branch that will be frozen (except for
major bugs) after a month we make a release.
Any objections/comments?
release will be for both x86 win32 (mingw) and linux
suggested build options will be (win32):
15 matches
Mail list logo
