esp32H2 connection issues as jtag debug device

i am trying to get an esp32H2 or ESP32 dev kit v1 connected to esphome. I run HA on a rpi4 and work from a windows 11 PC. I can upload a sketch through arduino just fine. I can also use the esp-idf as well. No matter what i do esphome says it cant connect. When i connect it and put it in bootloader mode it shows it as a USB/Jtag serial debug unit. If its not in bootloader mode it keeps connecting and disconnecting over and over. I am logged in through https (nabu casa). I have tried with esphome web installer and from within esphome. I am on the same network as my rpi4 HA. When I plugged the esp32 into the Pi4 it had the same issue, couldn’t connect.

First try it with Esp32 dev kit v1. What you get with web installer?

cp2102 USB …
but it just spins

on web installer i get failed to execute open on serial port: ‘Failed to open serial port’

If it is a board with two USB connections, then typically one is for flashing and the other is for debugging.

It sound like the board is in a boot loop, so try to connect to the debugging port and then run a serial monitor on it.

i only see one physical connection

Your dev kit has just one.
So the thing what sounds weird here is that arduino ide works on same computer with same cable and same board?

If it works with some combinations of software but not others, that narrows down the field to look out for considerably.

What does the Windoze system error log say?

Have you installed the correct drivers in Windoze for your ESP serial chip? Is it the CP2102?

Does Windoze Device Manager show errors for that particular device (a yellow warning blob is the giveaway)?

Have you closed everything down neatly (shutdown commands rather than yank the cord) and restarted? Twice? Compter as well as any connected devices?

Are you using the correct serial port? Often Plug-n-pray in Windoze reallocates new port numbers for the same device, especially if there is errors.

Are you putting your ESP32 in correct programming mode for Windoze to recognise it?

i just tried a new one and got it to work. I must have done something when i tried using arduino ide or esp-idf.

I’m guessing Wondoze recognised a new PID and loaded the correct drivers to the USB port when you plugged in the new device.

Your challenge, for ocd purposes, now that you have solved your problem, is to fix that other ESP to also work well. Does it have configuration jumpers, or do you have to hold down buttons during power up to put it into programming mode?

Good luck!