x__ has quit [Read error: Connection reset by peer]
x__ has joined #openocd
Hawk777 has joined #openocd
tsal has quit [Ping timeout: 256 seconds]
tsal has joined #openocd
dliviu has quit [Ping timeout: 252 seconds]
dliviu has joined #openocd
x__ has quit [Ping timeout: 255 seconds]
x__ has joined #openocd
x__ has quit [Ping timeout: 255 seconds]
PaulFertser has joined #openocd
nerozero has joined #openocd
renrelkha has quit [Quit: bye]
renrelkha has joined #openocd
Haohmaru has joined #openocd
Hawk777 has quit [Quit: Leaving.]
x__ has joined #openocd
x__ has quit [Ping timeout: 252 seconds]
x__ has joined #openocd
PaulFertser has quit [Read error: Connection reset by peer]
PaulFertser has joined #openocd
urja has quit [Ping timeout: 260 seconds]
urja has joined #openocd
ttmrichter has quit [Ping timeout: 260 seconds]
ttmrichter has joined #openocd
PaulFertser has quit [Read error: Connection reset by peer]
PaulFertser has joined #openocd
PsySc0rpi0n has quit [Ping timeout: 252 seconds]
PsySc0rpi0n has joined #openocd
wingsorc has quit [Ping timeout: 252 seconds]
x__ has quit [Ping timeout: 246 seconds]
x__ has joined #openocd
nerozero has quit [Ping timeout: 268 seconds]
<maribu[m]>
Sorry for nagging again. I'm still fighting with the TI CC2650 with the integrated ICEPick JTAG Router. I cleaned up the icepick.cfg to follow the sequence given in the datasheet to the latter. However, the icepick_c_tapenable procedure is for some reason called twice. It seems that the event tap-enable is for some reason triggered twice. Is this expected behavior?
<maribu[m]>
Also: I fail to find a good documentation regarding the events that are generated by OpenOCD. E.g. as someone new to OpenOCD it is not obvious to me what the actual high level flow is.
PsySc0rpi0n has quit [Ping timeout: 246 seconds]
PaulFertser has quit [Read error: Connection reset by peer]
<maribu[m]>
I am currently working around this by using the ICEPick warm reset feature and not asserting srst at all. In the first tap-enable I put the device in the wait-in-reset state, in the second I am releasing it. I think with that OpenOCD is reliably attaching. However, flashing still fails. This may actually be a different issue.
<maribu[m]>
At least I seem to have no issue with connecting via GDB
PaulFertser has quit [Read error: Connection reset by peer]
x__ has quit [Ping timeout: 252 seconds]
x__ has joined #openocd
<maribu[m]>
Note: flash verify_image works reliably every time (after having written the image with JLinkExe). Writing the image with OpenOCD fails reliably - except for the very first time when the MCU was still in factory state. It usually take a second or two before I see any output. Then I mostly get Error: Invalid ACK (0) in DAP response.