23:23 <Guest4> Hey, I'm getting an "Error: Error connecting DP: cannot read IDR" when trying to upload a firmware via platformio on an arduino uno r4 wifi. According to docs, debugging should be supported without external hardware, via cmsis=dap https://docs.platformio.org/en/latest/boards/renesas-ra/uno_r4_wifi.html#debugging . I looked with strace, it does not

23:23 <Guest4> seem to hit access problems to device files. I see the cmsis-dap device in lsusb. has anyone got a clue?

23:24 <Guest4> the command is `pio debug -e debug --interface gdb` and the platformio.io is this https://paste.centos.org/view/9b9619d7

23:25 <Guest4> .ini*

23:25 <antto> Guest4, this error sounds too familiar, it's one of the first things openocd tries to do, if not the very first one

23:26 <Guest4> yeah I cannot find anything related specifically to my board. a bunch of info about selecting the driver on windows, but I am on linux.

23:27 <Guest4> the device appears like this on lsusb https://paste.centos.org/view/21a043f2

23:27 <antto> oh, btw, i don't remember whether you had to adjust some things to allow your user to have access to USB stuff

23:28 <antto> have you used openocd+USB debugger on that PC+OS before?

23:28 <Guest4> I don't think so? I expect those to appear as EACCESS in strace. also I have no problem using normal upload and serial console

23:28 <Guest4> no I have never, I got just this board and no experience with others

23:28 <antto> but maybe it's not that

23:29 <antto> my nose tells me to check your connections between the MCU and the debugger

23:29 <antto> and power

23:31 <Guest95> openocd comes installed with platformio. I tried in the past with arduino ide, which packages openocd at a latter version (but with same openocd.cfg), and it didn't seem to work.

23:31 <Guest95> I also used espflash to flash the esp32 on the board

23:31 <Guest95> I guess that uses the same interface?

23:31 <Guest95> this one https://support.arduino.cc/hc/en-us/articles/16379769332892-Restore-the-USB-connectivity-firmware-on-UNO-R4-WiFi-with-espflash

23:31 <antto> wait, what's the MCU?

23:32 <Guest95> it's a board with a renesas and an esp32

23:33 <Guest95> the arduino stuff runs on renesas, esp32 the "wifi bridge"

23:33 <Guest95> I'm trying to debug code in the arduino framework on the renesas

23:33 <antto> so some Cortex-M then

23:34 <Guest95> ADC is flaky when powered by usb, so cannot rule out electrical issues. but it's the same with 3 boards

23:34 <antto> well, no clue, my only ideas from that error are: "is the MCU powered?" and "are the connections to the debugger right?"

23:35 <Guest95> is upload by cmsis-dap necessary for debugging? can't I use normal upload? I'm confused about the process to start a debugging session, on command line as well

23:36 <antto> no... to debug the MCU you just need to have debug symbols available and to connect to the MCU

23:37 <antto> well, you could also do it without debug symbols but that won't be "fun"

23:37 <Guest95> so is there anything else I can try other than `pio debug -e debug --interface gdb`

23:37 <antto> no idea what that is ^

23:37 <Guest95> it has been kind of unnerving developing a whole freertos thing without a debugger

23:37 <antto> ouch, freeftos

23:38 <antto> no clue about that either

23:38 <Guest95> it is a wrapper for `openocd -d2 -s /home/Guest95/.platformio/packages/framework-arduinorenesas-uno@1.2.2/variants/UNOWIFIR4 -s /home/Guest95/.platformio/packages/tool-openocd/openocd/scripts -f openocd.cfg -c "cmsis_dap_vid_pid 0x2341 0x1002" -c "program {.pio/build/debug/firmware.bin} 0x4000 verify reset; shutdown;"`

23:38 <Guest95> the usb ID is correct

23:40 <antto> so perhaps this command is supposed to just flash a firmware?

23:40 <Guest95> yeah, honestly no clue on how to use openocd directly

23:40 <Guest95> it's way to late to get a clue now

23:40 <antto> i use it directly

23:41 <Guest95> I guess I'll look it up

23:41 <Guest95> thanks

23:41 <antto> so, i run openocd from a terminal, it connects to the debugger (daplink-based), and then thru the debugger to the MCU, and then it sits and waits

23:41 <antto> meh