Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to fully integrate the esptool-ftdi utility in the idf.py build/flash system (IDFGH-5095) #6879

Closed
wants to merge 2 commits into from

Conversation

M-Bab
Copy link
Contributor

@M-Bab M-Bab commented Apr 15, 2021

To use this set the environment variable ESPTOOL_FTDI to the path to the utility.

This utility allows to flash an ESP event simpler/cheaper with a standard FTDI USB-serial cable.
The lack of RTS/DTR is compensated by bitbanging RTS/CTS.

Implements jimparis/esptool-ftdi#3

I am not sure, if you like this hacky approach. But after all, it is very comfortable to use a simple FTDI cable for flashing.

…/flash system.

To use this set the environment variable ESPTOOL_FTDI to the path to the utility.

This utility allows to flash an ESP event simpler/cheaper with a standard FTDI USB-serial cable.
The lack of RTS/DTR is compensated by bitbanging RTS/CTS.

Implements jimparis/esptool-ftdi#3
@CLAassistant
Copy link

CLAassistant commented Apr 15, 2021

CLA assistant check
All committers have signed the CLA.

@M-Bab
Copy link
Contributor Author

M-Bab commented Apr 15, 2021

Or alternatively, we could use a more generic environment variable like ESPTOOL_WRAPPER which is prepended, if it set?

@espressif-bot espressif-bot added the Status: Opened Issue is new label Apr 15, 2021
@github-actions github-actions bot changed the title Allow to fully integrate the esptool-ftdi utility in the idf.py build/flash system Allow to fully integrate the esptool-ftdi utility in the idf.py build/flash system (IDFGH-5095) Apr 15, 2021
@Alvin1Zhang
Copy link
Collaborator

Thanks for your contribution.

@dobairoland
Copy link
Collaborator

Hi @M-Bab. You have a nice project and thank you for your contribution.

Personally, I think this can be accepted but I don't promise anything because it will go through an internal review process.
Could you please correct the variable name to ESPTOOL_WRAPPER as you've suggested?

that it might be used for other esptool wrappers as well.
@M-Bab
Copy link
Contributor Author

M-Bab commented Apr 16, 2021

Renaming is done. Thanks a lot for your positive feedback.

The esptool-ftdi itself is not my development, this is the work of @jimparis .

Some background information on how to use it in practice (if anyone is curious):

Integrate in the eclipse environment:

image

Schematic implementation (works directly without the usual RTS/DTR transistor circuit):

image

Be aware that regularly opening the COM port with an FTDI fully connected will keep the ESP in reset because RTS is handled on open which keeps the ESP disabled. This can be handled by certain serial terminals which are able to toggle RTS like gtkterm.

This schematic with pin header can be combined with the cheap USB FTDI adapter: FTDI TTL-232R-3V3

Or even for footprint only production designs with e.g. tag-connect TC2030-FTDI-TTL-232R-3V3

@espressif-bot espressif-bot added Status: In Progress Work is in progress Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: Opened Issue is new Status: In Progress Work is in progress labels Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants