17973 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
garywill	3d2eb3b8e9	ports: Guard calls to machine_*_deinit_all() with #if where appropriate. ... To allow these features to be properly disabled.	2025-11-19 16:56:03 +11:00
Peter Harper	4e79698a99	rp2/pendsv: Fix PendSV_Handler dispatch check when threading enabled. ... If MICROPY_PY_THREAD is set, PendSV_Handler acquires a mutex and calls the dispatch functions. If pendsv_schedule_dispatch is called by a higher priority interrupt while the mutex is acquired by PendSV_Handler it's possible for the dispatch to not be triggered. Add a check for dispatch calls at the end of PendSV_Handler once the mutex has been released. Fixes issue #18365. Signed-off-by: Peter Harper <peter.harper@raspberrypi.com>	2025-11-19 16:35:10 +11:00
Ihor Nehrutsa	094437686f	tests/extmod_hardware/machine_encoder.py: Use target_wiring for encoder. ... Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>	2025-11-19 16:10:12 +11:00
Ihor Nehrutsa	d980bbd237	tests/extmod_hardware/machine_encoder.py: Fix initial rotation count. ... ESP32 requires initial high levels of the channels before starting the count, in order to have 4 pulse for the first rotation. Also add tests for encoder phases x2 and x4. Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>	2025-11-19 16:02:31 +11:00
Damien George	f3804c6589	tests/import: Remove .py.exp files where they match CPython. ... Signed-off-by: Damien George <damien@micropython.org>	2025-11-19 13:26:51 +11:00
Damien George	8b7d9819b7	tests/import: Make import_override and pkg7 tests behave under CPython. ... Signed-off-by: Damien George <damien@micropython.org>	2025-11-19 13:26:51 +11:00
Jos Verlinde	787d85e000	tests/extmod/machine_i2s_rate.py: Adjust pins when running on ESP32-C3. ... Changed the pin numbers used for the I2S rate testing as the pin numbers used were incompatible with the limited GPIO pins availalbe on the ESP32-C3, causing the tests to fail. Signed-off-by: Jos Verlinde <jos_verlinde@hotmail.com>	2025-11-19 13:19:32 +11:00
Angus Gratton	713f9dcd22	esp32: Fix USB Zero Length Packet issue with patched tinyusb. ... Temporarily switch from the espressif TinyUSB component to a MicroPython fork where this fix has been cherry-picked: https://github.com/hathach/tinyusb/pull/3293 This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-19 12:12:54 +11:00
Angus Gratton	4f193132d2	esp32: Remove dependency on esp_tinyusb. ... Instead, depend directly on espressif/tinyusb component (which is otherwise transitively included via esp_tinyusb). Turns out esp_tinyusb builds a bunch of source files with symbols that conflict with our tinyusb symbols (i.e. descriptors_control.c). This only works because nothing in MicroPython causes the linker to include the esp_tinyusb.a library, however in order to override the dcd_int_handler (in following commit) this caused the linker to pull this library in and break the build. There's also a problematic header skew - TinyUSB component was building with the tusb_config.h file from esp_tinyusb component, but we have our own tusb_config.h file in shared/tinyusb. The changes in parent commit allow us to build the TinyUSB component with our tusb_config.h header. User-facing impacts are: - Can no longer override USB VID & PID via sdkconfig, have to set MICROPY_HW_USB_VID/PID instead (changes applied in this commit). - esp32 boards will have the same USB serial number as other ports (i.e. based on the hardware MAC address, not hard-coded). Side effects include: - CFG_TUD_DWC2_SLAVE_ENABLE is now set, DMA mode is disabled. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-19 12:12:54 +11:00
Angus Gratton	a435e4ecfd	esp32: Take global dependencies out of mpconfigport.h. ... This is necessary so the ESP-IDF TinyUSB component can include py/mpconfig.h, but is also a good design goal (less creep of symbols into unrelated parts of the code). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-19 12:12:54 +11:00
Angus Gratton	4766f5680e	esp32: Fix USB deinit/reinit path via soft reset. ... Fixes problems with USB-CDC state after soft reset if USBDevice has been active with the default USB-CDC driver also enabled. This also brings ESP32 behaviour in line with RP2 and other ports, where boot.py is executed before the runtime USB device is initialised. This allows setting up a custom USB device in boot.py. There is still a bug here, because calling tud_disconnect() doesn't cause any UNPLUG or BUS_RESET events to arrive from TinyUSB - which means the USB device state stays out of sync until we call mp_usbd_init() again... This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-19 10:21:01 +11:00
Angus Gratton	8d05a8fc8a	shared/tinyusb/mp_usbd: Reorder the mp_usbd_init/deinit functions. ... Not a functional change, but makes it easier to see that mp_usbd_init() is available regardless of whether MICROPY_HW_ENABLE_USB_RUNTIME_DEVICE is set. Also adds a no-op inline mp_usbd_deinit() implementation, which means both a port's calls to mp_usbd_init()/deinit() can both be guarded on the same MICROPY_HW_ENABLE_USBDEV. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-19 10:16:48 +11:00
Daniël van de Giessen	4441fd655c	lib/littlefs: Update LittleFS to v2.11.2. ... Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-11-17 14:39:38 +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
yuan_mo	30c74fc3b4	esp32/boards: Add ESP32_GENERIC_C5 board definition. ... Signed-off-by: yuan_mo <2286087148@qq.com>	2025-11-17 13:57:38 +11:00
yuan_mo	713f40d204	esp32: Add support for ESP32-C5 SoCs. ... Signed-off-by: yuan_mo <2286087148@qq.com> Signed-off-by: Damien George <damien@micropython.org>	2025-11-17 13:56:49 +11:00
Elvis Pfutzenreuter	2a3b9b0b4b	esp32/esp32_rmt: Update RMT module to use the new RMT API. ... The current `esp32.RMT` class uses a legacy API from ESP-IDF 4.x. The ESP-IDF 5.x offers a new API, which is overall better, and easier to implement the RX side in the future. This commit updates the module and the documentation, preserving the current MicroPython RMT API as much as possible. The bitstream RMT implementation was updated as well, since ESP-IDF does not allow firmware to reference legacy and new APIs at the same time (it resets right after boot with an error message, even if neither module is imported). The documentation is updated accordingly. Signed-off-by: Elvis Pfutzenreuter <elvis.pfutzenreuter@gmail.com>	2025-11-17 10:45:19 +11:00
Patrick Van Oosterwijck	27544a2d81	esp32/boards: Add Silicognition ManT1S board definition. ... New board planned to be launched on Crowd Supply in late 2025. ESP32-based core module with IEEE 802.3cg 10BASE-T1S Single Pair Ethernet networking and power distribution over data lines. Signed-off-by: Patrick Van Oosterwijck <patrick@silicognition.com>	2025-11-13 14:35:05 +11:00
Meir Armon	b4ab3a893c	esp32/modesp32: Add esp32.wake_on_gpio() function. ... Some boards support waking up via GPIO pins, but this is not currently supported by MicroPython. This commit adds support for waking with GPIO in a similar interface to waking with ext0, ext1, touch and ulp. This commit adds documentation for this new function as well. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-11-13 14:27:30 +11:00
Angus Gratton	2762fe680a	tests/serial_test.py: Allow up to 2 seconds between bytes. ... Only a problem when UART TX is also enabled and goes first (i.e. esp32 port) as sending 16384 bytes in one go triggers the timeout. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-11-06 12:26:43 +11:00
Damien George	10b7dfd9f2	top: Include tools/cc1 in ruff search path. ... So that pre-commit and CI will check formatting and linting. Signed-off-by: Damien George <damien@micropython.org>	2025-11-05 12:46:55 +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
John Smith	1e5da2642c	shared/runtime: Set exit code according to the SystemExit exception. ... Add abort setup code `nlr_set_abort` to the standard runtime executor. This makes the standard runtime respond to abort signal without any further modifications. - When aborted, the program exits with 137 exit code (configurable, same as posix sig abort), to differentiate from a normal shutdown. - When exited by exception/crash, the program will exit with exit code 1 (configurable). - When exited by exception KeyboardInterrupt, the program will exit with exit code 130 (configurable, same as posix sig int). - When exited with a exit code (from Python environment), this code is propagated. When a different object is passed, exit code is set to 1 and the value printed, to be consistent with Python docs: https://python.readthedocs.io/en/latest/library/exceptions.html#SystemExit Signed-off-by: John Smith <jsmith@jsmith.cz>	2025-11-04 16:47:19 +11:00
Yanfeng Liu	4f2f520dc2	unix/modtime: Add type casting for mktime return value. ... This adds type casting to avoid build errors on certain systems. Signed-off-by: Yanfeng Liu <yfliu2008@qq.com>	2025-11-04 16:22:29 +11:00
Alessandro Gatti	2b5669d193	py/emitnative: Generate shorter RV32 code for exception handling. ... This commit lets the native emitter generate shorter code when clearing exception objects on RV32. Since there are no direct generic ASM functions to set a specific immediate to a local variable, the native emitter usually generates an immediate assignment to a temporary register and then a store of that register into the chosen local variable. This pattern is also followed when clearing certain local variables related to exception handling, using MP_OBJ_NULL as the immediate value to set. Given that at the moment MP_OBJ_NULL is defined to be 0 (with some other spots in the native emitter that leverage that fact when checking the state of the variables mentioned earlier), and that the RV32 CPU has a dedicated register that is hardwired to read 0, a new method to set local variables to MP_OBJ_NULL is introduced. When generating RV32 code, the new macro will skip the intermediate register assignment and directly uses the X0/ZERO register to set the chosen local variable to MP_OBJ_NULL. Other platforms will still generate the same code sequence as before this change. This is a followup to 40585eaa8f. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-04 02:21:30 +01:00
Anson Mansfield	e0a9b7023b	py/objcode: Remove mp_obj_code_t.lnotab field from v2 preview. ... This field exists to cache the lnotab field removed from v2 in #17639 by ddf2c3afb1, and is now unused. Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-11-03 14:02:55 +11:00
Alessandro Gatti	3cd95dda64	py/asmrv32: Generate better comparison sequences. ... This commit changes the sequences generated for not-equal and less-than-or-equal comparisons, in favour of better replacements. The new not-equal comparison generates a sequence of equal size but without the burden of a jump to set the output value, this also had the effect of reducing the size of the code generator as only two opcodes need to be generated instead of three. The less-than-or-equal sequence, on the other hand, is actually two bytes shorter and does not contain any jumps. If Zcb opcodes can be used for performing the final XOR operation then two more bytes could be saved on each comparison. The same remarks about having a shorter generator due to two opcodes being generated instead of three still applies here. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-03 13:53:45 +11:00
Alessandro Gatti	a1684ad2c1	py/asmrv32: Refactor register-indexed load/store emitters. ... This commit shortens register-indexed load/store emitter functions, by reusing integer-indexed equivalent operations as part of the sequence generation process. Before these changes, register-indexed load/store emitters would follow two steps to generate the sequence: generate opcodes to fix up the register offset to make it point to the exact position in memory where the operation should take place, and then perform the load/store operation itself using 0 as an offset from the recalculated address register. Since there is already a generic optimised emitter for integer-indexed load/stores, that bit of code can be reused rather than having an ad-hoc implementation that is tailored to operate on an offset of 0. Removing the custom emitter code in favour of calling the general integer-indexed emitter saves around 150 bytes without any changes in the emitter behaviour (generating the same opcode sequence and making use of future improvement in that emitter too). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-03 13:21:46 +11:00
Alessandro Gatti	385e4f3d0c	py/emitinlinerv32: Refactor load/store opcodes validation. ... This commit minimises the amount of code required to perform validation of load/store opcodes, streamlining their validation and serialisation. Load/store opcodes used to be handled as a special case due to how its peculiar syntax yields parse node arguments that cannot be handled by the regular validation and serialisation functions. The changes in this commit attempt to reduce the amount of special code needed for those opcodes to its bare minimum, by removing the special opcode handling step, merging the validation and serialisation pass for the combined offset + base register operand, and integrate said changes in the existing argument handling structure. That allowed to rework the special operand parsing function to make it smaller, and remove the code that performed the special case validation and emitted the opcode. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-03 12:39:01 +11:00
Alessandro Gatti	3da529554d	py/emitinlinerv32: Refactor opcode arguments validation. ... This commit simplifies the way arguments are validated when processing RV32 inline assembler opcodes. Opcode arguments were handled in two separate passes, one that performed a pure validation (with an early rejection in case of errors), and another that converted the parse node into a serialised value but without any error checking. Considering that the validation pass effectively performed the parse node conversion and then discarded its result once validated, it is preferable to hold onto the serialised result to reuse it later at opcode generation time. With these changes, those two passes are merged into one single operation when applicable (basically any opcode that doesn't use an integer offset), removing a fair amount of duplicate code. The size savings should be around half a kilobyte, with no other changes in the assembler's behaviour. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-11-03 12:39:01 +11:00
Andrew Leech	27b7bf36a3	stm32/usb: Add VBUS sensing configuration for TinyUSB on F4/F7. ... TinyUSB's `dwc2_phy_init()` only sets the PWRDWN bit in the GCCFG register but doesn't configure VBUS sensing, which is required for the DWC2 USB controller to detect host connection on STM32F4 and STM32F7 series. Without VBUS sensing configured, USB devices fail to enumerate on these platforms when using the TinyUSB stack, while the legacy STM32 USB stack works because it includes this configuration. This commit adds VBUS sensing configuration in `pyb_usbd_init()` for TinyUSB mode on STM32F4/F7: - When VBUS detect pin is configured (typically PA9): Enable "B device" VBUS sensing (USB_OTG_GCCFG_VBUSBSEN) - When no VBUS pin: Force VBUS valid (USB_OTG_GCCFG_NOVBUSSENS) Tested on: - NUCLEO-F429ZI: USB now enumerates successfully (CDC + MSC) - NUCLEO-H563ZI: No regression (STM32H5 uses different register layout) Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-10-31 10:54:33 +11:00
Andrew Leech	faae8e73ef	stm32/usb: Add TinyUSB Mass Storage support. ... Implements USB MSC functionality for STM32 port when using TinyUSB stack, supporting both internal Flash and SD card storage mediums. Signed-off-by: Andrew Leech <andrew@alelec.net>	2025-10-31 10:54:07 +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
Andrew Leech	6b0e1c2701	shared/runtime/pyexec: Remove legacy USB IRQ enable code. ... It's very STM32 USB stack specific and doesn't generalise well to other ports. So remove it. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-10-31 10:51:07 +11:00
ennyKey	4efc5e12b9	stm32/machine_uart: Implement TX/RX inversion parameter for UART on H7. ... Implemented the keyword-only parameter `invert` for the `UART.init` method in accordance with the docs: - added constants `UART.INV_TX` and `UART.INV_RX` - added the new `invert` keyword parameter to the `uart_init` function - adapted the `uart_init` call - added invert setting to `uart_print` output The feature applies only to STM32H7. Signed-off-by: ennyKey <ennyKey@fn.de>	2025-10-30 12:30:26 +11:00
Yuuki NAGAO	e58425a513	stm32/boards: Add NUCLEO-U5A5ZJ-Q board support. ... This change adds NUCLEO-U5A5ZJ-Q support to the STM32 port. NUCLEO-U5A5ZJ-Q: https://www.st.com/ja/evaluation-tools/nucleo-u5a5zj-q.html This board use STM32U5A5ZJ: https://www.st.com/ja/microcontrollers-microprocessors/stm32u5a5zj.html Signed-off-by: Yuuki NAGAO <wf.yn386@gmail.com>	2025-10-30 07:38:27 +09:00
Yuuki NAGAO	d20d19783d	stm32: Add STM32U5 support. ... This change adds STM32U5 support to the STM32 port. STM32U5A5ZJ: https://www.st.com/ja/microcontrollers-microprocessors/stm32u5a5zj.html Signed-off-by: Yuuki NAGAO <wf.yn386@gmail.com>	2025-10-30 07:38:18 +09:00
Andrew Leech	673524f55d	lib/stm32lib: Update N6, U5 & WB. ... Added STM32N6 with HAL1.2.0 Added STM32U5 with HAL1.8.0 Updated STM32WB from HAL1.10.0 to HAL1.23.0 Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-10-27 13:44:56 +11:00
Craftzman7	6773051b5a	rp2/boards: Add missing RP2350 RISC-V variants. ... There are multiple RP2350 boards missing RISC-V builds. Some were missing entries in their `board.json` or a CMake file altogether. This commit fixes them. Signed-off-by: Craftzman7 <zezetta@icloud.com>	2025-10-25 23:25:40 +11:00
robert-hh	72e67f0f02	samd/machine_bitstream: Tune ticks for SAMD51 and set pin to output. ... Changes in this commit: - Change ticks overhead value for SAMD51. The value was too large and thus timing was quite bad. At 120Mhz it's now within +/- 30ns. - Set the pin to output mode. That way, all Pin identifiers are accepted as argument, not only Pin objects. Tested with ItsyBitsy M4 and M0 boards. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-10-25 22:56:47 +11:00
Jeff Epler	2e74f0b6be	py/objlist: Make a small code size optimization in mp_quicksort. ... While clarifying the meaning of the arguments to `mp_quicksort`, I noticed that by pre-adjusting the `head` argument similar to what was already done for `tail`, code size could be saved by eliminating repeated calculation of `h + 1`. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-25 22:53:56 +11:00
Alessandro Gatti	a080585ffd	tests/ports/qemu: Add arch flags MPY import checks test. ... This commit introduces a test file (along with its necessary data) to test MPY files pass/reject cases, due to either mismatching architecture flag requirements or unneeded "no-flags" values set. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 19:13:15 +02:00
Alessandro Gatti	849c67bcdc	tests/run-tests.py: Pass auto-detected architecture flags to mpy-cross. ... This commit lets "run-tests.py" use the encoded architecture flags provided by the interpreter when invoking "mpy-cross". If architecture flags are detected, they're mapped into the necessary strings needed by "mpy-cross"'s "-march-flags" argument, so that tests will always use all available extensions reported by the target. Currently this is limited to the RV32 platform, as it is the only one that is making use of this facility as of now. This also lets the QEMU port remove forced arguments to "mpy-cross" when running the test suite. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 19:13:15 +02:00
Alessandro Gatti	331a5c46aa	tests/micropython: Extend MPY import tests for RV32. ... This commit extends the "micropython/import_mpy_native_gc" test with a pre-built serialised MPY file built for RV32. Before this commit, the test was skipped on said platform due to the lack of a known-good MPY file to test the import procedure against. Now the test is executed as part of the general CI test checks. The MPY file's Makefile script was also updated to cater for modern Linux environments where the required Python interpreter's command name isn't "python", but "python3" instead (this occurs when using the past two LTS Ubuntu releases for example). This is the same kind of change made in 31a008c6e2. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 19:13:15 +02:00
Alessandro Gatti	430837996b	py/modsys: Add architecture flags to MicroPython metadata. ... This commit adds the currently supported architecture flags value as the upper part of "sys.implementation._mpy". This had the side effect of perturbing quite a bit of testing infrastructure and invalidating documentation related to MPY files. To make the test suite run successfully and keep the documentation in sync the following changes have been made: * The target info feature check file now isolates eventual architecture flags and adds them as a separate field * The test runner now picks up the new architecture flags field, reports it to STDOUT if needed and stores it for future uses * Relevant test files for MPY files import code had to be updated to mask out the architecture flags bits in order to perform correctly * MPY file format documentation was updated to show how to mask off and properly display the architecture flags information. This works out of the box if the flag bits can fit in a smallint value once merged with the MPY file header value. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 19:13:15 +02:00
Alessandro Gatti	3e2b41f8f6	mpy-cross/main: Parse raw integer arch flags values too. ... This commit extends "mpy-cross"'s parsing of the architecture flags value command line, allowing raw integer values as well as flag strings. Integers can be represented as either decimal, binary, or hexadecimal values, using the usual C language prefixes to mark non-base 10 values. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 19:13:15 +02: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	64971f1a65	py/persistentcode: Add architecture flags check for RV32 platforms. ... This commit introduces the MPY architecture flags checking code specific for the RV32 target, currently checking for the only additional extension that is supported by the runtime: Zba. The warnings inside "mpy-cross" have also been removed since now there is a way to reject incompatible MPY files at runtime. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-10-24 18:30:55 +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