5216 Commits

Author	SHA1	Message	Date
Oliver Joos	230bbbbdf5	stm32/boards/NUCLEO_H7x3: Add UART1, remove UART5, slow down PLL1Q. ... STM32CubeMX shows a conflict of UART5 with ETH MII. However UART1 can be used with TX and RX on the pin headers. PLL1Q is reduced from 200 to 100 MHz because it may be used for FDCAN or SDMMC. FDCAN needs <= 150 MHz, and 100 MHz is enough for an SDCard connected to pin headers to work reliably. Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 17:08:08 +11:00
Oliver Joos	6b13e6c498	stm32/boards/NUCLEO_H7x3: Fix st-flash and add openocd configuration. ... To connect STM32H7 that is in SLEEPD1 state (e.g. during REPL) debuggers like st-flash or openocd must assert SRST. Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 17:08:08 +11:00
Oliver Joos	ee0b5ab2dc	stm32/boards/NUCLEO_H753ZI: Add NUCLEO_H753ZI board support. ... Configuration: - Clock is 8MHz from STLINK MCO, CPU runs at 400MHz - REPL on USB and on UART connected to ST-Link interface - Storage is configured for internal flash memory - 3x LEDs and 1x user button - Ethernet Product page: https://www.st.com/en/evaluation-tools/nucleo-h753zi.html Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 17:08:08 +11:00
Oliver Joos	4e98486830	stm32/boards: Add linker script for STMF412xE with 512k flash. ... The existing linker script for F412 is renamed to separate F412xG (with 1MB RAM) from F412xE (with 512K). Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 16:54:10 +11:00
Oliver Joos	e9bd1e2e08	stm32: Add support for all STM32F412xx MCUs. ... And fix typo in the usage string of plli2svalues.py. Signed-off-by: Oliver Joos <oliver.joos@hispeed.ch>	2026-01-14 16:54:10 +11:00
Damien George	bc7d264e86	stm32/sdcard: Use high speed mode for SD transfers on H5/H7/N6. ... This doubles the speed of SD card transfers. Signed-off-by: Damien George <damien@micropython.org>	2026-01-14 16:44:23 +11:00
Damien George	e48b98537f	stm32/main: Enable all AHB5 GRP1 clocks in low power mode. ... The main functional change here is to make sure that the SDMMC1/2 clocks are enabled in low power mode; they were not previously enabled for SD card use, only WLAN. It doesn't hurt to unconditionally enable the clocks in low power, like all the other peripherals. Signed-off-by: Damien George <damien@micropython.org>	2026-01-14 16:42:57 +11:00
FH	07540a8fd1	esp32/modesp32: Update available RTC pins for ESP32C6. ... According to https://wiki.seeedstudio.com/xiao_esp32c6_getting_started/#demo1-deep-sleep-with-external-wake-up and https://docs.espressif.com/projects/esp-idf/en/stable/esp32c6/api-reference/peripherals/gpio.html ESP32C6 supports RTC/LP on Pins 0-7. Signed-off-by: FH <fh3095-gitcommit@yahoo.com>	2026-01-13 14:45:10 +11:00
Elvis Pfutzenreuter	da6a18ffe0	esp32/esp32_rmt: Update FIXME on RMT module. ... Signed-off-by: Elvis Pfutzenreuter <elvis.pfutzenreuter@gmail.com>	2026-01-13 14:33:33 +11:00
Damien George	85a15f995c	esp32/machine_uart: Change default UART(1) pins on ESP32 with SPIRAM. ... SPIRAM usually uses GPIO 9 and 10 on ESP32, so don't use them as default UART pins. Fixes issue #18544. Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 13:43:02 +11:00
Damien George	b105677ac4	esp32/machine_pin: Rename legacy CONFIG_ESP32_SPIRAM_SUPPORT option. ... Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 13:43:02 +11:00
Damien George	3a487c32ba	all: Fix spelling of Micropython -> MicroPython. ... Signed-off-by: Damien George <damien@micropython.org>	2026-01-13 12:51:31 +11:00
iabdalkader	1947759c94	renesas-ra/boards/ARDUINO_PORTENTA_C33: Increase TinyUSB queue size. ... Default queue size is too small that it overflows easily if debugging printfs are enabled. Increase TinyUSB event queue size to 128. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 17:17:13 +11:00
Kwabena W. Agyeman	75eb197f9d	alif/boards/OPENMV_AE3: Make JTAG pins controllable as GPIOs. ... Allows user control of JTAG pins on the AE3 which are exposed via the B2B header. Signed-off-by: Kwabena W. Agyeman <kwagyeman@live.com>	2026-01-04 17:06:19 +11:00
iabdalkader	1174dda519	alif/boards/OPENMV_AE3: Update romfs partition size. ... Update romfs partition to reflect the latest layout. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 16:57:48 +11:00
iabdalkader	ab5f47c54d	alif/ospi_flash: Remove workaround for P10_7 OSPI pinmux issue. ... P5_6 doesn't have that alt function, and only has 7 alt functions. This workaround was never really needed, it was introduced in DFP because the wrong P10_7 alt function was used, in original DFP sources. This has been removed from DFP starting with 1.3.4, so remove it here also. Signed-off-by: iabdalkader <i.abdalkader@gmail.com>	2026-01-04 16:50:11 +11:00
Alessandro Gatti	2554e4172f	alif/Makefile: Enable job server support on Ubuntu LTS. ... This commit modifies the Alif port's Makefile to propagate to child make tasks the number of parallel jobs to run. On Ubuntu LTS 24.04, building the Alif port passing a parallel jobs number to make's command line will result in the command emitting this warning: make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. And building the two cores' firmware images using one compile job at a time instead of the number provided to the command line. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 16:42:50 +11:00
Alessandro Gatti	678dbd26f8	alif/Makefile: Do not hardcode the python interpreter name. ... This commit fixes a build issue occurring on systems where the Python 3.x interpreter isn't aliased to 'python' but has a different name (usually `python3'). The main Linux distribution where this occurs is Ubuntu LTS, where the Python 3.x interpreter is available as 'python3' since at least two major versions (so since about five years now). MicroPython's makefile environment setup file ('py/mkenv.mk') already defines a variable called '$(PYTHON)' that defaults to 'python3', so the Makefile was updated to use that instead of hardcoding the interpreter name. Without these changes, building a firmware image on Ubuntu LTS fails with this error: make: python: No such file or directory make: *** [Makefile:95: build-ALIF_ENSEMBLE/firmware.toc.bin] Error 127 This also allows overriding the interpreter name to something else if there's the need to perform tests with different interpreter versions or the like. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 16:42:50 +11:00
Alessandro Gatti	11861e96a9	nrf/modules/machine/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The "pin_obj_t" structure, holding pin information, had an unused word-sized field ("pull") that isn't used by any of the board definitions, yet it takes up space in each pin structure being compiled in the final firmware image. Images for all available boards were built successfully with this change, so there should be no unwanted issues arising from shrinking that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	6572ce84c9	samd/pin_af: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	31deee9060	rp2/machine_pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The data type used to store the QSTR name of both regular and alternate function pins ("machine_pin_obj_t" and "machine_pin_af_obj_t") is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	fb8ecaecf5	renesas-ra/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	8bda61a3af	mimxrt/pin: Reduce footprint of pin structures. ... This commit performs a few minor changes to the structures used to store board pin information, in order to reduce the impact on the .rodata section of the firmware of instances of those structures. The data type used to store the QSTR name of alternate function pins ("machine_pin_af_obj_t") is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Regular pin objects structure ("machine_pin_obj_t") instead has its QSTR variable holder changed from "qstr" to "qstr_short_t", and some elements of that structure have been rearranged to remove enough padding bytes inside structure elements to let the linker allocate less data for instances of that structure. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
Alessandro Gatti	049cdd0dd3	cc3200/mods/pybpin: Reduce footprint of AF pin structures. ... This commit performs a minor change to the "pin_af_t" structure, changing the data type used to store alternate function pin name QSTRs in order to have a smaller impact on the .rodata section of the firmware. The data type used to store the QSTR name of the pin is changed from "qstr" to "qstr_short_t", that is able to store the same name string index but in half the size. Other pin-related structures in the port that also store QSTRs do not benefit from a narrower data type, as their members are mostly word-aligned and thus the linker is forced to insert padding bytes between entries. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-04 11:48:11 +11:00
robert-hh	610552010d	nrf: Add support for VfsRom filesystem. ... The implementation uses the object based capabilities, which avoids complication about different flash block sizes. The ROM partition is placed between the text and writable filesystem sections, and the latter size is unchanged. VfsRom sizes are: - NRF51x22: 12K - NRF52832: 128K - NRF52840: 256K - NRF9160: 256K Use frozen `_boot.py` to set up and mount the filesystem, replacing a mix of C-Code and Python code. The mkfs part has been simplified to save code. Tested with Microbit and Arduino Nano Connect. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 15:28:02 +11:00
robert-hh	cee950673d	renesas-ra: Add support for VfsRom filesystem. ... The ROM partition is taken from the last part of the flash text section, so the existing writable filesystem is untouched. VfsRom file system sizes: - EK_RA4M1: 12K - RA4M1_CLICKER: 12k - EK_RA4W1: 64k - EK_RA6M1: 64k - EK_RA6M2: 256k - VK_RA6M5: 384k - ARDUINO_PORTENTA_C33: 256k Tested with Weact RA4M1 core board with EK_RA4M1 firmware and EK_RA6M2. Signed-off-by: robert-hh <robert@hammelrath.com> Signed-off-by: Damien George <damien@micropython.org>	2026-01-02 15:24:22 +11:00
robert-hh	c07b178dbd	samd: Add support for VfsRom filesystem for SAMD21 and SAMD51. ... The flash driver is update to support the new `mp_vfs_rom_ioctl()` function, and the buffer protocol is added to `samd_flash_type` (it is needed for VfsRom on devices without external flash). For SAMD21, only boards with external SPI flash have VfsRom enabled, due to size constraints. For such boards, the VfsRom filesystem has a size of 12k and is placed at the upper end of the flash. The `onewire`, `ds18x20` and `dht` drivers have been removed from frozen bytecode as they can be placed into the VfsRom files when needed. For SAMD51, the VfsRom filesystem has a default size of 64k for SAMD51x19 and 256K for SAMD51x20. It is placed at the upper end of the flash. For boards with external SPI flash, the code size is reduced from 496K to 432K. If that is not sufficient for some boards or configurations, it can be changed for each board or board variant. Tested with ADAFRUIT_ITSYBITSY_M0_EXPRESS, ADAFRUIT_ITSYBITSY_M4_EXPRESS, SPARKFUN_SAMD51_THING_PLUS, SEEED_XIAO_SAMD21, SAMD_GENERIC_D51X19, and SAMD_GENERIC_D51X20. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 15:23:49 +11:00
robert-hh	b857a9131e	mimxrt: Add support for VfsRom filesystem. ... The default size for the ROM partition is 256k, and it is placed in flash between the text and writable vfs sections. Its size can be changed in `mpconfigboard.mk` by defining `MICROPY_HW_ROMFS_BYTES` to a different value, but it must not be smaller than a single sector. The MIMXRT1170_EVK and SEEED ARCH MIX ROMFS boards use a larger size of 512kB. ROMFS support is disabled for MIMXRT1050_EVKB due to issues with Hyperflash. The extents of the ROM partition are defined by the linker-level symbols `_micropy_hw_romfs_part0_start` and `_micropy_hw_romfs_part0_size`, following existing ports. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: robert-hh <robert@hammelrath.com>	2026-01-02 14:48:16 +11:00
Alessandro Gatti	d44685e103	unix/mpconfigport: Enable natmod loading for RISC-V builds. ... This commit lets the Unix port load native modules when built for both RV32 and RV64. Since RV64 doesn't have a native emitter, the new native code loading configuration settings have been used to allow such a feature. RV32 is fully supported by the native emitter framework but the emitter wasn't enabled for Unix builds (and therefore no natmod support). RV64 builds have been tested on QEMU and on a MilkV-Duo board, and whilst RV32 isn't really tested, its native code loading functionality is routinely tested both on bare-metal QEMU and on microcontroller boards. Since the code for RV64 under Unix and RV32 is essentially the same, having RV64 working is a strong indicator that RV32 will work too. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-01 16:35:23 +01:00
Alessandro Gatti	9af103300f	qemu: Enable loading natmods on RV64. ... This commit lets the QEMU port's VIRT_RV64 board load and run native modules, via the appropriate configuration changes in mpconfigport.h. Now the CI test job for the QEMU/RV64 port can also run natmods and see whether they actually work, so the CI tasks script has been updated to bring RV64 to parity with RV32 as far as CI checks go. Documentation was also updated, since now all supported boards in the QEMU port should be able to run natmod tests. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2026-01-01 16:35:02 +01:00
Alessandro Gatti	14152e7f49	nrf/main: Allocate executable memory when needed. ... This commit lets the nRF port use the new MICROPY_PERSISTENT_CODE_LOAD_NATIVE configuration entry. The nRF port needs a special procedure to allocate memory used to hold executable native code. This functionality was gated behind the presence of a native emitter and thus its inclusion condition had to be updated. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:51:56 +01:00
Alessandro Gatti	14ea6d7fd8	esp8266/modesp: Allocate executable memory when needed. ... This commit lets the ESP8266 port use the new MICROPY_PERSISTENT_CODE_LOAD_NATIVE configuration entry. The ESP8266 port needs a special procedure to allocate memory used to hold executable native code. This functionality was gated behind the presence of a native emitter and thus its inclusion condition had to be updated. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:49:48 +01:00
Alessandro Gatti	ecf8873293	qemu/Makefile: Allow overriding the test natmods list. ... This commit modifies the QEMU port makefile to let the user provide their own list of natmods to test as part of "test_natmod". The makefile now will replace the list of natmods to test with the contents of the "TEST_NATMODS" command line variable, so if there's a specific subset of natmods causing problems test runs can be limited to that very subset. "TEST_NATMODS" accepts a whitespace-separated list of natmod names for which there are available matching tests in "tests/extmod" (eg. make test_natmod TEST_NATMODS="btree heapq"). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:49:48 +01:00
Alessandro Gatti	2b82f512d2	unix/alloc: Map executable memory for code loading when needed. ... This commit lets the Unix port use the new MICROPY_PERSISTENT_CODE_LOAD_NATIVE configuration entry. The Unix port needs to allocate memory with specific flags that let the operating system run executable code from there. This functionality was gated behind the presence of a native emitter and thus its inclusion condition had to be updated. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-26 11:49:48 +01:00
Alessandro Gatti	6341258207	esp32/mpconfigport: Enable Zcmp opcodes for ESP32P4. ... This commit enables support for Zcmp opcodes when the firmware is built to target ESP32P4 microcontrollers. The ESP32P4 explicitly supports the Zcmp extension for reducing the amount of code needed for function prologues and epilogues (see section 4.1.1.1 of the ESP32P4 datasheet). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Alessandro Gatti	ec5f2bc686	rp2/CMakeLists.txt: Set the appropriate mpy-cross flags on all targets. ... This commit lets the RP2 port build system use the appropriate flags to pass to "mpy-cross" when building frozen MPY files as part of the build process. Now all possible variants (RP2040, RP2350/Arm, and RP2350/RV32) have their right flags assigned, falling back the flags set of the RP2040 if a new variant is introduced. Before these changes all variants would use the RP2040 set of flags which may be a bit of an issue when building code for the RP2350 in RV32 mode. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Alessandro Gatti	08096392b5	rp2/mpconfigport: Enable Zcmp opcodes for RP2350 in RV32 mode. ... This commit enables support for Zcmp opcodes when the firmware is built for the RP2350 in RV32 mode. The RP2350 explicitly supports the Zcmp extension for reducing the amount of code needed for function prologues and epilogues (see section 3.8.1.20 of the datasheet). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
Alessandro Gatti	d938d5af4e	qemu/Makefile: Allow usage of a custom QEMU binary to run code. ... This commit introduces a new optional makefile variable to let the build system know that, when running code, a custom QEMU binary must be used instead of the one provided by the system's PATH. Given that the CI machine won't keep up with QEMU updates unless its base image tracks a new version of QEMU itself, sometimes it is needed to use a custom QEMU build to be able to test new code in an emulated context rather than having to perform on-device testing during development. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-12-19 17:06:53 +11:00
jetpax	e67d4a2a77	esp32/machine_sdcard: Fix SDMMC slot assignment for non-default slots. ... The SDMMC_HOST_DEFAULT() macro sets slot to SDMMC_HOST_SLOT_1, but this was not being overridden when the user specified a different slot number. This caused SDMMC initialization to fail on chips like ESP32-P4 when trying to use slot 0. This commit ensures the slot number passed to the SDCard constructor is properly assigned to the host configuration structure. Tested on ESP32-P4 with SD card on slot 0. Signed-off-by: jetpax <jep@alphabetiq.com>	2025-12-18 11:49:19 +11:00
Damien George	53052857e2	esp8266/boards/ESP8266_GENERIC: Remove OTA board variant. ... The OTA variant of the ESP8266_GENERIC board was never fully completed in its functionality. It relies on the https://github.com/pfalcon/yaota8266 component which was also never fully finished and has been unmaintained for many years. This commit removes this variant and it's associated build support. It makes it an "old_variant" so the existing historical firmware is still listed on the download page. Signed-off-by: Damien George <damien@micropython.org>	2025-12-16 16:30:04 +11:00
Damien George	9274f80130	esp32/boards/ESP32_GENERIC_S3: Reinstate old FLASH_4M variant. ... Commit 6201e77999 removed the ESP32_GENERIC_S3 FLASH_4M variant from `board.json`. But the firmware still exists on the download server, and it makes sense to still keep those old versions available for download, just like all other older versions are still available. This commit introduce a new scheme for `board.json` whereby old variants that are no longer built can be moved to the "old_variants" section. This keeps them available on the download page, allowing a way to deprecate individual board variants without removing them entirely. An optional string can be added to the old variant to describe why it's obsolete and what to use instead. Signed-off-by: Damien George <damien@micropython.org>	2025-12-16 16:22:03 +11:00
Damien George	7702f7f59d	esp32/main: Update esp_hosted component to latest version 2.7.0. ... This updates the esp_hosted component for ESP32-P4 boards to use the latest version 2.7.0. Testing on a P4 board with C6 WiFi shows there are no regressions for WiFi or BLE. Also rename the `CONFIG_ESP_ENABLE_BT` option to the new `CONFIG_ESP_HOSTED_ENABLE_BT_NIMBLE` option used by the component. This change is made partly to work around a current issue with the IDF component manager, that esp_hosted versions after 2.0.17 and prior to 2.7.0 have all disappeared. Signed-off-by: Damien George <damien@micropython.org>	2025-12-08 09:48:08 +11:00
Damien George	365cdb6f56	esp32/boards: Enable ESP32P4_REV_MIN_0 option for P4 boards. ... The ESP32-P4 currently comes in three revisions (0.0, 0.1 and 1.0) and all of them are out in the wild. Even though the IDF defaults to a minimum of 0.1 we would like to support as many as possible, so configure MicroPython to work down to revision 0.0. The firmware only grows by 32 bytes when enabling this option. Signed-off-by: Damien George <damien@micropython.org>	2025-12-08 09:48:08 +11:00
Steve Sanbeg	504adc689b	stm32/boards/NUCLEO_G474RE: Restore disabled modules on g474re. ... Among other things, the framebuf module is missing on NUCEO_G474RE. This board seems to disable a lot of modules, while other *E boards with the same flash configuration (eg NUCLEO_F411RE) don't seem to disable any modules in this way. So, remove all of the lines disabling modules to make it consistent with other boards. Signed-off-by: Steve Sanbeg <steve.sanbeg@gmail.com>	2025-12-08 09:15:25 +11:00
Yuuki NAGAO	4d7c2fd186	stm32/system_stm32: Fix clock config for STM32G4. ... Add peripheral clock selection for ADC345 to use analog port under ADC3. Fixes #18527. Signed-off-by: Yuuki NAGAO <wf.yn386@gmail.com>	2025-12-07 23:08:33 +11:00
Angus Gratton	5ea9a2662d	esp32: Don't disable component manager when updating submodules. ... - Reverts the change from ec527a1 - since later change cccac2cc we no longer exit CMake early to get the submodule list, so it's OK to run component manager during this phase. - Fixes issue where "make submodules BOARD=ESP32_GENERIC_S3" (or any other board that depends on USB) would fail due to missing component(s). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-12-03 15:04:21 +11:00
Damien George	a94f8114f3	esp32/boards/ESP32_GENERIC_P4: Add variants to board.json and .md files. ... Add variants to the new ESP32_GENERIC_P4 board, so they appear on the download page. Signed-off-by: Damien George <damien@micropython.org>	2025-12-03 14:50:04 +11:00
Angus Gratton	797925c057	esp32: Fix board images for ESP32_GENERIC_[C2|C5|P4]. ... These recently added boards had copy-paste image names, change them to match the images pending addition to micropython-media. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-12-03 14:21:14 +11:00
Damien George	e6a7dc1114	rp2/mpconfigport: Enable MD5, SHA1 and cryptolib on all boards. ... This fixes a regression introduced by PR #17926 / commit b5fcb33eaa which accidentally disabled `hashlib.sha1` and the `cryptolib` module on rp2 boards that don't have networking enabled, eg RPI_PICO. `hashlib.md5` is enabled to keep the configuration the same as boards that do have networking enabled. Signed-off-by: Damien George <damien@micropython.org>	2025-12-02 00:38:01 +11:00
Anson Mansfield	2db2f536ac	rp2/rp2_pio: Fix support for pin wrapping and RP2350B upper-bank pins. ... On RP2350B where there are more than 32 pins, using `pio_sm_set_pins_with_mask()` and `pio_sm_set_pindirs_with_mask()` is not correct because their arguments are `uint32_t` and higher bits get lost when `pio.gpio_base(16)` is used. This commit fixes the issue by using the 64-bit API functions on RP2350B. It also makes sure pin wrapping is supported, i.e. using [30, 31, 0, 1] or [46, 47, 16, 17] as contiguous pin ranges for a PIO program. Fixes issue #16199. Signed-off-by: Anson Mansfield <amansfield@mantaro.com>	2025-12-02 00:09:06 +11:00