<Guest94>
I got it working. Noticed something weird happened to the J-Trace and I reinstalled the drivers. Got it talking through telenet now. Appreciate you all throwing out suggestions.
tsal has quit [Ping timeout: 256 seconds]
tsal has joined #openocd
thinkfat has quit [Ping timeout: 250 seconds]
thinkfat has joined #openocd
emeb has left #openocd [#openocd]
Guest94 has quit [Ping timeout: 256 seconds]
Hawk777 has joined #openocd
jancoow has joined #openocd
nerozero has joined #openocd
michalkotyla has quit [Ping timeout: 256 seconds]
michalkotyla has joined #openocd
indy has quit [Ping timeout: 240 seconds]
indy has joined #openocd
michalkotyla has quit [Ping timeout: 268 seconds]
michalkotyla has joined #openocd
Haohmaru has joined #openocd
* karlp
cheers
Hawk777 has quit [Quit: Leaving.]
<Haohmaru>
but it's too early for alcohol
<karlp>
was cheering for something that happened overnight in the logs :)
<karlp>
but never too early or late for anything?
* Haohmaru
was kidding
<PaulFertser>
Guess WinUSB wasn't installed for that jtrace device. But it's strange libjaylink was just hanging.
Pokey is now known as ahorner
ahorner is now known as Pokey
sbach has quit [Read error: Connection reset by peer]
sbach has joined #openocd
wingsorc__ has joined #openocd
wingsorc has quit [Ping timeout: 252 seconds]
Bertl_oO is now known as Bertl
urja has quit [Quit: WeeChat 3.3]
urja has joined #openocd
v0|d has quit [Ping timeout: 260 seconds]
michalkotyla has quit [Ping timeout: 256 seconds]
michalkotyla has joined #openocd
michalkotyla has quit [Ping timeout: 240 seconds]
michalkotyla has joined #openocd
michalkotyla_ has joined #openocd
michalkotyla has quit [Ping timeout: 268 seconds]
Bertl is now known as Bertl_oO
Guest4423 has joined #openocd
gnom has quit [Ping timeout: 260 seconds]
Guest4423 has quit [Quit: Client closed]
gnom has joined #openocd
gnom has quit [Ping timeout: 240 seconds]
gnom has joined #openocd
Haohmaru has quit []
fenugrec has joined #openocd
<fenugrec>
Hi, I'm debugging a stm32 with a jlink (well, the STlink reflashed with jlink firmware), openocd and gdb. I find when I detach/quit from gdb, the target doesn't continue and becomes unresponsive. Is there a way to continue-on-detach ?
<PaulFertser>
Hm, it's not supposed to continue by default so that's expected.
<PaulFertser>
You can define gdb-detach event to do "resume" if you desire that.
<PaulFertser>
fenugrec: ^
<fenugrec>
PaulFertser, aah thanks. Will check
<fenugrec>
PaulFertser, note, gdb's builtin help gives this for 'detach: Detach a process [...] continues its execution". So it's oocd that interprets detach differently ? trying to imagine the use case for why this would be the desirable default behaviour, contrary to what I'm used to with gdb
tlwoerner has quit [Ping timeout: 268 seconds]
tlwoerner has joined #openocd
<PaulFertser>
fenugrec: I remember I had to restart GDB sometimes because of its internal bugs. It would be not cool if the target would get to run while I'm still willing to inspect some specific state.
nerozero has quit [Ping timeout: 240 seconds]
<fenugrec>
fair enough. I eventually found the right combination of "$_TARGETNAME configure -event gdb-detach {resume}"
<fenugrec>
wish I had bothered to ask sooner, it's been annoying me for a long time
c4017w has quit [Quit: Leaving]
c4017w has joined #openocd
zjason` has joined #openocd
zjason has quit [Ping timeout: 268 seconds]
Guest97 has joined #openocd
<Guest97>
hello
<Guest97>
how i can turn the 5V supply for jlink segger on?
<zapb_>
Guest97, "jlink targetpower on"
<Guest97>
thanks, i forgot it ever xD
<PaulFertser>
For that you always have the official manual.
<Guest97>
yes i have saved it now in my notes
<Guest97>
and nice that openocd supports also buspirate, this is such a strong circuit board for analyzing signals
<Guest97>
-also+so
<Guest97>
ehh sry, the also was correct, I keep getting this mixed up