title: Raspberry pi pico usb debbuging on Windows
body: <p>I recently bought raspberry pi pico and I follow the How to get started with raspberry pico in C/C++ tutorial, but I have only windows computer. I want to debug my pico with usb. I compiled the example hello world project with cmake usb configuration (as shown in <a href="https://datasheets.raspberrypi.org/pico/getting-started-with-pico.pdf" rel="nofollow noreferrer">tutorial</a>) and draged a usb/hello_usb.uf2 file to pico. Also there is a elf file <em>for debugger</em>, but I have no idea, what to do with it. Only thing about connecting pico usb stdout to computer, that I found in tutorials and datasheets is this command for minicom:</p>
  <pre><code>$ minicom -b 115200 -o -D /dev/ttyACM0
  </code></pre>
  <p>Unfortunately minicom is only available for Linux, but I found out what different parts of that command means:</p>
  <ol>
  <li>Port: /dev/ttyACM0</li>
  <li>Baud rate: 115200</li>
  <li>-o means that minicom doesn't initial setup (I don't exactly know what it is)</li>
  </ol>
  <p>And I tried to enter these informations to puTTY:</p>
  <p><a href="https://i.stack.imgur.com/JsnU3.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/JsnU3.png" alt="putty serial config" /></a></p>
  <p>I tried a lot of other combinations of values that are not specified in that command (On screenshot is config for some arduino board, that I found), but I always just heard windows fail tone. All stuff I do and describe here might be wrong, I am a beginner, but I didn't found a good source of information about this.</p>
  <p>Should I use something else (not puTTY)?</p>
  <p>EDIT:</p>
  <p>I got it! I did some mistakes during sdk setup and tinyUSB didn't work, so I couldn't even see pico in device manager. I did the whole setup again and everything works now. I also found video, how to connect pico via putty: <a href="https://youtu.be/BjGc60Mmwz8" rel="nofollow noreferrer">https://youtu.be/BjGc60Mmwz8</a> . Also as aMike said, you have to type just com port to puTTY, not /dev/ttyACM0.</p>