1384 Commits

Author	SHA1	Message	Date
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
Jeff Epler	007f127a61	all: Simplify mp_int_t/mp_uint_t definition. ... Assuming proper C99 language support, we can select "the int type as big as a pointer" (most of the time) or "the 64-bit int type" (nanboxing with REPR_D), and then define everything else automatically. This simplifies port configuration files. And the types can still be overridden if needed. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-10-23 15:12:28 +11:00
Damien George	0e1d857f80	README: Define and describe the port Tier levels. ... MicroPython has quite a few ports now (20 of them), but not all are in the same stage of development. This commit attempts to define port Tier levels and assign a Tier to each of the existing ports. The main aim here is to set expectations for the level of support and development each port gets. And also lower the bar of entry for new ports so they can enter at a low Tier and gradually rise up to Tier 1. See prior art here: - https://peps.python.org/pep-0011/ - https://doc.rust-lang.org/rustc/target-tier-policy.html - https://docs.zephyrproject.org/latest/project/release_process.html#hardware-support-tiers Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-23 11:23:17 +11:00
Ned Konz	7090fc5dd6	zephyr: Mount all disks and flash partition, formatting if necessary. ... Existing C code in `main.c` only mounts a flash filesystem if one exists, and doesn't do anything if the 'storage' partition is not formatted. This commit moves the mounting logic from `main.c` to frozen code using `modules/_boot.py` and adds the formatting of a previously unformatted partition if the mount fails. Every available disk (in the newly added `DiskAccess.disks` tuple) will be mounted on separate mount points (if they're formatted), and the 'storage' flash partition (if any) will be mounted on /flash (and will be formatted as LFS2 if necessary). Also, `sys.path` will be updated with appropriate 'lib' subdirectories for each mounted filesystem. The current working directory will be changed to the last `DiskAccess.disk` mounted, or to /flash if no disks were mounted. Then `boot.py` and `main.py` will be executed from the current working directory if they exist. Thanks to @VynDragon for the logic in `zephyr/zephyr_storage.c`. Signed-off-by: Ned Konz <ned@metamagix.tech>	2025-10-22 10:22:48 +11:00
Ned Konz	c6a78515fb	zephyr/modzsensor: Add set/get sensor attributes to zsensor. ... This commit adds `Sensor.attr_set()` and `Sensor.attr_get_*()` methods that are necessary to set various sensor attributes if they haven't been set statically in the device tree. This is needed, for example, because the LSM6DS3TR-C sensor on the XIAO BLE NRF52840 SENSE board will not work with `zsensor` because it doesn't have any default configuration for sampling frequency. Various `SENSOR_ATTR_*` constants from `zephyr/incude/zephyr/drivers/sensor.h` have been added as `ATTR_*` constants in the `zsensor` module. Signed-off-by: Ned Konz <ned@metamagix.tech>	2025-10-13 12:06:24 +11:00
Ned Konz	d42a301afd	zephyr/machine_adc: Add ADC support. ... This commit adds support for ADC peripherals in the Zephyr port. As is typical for Zephyr, the ADC channel setup is done in the devicetree (typically using an overlay). This code requires ADC channels to be listed in the io-channels property of the zephyr,user root node. Signed-off-by: Ned Konz <ned@metamagix.tech>	2025-10-13 11:39:59 +11:00
Damien George	ddd6ca75be	docs/develop/porting: Use mp_cstack_init_with_sp_here in docs. ... Signed-off-by: Damien George <damien@micropython.org>	2025-10-10 14:49:09 +11:00
Angus Gratton	3ec8b9a77c	all: Replace legacy name with MicroPython and MPy as applicable. ... With the aim of getting consistency, and removing the need to learn an additional term, replace uses of uPy/uPython with MPy/MicroPython. Rule of thumb was to use "MPy" abbreviation where "CPy" is used nearby, but the full word MicroPython otherwise. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-10-04 00:19:40 +10:00
Jeff Epler	adf6319884	docs/develop/gettingstarted: Document %.sz and %.pp targets. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-09-26 14:38:08 +10:00
Jeff Epler	1921d22b35	docs/develop/gettingstarted: Document the additional unix test targets. ... The docs in the port README are nice but don't appear at docs.micropython.org. Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-09-26 14:38:08 +10:00
Jeff Epler	70c4ffa770	tools/ci.sh: Add --bash-completion option. ... Signed-off-by: Jeff Epler <jepler@unpythonic.net>	2025-09-26 14:36:59 +10:00
Jos Verlinde	10b3d96b60	docs/README: Document sphinx-autobuild for local preview. ... Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>	2025-09-26 00:07:58 +10:00
Jos Verlinde	74270df9ac	docs/README: Update doc build dependency. ... The docs were changed in c304046384 to require sphinx_rtd_theme. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>	2025-09-26 00:07:58 +10:00
Jos Verlinde	2a03ade02c	docs/library/os: Document dupterm_notify function. ... Closes issue #17799. Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>	2025-09-26 00:07:55 +10:00
Chris Webb	b9523fd58c	docs: Document the cross-port Timer hard= option. ... Update the main machine.Timer specification, and any references to hard/soft interrupts in port-specific documentation. There is a separate copy of the machine.Timer documentation for the pyboard, so update that too to keep everything consistent. Signed-off-by: Chris Webb <chris@arachsys.com>	2025-09-25 23:59:24 +10:00
Alessandro Gatti	1b92bda5b8	mpy-cross: Add RISC-V RV64IMC support in MPY files. ... MPY files can now hold data to be run on RV64IMC. This can be accomplished by passing the `-march=rv64imc` flag to mpy-cross. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-09-19 11:11:31 +10:00
Jeff Epler	be1a1eb7ac	tools/ci.sh: Make this script runnable as command. ... This makes it easier to run a sequence of ci steps locally. A help message is also provided. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-09-18 14:13:12 +10:00
Jeff Epler	c304046384	docs: Always use sphinx_rtd_theme. ... Without this, the wy-alert block pushed all the content to the right, making the locally built pages nearly illegible. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-09-16 10:39:46 +10:00
Jeff Epler	f0c6f16b9e	all: Remove Python 2.7 support. ... Python 2.7 has been EOL since January 2020. Ubuntu oldoldlts (Focal Fossa, 20.04) has Python 3.8. Debian oldoldstable (Buster, from 2019) has Python 3.7. RHEL 8 (from 2019) has Python 3.6. It's easier than ever to install a modern Python using uv. Given this, it seems like a fine idea to drop Python 2.7 support. Even though the build is not tested on Python as old as 3.3, I left comments stating that "3.3+" is the baseline Python version. However, it might make sense to bump this to e.g., 3.10, the oldest Python 3 version used during CI. Or, using uv or another method actually test on the oldest Python interpreter that is desirable to support (uv goes back to Python 3.7 easily; in October 2025, the oldest supported Python interpreter version will be 3.10) Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-09-15 14:53:32 +10:00
Alessandro Gatti	c224e976f7	extmod/modplatform: Expose CPU features/extensions. ... This adds the ability to expose CPU-specific features/extensions to scripts when the `platform` module is compiled in, by implementing `platform.processor()`. Right now this is only available on bare-metal RV32 and RV64. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-09-11 11:58:29 +10:00
Maureen Helm	afa7265ffa	zephyr: Upgrade to Zephyr v4.2.0. ... Updates the Zephyr port build instructions and CI to use the latest Zephyr release tag. Tested on max32690fthr and frdm_k64f. Signed-off-by: Maureen Helm <maureen.helm@analog.com>	2025-08-16 15:10:30 +10:00
Jared Hancock	14ccdeb4d7	extmod/modre: Add support for start- and endpos. ... Pattern objects have two additional parameters for the ::search and ::match methods to define the starting and ending position of the subject within the string to be searched. This allows for searching a sub-string without creating a slice. However, one caveat of using the start-pos rather than a slice is that the start anchor (`^`) remains anchored to the beginning of the text. Signed-off-by: Jared Hancock <jared@greezybacon.me>	2025-08-11 14:11:56 +10:00
Jos Verlinde	a9dd741e66	docs/reference/mpremote: Document location of config file. ... Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>	2025-08-02 00:23:21 +10:00
Jonathan Hogg	641ca2eb06	docs/library/machine: Add docs for Counter and Encoder. ... Add documentation for `machine.Counter` and `machine.Encoder` as currently implemented by the esp32 port, but intended to be implemented by other ports. Originally authored by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com> and Jonathan Hogg <me@jonathanhogg.com>. Signed-off-by: Jim Mussared <jim.mussared@gmail.com>	2025-08-02 00:00:03 +10:00
Jonathan Hogg	e54553c496	docs/esp32: Add documentation for esp32.PCNT. ... Document the new `esp32.PCNT` class for hardware pulse counting. Originally authored by: Jonathan Hogg <me@jonathanhogg.com> Signed-off-by: Jim Mussared <jim.mussared@gmail.com>	2025-08-01 23:45:18 +10:00
Damien George	bf6f229cf3	docs/library: Document the new machine.I2CTarget class. ... With some working examples that show how to use all the features. Signed-off-by: Damien George <damien@micropython.org>	2025-08-01 23:03:17 +10:00
Koudai Aono	ab7c5a1733	docs/library/btree: Fix method links to explicitly specify class. ... So they don't clash with other potential references. Signed-off-by: Koudai Aono <koxudaxi@gmail.com>	2025-08-01 22:58:26 +10:00
Damien George	a9a606bf5d	docs/library/rp2.StateMachine: Add a note about PIO in and jmp pins. ... Signed-off-by: Damien George <damien@micropython.org>	2025-08-01 15:10:15 +10:00
Damien George	6a8c45b6c4	docs/library/bluetooth: Document all allowed args to UUID constructor. ... Signed-off-by: Damien George <damien@micropython.org>	2025-07-31 11:02:41 +10:00
TianShuang Ke	ca9916968c	esp32: Add support for ESP32-C2 (aka ESP8684). ... Includes: esp32/esp32c2: Adapt to target chip ESP32C2. esp32/esp32c2: Fix heap size is too small to enable Bluetooth. Signed-off-by: TianShuangKe <qinyun575@gmail.com> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-30 10:51:29 +10:00
Anson Mansfield	d5dc554742	docs: Document PEP487 __set_name__ implementation. ... Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-07-29 09:44:26 +10:00
Angus Gratton	9b7d85227e	extmod/mbedtls: Implement recommended DTLS features, make optional. ... - DTLS spec recommends HelloVerify and Anti Replay protection be enabled, and these are enabled in the default mbedTLS config. Implement them here. - To help compensate for the possible increase in code size, add a MICROPY_PY_SSL_DTLS build config macro that's enabled for EXTRA and above by default. This allows bare metal mbedTLS ports to use DTLS with HelloVerify support. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-23 15:47:16 +10:00
Damien George	677a0e0124	docs/reference/speed_python: Document schedule/GIL limitation of native. ... Signed-off-by: Damien George <damien@micropython.org>	2025-07-23 11:37:16 +10:00
Damien George	18f2e94846	py/modsys: Add sys.implementation._thread attribute. ... This is useful to distinguish between GIL and non-GIL builds. Signed-off-by: Damien George <damien@micropython.org>	2025-07-22 23:22:05 +10:00
Alessandro Gatti	e993f53877	docs/develop/natmod: Add notes on Picolibc and natmods. ... This commit adds some documentation on what are the limitations of using Picolibc as a standard C library for native modules. This also contains a reference to the "errno" issue when building natmods on RV32 that the PR this commit is part of, as it is not obvious how to approach this issue when encountered for the first time. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-07-20 23:03:40 +10:00
Chris Webb	816246836e	docs/rp2: Document the new rp2 Timer hard= option. ... Signed-off-by: Chris Webb <chris@arachsys.com>	2025-06-16 12:35:51 +01:00
Meir Armon	171d751242	esp32/modesp32: Make wake_on_ext1 available only on SoCs supporting it. ... The `esp32.wake_on_ext1()` method should only be available on boards that have SOC_PM_SUPPORT_EXT1_WAKEUP=y. And update docs to reflect this. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-06-16 14:18:02 +10:00
Meir Armon	4697a06fdb	esp32/modesp32: Make wake_on_ext0 available only on SoCs supporting it. ... The `esp32.wake_on_ext0()` method should only be available on boards that have SOC_PM_SUPPORT_EXT0_WAKEUP=y. And update docs to reflect this. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-06-16 14:17:14 +10:00
Meir Armon	cb315bb8e4	esp32/modesp32: Make wake_on_touch available only on SoCs supporting it. ... The `esp32.wake_on_touch()` method should only be available on boards that have SOC_TOUCH_SENSOR_SUPPORTED=y. And update docs to reflect this. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-06-16 14:16:16 +10:00
Meir Armon	42404b5588	esp32/modesp32: Make wake_on_ulp available only on SoCs that support it. ... The `esp32.wake_on_ulp()` method should only be available on boards that have SOC_ULP_SUPPORTED=y. Update docs to reflect this. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-06-16 11:24:25 +10:00
purewack	5f058e9863	esp32: Update ADC driver update to the new esp_adc API. ... This commit updates the ADC to use the new driver `esp_adc/adc_oneshot.h`. There are several errata notes about not being able to change the bit-width of the ADCs certain chips. The only chip that can switch resolution to a lower one is the normal ESP32. ESP32 C2 and S3 are stuck at 12 bits, while S2 is at 13 bits. On the S2, you can change the resolution, but it has no effect on the resolution, rather, it prevents attenuation from working at all! The resolution is set to the maximum possible for each SoC, with the ESP32 being the only one not throwing errors when trying to set the bit-width to 9, 10, 11 or 12 bits using `ADC.width(bits)`. Signed-off-by: Damian Nowacki (purewack) bobimaster15@gmail.com	2025-06-05 17:01:51 +10:00
Alessandro Gatti	bf2005de9e	tools/mpy_ld.py: Resolve fixed-address symbols if requested. ... This commit lets mpy_ld.py resolve symbols not only from the object files involved in the linking process, or from compiler-supplied static libraries, but also from a list of symbols referenced by an absolute address (usually provided by the system's ROM). This is needed for ESP8266 targets as some C stdlib functions are provided by the MCU's own ROM code to reduce the final code footprint, and therefore those functions' implementation was removed from the compiler's support libraries. This means that unless `LINK_RUNTIME` is set (which lets tooling look at more libraries to resolve symbols) the build process will fail as tooling is unaware of the ROM symbols' existence. With this change, fixed-address symbols can be exposed to the symbol resolution step when performing natmod linking. If there are symbols coming in from a fixed-address symbols list and internal code or external libraries, the fixed-address symbol address will take precedence in all cases. Although this is - in theory - also working for the whole range of ESP32 MCUs, testing is currently limited to Xtensa processors and the example natmods' makefiles only make use of this commit's changes for the ESP8266 target. Natmod builds can set the MPY_EXTERN_SYM_FILE variable pointing to a linkerscript file containing a series of symbols (weak or strong) at a fixed address; these symbols will then be used by the MicroPython linker when packaging the natmod. If a different natmod build method is used (eg. custom CMake scripts), `tools/mpy_ld.py` can now accept a command line parameter called `--externs` (or its short variant `-e`) that contains the path of a linkerscript file with the fixed-address symbols to use when performing the linking process. The linkerscript file parser can handle a very limited subset of binutils's linkerscript syntax, namely just block comments, strong symbols, and weak symbols. Each symbol must be in its own line for the parser to succeed, empty lines or comment blocks are skipped. For an example of what this parser was meant to handle, you can look at `ports/esp8266/boards/eagle.rom.addr.v6.ld` and follow its format. The natmod developer documentation is also updated to reflect the new command line argument accepted by `mpy_ld.py` and the use cases for the changes introduced by this commit. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Damien George	b15348415e	extmod/modframebuf: Add support for blit'ing read-only data. ... Currently the `FrameBuffer.blit(buf, x, y)` method requires the `buf` argument to be another `FrameBuffer`, which is quite restrictive because it doesn't allow blit'ing read-only memory/data. This commit extends `blit()` to allow the `buf` argument to be a tuple or list of the form: (buffer, width, height, format[, stride]) where `buffer` can be anything with the buffer protocol and may be read-only, eg `bytes`. Also, the palette argument to `blit()` may be of the same form. The form of this tuple/list was chosen to be the same as the signature of the `FrameBuffer` constructor (that saves quite a bit of code size doing it that way). Signed-off-by: Damien George <damien@micropython.org>	2025-06-04 02:40:45 +10:00
Angus Gratton	ba92063d64	docs: Add a description of recv/recvfrom flags argument. ... Implementation added for various ports in the parent commits. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-03 12:52:25 +10:00
robert-hh	5cfafb73da	docs/esp32: Mention the use of Timer(0) by UART.IRQ_RXIDLE. ... In both the machine.UART and esp32.quickref sections. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-28 12:13:51 +10:00
robert-hh	92c219afd6	docs/esp32/quickref: Mention the different timer counts. ... Since the are ESP32 variants with 1, 2 or 4 hardware timers. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-28 12:13:46 +10:00
robert-hh	2f864416c6	docs/library/time: Amend the documentation of time.mktime(). ... By showing the argument and refer to epoch instead of a fixed date. The note about epoch lists the ports using the POSIX epoch. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-28 12:13:28 +10:00
robert-hh	bbdc832ca9	samd/boards: Add two SparkFun SAMD21 boards. ... Add support for the boards: - SparkFun SAMD21 Dev Breakout - SparkFun RedBoard Turbo Both boards are SAMD21 based and actively sold by SparkFun. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-28 12:04:42 +10:00
Jos Verlinde	e39243c382	docs/reference/mpremote: Document the 'fs tree' command. ... Signed-off-by: Jos Verlinde <Jos_Verlinde@hotmail.com>	2025-05-18 00:20:46 +10:00