<Haohmaru>
that most likely is an electrical problem, right?
<cambrian_invader>
I'm having trouble getting a ft2232 board to work
<cambrian_invader>
when I probe, I get "JTAG scan chain interrogation failed: all ones" so something is wrong
<cambrian_invader>
if I create GPIOs for all the pins like for {set i 0} {$i < 16} {incr i} { ftdi layout_signal GPIO$i -data [expr {1 << $i}] }
<cambrian_invader>
I can toggle them like while {1} {for {set i 0} {$i < 16} {incr i} {ftdi set_signal GPIO$i 1}; sleep 1000; for {set i 0} {$i < 16} {incr i} {ftdi set_signal GPIO$i 0}; sleep 1000}
<cambrian_invader>
but I don't see TCK move at all
<cambrian_invader>
err
<cambrian_invader>
I see TCK move when I toggle it as a GPIO
<cambrian_invader>
but not when probing
<cambrian_invader>
hm, actually on closer inspection it is toggling both times
<cambrian_invader>
ok, fixed it by having TCK and TDI default to 0 and TMS default to 1
gpol has quit [Ping timeout: 240 seconds]
gpol has joined #openocd
<cambrian_invader>
I feel like that sort of thing should be documented...
<PaulFertser>
cambrian_invader: hi
<cambrian_invader>
hi
<PaulFertser>
cambrian_invader: basically, the lower half of the byte for ftdi init is the same in all configs as the signals are defined by hardware.
peeps[work] has joined #openocd
Hawk777 has joined #openocd
Haohmaru has quit [Ping timeout: 248 seconds]
peeps[work] has quit [Remote host closed the connection]
peeps[work] has joined #openocd
peeps[work] has quit [Remote host closed the connection]
peeps[work] has joined #openocd
nerozero has quit [Ping timeout: 240 seconds]
uartist has quit [Quit: Ping timeout (120 seconds)]
uartist has joined #openocd
piie has quit [Quit: WeeChat 3.1]
weepiie has joined #openocd
tlwoerner has quit [Quit: Leaving]
tlwoerner has joined #openocd
bluemeanie23 has joined #openocd
bluemeanie23 has quit [Remote host closed the connection]