18181 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
stijn	e08e3d796c	tests/run-tests.py: Output consistent test file paths. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but since that path is used to: - display which tests run - record which tests ran in the results.json - craft the filename for the .exp/.out file for failed tests it is desirable to always use the same file path irregardless of how the user passed the path. In practice this means that all forms of running our own tests like: >python ./run-tests.py -i extmod >python ./run-tests.py -d extmod >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod will now consistently all display the tests like pass extmod/time_time_ns.py FAIL extmod/some_failing_test.py and produce output files like results/extmod_some_failing_test.py.exp results/extmod_some_failing_test.py.out instead of displaying/using the exact path as passed. For external tests, meaning not in the tests/ directory, we also want to be consistent so there the choice was made to always use absolute paths. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	7b9163372d	tests/cmdline: Make tests succeed irregardless of invocation path. ... Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	b8098df3a7	tests/run-tests.py: Use normal discovery if tests dir passed explicitly. ... Scan the --test-dirs argument for the main tests directory being passed and if so do the same thing as if running from within that main test directory. In practice this makes the following (which used to counterintuitively try and fail to run the .py files in the tests/ directory itself) >python micropython/tests/run-tests.py -d micropython/tests do the same thing as >cd micropython/tests >python ./run-tests.py which is logical and convenient. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:20:17 +11:00
stijn	ff4d4bfade	tests/run-tests.py: Make skip logic work irregardless of test path. ... Test file paths which get passed to the run_tests function can be absolute or relative and with or without leading slash in the latter case, depending on the arguments to run-tests.py, but the skip_tests list with tests to skip only contains relative paths so using simple string equality comparison easily leads to false negatives. Compare the full absolute path instead such that it doesn't matter anymore in which form the tests are passed. Note: - use realpath to resolve symlinks plus make the comparison case insensitive on windows - the test_file passed to run_one_test is not altered by this commit, such that when the user inputs relative paths the tests are also still displayed with relative paths - likewise the test_file_abspath is not modified because functions like run_micropython rely on it having forward slashes In practice this means that it used to be so that the only forms of running tests for which the skip_tests lists actually worked were: >python ./run-tests.py >python ./run-tests.py -d extmod whereas it now works consistently so also for these invocations, which in the end all point to the exact same path: >python ./run-tests.py -d ./extmod >python ./run-tests.py -d ../tests/extmod >python ./run-tests.py -d /full/path/to/tests/extmod These examples used to not skip any of the tests in the extmod/ directory thereby leading to test failures. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
stijn	2ab88c3d58	tests/run-tests.py: Add an argument for showing which tests would run. ... This is convenient when trying to figure out the correct values for --include/--exclude/--test-dirs/... arguments. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
stijn	412ffd4b32	tools/codeformat.py: Use input files when formatting python code. ... Signed-off-by: stijn <stijn@ignitron.net>	2026-02-26 16:18:49 +11:00
Jeff Epler	2631b0614c	tests/cpydiff: Add a section for throwing incomplete exceptions. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Jeff Epler	c199ba9f71	py/objexcept: Check for incompletely constructed exceptions. ... This turns the reproducer into a sensible-ish crash: TypeError: exceptions must derive from BaseException Closes: #17117 Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Jeff Epler	aaa30abbcd	py/objtype: Expose mp_native_base_init_wrapper_obj. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Jeff Epler	20500558f8	tests/micropython: Add a test for throwing incomplete exception. ... This is a reproducer for #17117. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2026-02-26 16:15:54 +11:00
Damien George	6dbabc9267	tests/extmod/os_urandom.py: Add test for os.urandom. ... Signed-off-by: Damien George <damien@micropython.org>	2026-02-24 23:36:51 +11:00
robert-hh	6b8bcb6a29	extmod/modos: Raise an error at a negative argument of os.urandom(). ... Fixes issue #18825. Signed-off-by: robert-hh <robert@hammelrath.com>	2026-02-24 23:36:02 +11:00
robert-hh	2e62b56bdd	ports: Refactor os.urandom(). ... Factor out mp_os_urandom() of each port into extmod/modos.c, which then calls the port-specific function mp_hal_get_random(). Move mp_hal_get_random() to mphalport where suitable. At the MIMXRT and SAMD it is left in modos.c, since there are different implementation depending on the MCU family. At the ALIF, ESP32, CC3200 and RP2 port the file modos.c was removed, since it was empty after moving mp_hal_get_random(). Tested for the cc3200, esp32, esp8266, mimxrt, nrf, rp2, samd, stm32 and unix ports. Compiled for the alif and the renesas port. Signed-off-by: robert-hh <robert@hammelrath.com>	2026-02-24 23:36:02 +11:00
Jos Verlinde	fdb7c0f747	docs/develop/writingtests: Document parameters of run_test.py. ... The aim of this commit is to clarify the command line options available. While they are available as well as in the CLI with --help, it's useful to document them and provide a few examples. Signed-off-by: Jos Verlinde <jos_verlinde@hotmail.com>	2026-02-24 18:48:21 +11:00
iabdalkader	b006bb0dff	extmod/vfs_reader: Process pending events during file reads. ... Call `mp_event_handle_nowait()` in the VFS reader buffer refill path so that pending scheduled events (USB task, network poll, etc.) get processed during long-running import/parse/compile operations. Without this, importing a large Python module from the filesystem blocks for too long causing TinyUSB event queue to overflow. For example, on renesas-ra, running a script that imports iperf3 via mpremote run, asserts, most likely due to SOF interrupts not getting processing: queue_event at lib/tinyusb/src/device/usbd.c:382 dcd_event_handler at lib/tinyusb/src/device/usbd.c:1318 dcd_event_sof at lib/tinyusb/src/device/dcd.h:237 dcd_int_handler at tinyusb/src/portable/renesas/rusb2/dcd_rusb2.c:964 <signal handler called> disk_ioctl at extmod/vfs_fat_diskio.c:125 validate at lib/oofatfs/ff.c:3359 f_read at lib/oofatfs/ff.c:3625 file_obj_read at extmod/vfs_fat_file.c:75 mp_stream_rw at py/stream.c:60 mp_reader_vfs_readbyte at extmod/vfs_reader.c:59 next_char at py/lexer.c:174 mp_lexer_to_next at py/lexer.c:713 mp_parse at py/parse.c:1167 Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-02-24 18:46:01 +11:00
Alessandro Gatti	43a4914fe1	tests/micropython: Add a test for checking viper value clobbering. ... This commit introduces a test that should check whether viper load or store operations won't clobber either the buffer address or the index value being used. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-24 18:42:53 +11:00
Alessandro Gatti	424ae08680	py/asmrv32: Do not clobber index register on viper load/store. ... This commit lets the native emitter preserve the value of the index register when performing register-indexed loads or stores for halfword or word values on RV32. The original code was optimised too aggressively to reduce the generated code's size, using compressed opcodes that alias the target register to one of the operands. In register-indexed load/store operations, the index register was assumed to be allocated somewhere safe, but it was not always the case. To solve this, now all halfword and word register-indexed operations will use REG_TEMP2 to store the scaled index register. The size penalty on generated code varies across operation sizes and enabled extensions: - byte operations stay the same size with or without Zba - halfword operations will be 2 bytes larger without Zba, and will stay the same size with Zba - word operations will be 4 bytes larger without Zba, and 2 bytes larger with Zba There is also a minor firmware footprint increase to hold the extra logic needed for conditional register clobbering, but it shouldn't be that large anyway. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-24 18:42:53 +11:00
Alessandro Gatti	b46f9f503f	py/asmthumb: Do not clobber index register on viper load/store. ... This commit lets the native emitter preserve the value of the index register when performing register-indexed loads or stores of halfword or word values on Thumb. The original code was optimised too aggressively for a register-starved architecture like Thumb, and the index value in the sequence to generate was assumed to be allocated somewhere safe. This is valid on other architectures, but not on Thumb. To solve this, load operations do clobber a temporary register that should be safe to use, REG_TEMP2, to store the scaled register offset. REG_TEMP2's value is only used within the scope of a single ASM API instruction. Save operations unfortunately use a register that is aliased to REG_TEMP2, since they need to have three values in registers to perform the operation. This means the index register needs to be pushed to the stack before performing the scale + store operation, and then popped from the stack. That's a 4 bytes penalty on each store and a minor speed hit on generated code (plus a minor footprint increase of the firmware image). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-24 18:42:53 +11:00
Daniël van de Giessen	f02dc6dd8f	esp32/esp32_rmt: Release GIL while waiting for TX done. ... When the timeout parameter of `esp32.RMT.wait_done()` is set to a non-zero value, the underlying `rmt_tx_wait_all_done` blocks (it passes the timeout to `xQueueReceive`). Thus we should release the GIL so that other MicroPython threads are not blocked from running. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2026-02-24 18:38:51 +11:00
Michel Le Bihan	158cbd6065	rp2: Switch all RNG sources from ROSC to pico_rand. ... Replace the custom rosc_random_u8()/rosc_random_u32() implementation with the pico_rand API from the Pico SDK. The RP2040 datasheet notes that ROSC "does not meet the requirements of randomness for security systems because it can be compromised", and the current 8-bit LFSR conditioning is not a vetted algorithm under NIST SP 800-90B. pico_rand uses various hardware RNG sources depending on the available platform (including the RP2350 hardware TRNG) and is officially supported and maintained as part of the Pico SDK. This changes os.urandom(), the mbedTLS entropy source, the PRNG seed, and the lwIP random function to all use pico_rand, and removes the custom ROSC random functions from main.c. Signed-off-by: Michel Le Bihan <michel@lebihan.pl>	2026-02-24 18:34:30 +11:00
Paul Grayson	9e2df2da29	rp2/boards/POLOLU_ZUMO_2040_ROBOT: Remove header file. ... The Pololu Zumo 2040 Robot is supported in pico-sdk now so we should not include the header file here anymore, similarly to other boards. This is necessary for future changes from the SDK to be reflected in MicroPython builds. Signed-off-by: Paul Grayson <paul@pololu.com>	2026-02-24 18:32:35 +11:00
Antonio Galea	c1ed5f7697	lib/libhydrogen: Update to latest release. ... Fixes a build issue on newer Zephyr versions. Signed-off-by: Antonio Galea <antonio.galea@gmail.com>	2026-02-24 18:18:14 +11:00
Damien George	1ab9b66a48	zephyr/mpconfigport: Remove duplicate builtins.open definition. ... It's already provided because `MICROPY_PY_IO` is enabled. Tested on `bbc_microbit_v2`, there is now only a single open. Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 13:27:49 +11:00
Damien George	1e164be085	powerpc/mpconfigport: Remove dummy builtins.open function. ... The function does nothing so it's better that it doesn't exist at all. Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 13:27:49 +11:00
Damien George	de7e3607b0	pic16bit/mpconfigport: Remove dummy builtins.open function. ... The function does nothing so it's better that it doesn't exist at all. Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 13:27:49 +11:00
Damien George	88343302ae	nrf/mpconfigport: Remove duplicate help and open from builtins module. ... The `builtins.help` function is automatically included when `MICROPY_PY_BUILTINS_HELP` is enabled, which is true for this port. The `builtins.open` function is automatically included when `MICROPY_PY_IO` is enabled, which is true when `MICROPY_VFS` is enabled on this port. If `MICROPY_MBFS` is enabled instead of the VFS then `open` must be explicitly provided. Tested on: - ARDUINO_NANO_33_BLE_SENSE: now has only a single `help` and `open` - MICROBIT: now has only a single `help` and `open` - MICROBIT with MICROPY_MBFS enabled: `help` and `open` both still exist and `open` works with mbfs Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 13:27:49 +11:00
Damien George	9dea789f5f	webassembly: Convert port to use new event waiting functions. ... The webassembly port does not have anything that needs polling when waiting for events, so it can just use the default (empty) definitions of `MICROPY_INTERNAL_WFE` and `MICROPY_INTERNAL_EVENT_HOOK`. Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 13:17:35 +11:00
Thomas Propst	43cfbbb779	stm32: Support more stm32g4 variants. ... - `timer.c` - `TIM_ENTRY(7, ...)` sets IRQ based on specific STM32G4 part - `system_stm32.c` - Support parts without external clock - `boards/NUCLEO_G474RE/mpconfigboard.h` - Explicitly enable `MICROPY_HW_RTC_USE_LSE` Signed-off-by: Thomas Propst <tom.propst@gmail.com>	2026-02-23 13:12:38 +11:00
Alessandro Gatti	d278d6b3d8	stm32/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-02-23 13:10:47 +11:00
Thomas Propst	7e1f754ca2	stm32/boards/stm32l072xz.ld: Correct comment in linker script. ... Header comment said "STM32F072xZ" for the STM32L072xZ linker script. Signed-off-by: Thomas Propst <tom.propst@gmail.com>	2026-02-23 13:09:27 +11:00
Yuuki NAGAO	fd009e6c4f	stm32/boards: Add WeAct STM32U585 board support. ... This change adds WeAct STM32U585 board support to the STM32 port. WeAct STM32U585: https://github.com/WeActStudio/WeActStudio.STM32U585Cx_CoreBoard This board use STM32U585CI: https://www.st.com/ja/microcontrollers-microprocessors/stm32u585ci.html Signed-off-by: Yuuki NAGAO <wf.yn386@gmail.com>	2026-02-23 13:07:59 +11:00
Yuuki NAGAO	746e2c985a	stm32: Update STM32U5 suppport. ... Add USB FS configuration to enable for STM32U5. Signed-off-by: Yuuki NAGAO <wf.yn386@gmail.com>	2026-02-23 13:07:58 +11:00
mdaeron	f94980677c	stm32/boards: Add UARTs to NUCLEO F746ZG and NUCLEO F439ZI. ... Adds the following UARTs: 1, 4, 5, 7, 8, assigned to pins that were not otherwise assigned. Signed-off-by: mdaeron <mathieu@daeron.fr>	2026-02-23 13:06:54 +11:00
Damien George	b89246159d	stm32: Convert port to use new event waiting functions. ... Convert the stm32 port from the old `MICROPY_EVENT_POLL_HOOK` macro to use the new `mp_event_wait_xxx()` functions in conjunction with `MICROPY_INTERNAL_WFE`. This change should be functionally equivalent to the existing behaivour because `mp_event_wait_ms()` and `mp_event_wait_indefinite()` are equal to `mp_handle_pending(true); __WFI()`, which is what `MICROPY_EVENT_POLL_HOOK` was. Note that the `CYW43_EVENT_POLL_HOOK` macro needed to be overridden, otherwise it would just call `mp_event_handle_nowait()` which would create power hungry busy loops. Signed-off-by: Damien George <damien@micropython.org>	2026-02-23 12:54:39 +11:00
Fin Maaß	a8b71559cf	shared/readline: Handle \r and \n correctly as a newline. ... The old code was only handling `\r` and ignoring `\n`, which is a problem for systems that only send `\n` as a newline. This commit handles it better, supporting both characters. Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>	2026-02-12 14:32:50 +11:00
Fin Maaß	97219553ed	zephyr: Add support for RISC-V RV32IMC native code emitter. ... Add support for RISC-V RV32IMC native code emitter in the zephyr port. It will be automatically enabled by default, but can be overridden by defining `MICROPY_EMIT_RV32` and/or `MICROPY_EMIT_INLINE_RV32`. Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>	2026-02-11 11:23:05 +11:00
Fin Maaß	6ae08eaf75	zephyr/modzsensor: Add additional sensor type constants. ... Add additional sensor type constants. Commonly used by power and current measurement sensors. Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>	2026-02-10 23:55:01 +11:00
Fin Maaß	05c2f88d6e	zephyr/main: Put GC heap in noinit linker area. ... By putting the heap in the noinit area instead of the bss area, zephyr won't memset it to zero during start. This improves startup time, in particular if the heap is very big. The system heap of zephyr is also in the same section. Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>	2026-02-10 23:51:54 +11:00
Fin Maaß	92d64ca5a7	zephyr/Kconfig: Resolve build problem with multiple FatFs libs. ... Zephyr and MicroPython both have a variant of FatFs, but having both enabled leads to build fails. Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>	2026-02-10 23:46:03 +11:00
robert-hh	588fa2b388	extmod/modlwip: Always set the lwip_socket_ioctl() return value. ... If the return value is set only when certain condition are true, the compiler sometimes raises an error. Signed-off-by: robert-hh <robert@hammelrath.com>	2026-02-10 15:58:44 +11:00
Alessandro Gatti	b7d7a26c8f	py/emitinlinextensa: Refactor handling of selected narrow opcodes. ... This commit migrates handling of certain narrow (ie. 16-bits) opcodes from a per-opcode dedicated code snippet to the existing table-driven opcode handler. The final ESP8266 firmware binary is 64 bytes shorter, without any change in the existing behaviour and with a reduced source code lines count too. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-10 14:17:25 +11:00
Alessandro Gatti	9dcad25de6	py/emitinlinextensa: Add inline assembler support for windowed cores. ... This commit introduces support for writing inline assembler code snippets when targeting Xtensa cores that use register windows (eg. the whole ESP32 family). Opcodes support is still limited to what the ESP8266 supports (as in, LX3 cores opcodes), however each LX core version is guaranteed to support all previous versions' opcodes as well. The ESP32 does not have the inline assembler enabled by default, following the existing expectations when it comes to firmware footprint. Since now emitted functions may have one of two possible exit sequences, the L32I test had to be fixed. It would return the word containing the L32I opcode itself, but the upper 8 bits of the word came from the following opcode - which can change depending on the exit code sequence. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-02-07 18:36:22 +11:00
stijn	dc91fa6548	py/misc: Fix truncating cast to char. ... Explicitly specify the wanted cast otherwise this results in warning C4244: '=': conversion from 'unichar' to 'char', possible loss of data when building with msvc with most warnings enabled. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-07 18:16:54 +11:00
stijn	39d777cb86	py/gc: Differentiate between root and subtree pointers for debug log. ... This is more informative when debugging possible gc issues. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-07 17:41:26 +11:00
stijn	eaf03bd68c	py/gc: Trace all marked heads in debug log. ... Otherwise only those in gc_mark_subtree get logged, which is incomplete and hence not very useful. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-07 17:40:45 +11:00
stijn	1ebeee09c1	windows: Compile printf.c for the msvc port. ... This provides the DEBUG_printf definition which is needed when defining MICROPY_DEBUG_VERBOSE, and is consistent with all other ports. Signed-off-by: stijn <stijn@ignitron.net>	2026-02-07 17:40:08 +11:00
Damien George	a2aad14506	py/objtuple: Remove unused mp_obj_tulpe_del function. ... Since the parent commit, this is now unused. Signed-off-by: Damien George <damien@micropython.org>	2026-02-07 17:09:22 +11:00
Damien George	3332e1ec0b	py/objzip: Adjust zip iter code to not use mp_obj_tuple_del. ... This is the only location in the code base that uses `mp_obj_tuple_del()`, so we can reduce code size by reworking the iter code not to use that function. The zip iter implementation should now have slightly better GC behaviour: it only allocates the return tuple if needed, instead of allocating it and then freeing it when the zip iterator is exhausted. Signed-off-by: Damien George <damien@micropython.org>	2026-02-07 17:08:18 +11:00
Daniël van de Giessen	71866edc13	py/stream: Use detailed error strings for TLS sockets. ... Both mbedTLS and axTLS have support for producing more detailed error strings. However, these are not used if the error is raised in stream protocol functions (read/write/ioctl). This commit adds support for more detailed error messages from streams. Under the hood it's using a new MP_STREAM_RAISE_ERROR ioctl request to pass the error code back to the stream implementation which can raise a more detailed error. If the ioctl is not implemented, we fall back to the old behaviour and raise an OSError with the error code. Currently the detailed messages are only implemented for TLS sockets since those already had helper functions for raising detailed exceptions, but can be easily implemented in any other stream. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2026-02-07 16:34:20 +11:00
Daniël van de Giessen	633a27b0a3	extmod: Ensure stream ioctl's are a no-op for unknown requests. ... An ioctl should not have any side effects if the request is unknown. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2026-02-07 16:33:21 +11:00