**** BEGIN LOGGING AT Tue Dec 29 02:59:57 2009
Dec 29 11:19:37 <Spida> anybody at 26c3?
Dec 29 11:37:54 <kay2> hi
Dec 29 11:38:05 <kay2> has anyone successfully jtag'ed an arm926ejs ?
Dec 29 11:39:57 <kay2> I wonder if more pins than TRST/TMS/TDI/TDO/TCK are needed
Dec 29 11:40:08 <kay2> because i can't get the ID from it
Dec 29 13:00:40 <Weaselweb> kay2: yes, i used it in a at91sam9g20
Dec 29 13:01:19 <Weaselweb> I don't think you need more pins than mentioned
Dec 29 13:35:30 <kay2> Weaselweb: so dont nead rtck ?
Dec 29 13:36:03 <kay2> also how do you tell openocd if it's a TRST or a nTRST ?
Dec 29 13:36:25 <Weaselweb> afaik rtck is only needed, if you do adaptive clocking
Dec 29 13:36:37 <kay2> for some reason, i get Error: JTAG scan chain interrogation failed: all ones
Dec 29 13:36:50 <Weaselweb> ah, that seems like you jtag_speed is too fast
Dec 29 13:37:05 <kay2> but when I shortcut TDI and TDO to test the ft2232, it detects 0s
Dec 29 13:37:07 <Weaselweb> which arm do you use?
Dec 29 13:37:13 <kay2> Weaselweb: any way to reduce this speed ?
Dec 29 13:37:32 <Weaselweb> the config file you use with openocd
Dec 29 13:38:03 <kay2> interface ft2232
Dec 29 13:38:03 <kay2> ft2232_device_desc "USB <-> Serial Cable A"
Dec 29 13:38:03 <kay2> ft2232_layout oocdlink
Dec 29 13:38:03 <kay2> ft2232_vid_pid 0x0403 0x6010
Dec 29 13:39:37 <Weaselweb> you can base your config file from some config files from $(PREFIX)/share/openocd/scripts/board
Dec 29 13:40:14 <kay2> config file for the ft2232 ? or for the target ?
Dec 29 13:40:22 <Weaselweb> target
Dec 29 13:46:22 <kay2> I set it at 1khz
Dec 29 13:46:24 <kay2> didnt change much
**** ENDING LOGGING AT Wed Dec 30 02:59:57 2009