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

"erase_otadata" and "read_otadata" targets don't use configured port (IDFGH-686) #3135

Closed
jimparis opened this issue Mar 6, 2019 · 0 comments

Comments

@jimparis
Copy link

jimparis commented Mar 6, 2019

The erase_otadata and read_otadata targets added in 5e08698 don't use the project's configured ESPTOOLPY_PORT, ESPTOOLPY_BAUD, ESPTOOLPY_BEFORE, ESPTOOLPY_AFTER. The previous erase_ota target did, because all these settings were included in $(ESPTOOLPY_SERIAL).

@projectgus projectgus changed the title "erase_otadata" and "read_otadata" targets don't use configured port "erase_otadata" and "read_otadata" targets don't use configured port (IDFGH-686) Mar 12, 2019
@igrr igrr closed this as completed in 94e0569 Jul 15, 2019
trombik pushed a commit to trombik/esp-idf that referenced this issue Aug 9, 2019
0xFEEDC0DE64 pushed a commit to 0xFEEDC0DE64/esp-idf that referenced this issue May 5, 2021
Some ESP32 chips are rated only to 160MHz. This change adds support for them and does not allow frequency to be switched to 240MHz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant