OpenOCD - Open On-Chip Debugger / Mailing Lists
Thanks for helping keep SourceForge clean.
Screenshot instructions:
Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here &
(This may not be possible with some types of ads)
You seem to have CSS turned off.
Please don't fill out this field.
You seem to have CSS turned off.
Please don't fill out this field.
Briefly describe the problem (required):
Upload screenshot of ad (required):
, or drag & drop file here.
Please provide the ad click URL, if possible:
Mailing Lists
The Open On-Chip Debugger
Brought to you by:
openocd-devel
I'm currently testing the FTDI based variant of the xds100v2 driver with
a TMS570 target using these scripts:
When using the FTDI-based driver for an initial connnect (target powered
down), I cannot connect using the fdti/xds100v2 driver, the scan of the
JTAG chain fails:
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: tms570.jrc: IR saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
However, I can connect using the ft2232-based driver. After such an
initial connect, the FTDI-based driver also works flawlessly.
I attached the -d 3 debug output of the three tries:
1. FDTI driver fails initially
2. ft2232 driver, connects
3. FDTI driver connects as well
Any ideas?
Best regards,
On Fri, Nov 15, 2013 at 11:19 AM, Alex Züpke &alexander.zuepke@...&wrote:
& I'm currently testing the FTDI based variant of the xds100v2 driver with a
& TMS570 target using these scripts:
& When using the FTDI-based driver for an initial connnect (target powered
& down), I cannot connect using the fdti/xds100v2 driver, the scan of the
& JTAG chain fails:
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: tms570.jrc: IR saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
I get something similar when using adapters which doesn't have a well
defined pin state after power-up, such as the JTAGkey-Tiny. But if I'm not
mistaken, it only happens if I power up the adapter before the target
board. Or the other way around. I don't really remember. And I don't have
to use the ft2232 driver to fix it.
& However, I can connect using the ft2232-based driver. After such an
& initial connect, the FTDI-based driver also works flawlessly.
& I attached the -d 3 debug output of the three tries:
& 1. FDTI driver fails initially
& 2. ft2232 driver, connects
& 3. FDTI driver connects as well
& Any ideas?
Have you tried 1 followed by 3? I mean restarting with the FTDI driver
after the first failed attempt?
Hi Andreas,
Am 17.11., schrieb Andreas Fritiofson:
& On Fri, Nov 15, 2013 at 11:19 AM, Alex Züpke &alexander.zuepke@...
& &mailto:alexander.zuepke@...&& wrote:
I'm currently testing the FTDI based variant of the xds100v2 driver
with a TMS570 target using these scripts:
When using the FTDI-based driver for an initial connnect (target
powered down), I cannot connect using the fdti/xds100v2 driver, the
scan of the JTAG chain fails:
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: tms570.jrc: IR saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
& I get something similar when using adapters which doesn't have a well
& defined pin state after power-up, such as the JTAGkey-Tiny. But if I'm
& not mistaken, it only happens if I power up the adapter before the
& target board. Or the other way around. I don't really remember. And I
& don't have to use the ft2232 driver to fix it.
It happens regardless of the order I connect power or USB.
However, I can connect using the ft2232-based driver. After such an
initial connect, the FTDI-based driver also works flawlessly.
I attached the -d 3 debug output of the three tries:
1. FDTI driver fails initially
2. ft2232 driver, connects
3. FDTI driver connects as well
Any ideas?
& Have you tried 1 followed by 3? I mean restarting with the FTDI driver
& after the first failed attempt?
& /Andreas
Yes, the state remains "broken" until I have a successful connect using
the ft2232 driver.
help with this?
Be free, use free () software!
mailto:fercerpav@...
Am 18.01., schrieb Paul Fertser:
help with this?
It's getting better, but putting
ftdi_set_signal PWR_RST 1
at the end of my config file doesn't help.
I need to restart openocd to get a connection on 2nd try.
I'm using GIT Head and the stock tcl/target/ti_tms570.cfg, so I tried to
hook the FTDI-reset into JTAG's post-reset event (see attached patch)
and it works reliably, but I don't know if this is the right hook for that?
Thanks && best regards,
On Fri, Jan 24, 2014 at 3:27 PM, Alex Züpke &alexander.zuepke@...&wrote:
& Hi Paul,
& Am 18.01., schrieb Paul Fertser:
help with this?
& It's getting better, but putting
& ftdi_set_signal PWR_RST 1
& at the end of my config file doesn't help.
& I need to restart openocd to get a connection on 2nd try.
Actually, that won't work. The PWR_RST pin probably have to be toggled to
get the adapter to work at all. Then it must be done *before* init, but
then we do not have the ability to set the pin. Catch 22.
That's why we need to add (or find) a hook that's run after the adapter
driver is initialized but before the chain is examined.
& I'm using GIT Head and the stock tcl/target/ti_tms570.cfg, so I tried to
& hook the FTDI-reset into JTAG's post-reset event (see attached patch) and
& it works reliably, but I don't know if this is the right hook for that?
No, that's far too late unfortunately. Or does "works reliably" mean that
you get it working at the first attempt without having to restart?? That
would be odd.
Am 24.01., schrieb Andreas Fritiofson:
& On Fri, Jan 24, 2014 at 3:27 PM, Alex Züpke &alexander.zuepke@...
& &mailto:alexander.zuepke@...&& wrote:
Am 18.01., schrieb Paul Fertser:
help with this?
It's getting better, but putting
& ftdi_set_signal PWR_RST 1
at the end of my config file doesn't help.
I need to restart openocd to get a connection on 2nd try.
& Actually, that won't work. The PWR_RST pin probably have to be toggled
& to get the adapter to work at all. Then it must be done *before* init,
& but then we do not have the ability to set the pin. Catch 22.
& That's why we need to add (or find) a hook that's run after the adapter
& driver is initialized but before the chain is examined.
I'm using GIT Head and the stock tcl/target/ti_tms570.cfg, so I
tried to hook the FTDI-reset into JTAG's post-reset event (see
attached patch) and it works reliably, but I don't know if this is
the right hook for that?
& No, that's far too late unfortunately. Or does "works reliably" mean
& that you get it working at the first attempt without having to restart??
& That would be odd.
Yes, I get a connection with the patch from the previous email. I tried
it about 20 times so far, with plugging in USB first, then power, and
vice versa.
Best regards,
On Fri, Jan 24, 2014 at 03:27:39PM +0100, Alex Züpke wrote:
& Am 18.01., schrieb Paul Fertser:
help with this?
& It's getting better, but putting
& ftdi_set_signal PWR_RST 1
& at the end of my config file doesn't help.
& I need to restart openocd to get a connection on 2nd try.
What if you add "; jtag arp_init" to that (that might be silly but
might be not, I can't really tell).
Can please you also show -d3 for this attempt (if it doesn't work)?
Be free, use free () software!
mailto:fercerpav@...
Am 24.01., schrieb Paul Fertser:
& On Fri, Jan 24, 2014 at 03:27:39PM +0100, Alex Züpke wrote:
&& Am 18.01., schrieb Paul Fertser:
help with this?
&& It's getting better, but putting
&& ftdi_set_signal PWR_RST 1
&& at the end of my config file doesn't help.
&& I need to restart openocd to get a connection on 2nd try.
& What if you add "; jtag arp_init" to that (that might be silly but
& might be not, I can't really tell).
& Can please you also show -d3 for this attempt (if it doesn't work)?
Adding `` ;jtag arp_init ?? works as well (I reverted my previous change
to the post-reset hook before testing).
Any more info required?
Hi Alex :)
On Mon, Jan 27, 2014 at 01:07:21PM +0100, Alex Züpke wrote:
& Adding `` ;jtag arp_init ?? works as well (I reverted my previous change
& to the post-reset hook before testing).
& Any more info required?
Thank you for the testing. I think this xds adapter is the last one
preventing full deprecation and elimination of the old ft2232 driver
I've added the arp_init command to
(pushed rev.2), so if you can take a look at the exact patch again and
tell if it's now fully solving the issue in its current form, please
do, I can add a comment to Gerrit for you :)
Be free, use free () software!
mailto:fercerpav@...
Am 27.01., schrieb Paul Fertser:
& Hi Alex :)
& On Mon, Jan 27, 2014 at 01:07:21PM +0100, Alex Züpke wrote:
&& Adding `` ;jtag arp_init ?? works as well (I reverted my previous change
&& to the post-reset hook before testing).
&& Any more info required?
& Thank you for the testing. I think this xds adapter is the last one
& preventing full deprecation and elimination of the old ft2232 driver
& I've added the arp_init command to
& (pushed rev.2), so if you can take a look at the exact patch again and
& tell if it's now fully solving the issue in its current form, please
& do, I can add a comment to Gerrit for you :)
Tested your proposed patch -& works fine for me.
Thank and best regards,
Dipl.-Ing. (FH) Alexander Züpke
Fachbereich DCSM/Informatik
Hochschule RheinMain
Unter den Eichen 5, 65195 Wiesbaden, Germany
On Mon, Jan 27, 2014 at 1:31 PM, Alex Züpke &alexander.zuepke@...&wrote:
& Hi Paul,
& Am 27.01., schrieb Paul Fertser:
& & Hi Alex :)
& & On Mon, Jan 27, 2014 at 01:07:21PM +0100, Alex Züpke wrote:
& && Adding `` ;jtag arp_init ?? works as well (I reverted my previous change
& && to the post-reset hook before testing).
& && Any more info required?
& & Thank you for the testing. I think this xds adapter is the last one
& & preventing full deprecation and elimination of the old ft2232 driver
& & I've added the arp_init command to
& & (pushed rev.2), so if you can take a look at the exact patch again and
& & tell if it's now fully solving the issue in its current form, please
& & do, I can add a comment to Gerrit for you :)
& Tested your proposed patch -& works fine for me.
I'm just wondering if you considered/tried doing ftdi_set_signal PWR_RST 1
(plus maybe jtag arp_init) in the examine-start handler, which would be the
closest available hook? Unfortunately it can't be added to the interface
config file as all the hooks are target specific and at that point there's
no target defined.
If this works (with some inconvenience) I guess it's OK. Long term I think
it would be good having an optional Tcl proc defined in the interface
config that is called by the ftdi driver post-init. Future adapters may
need similar tweaks. Shouldn't be too hard to add but I'm not fluent in the
JimTcl integration.01天天酷跑叉叉助手安卓版(天天酷跑辅助) 2.5.8 最新下载01
休闲益智 / 2.0M02天天酷跑明哥破解版 v1.0.24 最新自动版本02
休闲益智 / 65.1M03捕鱼达人3d版 v1.0.2 安卓无限金币版03
休闲益智 / 35.5M04小鸟爆破免费版 v2.2.6 安卓破解版04
休闲益智 / 39.2M05三国Kill v3.2.1 官网安卓版05
休闲益智 / 50.4M06我的世界手机版下载 v1.1.1.1
休闲益智 / 12.4M07天天爱闯关 2.3.0 内购破解版07
休闲益智 / 9M08飞鸟战争游戏 v1.0 安卓版08
休闲益智 / 951KB09天天酷跑炫飞版1.0.13.0 徐哥破解0711 最新版09
休闲益智 / 64.9M10爱丽丝快跑 v1.6.0 安卓破解版10
休闲益智 / 33.5M
01天天酷跑叉叉助手安卓版(天天酷跑辅助) 2.5.8 最新下载01
休闲益智 / 2.0M02天天酷跑明哥破解版 v1.0.24 最新自动版本02
休闲益智 / 65.1M03捕鱼达人3d版 v1.0.2 安卓无限金币版03
休闲益智 / 35.5M04小鸟爆破免费版 v2.2.6 安卓破解版04
休闲益智 / 39.2M05三国Kill v3.2.1 官网安卓版05
休闲益智 / 50.4M06爱丽丝快跑 v1.6.0 安卓破解版06
休闲益智 / 33.5M07我的世界手机版下载 v1.1.1.1
休闲益智 / 12.4M08乐动达人2012安卓版 V1.0.9 官方版08
休闲益智 / 37M09天天爱闯关 2.3.0 内购破解版09
休闲益智 / 9M10捕鱼达人2中文版下载 v1.2.9 破解版10
休闲益智 / 36M
连筹码 Chip Chain v1.1.14A 安卓版
共0人评分 | 共0人评论
连筹码Chip Chain是一款轻松上手的免费休闲游戏，当你有3个或者更多相同相邻的筹码时你就配对成功。并且你会获得一个更高值的筹码。匹配链越长就能获得巨额奖赏。使用Power-Up卡片来获得配对链组合，延伸配对链，以及最大限度提升分数。【连筹码基本介绍】连筹码安卓版 Chip Chain：玩这个游戏还是跟大家介绍下有限规则吧。整个游戏的界面有些类似象棋，筹码会被放置在界面上的格子里，并按照牌面上的阿拉伯数字划分。游戏的核心自然就是消除，相邻的三个或以上同样数字的筹码可以进行消除。【连筹码更新日志】- Screen won't turn off while planning your next move. - Shop Update: Watch a Video to earn some free gems! - Google Leaderboards and Achievements
软件名称：连筹码 Chip Chain v1.1.14A 安卓版
类型：休闲益智
语言：简体中文
更新时间：13-10-24
共0人参与,0条评论（您的评论需要经过审核才能显示）
所有软件均来自网络如有版权问题请联系我们 - 浙公网安备 47号 - 浙ICP备号
Copyright & 2004- online services. All rights reserved.
请简要描述您遇到的错误，我们将尽快予以修订}