I have the same problem. I also don't know how to set this specific item in whatever configuration file.

@PaulskPt I've just been specifying it on the command line to launch openocd. Here's a somewhat over-complicated example:

https://github.com/Blinkinlabs/rp2350_tinygo_dev/blob/42842292f174d4a9e6339a2a9435e67a22e3ff93/docker/Makefile#L46

@cibomahto. Thank you for your message. What I need is to know where I can add the command line: -c "rp2350.dap.core1 cortex_m reset_config sysresetreq" inside the Arduino IDE v2.3.4. I searched in places like:

<drive>:\Users\<user>\AppData\Local\Arduino15\packages\rp2040\tools\pqt-openocd\4.0.1-8ec9d6f,

however, I didn't find where I could add a command like mentioned.

@cibomahto. Thank you for your message. What I need is to know where I can add the command line: -c "rp2350.dap.core1 cortex_m reset_config sysresetreq" inside the Arduino IDE v2.3.4. I searched in places like:

<drive>:\Users\<user>\AppData\Local\Arduino15\packages\rp2040\tools\pqt-openocd\4.0.1-8ec9d6f,

however, I didn't find where I could add a command like mentioned.

I'm not using Arduino so I don't know specifically, but try searching those directories for another part of the command, such as "interface/cmsis-dap.cfg". That should help narrow down where the configuration is.

Thank you. I go to look in there.

where I can add the command line: -c "rp2350.dap.core1 cortex_m reset_config sysresetreq" inside the Arduino IDE v2.3.4

Perhaps @earlephilhower can help?

Not really sure that the Arduino core (which already has its own OpenOCD core built from the new SDK and RPI's OpenOCD fork) would ever call your own custom built OpenOCD. I suppose you could hack file places, overwriting the Arduino package manager installed copy, but that's not a good long term plan. FWIW, the distributed OpenOCD app also does uploads (and believe me, plenty of debugging too 😆 ) from the IDE w/o any issue that I've heard about.

In any case you can look in the installed core's lib/rp2350(or rp2350-riscv)/picoprobe_cmsis_dap.tcl which is what's used to start OpenOCD for debugging or the tools.picoprobe_cmsis_dap.upload.pattern=... command line in platform.txt

@earlephilhower, thank you for your message. In this moment I am using MS Windows 11 Pro. board to test: iLabs cPico (RP2350 with a 3-wire debug connector), an iLabs iProbe (clone of the PicoProbe). Using Arduino IDE v2.3.4. As far as I know, I am not using an "own custom built OpenOCD". In the Arduino IDE v2.3.4 settings, your library https://github.com/earlephilhower/arduino-pico/releases/download/global/package_rp2040_index.json. In the sketch menu > Optimize for debugging and in the tools menu > Upload method > Picoprobe/Debuggingprobe (CMSIS-DAP). Debugging is functioning. The only thing is the error mentioned above regarding core1 reset_config sysresetreq.

Ah, I think I see. Two different users using two different builds of OpenOCD (one from source, one from the arduino-pico core). But both do generate the same warning (which makes sense since I don't patch the source, just take it and build for the ~9 architectures).

In any case the warning message seems to be just a warning and not a real problem. Uploads work fine and multicore operations also seem good in all my testing. You can edit those files I suggested or ignore the warning, it seems benign.

That said the TCL for the RP2350 here probably needs a patch to remove the warning as @cibomahto suggested. #127 implements his suggestion and does clear things up in testing here.

I added the line as in #127 in rp2350.cfg. Now the warning is gone. Tnx!

See the image of the test sketch halting at a breakpoint.

Note that in the Arduino IDE I had to choose as board: "iLabs Challenger 2350 Bconnect" because there does not yet exist a definition for the iLabs CPico RP2350 board.

Note that in the Arduino IDE I had to choose as board: "iLabs Challenger 2350 Bconnect" because there does not yet exist a definition for the iLabs CPico RP2350 board.

That hasn't been added to Pico-SDK either yet: https://github.com/raspberrypi/pico-sdk/tree/develop/src/boards/include/boards

Ah, I think I see. Two different users using two different builds of OpenOCD (one from source, one from the arduino-pico core). But both do generate the same warning (which makes sense since I don't patch the source, just take it and build for the ~9 architectures).

In any case the warning message seems to be just a warning and not a real problem. Uploads work fine and multicore operations also seem good in all my testing. You can edit those files I suggested or ignore the warning, it seems benign.

That said the TCL for the RP2350 here probably needs a patch to remove the warning as @cibomahto suggested. #127 implements his suggestion and does clear things up in testing here.

It's seems that core 1 is not properly reset in my testing.

I ran stdio on core 1 on the RP2350. After uploading the binaries using OpenOCD, the input and output are not produced (both USB and UART are checked). I need to reset the target RP2350 by shorting RUN to GND to have input/output working normally.

Here is the code used in my testing.

#include <stdio.h>
#include "pico/stdlib.h"
#include "pico/multicore.h"

void core1_main(void) {
    for(int i = 0; i < 10; i++) {
        printf("Hello, it's me.\n");
        sleep_ms(1000);
    }

    while(true) {
        int tmp = getchar_timeout_us(0);
        if(tmp == PICO_ERROR_TIMEOUT) {
            sleep_ms(5);
        } else {
            putchar(tmp);
        }
    }

    return;
}

int main(void) {
    stdio_init_all();

    multicore_launch_core1(core1_main);

    while(true) {
        tight_loop_contents();
    }

    return 0;
}

The OpenOCD version is 0.12.0+dev-gcf9c0b41c and the command used for uploading the binaries is:
openocd -f interface/cmsis-dap.cfg -c "adapter speed 5000" -f /target/rp2350.cfg -c "program $(dirname $0)/build/picoprobe_stdio_test.elf verify reset exit"

I don't think anyone here is reporting that, @light655 . My own multicore I/O tests (using the Arduino core and rp2350) run just fine with or without the extra line to remove the warning (AIUI OpenOCD is doing the exact same thing in both cases, anyway, just removing a warning). You should double check your setup (especially serial ports -> when the chip is reset asynchronously like w/OpenOCD the host USB stack may take some time to reconnect after it runs and may give it a different devnode (COM*: or /dev/tty*). If that's still the case then the forum or the SDK repo would be the right spot for it...

I've also see the same [rp2350.dap.core1] warnings so I thought it belongs here.
I've checked that the port is still the same after resetting. Also, the issue only occurs when the target is RP2350, RP2040 doesn't have any issue.
Thank you for the information, I'll report it on the forum or the SDK repo.