18047 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Oliver Joos	4e98486830	stm32/boards: Add linker script for STMF412xE with 512k flash. ... The existing linker script for F412 is renamed to separate F412xG (with 1MB RAM) from F412xE (with 512K). Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 16:54:10 +11:00
Oliver Joos	e9bd1e2e08	stm32: Add support for all STM32F412xx MCUs. ... And fix typo in the usage string of plli2svalues.py. Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 16:54:10 +11:00
Damien George	bc7d264e86	stm32/sdcard: Use high speed mode for SD transfers on H5/H7/N6. ... This doubles the speed of SD card transfers. Signed-off-by: Damien George <damien@micropython.org>	2026-01-14 16:44:23 +11:00
Damien George	e48b98537f	stm32/main: Enable all AHB5 GRP1 clocks in low power mode. ... The main functional change here is to make sure that the SDMMC1/2 clocks are enabled in low power mode; they were not previously enabled for SD card use, only WLAN. It doesn't hurt to unconditionally enable the clocks in low power, like all the other peripherals. Signed-off-by: Damien George <damien@micropython.org>	2026-01-14 16:42:57 +11:00
FH	07540a8fd1	esp32/modesp32: Update available RTC pins for ESP32C6. ... According to https://wiki.seeedstudio.com/xiao_esp32c6_getting_started/#demo1-deep-sleep-with-external-wake-up and https://docs.espressif.com/projects/esp-idf/en/stable/esp32c6/api-reference/peripherals/gpio.html ESP32C6 supports RTC/LP on Pins 0-7. Signed-off-by: FH <fh3095-gitcommit@yahoo.com>	2026-01-13 14:45:10 +11:00
Elvis Pfutzenreuter	da6a18ffe0	esp32/esp32_rmt: Update FIXME on RMT module. ... Signed-off-by: Elvis Pfutzenreuter <elvis.pfutzenreuter@gmail.com>	2026-01-13 14:33:33 +11:00
Damien George	85a15f995c	esp32/machine_uart: Change default UART(1) pins on ESP32 with SPIRAM. ... SPIRAM usually uses GPIO 9 and 10 on ESP32, so don't use them as default UART pins. Fixes issue #18544. Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 13:43:02 +11:00
Damien George	b105677ac4	esp32/machine_pin: Rename legacy CONFIG_ESP32_SPIRAM_SUPPORT option. ... Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 13:43:02 +11:00
Damien George	e52916daaa	github/workflows: Add check for misspelling of "MicroPython". ... "MicroPython" is sometimes misspelled as "Micropython". Add an explicit check for that as part of CI (note that codespell doesn't consider case when spelling, hence the need to do it this way). Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 12:51:44 +11:00
Damien George	3a487c32ba	all: Fix spelling of Micropython -> MicroPython. ... Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 12:51:31 +11:00
dependabot[bot]	83996f057f	github/workflows: Bump actions/cache from 4 to 5. ... Bumps [actions/cache](https://github.com/actions/cache) from 4 to 5. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](https://github.com/actions/cache/compare/v4...v5) --- updated-dependencies: - dependency-name: actions/cache dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>	2026-01-13 11:30:01 +11:00
Alessandro Gatti	b87d73f2e9	tools/mpy_ld.py: Write architecture flags to output natmod if needed. ... This commit lets "tools/mpy_ld.py" store architecture flags in generated MPY files if explicitly requested, like "mpy-cross" does. To achieve this, a new command-line option ("--arch-flags") was added to receive the architecture flags value, accepting the same arguments' format as "mpy-cross", and performing the same input validation. The rest of the MPY toolchain was also modified to let the user pass the arch flags to standard native module makefiles. Given that there's already a well-established "ARCH" argument, "ARCH_FLAGS" was chosen to pass the optional flags to "mpy_ld.py". Finally, documentation was updated to mention the new variable. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-11 09:22:13 +01:00
Alessandro Gatti	0fd084363a	tools/mpy_ld.py: Optimise MPY trampoline sizes if possible. ... This commit changes the way native modules' trampoline code sequence is emitted, generating an optimised code sequence to jump to the entry symbol. Turns out the address of the entry point is known even before the segments are built and the address of the entry point doesn't change when processing the module on anything but Xtensa. This means that the jump trampoline doesn't have to be a dummy fixed-size block to be filled in later, but it can be the final trampoline being used in the module. On Xtensa the address of the symbol is offset by the length of the literals pool, but since the trampoline being generated is always the shortest one said platform is left alone (handling distances greater than 128KiB would require more extensive changes). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-09 14:46:52 +11:00
Alessandro Gatti	21e4c036af	tools/ci.sh: Update Unix/x86 target to Ubuntu 24.04 LTS. ... This commit updates the Unix/x86 target's environment to use the latest available LTS version of Ubuntu Linux (24.04). Since the new OS updated some key components used in the CI build process, a few modifications have been made to the setup and build procedure. The new OS introduces a CPython version that is known to not be compatible with a subset of settrace tests, so even though the OS is updated, an older version of CPython is installed as part of the image provisioning process. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-07 12:04:41 +01:00
Jeff Epler	26c16969ab	github/workflows: Use same Ubuntu for code_size as ports_esp32. ... Also make sure code_size runs when the esp32 port source changes, as per the other ports that are built as part of code_size. Signed-off-by: Jeff Epler <jepler@unpythonic.net> Signed-off-by: Damien George <damien@micropython.org>	2026-01-07 11:26:07 +11:00
Alessandro Gatti	31fe865460	tools/ci.sh: Use CPython 3.11 for Unix/RV64. ... This commit forces the installation of CPython 3.11 instead of CPython 3.12 in the OS image for Unix/RV64 CI jobs. CPython 3.12 is not compatible with settrace tests, but it is the CPython version that is installed by default in "ubuntu-latest" (which is Ubuntu 24.04 LTS right now). Updating the base image for the RV64 tests also disabled settrace tests to work around its incompatibility, however turns out there is a way to force CI to set up a base OS image with an arbitrary CPython version. Now the RV64 CI jobs are now going to be executed using CPython 3.11, and thus the settrace tests can be removed from the ignore list. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-07 00:09:54 +11:00
Alessandro Gatti	16844bb027	tools/ci.sh: Update Unix/Arm target to Ubuntu 24.04 LTS. ... This commit updates the Unix/Arm target's environment to use the latest available LTS version of Ubuntu Linux (24.04). Since the new OS updated some key components used in the CI build process, a few modifications have been made to the setup and build procedure. Newer QEMU's sysroot location changed and the "static" variant of the QEMU emulators has to be used to make binfmt work, and updated autotools versions split some macros into an optional package that has to be manually installed. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-07 00:09:54 +11:00
Alessandro Gatti	6dea53cb27	tools/ci.sh: Update Unix/MIPS target to Ubuntu 24.04 LTS. ... This commit updates the Unix/MIPS target's environment to use the latest available LTS version of Ubuntu Linux (24.04). Since the new OS updated some key components used in the CI build process, a few modifications have been made to the setup and build procedure. Newer QEMU's sysroot location changed and the "static" variant of the QEMU emulators has to be used to make binfmt work, and updated autotools versions split some macros into an optional package that has to be manually installed. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-07 00:09:54 +11:00
Jeff Epler	569ebaa828	tools/ci.sh: Put embedding build rules in ci.sh. ... To make this CI step runnable locally by `ci.sh`. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-05 12:01:59 +11:00
Jeff Epler	6c7edce76c	github/workflows: Add esp32 to code size report. ... Add an esp32 build (specifically ESP32_GENERIC) to the CI code-size check. Multiple new steps must be done to prepare for building esp32, and caching is used to speed up both the install of the IDF and the build process. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-05 11:40:08 +11:00
Jeff Epler	0aa6115aac	github/workflows: Introduce and use ci_esp32_idf_ver helper. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-01-05 11:39:25 +11:00
dependabot[bot]	99c59fabdb	github/workflows: Bump actions/cache from 4 to 5. ... Bumps [actions/cache](https://github.com/actions/cache) from 4 to 5. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](https://github.com/actions/cache/compare/v4...v5) --- updated-dependencies: - dependency-name: actions/cache dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>	2026-01-04 19:54:29 +11:00
dependabot[bot]	2cb41ff97b	github/workflows: Bump actions/upload-artifact from 4 to 6. ... Bumps [actions/upload-artifact](https://github.com/actions/upload-artifact) from 4 to 6. - [Release notes](https://github.com/actions/upload-artifact/releases) - [Commits](https://github.com/actions/upload-artifact/compare/v4...v6) --- updated-dependencies: - dependency-name: actions/upload-artifact dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>	2026-01-04 17:30:33 +11:00
iabdalkader	1947759c94	renesas-ra/boards/ARDUINO_PORTENTA_C33: Increase TinyUSB queue size. ... Default queue size is too small that it overflows easily if debugging printfs are enabled. Increase TinyUSB event queue size to 128. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 17:17:13 +11:00
Kwabena W. Agyeman	75eb197f9d	alif/boards/OPENMV_AE3: Make JTAG pins controllable as GPIOs. ... Allows user control of JTAG pins on the AE3 which are exposed via the B2B header. Signed-off-by: Kwabena W. Agyeman <kwagyeman@live.com>	2026-01-04 17:06:19 +11:00
iabdalkader	1174dda519	alif/boards/OPENMV_AE3: Update romfs partition size. ... Update romfs partition to reflect the latest layout. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 16:57:48 +11:00
iabdalkader	ab5f47c54d	alif/ospi_flash: Remove workaround for P10_7 OSPI pinmux issue. ... P5_6 doesn't have that alt function, and only has 7 alt functions. This workaround was never really needed, it was introduced in DFP because the wrong P10_7 alt function was used, in original DFP sources. This has been removed from DFP starting with 1.3.4, so remove it here also. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 16:50:11 +11:00
Alessandro Gatti	2554e4172f	alif/Makefile: Enable job server support on Ubuntu LTS. ... This commit modifies the Alif port's Makefile to propagate to child make tasks the number of parallel jobs to run. On Ubuntu LTS 24.04, building the Alif port passing a parallel jobs number to make's command line will result in the command emitting this warning: make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. And building the two cores' firmware images using one compile job at a time instead of the number provided to the command line. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 16:42:50 +11:00
Alessandro Gatti	678dbd26f8	alif/Makefile: Do not hardcode the python interpreter name. ... This commit fixes a build issue occurring on systems where the Python 3.x interpreter isn't aliased to 'python' but has a different name (usually `python3'). The main Linux distribution where this occurs is Ubuntu LTS, where the Python 3.x interpreter is available as 'python3' since at least two major versions (so since about five years now). MicroPython's makefile environment setup file ('py/mkenv.mk') already defines a variable called '$(PYTHON)' that defaults to 'python3', so the Makefile was updated to use that instead of hardcoding the interpreter name. Without these changes, building a firmware image on Ubuntu LTS fails with this error: make: python: No such file or directory make: *** [Makefile:95: build-ALIF_ENSEMBLE/firmware.toc.bin] Error 127 This also allows overriding the interpreter name to something else if there's the need to perform tests with different interpreter versions or the like. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 16:42:50 +11:00
Alessandro Gatti	3980a0c01f	py/misc: Add byte-swapping macros. ... This commit adds byte-swapping macros for 16-, 32-, and 64-bit values. Modern compilers are usually able to detect manual byte/endian swaps and will generate optimised code sequences if they know how to do that. However, in certain situations it may be helpful to let the compiler generate an optimised sequence if it doesn't recognise the pattern. Most compilers provide built-in byte swap operations for 16, 32, and 64 bit values, accessed via "__builtin_bswap<size>", but if those are not available a fallback implementation is provided. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 12:13:34 +11:00
Alessandro Gatti	d468ccce62	extmod/modopenamp: Rework trace buffer setup procedure. ... This commit reworks the setup procedure for the OpenAMP trace buffer, used by the libmetal framework to provide cross-core logging data if needed. Before these changes, the buffer was provided by MicroPython, as a fixed size 128 bytes chunk that was accidentally put into the .rodata section, making it not usable for its intended purpose. Now, a buffer placed in .bss with a default size of 128 bytes is provided by MicroPython unless chosen otherwise. A user-chosen buffer pointer can be provided to MicroPython using the MICROPY_PY_OPENAMP_TRACE_BUF preprocessor definition. If what MicroPython provides by default is fine, the buffer size can be overridden with a new value for the MICROPY_PY_OPENAMP_TRACE_BUF_LEN preprocessor definition instead. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 12:02:59 +11:00
Alessandro Gatti	11861e96a9	nrf/modules/machine/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The "pin_obj_t" structure, holding pin information, had an unused word-sized field ("pull") that isn't used by any of the board definitions, yet it takes up space in each pin structure being compiled in the final firmware image. Images for all available boards were built successfully with this change, so there should be no unwanted issues arising from shrinking that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	6572ce84c9	samd/pin_af: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	31deee9060	rp2/machine_pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The data type used to store the QSTR name of both regular and alternate function pins ("machine_pin_obj_t" and "machine_pin_af_obj_t") is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	fb8ecaecf5	renesas-ra/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	8bda61a3af	mimxrt/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The data type used to store the QSTR name of alternate function pins ("machine_pin_af_obj_t") is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Regular pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	049cdd0dd3	cc3200/mods/pybpin: Reduce footprint of AF pin structures. ... This commit performs a minor change to the "pin_af_t" structure, changing the data type used to store alternate function pin name QSTRs in order to have a smaller impact on the .rodata section of the firmware. The data type used to store the QSTR name of the pin is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Other pin-related structures in the port that also store QSTRs do not benefit from a narrower data type, as their members are mostly word-aligned and thus the linker is forced to insert padding bytes between entries. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
robert-hh	610552010d	nrf: Add support for VfsRom filesystem. ... The implementation uses the object based capabilities, which avoids complication about different flash block sizes. The ROM partition is placed between the text and writable filesystem sections, and the latter size is unchanged. VfsRom sizes are: - NRF51x22: 12K - NRF52832: 128K - NRF52840: 256K - NRF9160: 256K Use frozen `_boot.py` to set up and mount the filesystem, replacing a mix of C-Code and Python code. The mkfs part has been simplified to save code. Tested with Microbit and Arduino Nano Connect. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 15:28:02 +11:00
robert-hh	cee950673d	renesas-ra: Add support for VfsRom filesystem. ... The ROM partition is taken from the last part of the flash text section, so the existing writable filesystem is untouched. VfsRom file system sizes: - EK_RA4M1: 12K - RA4M1_CLICKER: 12k - EK_RA4W1: 64k - EK_RA6M1: 64k - EK_RA6M2: 256k - VK_RA6M5: 384k - ARDUINO_PORTENTA_C33: 256k Tested with Weact RA4M1 core board with EK_RA4M1 firmware and EK_RA6M2. Signed-off-by: robert-hh <robert@hammelrath.com> Signed-off-by: Damien George <damien@micropython.org>	2026-01-02 15:24:22 +11:00
robert-hh	c07b178dbd	samd: Add support for VfsRom filesystem for SAMD21 and SAMD51. ... The flash driver is update to support the new `mp_vfs_rom_ioctl()` function, and the buffer protocol is added to `samd_flash_type` (it is needed for VfsRom on devices without external flash). For SAMD21, only boards with external SPI flash have VfsRom enabled, due to size constraints. For such boards, the VfsRom filesystem has a size of 12k and is placed at the upper end of the flash. The `onewire`, `ds18x20` and `dht` drivers have been removed from frozen bytecode as they can be placed into the VfsRom files when needed. For SAMD51, the VfsRom filesystem has a default size of 64k for SAMD51x19 and 256K for SAMD51x20. It is placed at the upper end of the flash. For boards with external SPI flash, the code size is reduced from 496K to 432K. If that is not sufficient for some boards or configurations, it can be changed for each board or board variant. Tested with ADAFRUIT_ITSYBITSY_M0_EXPRESS, ADAFRUIT_ITSYBITSY_M4_EXPRESS, SPARKFUN_SAMD51_THING_PLUS, SEEED_XIAO_SAMD21, SAMD_GENERIC_D51X19, and SAMD_GENERIC_D51X20. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 15:23:49 +11:00
robert-hh	b857a9131e	mimxrt: Add support for VfsRom filesystem. ... The default size for the ROM partition is 256k, and it is placed in flash between the text and writable vfs sections. Its size can be changed in `mpconfigboard.mk` by defining `MICROPY_HW_ROMFS_BYTES` to a different value, but it must not be smaller than a single sector. The MIMXRT1170_EVK and SEEED ARCH MIX ROMFS boards use a larger size of 512kB. ROMFS support is disabled for MIMXRT1050_EVKB due to issues with Hyperflash. The extents of the ROM partition are defined by the linker-level symbols `_micropy_hw_romfs_part0_start` and `_micropy_hw_romfs_part0_size`, following existing ports. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 14:48:16 +11:00
Alessandro Gatti	d871c970c0	tools/ci.sh: Run natmod tests as part of CI for Unix/RV64. ... This commit updates the test procedure for the Unix port targeting the RV64 platform to also run the battery of native modules test that is part of the QEMU port. Unfortunately this required a few changes to the CI setup since the Unix port was still using an older version of Ubuntu LTS than the RISC-V natmods build infrastructure expects. Updating the OS version just for the RV64 Unix target brought a couple of issues when building the code (an extra package is now needed to let FFI build) and running tests (QEMU binfmt support requires a new setup). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-01 17:08:56 +01:00
Alessandro Gatti	d44685e103	unix/mpconfigport: Enable natmod loading for RISC-V builds. ... This commit lets the Unix port load native modules when built for both RV32 and RV64. Since RV64 doesn't have a native emitter, the new native code loading configuration settings have been used to allow such a feature. RV32 is fully supported by the native emitter framework but the emitter wasn't enabled for Unix builds (and therefore no natmod support). RV64 builds have been tested on QEMU and on a MilkV-Duo board, and whilst RV32 isn't really tested, its native code loading functionality is routinely tested both on bare-metal QEMU and on microcontroller boards. Since the code for RV64 under Unix and RV32 is essentially the same, having RV64 working is a strong indicator that RV32 will work too. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-01 16:35:23 +01:00
Alessandro Gatti	9af103300f	qemu: Enable loading natmods on RV64. ... This commit lets the QEMU port's VIRT_RV64 board load and run native modules, via the appropriate configuration changes in mpconfigport.h. Now the CI test job for the QEMU/RV64 port can also run natmods and see whether they actually work, so the CI tasks script has been updated to bring RV64 to parity with RV32 as far as CI checks go. Documentation was also updated, since now all supported boards in the QEMU port should be able to run natmod tests. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-01 16:35:02 +01:00
Alessandro Gatti	e939d3ec76	tools/mpy_ld.py: Add RV64 natmod support. ... This commit adds the ability to compile native modules for the RV64 platform, using "rv64imc" as its architecture name (eg. "make ARCH=rv64imc" should build a RV64 natmod). The rest of 64-bits relocations needed to build a native module are now implemented, and all sample native modules build without errors or warnings. The same Picolibc caveats on RV32 also apply on RV64, thus the documentation was updated accordingly. RV64 native modules are also built as part of the CI process, but not yet executed as the QEMU port is not yet able to load and run them. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-30 18:18:42 +01:00
Alessandro Gatti	1f67289a9e	tools/mpy_ld.py: Fix handling of R_RISCV_TLSDESC_LOAD_LO12. ... This commit fixes handling of the R_RISCV_TLSDESC_LOAD_LO12 RISC-V object file relocation, fixing a couple of mistakes in its usage. The condition check for TLS relocations presence and their rejection when found in object files skipped checking for R_RISCV_TLSDESC_LOAD_LO12 relocations, which is part of the set of unsupported TLS relocations and thus needing an object file rejection. Interestingly, that relocation name constant was actually misspelled in the file - since it was skipped in the list of relocations being checked its wrong name did pass unnoticed until now. This is not a critical change as the linker will raise an error about an unknown relocation type rather than report a more descriptive message to the user, but it's nice to have nonetheless. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-30 17:56:02 +01:00
Alessandro Gatti	984027b88e	tools/mpy_ld.py: Fix R_RISCV_GOT32_PCREL handling. ... This commit fixes the implementation of the R_RISCV_GOT32_PCREL RISC-V relocation type when linking native modules for RV32IMC. The previous implementation of R_RISCV_GOT32_PCREL ended up not being fully updated when the initial RV32 support was checked in. Said relocation was not emitted in the sample natmods that ship with the MicroPython source tree, and since they're the testbed for CI jobs that should check RV32 natmod support, this was not caught. On the other hand, nobody raised an issue about this problem yet, so hopefully it didn't cause much trouble. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-30 17:56:02 +01:00
Alessandro Gatti	8fb848f3aa	mpy-cross/mpconfigport: Explicitly disable native code loading. ... This commit makes use of the new native code loading changes to provide a test bed for a target with the native compiler framework available but without no code loading capabilities. mpy-cross already fully disables native code loading, however those changes do not really propagate anywhere outside `py/persistentcode`. Recent changes in the code loading framework actually touch the core code in a few more places, but no default CI target is configured to run with the new native code loading defines switched off. Given that mpy-cross doesn't really need to load code anyway, it is a good target for setting up a configuration that goes a bit deeper when it comes to disabling code loading. Since mpy-cross is built several times during the CI process, it can be repurposed as an early warning system for issues related to these new changes. Normal operation should not be affected in any way. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:51:56 +01:00
Alessandro Gatti	7173ddee5f	tests/run-natmodtests.py: Explicitly open prelude file. ... This change lets the natmod test runner report status information on session end if a prelude script file is chosen. The script serialises its input data as part of the end of session reporting data, but since the prelude file is not a serialisable object serialisation would fail (it's a file handle as far as the argument container structure is aware). Now the file is explicitly open by the script rather than relying on argparse's file handle argument class wrapper. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:51:56 +01:00
Alessandro Gatti	14152e7f49	nrf/main: Allocate executable memory when needed. ... This commit lets the nRF port use the new MICROPY_PERSISTENT_CODE_LOAD_NATIVE configuration entry. The nRF port needs a special procedure to allocate memory used to hold executable native code. This functionality was gated behind the presence of a native emitter and thus its inclusion condition had to be updated. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:51:56 +01:00