In this patch, parameter to jtag_add_reset is error.
Shouldn't it be:
case XTRST_ON:
jtag_add_reset(1, 0);
break;
case XTRST_OFF:
jtag_add_reset(0, 0);
break;
2009-01-22
Best Regards, Simon Qian
SimonQian(simonq...@simonqian.com) www.SimonQian.com
发件人： Dick Hollenbeck
发送时间： 2009-0
I've created a spec file that can be used to build Fedora 10, or
possibly other OS's, binary and source RPMs. I've attached the spec
file. I also wanted to see if somebody was already responsible for this
particular package. I can build it and send it to Rick Altherr if no
one is currently h
Hmm, guess I should have read the whole thread before I posted. ;-)
I see the openocd.udev patch is worrying about permissions for the USB
devices. For my FT2232 based OpenOCD USB device the tty devices are
also important.
This becomes a real headache when you have multiple ttyUSB devices
(OpenOC
how about this one for the OpenOCD USB from Embedded-Projects.net:
SUBSYSTEMS=="usb", ATTRS{product}=="Dual RS232", ATTRS{idProduct}=="6010",
ATTRS{idVendor}=="0403", KERNEL=="ttyUSB*",
SYMLINK+="openocd$attr{bInterfaceNumber}"
creates /dev/openocd00 and /dev/openocd01 for the two serial i
On Jan 21, 2009, at 2:27 PM, Dimitar Dimitrov wrote:
Hi,
I built openocd-0.1 straight out of SVN branch openocd-0.1. I used
cygwin to
compile a mingw executable and issued "make install" to create the
openocd
install tree. Openocd.exe however was not able to find its script
library
direc
Hi,
I built openocd-0.1 straight out of SVN branch openocd-0.1. I used cygwin to
compile a mingw executable and issued "make install" to create the openocd
install tree. Openocd.exe however was not able to find its script library
directories when run from the windows (NOT cygwin) CMD prompt. I'
Sorry, this one is better.
Index: src/jtag/bitbang.c
===
--- src/jtag/bitbang.c (revision 1355)
+++ src/jtag/bitbang.c (working copy)
@@ -38,6 +38,14 @@
#include
+/**
+ * Function bitbang_stableclocks
+ * issues a number of clo
Please look over this patch and commit if acceptable.
It moves the test for a stable state into the jtag_add_clocks() call and
out of each driver , introducing ERROR_JTAG_NOT_STABLE_STATE to report
this problem.
It recognizes that a TMS=1 is required for staying in the stable state
TAP_RES
On Wed, Jan 21, 2009 at 8:56 PM, Sergey Lapin wrote:
> On Wed, Jan 21, 2009 at 8:26 PM, Alan Carvalho de Assis
> wrote:
>> Hi Sergey,
>>
>> On Wed, Jan 21, 2009 at 4:30 PM, Sergey Lapin wrote:
>>> Hi, all!
>>>
>>> I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant
>>> communic
> We can add a "quiet" argument to the command for you. I personally do
> not want to have to turn on debug logging to get the output that is
> currently in there, because then the logging format changes and it is
> intermingled with other output. I personally do not mind that it scrolls
> off the
On Wed, Jan 21, 2009 at 8:26 PM, Alan Carvalho de Assis
wrote:
> Hi Sergey,
>
> On Wed, Jan 21, 2009 at 4:30 PM, Sergey Lapin wrote:
>> Hi, all!
>>
>> I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant
>> communication chip. Chip is quite new, documentation is in weird state
>>
Hi Sergey,
On Wed, Jan 21, 2009 at 4:30 PM, Sergey Lapin wrote:
> Hi, all!
>
> I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant
> communication chip. Chip is quite new, documentation is in weird state
> and is not full, but core and basic peripherals like SPI are
> documented
SimonQian wrote:
> In OpenoCD, we can handle TRST ON/OFF/ABSENT. But we can not
> handle TRST Z, not all the jtag tool can support this. So should it be
> interpreted as TRST OFF?
> My SVF code doesn't handle TRST Z, I'll provide a patch for TRST
> command and using jtag_add_clocks.
> According to
Hi, all!
I write support for mc13224 - arm7tdmi-based ieee8021.15.4 -compliant
communication chip. Chip is quite new, documentation is in weird state
and is not full, but core and basic peripherals like SPI are
documented normally. I already managed to make core work,
but I can't manage it to rese
In OpenoCD, we can handle TRST ON/OFF/ABSENT. But we can not
handle TRST Z, not all the jtag tool can support this. So should it be
interpreted as TRST OFF?
My SVF code doesn't handle TRST Z, I'll provide a patch for TRST
command and using jtag_add_clocks.
According to the SVF specification, TR
This patch adds xsvf_tools support for parsing the SVF TRST command.
The corresponding patch to xsvf.c is still needed, pending agreement on
direction.In its simplest form, the xsvf.c change could merely skip
the new XSVF opcode. But if the cable API supports it, we can do better.
The v
SimonQian wrote:
> Hi,
> When try to convert svf file to xsvf, i got this:
> --
> H:\MyProject\Versaloon\test>python --version
> Python 3.0
> H:\MyProject\Versaloon\test>python svf2xsvf.py temp.svf temp.xsvf
> Error in file 'temp.svf' at line 29 near
Thanks to Dick, I tried the xsvf player, and succeeded in adding support to
JTAG_STABLECLOCKS.
It works on my EPM240T100 demo board.
Attachment is the patch for the JTAG_STABLECLOCKS support for vsllink.
Suggestion to xsvf player.
No need to print message if not in debug mode.
My xsvf file contai
Hi,
When try to convert svf file to xsvf, i got this:
--
H:\MyProject\Versaloon\test>python --version
Python 3.0
H:\MyProject\Versaloon\test>python svf2xsvf.py temp.svf temp.xsvf
Error in file 'temp.svf' at line 29 near token 'TRST'
Unknown token '
19 matches
Mail list logo
