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'm using espflash for Rust based and non-Rust based ESP32 project. It is great.
However when I'm debugging non-Rust based app like Erlang with AtomVM, I'm stressed a bit to execute espflash monitor just after espflash write-bin again and again.
How about adding --monitor option to write-bin just like flash command?
It looks cli::FlashArgs::{monitor,monitor_baud,log_format} is safe to be copied into WriteBinArgs, and the same logic here can be added at the end of write_bin function as well.
The text was updated successfully, but these errors were encountered:
On AtomVM project, you write a program first with Erlang, Elixir or any other compatible languages, and then compiles it into BEAM format as usual.
AtomVM's packbeam utility will then packs it into AVM binary, which you can espflash write-bin into ESP32's 0x210000 address. AtomVM, flashed at bootloader partition in advance, will execute that AVM binary.
Do you think I can use flash command in my case?
Regardless, I think we'd accept a PR that extended the monitor flag to write-bin.
Thank you for mentioning this! I'll try implementing it and open a PR when I have some time, hopefully.
I'm using espflash for Rust based and non-Rust based ESP32 project. It is great.
However when I'm debugging non-Rust based app like Erlang with AtomVM, I'm stressed a bit to execute
espflash monitor
just afterespflash write-bin
again and again.How about adding
--monitor
option towrite-bin
just likeflash
command?It looks
cli::FlashArgs::{monitor,monitor_baud,log_format}
is safe to be copied intoWriteBinArgs
, and the same logic here can be added at the end ofwrite_bin
function as well.The text was updated successfully, but these errors were encountered: