4767 Commits

Author	SHA1	Message	Date
Angus Gratton	4545eb844d	rp2: Disable the LWIP tick timer when not needed. ... Prevents lightsleep being woken up every 64ms to service LWIP timers, when: 1. No netif is up, and 2. No TCP sockets are active The TCP socket check may not be strictly necessary, but without ticking the tcp timer they won't ever time out by themselves. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-21 13:47:45 +10:00
Damien George	a1ee42cd3e	nrf: Use common implementation of machine disable/enable IRQ. ... This is a breaking change due to the signature change of `enable_irq()`. Previously the signature was: machine.enable_irq() Now the signature matches other ports, and the docs, and is: machine.enable_irq(state) Where `state` is the return value from `machine.disable_irq()`. Signed-off-by: Damien George <damien@micropython.org>	2025-05-21 13:30:40 +10:00
Damien George	cc7eb1a535	nrf/boards: Use 64 byte raw-paste buffer on PCA10028 and PCA10040. ... To workaround issues with JLink CDC. Signed-off-by: Damien George <damien@micropython.org>	2025-05-21 13:14:42 +10:00
Damien George	e676b58d9f	nrf: Fix UART write on parts that can't write more than 255 bytes. ... Some MCUs cannot write more than 255 bytes to the UART at once. Eg writing 256 bytes gets truncated to 0, writing 257 gets truncated to 1, etc. Signed-off-by: Damien George <damien@micropython.org>	2025-05-21 13:14:26 +10:00
Damien George	32c65ad455	nrf: Only process interrupt chars on UARTs used for REPL. ... This commit adds an `attached_to_repl` property to each UART, and makes sure that property is correctly set/unset when the UART is attached to or detached from the REPL. That property is then used to make sure incoming characters on the UART are only checked for the interrupt character if the UART is attached to the REPL. Otherwise a board without REPL on UART can have its code interrupted if ctrl-C is received on the UART. Also, put incoming UART characters on to `stdin_ringbuf` instead of the UARTs ring buffer (the former is much larger than the latter). Signed-off-by: Damien George <damien@micropython.org>	2025-05-21 13:10:01 +10:00
Damien George	d5db8f0461	nrf: Use correct IRAM address for native code execution on nRF52. ... On nRF52, the physical SRAM is mapped to 0x20000000 for data access and 0x00800000 for instruction access. So, while native code is allocated and written using addresses in the 0x20000000 range, it must execute from the 0x00800000 range. This commit makes this work correctly on nRF52 MCUs by adjusting the address. Signed-off-by: Damien George <damien@micropython.org>	2025-05-21 12:53:25 +10:00
Elvis Pfutzenreuter	ecbbc512b2	esp32/network_lan: Add PHY_GENERIC device type. ... Support the new PHY_GENERIC device type, added in ESP-IDF v5.4.0 [1]. This PHY driver was added to ESP-IDF to support "generic"/oddball PHY LAN chips like the JL1101, which offer no features beyond the bare 802.3 PHY standard and don't actually need a chip-specific driver (see discussion at [2]). [1] 0738314308 [2] https://github.com/espressif/esp-eth-drivers/pull/28 Signed-off-by: Elvis Pfutzenreuter <epxx@epxx.co>	2025-05-16 15:34:20 -03:00
Rick Sorensen	90aeac800a	esp32/machine_i2c: Fix default I2C pins for C3, S3. ... The default I2C init does not require setting SCL or SDA but the default I2C0 pins for C3, S3 conflict with the espressif GPIO usage. For the C3, pins 18/19 are for USB/JTAG. If used for I2C() they will cause the REPL to hang on initialization of the I2C. For the S3 pin 19 is allocated for USB/JTAG also but the defaults do not seem to affect the REPL. See related #16956. Fixes issue #17103. Signed-off-by: Rick Sorensen <rick.sorensen@gmail.com> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-16 17:39:10 +10:00
Daniël van de Giessen	06d8c084b9	esp32/modesp32: Implement esp32.idf_task_info(). ... This adds a new function, `esp32.idf_task_info()`, that can be used to retrieve task statistics which is useful for diagnosing issues where some tasks are using up a lot of CPU time. It's best used in conjunction with the `utop` module from micropython-lib. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-05-16 16:49:59 +10:00
Angus Gratton	10f6c0699e	esp32/network_lan: Add support for LAN8670 PHY. ... This adds support for LAN8670 to the esp32 port. Enabled conditionally for the esp32 target, if ESP-IDF version is new enough (v5.3 or newer). Fixes issue #15731. Signed-off-by: Damien George <damien@micropython.org> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-16 15:16:06 +10:00
IhorNehrutsa	f48b981567	esp32: Update to use ESP-IDF v5.4.1. ... This version of the IDF uses about 1KB more IRAM and 1KB more DRAM on most boards, but 6.5KB more DRAM usage on the S3. It seems that's due to a lot of small increases in many components. Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>	2025-05-16 14:02:39 +10:00
Damien George	e1ab04e820	esp32/mpthreadport: Fix double delete of tasks on soft reset. ... Python threads (created via the `_thread` module) are backed by a FreeRTOS task. Managing the deletion of the task can be tricky, and there are currently some bugs with this in the esp32 port. The actual crash seen was in FreeRTOS' `uxListRemove()`, and that's because of two calls to `vTaskDelete()` for the same task: one in `freertos_entry()` when the task ran to completion, and the other in `mp_thread_deinit()`. The latter tried to delete the task a second time because it was still in the linked list, because `vTaskPreDeletionHook()` had not yet been called. And the reason `vTaskPreDeletionHook()` was yet to be called is because the FreeRTOS idle task was starved. This commit fixes that. There are three things done by this commit: - remove the `vTaskPreDeletionHook`, it's not needed anymore because task stack memory is allocated by the IDF, not on the MicroPython heap - when a task finishes it now removes itself from the linked list, just before it deletes itself - on soft reset, all tasks are deleted and removed from the linked list in one swoop (while the mutex is held) Signed-off-by: Damien George <damien@micropython.org>	2025-05-16 13:31:34 +10:00
IhorNehrutsa	a724545193	esp32/mpconfigport: Document how to get more debug info. ... Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>	2025-05-16 12:37:14 +10:00
IhorNehrutsa	150a5aa3a1	esp32/machine_pwm: Improve PWM and make its API match other ports. ... This reduce inconsistencies between esp32 PWM and other ports: 1. duty_u16() high value is 2**16-1 == 65535 2. Invert PWM wave with invert=1 parameter 3. Enable PWM in light sleep mode 4. Allow PWM output and read pulse input simultaneously on the same Pin() 5. Code refactoring Co-Authored-By: Angus Gratton <angus@redyak.com.au> Co-Authored-By: robert-hh <robert@hammelrath.com> Co-Authored-By: Andrew Leech <andrew.leech@planetinnovation.com.au> Co-Authored-By: Yoann Darche <yoannd@hotmail.com> Signed-off-by: Ihor Nehrutsa <Ihor.Nehrutsa@gmail.com>	2025-05-16 12:35:58 +10:00
Daniël van de Giessen	3b1e22c669	esp32/network_ppp: Restructure to match extmod/network_ppp_lwip. ... The ESP32 PPP implementation predates the generic implementation in extmod. The new extmod implementation has a few advantages such as a better deinitialisation procedure (the ESP32 implemementation would not clean up properly and cause crashes if recreated) and using the UART IRQ functionality instead of running a task to read data from the UART. This change restructures the ESP implementation to be much closer to the new extmod version, while also bringing a few tiny improvements from the ESP32 version to the extmod version. The diff between extmod/network_ppp_lwip.c and ports/esp32/network_ppp.c is now a small set of easy to review ESP32 port-specific changes. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-05-15 11:56:14 +10:00
Alessandro Gatti	2406582479	esp32/network_common: Raise a memory error on ESP_ERR_NO_MEM. ... This commit changes the error handler for WiFi operations to recognise out of memory conditions reported by ESP-IDF functions, and report them as more descriptive exceptions rather than a generic "error 0x101". The error handler only provided a human-readable error description for WiFi-specific error codes (codes in the ESP_ERR_WIFI_BASE range), but WiFi functions are known to return other codes. Now ESP_ERR_NO_MEM is covered with a specific error message, making it easier to debug issues related to running out of ESP-IDF heap. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-15 11:29:41 +10:00
Daniël van de Giessen	155fa94fbf	esp32/machine_uart: Correctly manage UART queue and event task. ... If the driver was reinitialised while there was already an event task running the queue that task is trying to receive from would be deleted, causing it to try to take a lock that no longer existed and deadlocking the CPU. This change ensures the task is always shut down before recreating the queue and recreates the task afterwards. It also allows setting an IRQ handler before the UART is initialized (like other ports allow), removes the task when the UART is deinitialized (which was previously missing), adds a check that no event task can be started when no queue exists, and adds a check to prevent reinitialising the UART driver unnecessarily. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-05-14 15:55:31 +02:00
Alessandro Gatti	883dc41d46	esp32/main: Make the entry point function name configurable. ... This commit introduces a new port configuration entry allowing the entry point function name to be changed, from "app_main" to a custom name. This is needed when MicroPython is embedded as an ESP-IDF component, since the "app_main" symbol is already provided elsewhere, making compilation not possible. Marking MicroPython's symbol as weak would make it compile and make it possible to create and start the MicroPython task anyway with the right FreeRTOS task creation incantation, but it is probably easier to just rename the initialisation function into something else that can be accessed from outside. When MicroPython is embedded as an ESP-IDF component, the MICROPY_ESP_IDF_ENTRY definition can be set to indicate the new entry point function name. The new function name prototype should still be defined in external code to let linking succeed. Also, the NLR failure callback is marked as weak to give the chance of handling such error in a more controlled fashion rather than trigger an unconditional board restart. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-14 06:26:31 +02:00
Alessandro Gatti	116d0d4945	esp32/esp32_common.cmake: Allow adding defines and compiler flags. ... This commit introduces two extra CMake variables, MICROPY_DEF_COMPONENT and MICROPY_COMPILE_COMPONENT, that make it easier to integrate MicroPython as a custom ESP-IDF component. Whilst there is no official MicroPython component available for ESP-IDF, integration can be achieved with some minor CMake scripting outside the MicroPython tree - except for customisation of compilation defines and build flags, which is what this commit tries to provide. Compilation defines customisation is especially important for MicroPython configuration, as it is not possible to inject a value for MP_CONFIGFILE otherwise. This means that unless MicroPython itself is forked first to edit ports/esp32/mpconfigport.h, it is not possible to perform any meaningful configuration of the interpreter/runtime when included as a component. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-14 06:25:59 +02:00
robert-hh	1d4bf8ac40	esp32/machine_timer: Fix timer.value() for an uninitialized timer. ... Raises a value error in that case, which happens after a timer was created but not initialized, or after calling `timer.deinit()`. Fixes issue #17033. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-14 11:58:36 +10:00
Alessandro Gatti	d7371124d2	esp32/esp32_common.cmake: Use the tinyusb source files from ESP-IDF. ... This commit removes the explicit dependency on the vendored tinyusb version for the ESP32S2 and ESP32S3 boards. Tinyusb is still available to MicroPython through a dependency on the `espressif/esp_tinyusb` ESP-IDF component, which in turn depends on the `espressif/tinyusb` component itself. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-14 11:02:31 +10:00
Alessandro Gatti	f47e214cdc	all: Rename the "NORETURN" macro to "MP_NORETURN". ... This commit renames the NORETURN macro, indicating to the compiler that a function does not return, into MP_NORETURN to maintain the same naming convention of other similar macros. To maintain compaitiblity with existing code NORETURN is aliased to MP_NORETURN, but it is also deprecated for MicroPython v2. This changeset was created using a similar process to decf8e6a8b ("all: Remove the "STATIC" macro and just use "static" instead."), with no documentation or python scripts to change to reflect the new macro name. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-13 10:36:47 +10:00
Angus Gratton	69993daa5c	rp2/modmachine: Add mutual exclusion for machine.lightsleep(). ... There's no specified behaviour for what should happen if both CPUs call `lightsleep()` together, but the latest changes could cause a permanent hang due to a race in the timer cleanup code. Add a flag to prevent hangs if two threads accidentally lightsleep, at least. This allows the new lightsleep test to pass on RPI_PICO and RPI_PICO2, and even have much tighter time deltas. However, the test still fails on wireless boards where the lwIP tick wakes them up too frequently. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-12 16:30:46 +10:00
Peter Harper	2a4f1c9f0f	rp2/modmachine: Add debug code for mp_machine_lightsleep. ... Add some debug code that can be enabled to determine why lightsleep is returning early. Signed-off-by: Peter Harper <peter.harper@raspberrypi.com>	2025-05-12 16:29:37 +10:00
Peter Harper	ee2c78cd97	rp2: Use pico-sdk alarm pool instead of soft timer for sleep. ... Stop using soft timer for `mp_wfe_or_timeout`. Now uses the alarm pool again as issues with this code have been fixed. This resolves the "sev" issue that stops the RP2350 going idle. Also, change the lightsleep code to use the hardware timer library and alarm 1, as alarm 2 is used by and soft timers and alarm 3 is used by the alarm pool. Signed-off-by: Peter Harper <peter.harper@raspberrypi.com>	2025-05-12 16:24:51 +10:00
Angus Gratton	3fa77bdc7d	rp2: Add temporary workaround for GCC 15.1 build failure. ... This is a workaround for this upstream issue: https://github.com/raspberrypi/pico-sdk/issues/2448 Can be removed after the next pico-sdk update. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-09 18:31:25 +10:00
Damien George	9c8c219f8a	rp2/rp2_dma: Fix default value used in pack_ctrl on RP2350. ... The bit position of CHAIN_TO is not the same as on RP2040. Signed-off-by: Damien George <damien@micropython.org>	2025-05-09 12:05:04 +10:00
Damien George	928466d74c	rp2/Makefile: Add deploy target that uses picotool load. ... This is a convenient way to deploy firmware to an RP2xxx-based board. Signed-off-by: Damien George <damien@micropython.org>	2025-05-09 12:01:50 +10:00
Angus Gratton	d00eab4a30	rp2,extmod/cyw43: Move the LWIP responder fix into common CYW43 config. ... This means the fix from dd1465e7 will also apply to stm32 and mimxrt ports that use CYW43. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-08 15:32:05 +10:00
Angus Gratton	b2cda6c604	extmod,alif,mimxrt,rp2,stm32: Create common cyw43 driver config header. ... This is only a surface level refactor, some deeper refactoring would be possible with (for example) the SDIO interface in mimxrt and stm32, or the BTHCI interface which is is similar on supported ports. But sticking to cases where the macros are the same across all ports. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-08 15:32:05 +10:00
Anton Blanchard	45e4deb96d	zephyr/mpconfigport: Fix mp_int_t and mp_uint_t to work on 64-bit archs. ... These both need to fit a pointer, so make them `intptr_t` and `uintptr_t`, similar to other ports. Signed-off-by: Anton Blanchard <antonb@tenstorrent.com>	2025-05-07 21:36:54 +10:00
danicampora	fe28cd78fe	zephyr/modbluetooth_zephyr: Allow BLE to create services at runtime. ... This commit adds the required functionality for a peripheral to create services at runtime, using `BLE.register_services()`. The feature is enabled on the nrf52840dk_nrf52840 board. Note that the `CONFIG_BT_GATT_ENFORCE_SUBSCRIPTION=n` option must be used so that BLE notifications/indications can be sent even if not subscribed. Signed-off-by: danicampora <danicampora@gmail.com>	2025-05-07 21:25:53 +10:00
robert-hh	80d03b7780	samd/samd_qspiflash: Remove the attempt to handle a unknown device. ... Since all QSPI flash device used by this port are defined, this code was only used unintentionally. Besides that it was incomplete, so better drop it. Note: The flash type for Mini-SAM had to be changed too. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:20:19 +10:00
robert-hh	2e6df08e05	samd/samd_spiflash: Improve the flash type detection. ... Changes in this commit: - Check for the proper SFDP header. - Use the flash size information from SFDP, if present. - Add two more special flash chips <= 1 MByte without SFDP. JEDEC-ID table for special flash types instead of a series of conditional statements. - Add a compile flag `MICROPY_HW_SPIFLASH_SIZE` to set the size in `mpconfigboard.h`, which replaces getting the size from the JEDEC ID or the SFDP record. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:19:48 +10:00
robert-hh	c22c2c8066	samd/boards/SAMD_GENERIC_D51xxx: Fix VFS settings for internal flash. ... Fixes in this commit: - The wrong loader script was assigned for SAMD_GENERIC_D51X20, causing the VFS block count to be wrong. - Change the VFS block size from 1536 to 2048. With the setting of 1536, writing more that 1536 bytes at once failed. This applies to SAMD_GENERIC_D51X19 and SAMD_GENERIC_D51X20. No other SAMD51 board uses the internal flash for the file system. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:18:07 +10:00
robert-hh	ff9e01782b	samd/modtime: Change time.time_ns() to follow the RTC time. ... That is done by adding the offset to epoch, following the scheme from the RP2 port. RTC and `ticks_us()` are not precisely in sync, and so the difference between `time.time_ns()/1e9` and `time.time()` will increase by more than 9 seconds/24h. So applications should avoid using `time.time()` and `time.time_ns()` in the same context. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:17:07 +10:00
robert-hh	2fda4bbe05	samd/machine_i2c: Add the timeout keyword argument to the constructor. ... To make it compliant with the documentation. The default value is 50000us. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:16:45 +10:00
robert-hh	8e328da9bf	samd/boards/SAMD_GENERIC_Dxxx: Add Microchip URL to board.json. ... To the Microchip Web site. Thanks to Matt Trentini for suggesting this site. Signed-off-by: robert-hh <robert@hammelrath.com>	2025-05-07 16:16:11 +10:00
Malcolm McKellips	288dce26bd	docs,ports: Fix SparkFun capitalization. ... This is a follow-up to 1e92bdd206 correcting more of the instances where "Sparkfun" should be "SparkFun". Signed-off-by: Damien George <damien@micropython.org>	2025-05-07 15:16:55 +10:00
Ayush Singh	bee1fd5e78	zephyr/boards: Enable ADC on beagleconnect_freedom. ... Enable Analog inputs. Requires Zephyr >= v3.8.0. Signed-off-by: Ayush Singh <ayush@beagleboard.org>	2025-05-02 12:39:16 +10:00
Vdragon	8728db3e41	zephyr: Introduce auto-listing of FlashArea Partitions. ... This enables listing all flash area partitions automagically instead of just sotrage_partitions. It uses the label, and the ID when not present. Signed-off-by: Vdragon <mail@massdriver.space>	2025-05-02 12:37:20 +10:00
Vdragon	6601d4d7eb	zephyr: Create ability to use device_next with CDC ACM as REPL. ... This enables using the newer USB stack and its CDC ACM for the REPL. To switch to it, board file must contain `CONFIG_USB_DEVICE_STACK_NEXT=y` and `CONFIG_USBD_CDC_ACM_CLASS=y`. In the case of a board that is a platform that supports the older device stack, `CONFIG_USB_DEVICE_STACK=n` may be necessary. Signed-off-by: Vdragon <mail@massdriver.space>	2025-05-02 12:27:14 +10:00
Patrick Joy	62479f2cb6	zephyr/boards: Add nrf9151dk board configuration. ... Add support for the nrf9151dk. This DK has a GD25WB256 32mb external QSPI flash chip. Signed-off-by: Patrick Joy <patrick@thinktransit.com.au>	2025-04-30 12:44:12 +10:00
Patrick Joy	e3d9d8ef51	zephyr/boards: Add nrf5340dk board configuration. ... Add support for the nrf5340dk. This DK has a MX25R64 8mb external QSPI flash chip. Compile using: $ west build -b nrf5340dk/nrf5340/cpuapp Signed-off-by: Patrick Joy <patrick@thinktransit.com.au>	2025-04-30 12:29:11 +10:00
Vdragon	d939511dae	zephyr: Create options to enable frozen modules. ... Enables the ability to use frozen modules in the zephyr port. Enabled by adding `CONFIG_MICROPY_FROZEN_MODULES` to the board configuration file. Manually set manifest path with `CONFIG_MICROPY_FROZEN_MANIFEST`. Signed-off-by: Vdragon <mail@massdriver.space>	2025-04-30 11:59:17 +10:00
Ayush Singh	f9a755c91c	zephyr/boards: Enable PWM on beagleconnect_freedom. ... Enable PWM config for bcf. Signed-off-by: Ayush Singh <ayush@beagleboard.org>	2025-04-30 00:30:27 +10:00
Ayush Singh	f4a7e713ea	zephyr/machine_pwm: Implement PWM support. ... Implement PWM support using standard zephyr APIs, exposed as the standard MicroPython `machine.PWM` class. Signed-off-by: Ayush Singh <ayush@beagleboard.org>	2025-04-30 00:28:45 +10:00
Maureen Helm	3c8d1b13f5	zephyr: Upgrade to Zephyr v4.0.0. ... Updates the Zephyr port build instructions. The CI is updated to use Zephyr docker image 0.27.4, SDK 0.17.0 and the latest Zephyr release tag. Tested on max32690fthr and frdm_k64f. Signed-off-by: Maureen Helm <maureen.helm@analog.com> Signed-off-by: Detlev Zundel <dzu@member.fsf.org>	2025-04-29 23:00:37 +10:00
Detlev Zundel	b83606fe33	zephyr: Remove reference to CONFIG_MMC_VOLUME_NAME for v4.0. ... Commit 07a8e3253a2d8a2076c9c83c4ed4158fa3fbb2a2 removes CONFIG_MMC_VOLUME_NAME from the Kconfig space. Instead we need to use the device tree to find the "disk-name" property of "zephyr,mmc-disk" devices. Signed-off-by: Detlev Zundel <dzu@member.fsf.org>	2025-04-29 23:00:37 +10:00
Detlev Zundel	cd3eaad05c	zephyr: Fix call to thread_analyzer_print for v4.0. ... Commit 1b6e0f64796dfd6f86a8679ea6d24e1fca1e63a8 for Zephyr v4.0.0 changed the function "thread_analyzer_print" to require a cpu argument and allow thread analysis on each cpu separately. The argument is ignored when THREAD_ANALYZER_AUTO_SEPARATE_CORES=n which is the default on single core machines. Promote this change to the MicroPython zephyr module. Signed-off-by: Detlev Zundel <dzu@member.fsf.org> Signed-off-by: Maureen Helm <maureen.helm@analog.com>	2025-04-29 23:00:37 +10:00