Hi, yes I understand merely trying to find a solution.

Yes serial works fine in Arduino although I have no used it in a while. It worked last time I was in it. I am aware about setup and loop. those are simplified loops and setup to make it easier to code for people. 

I see a delay in there about 5000. you can see it on one of my posts I think of the IDE.

Pico makes the port when you hold down bootloader and short some pins. That part works. I also can use pico in Arduino, just not in Picoprobe mode.

I have not had time to day to work on it but will try to.

Hi, I tested in arduino IDE. I had to use a different file although same code. I cant get Picoprobe working on arduino IDE just he regular Earl RP2040 library. But you can see it works. Have not done more testing in VS2022 but will try to today.

Please try the attached simple project (we have tested on v2.0.2 of the board package), and we found the delay(1) seemed to lock up the board after the first button press, hence it being extended in our very simple example.

This was tested with:
Debug: Off
Board: Raspberry Pi Pico (Picoprobe)
DTR + RTS Enabled on Serial Monitor

As you have both the Pico board, and PicoProbe board connected via USB, there will be two serial ports presented.  Make sure the one for the Pico is selected when both are connected via USB.

It is also worth ensuring the Serial lines are not connected between the Pico and the Pico Probe.  If they are please let us know as this will forward the serial traffic through the PicoProbe board as well.

Note: The same sketch worked fine in the Arduino IDE as well, with the same board selected, and both boards connected via USB.

Hi, Ok I have tested it. I dont have both serial connected because one will be a host USB when I get this to the point where I can write code and test it. Thus It is only going through the pico probe Com 9. 

So far no success. Release, Debug, Debug off, Debug on same thing, nada. Release won't compile so that 

the breaks will hit in Debug mode so I can verify that. I assume the code is getting loaded onto the board. I have tried different combinations. Should I try to uninstall my previous OpenOCD and GDB or.. whatever all that other stuff I put in to get PicoProbe to work on Ard IDE that never did? Maybe it is getting in the way. I do not think it is the COM port as 6 did work on Ard IDE. If you can get it to work must be something in my system not connecting to VS. 

Soo I changed the library to just Earls Ras Pi Pico so am plugged into COM 10 direct to the target not through PicoProbe and with Debug off I GET SERIAL OUTPUT! yeah!

SOO its something on the PicoProbe side. 

Hope that gives you some ideas. 

Hi, I can't seem to get instance of Serial to be used as Serial1. can you help me with some code?

Hi, yes i tried that in the past also. No Success.

Compiling 'RPiPico_SerialTest' for 'Raspberry Pi Pico (Picoprobe)                                                                                             (rp2040_rpipicopicoprobe)'
CoreMutex.h: In constructor CoreMutex::CoreMutex(mutex_t*)
 
   error: Serial1 was not declared in this scope; did you mean Serial?
debug_internal.h:30: note  in expansion of macro DEBUG_RP2040_PORT
   30 | #define DEBUGCORE(fmt, ...) do { DEBUG_RP2040_PORT.printf(fmt, ## __VA_ARGS__); DEBUG_RP2040_PORT.flush(); } while (0)
   |                                  ^~~~~~~~~~~~~~~~~
CoreMutex.h:36: note  in expansion of macro DEBUGCORE
   36 |                 DEBUGCORE("CoreMutex - Deadlock detected!\n")
   |                 ^~~~~~~~~
Error compiling core
Build failed for project 'RPiPico_SerialTest'

Hi, here is the output with Serial1 in the sketch and Serial1 for the RP2040 settings as the Serial to use. 

it will not let me attach a file anymore here. so here it is.

edited.. ok emailed text file to you.

If you change the board options to match the defaults below it should resolve this error:
Debug Port: Disabled
Debug Level: None

These debug options are for logging from the core itself which is unrelated to vMicro Serial / Hardware debugging functionality.

What happens if you set it to Disabled and None as suggested in the previous post?

Simon and Tim have been very helpful. As I had torn the wiring out and rewired it I did lack the UART0 wires. I had gotten distracted and forgot to add them back in. However it still was not working even this morning.

I finally updated the test code from Simon to be Serial1 and the RP2040 options to use Serial for debugging, not Serial1 or Serial2, and suddenly it started working. Looks like a combination of things. Anything can mess up these systems so it all has to be right to work.

Thanks again!