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
When I added stm32 support I did not consider the inconvenience reusing the flash_offset setting, also used by esp32, could cause. This could be quite inconvenient for anyone developing an app meant to run on either device family.
I think changing the stm32 platform to use stm_flash_offset would be helpful for users, as they could configure the offset for both platforms independently and just run the respective flash tasks without passing an offset or changing mix.exs.
The text was updated successfully, but these errors were encountered:
Another possibility (I don’t know if mix supports this or how it would be done) would be to have per-task configuration sections like the atomvm_rebar3_plugin uses.
and we should implement support for esp_flash_offset for explicitness, and start using that instead of a soft deprecated flash_offset (still support it but always document esp_flash_offset to be used..)
I had a similar thought about using a more explicit esp_flash_offset too. Even if per-task configuration is supported, an explicit difference still sounds like a good change.
When I added stm32 support I did not consider the inconvenience reusing the flash_offset setting, also used by esp32, could cause. This could be quite inconvenient for anyone developing an app meant to run on either device family.
I think changing the stm32 platform to use stm_flash_offset would be helpful for users, as they could configure the offset for both platforms independently and just run the respective flash tasks without passing an offset or changing mix.exs.
The text was updated successfully, but these errors were encountered: