esp32-mkimage: release Elixir flavour with bigger boot.avm partition

esp32boot.avm when including Elixir library doesn't fit into standard boot.avm
partition.
Starting from this, and Elixir flavour with a bigger boot.avm partition
will be released.

Signed-off-by: Davide Bettio <davide@uninstall.it>

Author: bettio

.github/workflows/esp32-mkimage.yaml

@@ -43,6 +43,7 @@ jobs:
         elixir_version: ["1.17"]
         compiler_pkgs: ["clang-10"]
         soc: ["esp32", "esp32c2", "esp32c3", "esp32s2", "esp32s3", "esp32c6", "esp32h2"]
+        flavor: ["", "-elixir"]
 
     env:
       CC: ${{ matrix.cc }}
@@ -117,36 +118,44 @@ jobs:
       run: |
         cp sdkconfig.release-defaults sdkconfig.defaults
 
-    - name: "Build ${{ matrix.soc }} with idf.py"
+    - name: "Build ${{ matrix.soc }}${{ matrix.flavor }} with idf.py"
       shell: bash
       working-directory: ./src/platforms/esp32/
       run: |
         rm -rf build
         . $IDF_PATH/export.sh
+        if [ ! -z "${{ matrix.flavor }}" ]
+        then
+          mv partitions${{ matrix.flavor }}.csv partitions.csv
+        fi
         idf.py set-target ${{ matrix.soc }}
         idf.py reconfigure
         idf.py build
 
-    - name: "Create a ${{ matrix.soc }} image"
+    - name: "Create a ${{ matrix.soc }}${{ matrix.flavor }} image"
       working-directory: ./src/platforms/esp32/build
       run: |
         ./mkimage.sh
+        if [ ! -z "${{ matrix.flavor }}" ]
+        then
+          mv atomvm-${{ matrix.soc }}.img atomvm-${{ matrix.soc }}${{ matrix.flavor }}.img
+        fi
         ls -l *.img
 
     - name: "Upload ${{ matrix.soc }} artifacts"
       uses: actions/upload-artifact@v4
       with:
-        name: atomvm-${{ matrix.soc }}-image
-        path: ./src/platforms/esp32/build/atomvm-${{ matrix.soc }}.img
+        name: atomvm-${{ matrix.soc }}${{ matrix.flavor }}-image
+        path: ./src/platforms/esp32/build/atomvm-${{ matrix.soc }}${{ matrix.flavor }}.img
         if-no-files-found: error
 
     - name: "Rename and write sha256sum"
       if: startsWith(github.ref, 'refs/tags/')
       shell: bash
       working-directory: src/platforms/esp32/build
       run: |
-        ATOMVM_IMG="AtomVM-${{ matrix.soc }}-${{ github.ref_name }}.img"
-        mv atomvm-${{ matrix.soc }}.img "${ATOMVM_IMG}"
+        ATOMVM_IMG="AtomVM-${{ matrix.soc }}${{ matrix.flavor }}-${{ github.ref_name }}.img"
+        mv atomvm-${{ matrix.soc }}${{ matrix.flavor }}.img "${ATOMVM_IMG}"
         sha256sum "${ATOMVM_IMG}" > "${ATOMVM_IMG}.sha256"
 
     - name: Release
@@ -156,5 +165,5 @@ jobs:
         draft: true
         fail_on_unmatched_files: true
         files: |
-          src/platforms/esp32/build/AtomVM-${{ matrix.soc }}-${{ github.ref_name }}.img
-          src/platforms/esp32/build/AtomVM-${{ matrix.soc }}-${{ github.ref_name }}.img.sha256
+          src/platforms/esp32/build/AtomVM-${{ matrix.soc }}${{ matrix.flavor }}-${{ github.ref_name }}.img
+          src/platforms/esp32/build/AtomVM-${{ matrix.soc }}${{ matrix.flavor }}-${{ github.ref_name }}.img.sha256

CHANGELOG.md

@@ -6,6 +6,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [0.6.5] - Unreleased
 
+### Added
+
+- ESP32: add a new Elixir release "flavor" with a bigger boot.avm partition that has room for
+Elixir standard library modules
+
 ## [0.6.4] - 2024-08-18
 
 ### Added

UPDATING.md

@@ -6,6 +6,12 @@
 
 # AtomVM Update Instructions
 
+## v0.6.4 -> v0.6.5
+
+- ESP32: partitioning schema for Elixir flavor is different, so app offset has been changed for
+Elixir images. Make sure to use `0x250000` as offset in your mix.exs or when performing manual
+flashing.
+
 ## v0.6.0-beta.1 -> v0.6.0-rc.0
 
 - Drivers that send messages from Esp32 callbacks should use new functions

src/platforms/esp32/partitions-elixir.csv

@@ -0,0 +1,12 @@
+# Copyright 2018-2021 Davide Bettio <davide@uninstall.it>
+# Copyright 2018-2021 Fred Dushin <fred@dushin.net>
+#
+# SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later
+
+# Name,   Type, SubType, Offset,  Size, Flags
+# Note: if you change the phy_init or app partition offset, make sure to change the offset in Kconfig.projbuild
+nvs,      data, nvs,       0x9000,     0x6000,
+phy_init, data, phy,       0xf000,     0x1000,
+factory,  app,  factory,  0x10000,   0x1C0000,
+boot.avm,  data, phy,     0x1D0000,    0x80000,
+main.avm, data, phy,     0x250000,   0x100000