NishanthMenon changed the topic of #openocd to: this is the place to discuss all things OpenOCD | Logs: https://libera.irclog.whitequark.org/openocd/
akaWolf has joined #openocd
jancoow has joined #openocd
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 246 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 260 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 246 seconds]
Haohmaru has joined #openocd
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 248 seconds]
akaWolf has joined #openocd
Guest2997 has joined #openocd
akaWolf has quit [Ping timeout: 268 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 255 seconds]
akaWolf has joined #openocd
Guest2997 has quit [Quit: Client closed]
merethan_ has joined #openocd
akaWolf has quit [Ping timeout: 268 seconds]
akaWolf has joined #openocd
akaWolf has quit [Ping timeout: 252 seconds]
akaWolf has joined #openocd
PsySc0rpi0n has quit [Quit: Leaving]
knicklicht has joined #openocd
Hawk777 has joined #openocd
akaWolf has quit [Ping timeout: 268 seconds]
knicklicht has quit [Quit: Client closed]
Haohmaru has quit []
merethan_ has quit [Ping timeout: 248 seconds]
Mis012[m] has joined #openocd
<Mis012[m]> test
<Mis012[m]> yay
<PaulFertser> Mis012[m]: hi
<Mis012[m]> hello :)
<Mis012[m]> does anyone here remember that 2015 conversation? :P
<Mis012[m]> msm8998 here, `"-ignore-syspwrupack"` is definitely helpful, but if I try to define a target I get a nice little infinite loop
<PaulFertser> Mis012[m]: hah, 2015
<PaulFertser> Mis012[m]: you know where it loops?
<Mis012[m]> it does this
<PaulFertser> Mis012[m]: I think WAIT means the target tells you it can't yet provide what you ask for
<Mis012[m]> this is without -d4
<Mis012[m]> -d4 spams the whole terminal
<PaulFertser> WAIT is the target noot read for whatever reason
<PaulFertser> You can read more about it in ARM ADIv5 document.
<PaulFertser> But it essentially means "can't do what you ask for now, try again later".
<PaulFertser> iirc
<Mis012[m]> if I kill -9 openocd (it doesn't exit otherwise) and try again, it doesn't even get this far until I reboot the whole device
<Mis012[m]> the -d4 spam looks similar
<Mis012[m]> not sure which one this is even, obviously the context was scrolled away
<PaulFertser> Looks like this msm is nasty
<PaulFertser> I know some CPUs need Linux cpuidle disabled, some might need other tricks too.
<Mis012[m]> I'm not even really sure what state it's in fwiw
<Mis012[m]> this suggests that if you don't do the workaround, it SRSTs itself
<Mis012[m]> I tried doing the workaround, it still disconnects from USB when I switch the mux...
<Mis012[m]> I'm using firehose with a hackily patched loader which hacks into EL3
<Mis012[m]> not sure why that mux register is not accessible from EL1 on this SoC, judging from those downstream drivers it was accessible in EL1 on msm8996
<Mis012[m]> basically I load this into EL3 exception vector, run custom firehose command to use an scm call, usb disconnects and I have SWD
<Mis012[m]> so not exactly a known state :P
<Mis012[m]> it seems weird to me that it mentions pulling sRST down
<Mis012[m]> (it's muxed with cmd)
Hawk777 has quit [Ping timeout: 260 seconds]
<PaulFertser> Mis012[m]: not much I can help you with, unfortunately. Other than giving the reference to ADI so that it complements your picture.
<Mis012[m]> I guess qcom did overhaul qdss since apq8064, but I was hoping maybe the people who got jtag to work on apq8064 could help
Hawk777 has joined #openocd
<Mis012[m]> hm
<Mis012[m]> maybe the real error has scrolled away?
<Mis012[m]> should try head