On Fri, Mar 20, 2009 at 05:54:20PM +0100, Uwe Hermann wrote:
> > Found a couple of typo's in the cfg - should be fixed in svn now.
> 
> Thanks, works a bit better now. However, I needed the following patch to
> make the device detectable:
> 
> Index: src/target/interface/str9-comstick.cfg
> ===================================================================
> --- src/target/interface/str9-comstick.cfg      (revision 1424)
> +++ src/target/interface/str9-comstick.cfg      (working copy)
> @@ -1,3 +1,4 @@
>  interface ft2232
>  ft2232_device_desc "STR9-comStick A"
>  ft2232_layout comstick
> +ft2232_vid_pid 0x0640 0x002c

Quick update: the attached patch fixes all STR9-comstick issues so far
for me. On my STR9-comstick the _BSTAPID is 0x2457f041 (contrary to
0x1457f041 which is indeed correct as per manual). Maybe there are
multiple versions of the STR9-comstick? My device says STR912CS-A2 on
the back. The chip marking is STR912FA W44X6 HPACD VG KOR HP 717.


Uwe.
-- 
http://www.hermann-uwe.de  | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/target/str9comstick.cfg
===================================================================
--- src/target/target/str9comstick.cfg	(Revision 1424)
+++ src/target/target/str9comstick.cfg	(Arbeitskopie)
@@ -39,7 +39,7 @@
 if { [info exists BSTAPID ] } {
    set _BSTAPID $BSTAPID
 } else {
-   set _BSTAPID 0x1457f041
+   set _BSTAPID 0x2457f041
 }
 jtag newtap $_CHIPNAME bs    -irlen 5 -ircapture 0x1 -irmask 0x1 -expected-id $_BSTAPID
 
Index: src/target/interface/str9-comstick.cfg
===================================================================
--- src/target/interface/str9-comstick.cfg	(Revision 1424)
+++ src/target/interface/str9-comstick.cfg	(Arbeitskopie)
@@ -1,3 +1,4 @@
 interface ft2232
 ft2232_device_desc "STR9-comStick A"
 ft2232_layout comstick
+ft2232_vid_pid 0x0640 0x002c
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to