using the usb serial / jtag interface with esp-idf

[davidzuhn]

I know exactly what the problem is. Dev boards include a little usb to uart chip that drives the boot and EN pins using its RTS and CTS outputs. This configuration is known as "default_reset" in the toolchain, and as the name suggests, all the command lines generated by the toolchain include "--before default_resest" to reset the board and kick it into the bootloader. The USB / JTAG peripheral is also capable of generating the correct reset behavior but only when "--before usb_reset" is used on the CLI. I cant figure out how the toolchain configures this and I have spent hours trying. I am guessing its just hardcoded someplace.

I believe there is some other issue going on here. My boards do not have any USB<->serial interface chips, nor the transistors to tickle EN/reset based on the CTS/RTS signals. Yet I have no trouble working with idf.py commands (app-flash, flash, erase, monitor, etc.) without needing any other command line options.

So there isn't a requirement for the CTS/RTS supporting hardware, nor for additional options to idf.py.

[MicroController]

I believe there is some other issue going on here. [...] I have no trouble working with idf.py commands (app-flash, flash, erase, monitor, etc.) without needing any other command line options.

Yep, same here.

Maybe a driver issue? Windows or Linux?

[bram128]

thats really interesting. im on windows with the latest esp-idf release (5.4)

[bram128]

when you look at the esptool command line that is printed after running "idf.py build", does it include "-before usb-reset"?

is there some idf configuration command that sets this? Similar to "idf.py --set-target esp32s3"?

I know exactly what the problem is. Dev boards include a little usb to uart chip that drives the boot and EN pins using its RTS and CTS outputs. This configuration is known as "default_reset" in the toolchain, and as the name suggests, all the command lines generated by the toolchain include "--before default_resest" to reset the board and kick it into the bootloader. The USB / JTAG peripheral is also capable of generating the correct reset behavior but only when "--before usb_reset" is used on the CLI. I cant figure out how the toolchain configures this and I have spent hours trying. I am guessing its just hardcoded someplace.

I believe there is some other issue going on here. My boards do not have any USB<->serial interface chips, nor the transistors to tickle EN/reset based on the CTS/RTS signals. Yet I have no trouble working with idf.py commands (app-flash, flash, erase, monitor, etc.) without needing any other command line options.

So there isn't a requirement for the CTS/RTS supporting hardware, nor for additional options to idf.py.