ports/alif/boards/ALIF_ENSEMBLE: Add deploy instructions.

[iabdalkader]

Summary

Add deploy/build instructions for Ensemble E7 DevKit.

• Board images: boards/ALIF_ENSEMBLE: Add ALIF_ENSEMBLE board image. micropython-media#95

Testing

I've tested these instructions, with another board, and they work fine. Testing with the devkit itself would be helpful.

[iabdalkader]

@dpgeorge I'm not sure how to add the firmware to the hosted files, we probably need to add the entire build dir. Could you please add it? Also, I don't have a devkit to test with, but I did test these instructions with AE3.

./ports/alif/boards/ALIF_ENSEMBLE/board.json unknown features: {'OSPI Flash', 'I2S/PDM Microphone', 'SD Card', 'OSPI HyperRAM', 'Joystick'}

I'm not really sure what the purpose of the "features" tag is, but I can just remove these.

[dpgeorge]

I'm not sure how to add the firmware to the hosted files, we probably need to add the entire build dir.

I think we should add just the files that are needed for deployment over serial. To do that, we should create a target in the Makefile like package which packages up all the needed files into a .zip (or .tgz?). And then tools/autobuild/build-boards.sh can have a function added to it which builds and collects this .zip. That will be very similar to how the cc3200 port works.

[iabdalkader]

I think we should add just the files that are needed for deployment over serial. To do that, we should create a target in the Makefile like package which packages up all the needed files into a .zip (or .tgz?). And then tools/autobuild/build-boards.sh can have a function added to it which builds and collects this .zip. That will be very similar to how the cc3200 port works.

This is fine with me, but it's probably best if you do this step. We could merge the build instructions and board images contained in this PR or feel free to push to the branch/cherry-pick the commits here.

[dpgeorge]

I've now pushed 2 commits to this PR:

• create firmware.zip as part of the alif build process, containing relevant files needed to deploy over SEUART
• add alif to the auto-build scripts, so the boards are built along with all the other boards

I didn't test the zip yet!

[github-actions]

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.54%. Comparing base (2c2f0b2) to head (a8d3ef5).
Report is 36 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #17435   +/-   ##
=======================================
  Coverage   98.54%   98.54%           
=======================================
  Files         169      169           
  Lines       21943    21946    +3     
=======================================
+ Hits        21623    21626    +3     
  Misses        320      320           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kwagyeman]

Tested the build and everything works.

[iabdalkader]

@dpgeorge Is the readme/deploy here clear enough? Should we move forward with this PR?