Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.38%. Comparing base (cbc6aed) to head (f6e23fd).
Report is 3 commits behind head on master.

@@           Coverage Diff           @@
##           master   #17737   +/-   ##
=======================================
  Coverage   98.38%   98.38%           
=======================================
  Files         171      171           
  Lines       22238    22238           
=======================================
  Hits        21879    21879           
  Misses        359      359           

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

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

@agatti FYI

Nice! I wonder if it makes sense to also test those under QEMU.

If memory serves ARMv7 is a superset of ARMv6 so MPS2_AN385 should in theory be able to run some of the new targets unmodified. For hardfp targets, if the mps2-an500 QEMU machine definition allows to reuse most of the '385 implementation details this could be something interesting to look at.

Maybe I can give a shot at the hardfp targets for inclusion in the next release?

I wonder if it makes sense to also test those under QEMU.

Good idea. I've now added armv6m tests under QEMU. See what you think.

Maybe I can give a shot at the hardfp targets for inclusion in the next release?

Yes, that would be good. Shouldn't be too difficult.

Maybe I can give a shot at the hardfp targets for inclusion in the next release?
Yes, that would be good. Shouldn't be too difficult.

Indeed. Here's something working on the QEMU side: 6515cd0...agatti:micropython:qemu-armv7-machine - I haven't created a PR for it as I'll wait for this to get merged first. My plan was also to change the default Arm target from the '385 to the '500 but that may have some unintended consequences I'm not fully aware of.

That is pretty simple.

Well, let's wait for this PR to be merged, then we can take the next step there.

If you have any further comments about this one, let me know. Otherwise I think it's good to go in.

LGTM!

In fact, I've successfully run tests for all variants using my mps2_an500 machine definition with this:

diff --git i/ports/qemu/Makefile w/ports/qemu/Makefile
index b854a4ba2..7813a7e59 100644
--- i/ports/qemu/Makefile
+++ w/ports/qemu/Makefile
@@ -1,7 +1,7 @@
 ################################################################################
 # Initial setup of Makefile environment
 
-BOARD ?= MPS2_AN385
+BOARD ?= MPS2_AN500
 BOARD_DIR ?= boards/$(BOARD)
 
 ifeq ($(wildcard $(BOARD_DIR)/.),)
diff --git i/tools/ci.sh w/tools/ci.sh
index 7733ba494..e558e6b4c 100755
--- i/tools/ci.sh
+++ w/tools/ci.sh
@@ -346,15 +346,12 @@ function ci_qemu_build_arm_thumb {
     ci_qemu_build_arm_prepare
     make ${MAKEOPTS} -C ports/qemu test_full
 
-    # Test building native .mpy with all ARM-M architectures.
-    ci_native_mpy_modules_build armv6m
-    ci_native_mpy_modules_build armv7m
-    ci_native_mpy_modules_build armv7emsp
-    ci_native_mpy_modules_build armv7emdp
-
-    # Test running native .mpy with armv6m and armv7m architectures.
-    make ${MAKEOPTS} -C ports/qemu test_natmod RUN_TESTS_EXTRA="--arch armv6m"
-    make ${MAKEOPTS} -C ports/qemu test_natmod RUN_TESTS_EXTRA="--arch armv7m"
+    # Test building and running native .mpy with all ARM-M architectures.
+    for ARCH in armv6m armv7m armv7emsp armv7emdp
+    do
+        ci_native_mpy_modules_build $arch
+        make ${MAKEOPTS} -C ports/qemu test_natmod RUN_TESTS_EXTRA="--arch ${ARCH}"
+    done
 }
 
 function ci_qemu_build_rv32 {