888 Commits

Author	SHA1	Message	Date
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
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
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
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	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
Damien George	3f796b687b	tools/autobuild: Make firmware destination directory configurable. ... The destination directory for the firmware built by `autobuild.sh` is currently hard-coded to `/tmp/autobuild-firmware-$$`. Now that there are many boards built by this script, the `/tmp` partition can run out of space. This commit makes the destination directory configurable via the `MICROPY_AUTOBUILD_DEST` environment variable. Signed-off-by: Damien George <damien@micropython.org>	2025-12-04 00:33:04 +11:00
Matt Trentini	bfacf821f4	rp2/boards/WEACTSTUDIO_RP2350B_CORE: Add board.pinout. ... This adds an ANSI-rendered pinout for the WeAct Studio RP2350B Core board. Signed-off-by: Matt Trentini <matt.trentini@gmail.com>	2025-12-01 16:05:49 +11:00
Vincent1-python	50a06b6404	esp32/boards/ESP32_GENERIC_P4: Add board definition for ESP32P4. ... Includes a base variant with LAN, and C5_WIFI and C6_WIFI variants with LAN, WiFi and BLE. And builds this board in the esp32 CI, to cover the P4 support. Signed-off-by: Vincent1-python <pywei201209@163.com> Signed-off-by: Angus Gratton <angus@redyak.com.au> Signed-off-by: Damien George <damien@micropython.org>	2025-12-01 13:08:52 +11:00
Damien George	2fbd72ad78	tools/ci.sh: Build all stm32 MCU families in stm32 CI functions. ... Currently the CI for stm32 only tests building about half of the available MCU families. This commit adds the remaining families to the stm32 CI jobs. Signed-off-by: Damien George <damien@micropython.org>	2025-11-30 15:26:41 +11:00
Damien George	f63e64f4bc	tools/ci.sh: Install latest ARM toolchain for stm32 CI. ... This is needed to build Cortex-M55 (STM32N6) based boards. Signed-off-by: Damien George <damien@micropython.org>	2025-11-30 15:26:41 +11:00
Alessandro Gatti	6b661ca3f6	github/workflows: Test mpy-cross debug emitter. ... This commit adds a new workflow step to the CI, to test the debug emitter provided by mpy-cross. The checks being done are limited to make sure that the debug emitter does not crash and emits opcodes for a simple test file that is guaranteed to work for all configurations. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-27 14:18:04 +11:00
Alessandro Gatti	4633d2a037	tools/ci.sh: Add zsh and fish shell completion support. ... This commit adds custom command completion functions for both the zsh and fish shell. The behaviour for those new completions follow the existing completion for the bash shell, including the way to generate the completion alias (with appropriately named command line switches). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-26 13:50:39 +11:00
Anson Mansfield	c9af4e1a7e	tools/mpy-tool.py: Add Compiler Explorer JSON output. ... This commit adds a `--json` option to `mpy-tool.py`, in order to generate Compiler-Explorer-compatible JSON annotation information for the bytecode disassembly. Some of this information might be theoretically possible to parse out from the text itself, but not all of it is, e.g. disambiguating child references with non-unique simple names. Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-11-24 12:40:39 +11:00
Damien George	336d463eb2	tools/ci.sh: Build ESP32_GENERIC_C5 as part of esp32 CI. ... Signed-off-by: Damien George <damien@micropython.org>	2025-11-17 13:57:48 +11:00
Damien George	2a5c5093ec	tools/cc1: Fix ruff lint check with list length. ... Signed-off-by: Damien George <damien@micropython.org>	2025-11-05 12:46:29 +11:00
Christian Clauss	509207c9d0	tools/cc1: Apply ruff formatting to cc1 script. ... Running `ruff format tools/cc1` picks up `tools/cc1` which is a Python file that does not have a .py file extension. Signed-off-by: Christian Clauss <cclauss@me.com> Signed-off-by: Damien George <damien@micropython.org>	2025-11-05 12:42:42 +11:00
Andrew Leech	9bb266e311	stm32/usb: Add support for using TinyUSB stack. ... This commit adapts the stm32 port to allow switching from STM USB stack to TinyUSB stack. Using TinyUSB improves consistancy with other MicroPython ports and brings in the ability to use the runtime USB definition support recently added to other TinyUSB based ports. By default the existing STM USB stack is used. TinyUSB can be enabled in a board configuration with: #define MICROPY_HW_TINYUSB_STACK (1) Or, it can be enabled from the command line with: make -C ports/stm32 CFLAGS_EXTRA='-DMICROPY_HW_TINYUSB_STACK=1' Signed-off-by: Andrew Leech <andrew@alelec.net>	2025-10-31 10:52:11 +11:00
Alessandro Gatti	b255224d09	tools/mpy-tool.py: Add architecture flags to disassembly output. ... This commit extends "mpy-tool.py"'s disassembly output of a given MPY file (triggered via the "-d" command line option) to include newly added fields. Now the target architecture for the chosen MPY file is printed out to screen in human-readable format and, if present, architecture-specific flags. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 18:31:05 +02:00
Alessandro Gatti	a6bc1ccbe5	py/persistentcode: Add architecture flags compatibility checks. ... This commit extends the MPY file format in a backwards-compatible way to store an encoded form of architecture-specific flags that have been specified in the "mpy-cross" command line, or that have been explicitly set as part of a native emitter configuration. The file format changes are as follows: * The features byte, previously containing the target native architecture and the minor file format version, now claims bit 6 as a flag indicating the presence of an encoded architecture flags integer * If architecture flags need to be stored, they are placed right after the MPY file header. This means that properly-written MPY parsers, if encountering a MPY file containing encoded architecture flags, should raise an error since no architecture identifiers have been defined that make use of bits 6 and 7 in the referenced header byte. This should give enough guarantees of backwards compatibility when this feature is used (improper parsers were subjected to breakage anyway). The encoded architecture flags could have been placed at the end, but: * Having them right after the header makes the architecture compatibility checks occur before having read the whole file in memory (which still happens on certain platforms as the reader may be backed by a memory buffer), and prevents eventual memory allocations that do not take place if the module is rejected early * Properly-written MPY file parsers should have checked the upper two bits of the flags byte to be actually zero according to the format specification available right before this change, so no assumptions should have been made on the exact order of the chunks for an unexpected format. The meaning of the architecture flags value is backend-specific, with the only common characteristic of being a variable-encoded unsigned integer for the time being. The changes made to the file format effectively limit the number of possible target architectures to 16, of which 13 are already claimed. There aren't that many new architectures planned to be supported for the lifetime of the current MPY file format, so this change still leaves space for architecture updates if needed. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 16:32:53 +02:00
iabdalkader	15401a3ae8	tools/mpremote: Fix exception when using pts. ... Setting RTS/DTR raises "Inappropriate ioctl for device" for pts devices. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2025-10-24 17:31:51 +11:00
Daniël van de Giessen	be4892097e	tools/autobuild: Use same length Git hash abbreviation in file names. ... This makes the version string consistent with the one used in code, see commit 9e89c752cb. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-10-23 16:23:56 +11:00
Jeff Epler	6f4fd6aed9	tools/ci.sh: Use a better default reference ref in code_size_build. ... Now the default reference commit is the first parent of the selected commit, instead of the first parent of HEAD. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-23 16:16:44 +11:00
Jeff Epler	3bea897073	tools/metrics.py: Tersely show the commits in the size report. ... This will show a line for both the reference and comparison, e.g., Reference: zephyr/boards: Add PocketBeagle 2 rev A1… [00a926e99e] Comparison: metrics: Tersely show the commi… [merge of c7ac411e22] When the comparison is a merge commit (as it is during CI) the second parent of that commit is shown instead. This will be helpful when checking which revision of the code size report comment on a PR corresponds to which revision of the code. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-23 16:15:26 +11:00
Jeff Epler	eac81de4e0	tools/ci.sh: Cross build 64-bit windows on Linux. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-23 15:07:17 +11:00
Damien George	b1802eb0e1	tools/ci.sh: Init micropython-lib submodule for zephyr build. ... The zephyr port doesn't have a Makefile so can't run `make submodules`. Instead they must be explicitly initialized. Signed-off-by: Damien George <damien@micropython.org>	2025-10-22 10:16:20 +11:00
Angus Gratton	8995a291e0	tools/ci: Fix typo of pipefail. ... Regression from 449866cb0a. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-08 17:03:52 +11:00
Jeff Epler	13d49751f4	tools/ci.sh: Re-add IGNORE_ERRORS to ci_code_size_build. ... It was removed (possibly inadvertently) in 4c55b0879b Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:09:41 +11:00
Jeff Epler	61988ee8fa	tools/ci.sh: Return to old branch after code_size_build. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:09:34 +11:00
Jeff Epler	7778e78843	tools/metrics.py: Allow pre_cmd to set up environment. ... This is a necessary step to allow cleanly building the xtensa port during CI, as it's undesirable to apply the esp-idf environment settings while building other ports. PRE_CMD_<letter> can be used to override the command, or add a command if not otherwise specified. Note that <letter> is case sensitive. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:09:12 +11:00
Jeff Epler	f982158f42	tools/ci.sh: Let code_size_build be customized via environment. ... For instance, to compare HEAD to origin/master on only the minimal x86 build, use PORTS_TO_CHECK=m REFERENCE=origin/master tools/ci.sh code_size_build Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:55 +11:00
Jeff Epler	2c34497bd1	tools/metrics.py: When cleaning also clean mpy-cross. ... Changes of interest could be in emitted mpy frozen files. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:46 +11:00
Jeff Epler	449866cb0a	tools/ci.sh: Exit with error if zcat fails during ci_esp8266_setup. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:41 +11:00
Jeff Epler	0224b99863	tools/ci.sh: Add and use new ci_code_size_report function. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:28 +11:00
Jeff Epler	77729fe3f7	tools/ci.sh: Manipulate pipefail better. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:21 +11:00
Jeff Epler	fef414eca4	tools/metrics.py: Use all CPUs during comparison builds. ... Don't simply hard-code a parallelism of 3 for the build. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-08 15:08:12 +11:00
Angus Gratton	fb2b638ba0	docs: Label table columns as "CPython output" and "MicroPython output". ... Abbreviating these doesn't really save space in the docs, as the code blocks in the next row are always wider than the column headings. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-03 23:29:11 +10:00
Damien George	b2871e0d0a	tools/ci.sh: Enable the full test suite for unix minimal variant. ... With all the preceeding improvements to the test suite, it's now possible to just run `make VARIANT=minimal test` -- which is equivalent to just `./run-tests.py` -- on the unix minimal variant. Signed-off-by: Damien George <damien@micropython.org>	2025-10-02 00:37:29 +10:00
Damien George	957e6b05e6	tools/ci.sh: Enable all possible tests on zephyr CI. ... With the recent improvements to the test suite, and fixes for `pow`, the full test suite can now be run (and appropriate tests will be automatically skipped). Signed-off-by: Damien George <damien@micropython.org>	2025-10-01 23:59:15 +10:00
Angus Gratton	3dd8073c29	tools/mpremote: Workaround ESP DTR/RTS reset quirk at disconnect time. ... The problem with ESP board spurious reset happens at disconnect time on Windows (clearing DTR before RTS triggers a reset). Previous workarounds tried to detect possible ESP boards and apply the correct DTR and RTS settings when opening the port. Instead, we can manually clear RTS before closing the port and thereby avoid the reset issue. Opening the port can keep the default behaviour (RTS & DTR both set). close() is called from a finally block in the mpremote main module (via do_disconnect()) - so this should always happen provided the Python process isn't terminated by the OS. One additional workaround is needed to prevent a spurious reset first time a Silicon Labs CP210x-based ESP board is opened by mpremote after enumeration. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-01 09:10:38 +10:00
Jeff Epler	e3ef682156	github/workflows: Add 32-bit OBJ_REPR_B CI job. ... This showed up some interesting errors (hopefully all fixed now). Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-09-28 23:24:54 +10:00