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
Currently the flash command expects an ELF image to be flashed to the device. This makes sense in the context of a cargo project since the output there will always be an ELF image. But on the command line it would be useful to be able to directly flash an already converted image. In our case we already build those for OTA updates and it would be convenient to be able to use the same files when flashing directly.
It looks to me like it's should be doable to just detect the type of file passed to the flash command based on the magic bytes in the file. An ELF file could be converted and flashed, but when a ESP binary is found it's just flashed directly. All of that would then be transparent for the user and 'just work' regardless of the type of image used. Would this be a sensible approach, or would a more explicit (separate command or extra argument) be preferred?
Currently the flash command expects an ELF image to be flashed to the device. This makes sense in the context of a cargo project since the output there will always be an ELF image. But on the command line it would be useful to be able to directly flash an already converted image. In our case we already build those for OTA updates and it would be convenient to be able to use the same files when flashing directly.
It looks to me like it's should be doable to just detect the type of file passed to the flash command based on the magic bytes in the file. An ELF file could be converted and flashed, but when a ESP binary is found it's just flashed directly. All of that would then be transparent for the user and 'just work' regardless of the type of image used. Would this be a sensible approach, or would a more explicit (separate command or extra argument) be preferred?
This might be a solution to #684 as well.
The text was updated successfully, but these errors were encountered: