crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #openocd
tsal has quit [Ping timeout: 272 seconds]
tsal has joined #openocd
Hawk777 has left #openocd [#openocd]
Hawk777 has joined #openocd
erhankur has quit [Ping timeout: 246 seconds]
wingsorc has quit [Ping timeout: 260 seconds]
erhankur has joined #openocd
Hawk777 has quit [Quit: Leaving.]
erhankur has quit [Remote host closed the connection]
crabbedhaloablut has quit [Quit: No Ping reply in 180 seconds.]
crabbedhaloablut has joined #openocd
erhankur has joined #openocd
erhankur has quit [Remote host closed the connection]
Haohmaru has joined #openocd
<JakeSays>
hey i'm getting an error and i'm not sure where it's coming from. when i try to start debugging, i get this: 02:33:19: Cannot debug: Could not find executable for "device://{414fc88b-a868-4490-b9bf-1a1b7bfbf46b}/p/clock/SuperClock2/out/debug/mcu1/controller.elf".
<karlp>
what environment are you in?
<JakeSays>
is that 'device://{guid}' prefix added by openocd?
<JakeSays>
linux
<karlp>
more precisely please :)
<JakeSays>
kubuntu 22.04:)
<karlp>
no, I mean, your tooling environment that is building "controller.elf"
<JakeSays>
ah
<karlp>
because openocd can't access that path (obviously)
<karlp>
I suspect you have some sort of magicv "lets hide our development in containers" ?
<JakeSays>
i'm using qt creator version 8
<JakeSays>
no dev containers
<karlp>
and where does it believe the project is? it it some cloud shared repository or something?
<karlp>
do you start "deebugging" from within qt creator?
<JakeSays>
no. this is 100% on my local machine. no cloud - old school
<JakeSays>
yes
<karlp>
well, you've got a qt creator issue then I'm afraid :|
<karlp>
do you see the controlelr.elf somewhere in your local source tree?
<karlp>
or has qt creator built it somewhere strange as well?
<JakeSays>
no creator isn't actually doing the build. i just have it run a script that uses ninja to do the build.
<karlp>
so "gdb controller.elf" "target ext localhost:3333" and "load" and "run" ?
<karlp>
if those all work, it's qt creator.
<karlp>
but it looks like you're not even getting to openocd, qt creator is doing something wrong trying to find your scripts output to pass to the debugger.
<JakeSays>
first it starts openocd with this: /usr/local/bin/openocd -c 'gdb_port 9000' -s /p/personal/truck/arduino/variants/XIAO_m0/openocd_scripts -f /p/personal/truck/arduino/variants/XIAO_m0/openocd_scripts/XIAO_m0.cfg -c "tcl_port disabled" -c "telnet_port disabled"
<karlp>
yeah, it's not getting that far.
<JakeSays>
which in a console runs fine
<karlp>
it can't find the elf to even start debugging, let alone connecting to the target.
<JakeSays>
right
<karlp>
good luck :)
<JakeSays>
ugh. this worked fine in creator 4.15.
<JakeSays>
the quality of creator releases isn't what it used to be im afraid
<karlp>
if you do "realpath blah/elf" does it spit out this device://uuid?
<karlp>
and does that uuid look familiar if you use "blkid" ?
<karlp>
something in your system is possibly tyrying to be very helpful and precise.