# Debugging Nano 33 iot issues

**URL:** <https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358>\
**Category:** IDE 2.x\
**Created:** [April 29, 2021, 3:55pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358 "2021-04-29T15:55:10Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![eheadj](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/eheadj/32/1112581_2.png) [@eheadj](https://forum.arduino.cc/u/eheadj)\
**Post date:** [April 29, 2021, 3:55pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358/1 "2021-04-29T15:55:10Z")

</div>

Hello,

I am super excited regarding the debugging feature the new IDE has. For me this is a reason to invest on arduino. This is why I purchased a nano 33 iot. But I am having some issues.

I am simply trying to "debug" the blink sketch , but I can't.

I compile/ upload the sketch to the nano, which blinks, and get 3 issues:

#1: on the top of debug window I get: No Configurations  
and a launch.json file is opened with the following:

```cpp
{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  "version": "0.2.0",
  "configurations": []
}

```

#2: In the Notifications I get: Failed to launch OpenOCD GDB Server: Timeout.

#3: In the Cortex Peripherals I get: Unable to load SVD file: Not specified

I have tried to google and search the forums and stuff but information on the debug issue is scarce to sayt the least. Additionally whatever info I got was for different configurations and above my level..

Could someone explain what could be the issue? In as simple English as possible : ) ?  
Thank you community!!

---

<div class="post-metadata">

**Author:** ![pert](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/pert/32/217111_2.png) [@pert](https://forum.arduino.cc/u/pert)\
**Post date:** [April 29, 2021, 4:16pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358/2 "2021-04-29T16:16:52Z")

</div>

> [@eheadj](#):
>
> on the top of debug window I get: No Configurations  
> and a launch.json file is opened with the following:

You should start the debugger by clicking the "Start Debugging" icon on the top bar of the Arduino IDE, not by clicking the one on the side bar

> [@eheadj](#):
>
> In the Notifications I get: Failed to launch OpenOCD GDB Server: Timeout.

Do you have a CMSIS-DAP compliant debug probe connected to the SWD test pads on the bottom of the Nano 33 IoT board?

---

<div class="post-metadata">

**Author:** ![eheadj](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/eheadj/32/1112581_2.png) [@eheadj](https://forum.arduino.cc/u/eheadj)\
**Post date:** [April 29, 2021, 5:10pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358/3 "2021-04-29T17:10:34Z")

</div>

Thank you!

1st point taken..

2nd point.. Err... Nope. : )  
I thought "support out of the box" meant no debugger.. The only thing I have right now is this:  
[https://www.amazon.com/FT232H-Multifunction-High-Speed-CJMCU-Module/dp/B07L15J1F9](https://www.amazon.com/FT232H-Multifunction-High-Speed-CJMCU-Module/dp/B07L15J1F9)

Will it do? Any guides on how to connect?  
If not what is a cheap alternative? Or any alternative if a cheap one is not handy..? Thanks!

---

<div class="post-metadata">

**Author:** ![pert](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/pert/32/217111_2.png) [@pert](https://forum.arduino.cc/u/pert)\
**Post date:** [April 29, 2021, 9:53pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358/4 "2021-04-29T21:53:51Z")

</div>

> [@eheadj](#):
>
> Will it do?

Unfortunately, I don't know anything about this FT232H. It looks interesting though.

> [@eheadj](#):
>
> Any guides on how to connect?

This is the SWD pinout on the Nano 33 IoT:  
 ![Nano 33 IoT SWD](https://europe1.discourse-cdn.com/arduino/original/4X/1/a/f/1af50cd45ad3c44e48e6dba9ec610827df68defc.jpeg)  
Most debug probes use a standardized 2x5 0.05" pitch connector. You will want a way to easily make the connections between the two. The 0.05" pitch is not friendly to jumper wires. You can get adapters like this one:

> **[SWD (2x5 1.27mm) Cable Breakout Board](https://www.adafruit.com/product/2743)**
>
> This adapter board is designed to make it easier to use ARM dev boards that use slimmer 2x5 (0.05"/1.27mm pitch) SWD cables for programming.  It's helpful for using products ...

You can see the pinout of the connector is labeled on the adapter, so it's only a matter of making the connections between the board and the cable.

I have used a [a 0.1" pitch 2x3 POGO adapter](https://www.sparkfun.com/products/11591) pressed down on the test pads on the Nano 33 IoT for making a short term connection to burn the bootloader, but for the longer term connections you would certainly want for debugging you will find that is not feasible. It would be super cool to have a jig like [this](https://www.instagram.com/p/B9eTOlcnSQP/), but you might decide to go with the most simple solution and just solder wires to the test points.

> [@eheadj](#):
>
> what is a cheap alternative?

I use this little open source debugger:

> **[CMSIS-DAP Compliant SWD Debugger by Alex Taradov on Tindie](https://www.tindie.com/products/ataradov/cmsis-dap-compliant-swd-debugger/)**
>
> CMSIS-DAP compliant debugger based on a free and open hardware and software

I'm really happy with it.

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/system/32/1140315_2.png) [@system](https://forum.arduino.cc/u/system)\
**Post date:** [August 27, 2021, 9:54pm UTC](https://forum.arduino.cc/t/debugging-nano-33-iot-issues/855358/5 "2021-08-27T21:54:36Z")

</div>

Closed on August 27, 2021, 9:54pm UTC

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.