You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like your tool, it is fast, simple, does the job and has UART monitor with reset.
But I am using it to flash bare metal programs not written in C nor Rust which don't use bootloader.
I am using direct-boot for ESP32-C3 but I keep my flasher at 074f8bc (2024.01.15) (last commit with direct-boot).
As I am preparing to jump to ESP32-P4 I am wondering if that old version will be enough for it?
Is there a possibility for return of direct-boot to the espflasher?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
@JohnnyZig just wondering, what is the functionality you need from the flasher tool to support direct-boot binaries?
Generating direct boot binaries from ELF files can be done with objcopy (which you get along with the linker anyway), while the flashing tool doesn't have to know or care how the binary was generated.
We have no plans to re-add this functionality at this time. Probably adding new image formats is not currently possible without a new major release, we will have to do this for #701 at some point. Once this refactoring has been completed then we would likely accept a PR for this, however.
As @igrr mentioned, you should be able to produce a binary using objcopy, which should be writable using the espflash write-bin subcommand.
I like your tool, it is fast, simple, does the job and has UART monitor with reset.
But I am using it to flash bare metal programs not written in C nor Rust which don't use bootloader.
I am using direct-boot for ESP32-C3 but I keep my flasher at 074f8bc (2024.01.15) (last commit with direct-boot).
As I am preparing to jump to ESP32-P4 I am wondering if that old version will be enough for it?
Is there a possibility for return of direct-boot to the espflasher?
Thanks in advance!
The text was updated successfully, but these errors were encountered: