Skip to content

Conversation

@Jeija
Copy link

@Jeija Jeija commented Oct 16, 2025

Description

I wanted to use esp-serial-flasher with the new ESP32-C61 as a target device and realized that the library has not yet been updated to include support for that. I added the required code and binaries.

Testing

  • Only tested with ESP32 as host device and ESP32-C61 as target
  • Only tested with UART interface using the two example apps:
    • examples/esp32_example: Writes "Hello world" app to flash via UART
    • examples/esp32_load_ram_example: Loads "Hello world" app to RAM

It works fine under these tested configurations.

I have not tested any other configurations (different host microcontrollers, interfaces other than UART), but wanted to leave this here maybe as a starting point for future work.

@github-actions
Copy link

github-actions bot commented Oct 16, 2025

Messages
📖 🎉 Good Job! All checks are passing!

👋 Hello Jeija, we appreciate your contribution to this project!


Click to see more instructions ...


This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...


We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 366974f

@github-actions github-actions bot changed the title Add support for ESP32-C61 as target device Add support for ESP32-C61 as target device (ESF-251) Oct 16, 2025
@Dzarda7
Copy link
Collaborator

Dzarda7 commented Oct 16, 2025

Hello @Jeija, very nice, thanks, interesting, I thought there is no way to get a hands on ESP32-C61 😄 . We plan to remove the example binaries for all the chips, so if you are okay with that, I would like to merge this after the change (week or two I believe). If you want this ASAP, we can do that, but seems like you are not in a hurry. Would you be okay with modifying this PR after the change so you have all the credit you deserve for this PR or you want us to finis this? I believe only small changes would be necessary.

@Jeija
Copy link
Author

Jeija commented Oct 16, 2025

Hi @Dzarda7, I can just use my own fork of esp-serial-flasher in the meantime, so there is no rush in getting this upstream. Feel free to add support for ESP32-C61 after the change, I don't really care about getting credit for this commit. But I'd also be fine with modifying this PR and to test it on my hardware if that is easier for you. Basically I don't care either way as long as support for the ESP32-C61 ends up in esp-serial-flasher at some point 😉

@Dzarda7
Copy link
Collaborator

Dzarda7 commented Oct 16, 2025

Thanks @Jeija, I will let you know. All the new chips are planned to be supported.

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

Successfully merging this pull request may close these issues.

2 participants