950 Commits

Author	SHA1	Message	Date
Damien George	b3cd1a355e	extmod/modtime: Move tuple creation to common localtime implementation. ... This factors code out of the ports and into the common `time.localtime` implementation in `extmod/modtime.c`. That helps to reduce code duplication, prevent errors in implementation, and reduce code size on some ports (mimxrt and stm32 at least). Signed-off-by: Damien George <damien@micropython.org>	2025-08-15 12:09:13 +10:00
Daniël van de Giessen	8c47ff7153	esp32/network_ppp: Correctly clean up PPP PCB after close. ... If PPP is still connected, freeing the PCB will fail and thus instead we should trigger a disconnect and wait for the lwIP callback to actually free the PCB. When PPP is not connected we should check if the freeing failed, warn the user if so, and only mark the connection as inactive if not. When all this happens during garbage collection the best case is that the PPP connection is already dead, which means the callback will be called immediately and cleanup will happen correctly. The worst case is that the connection is still alive, thus we are unable to free the PCB (lwIP won't let us) and it remains referenced in the netif_list, meaning a use-after-free happens later when lwIP traverses that linked list. This change does not fully prevent that, but it *does* improve how the PPP.active(False) method on the ESP32 port behaves: It no longer immediately tries to free (and fails), but instead triggers a disconnect and lets the cleanup happen correctly through the status callback. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-08-11 12:38:37 +10:00
Daniël van de Giessen	adcfdf625b	esp32/network_ppp: Use non-thread-safe API inside status callback. ... The status callback runs on the lwIP tcpip_thread, and thus must use the non-thread-safe API because the thread-safe API would cause a deadlock. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-08-11 12:38:37 +10:00
Daniël van de Giessen	361c615f3e	esp32/network_ppp: Use thread-safe API for PPPoS input. ... A small follow-up to 3b1e22c669, in which the entire PPP implementation was reworked to more closely resemble the extmod version. One of the differences between extmod and the ESP32 port is that the ESP32 port uses the thread-safe API, but in that changeset the PPP input function was accidentally changed to use the non-safe API. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-08-11 12:38:37 +10:00
Daniël van de Giessen	1273751a3b	esp32: Support building against IDFv5.5. ... Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-08-11 12:23:02 +10:00
Angus Gratton	593ae04eeb	esp32/machine_timer: Fix machine.Timer() tick frequency on ESP32C2,C6. ... Also future-proofs this code for other chips. Apart form C6 and C2, all currently supported chips use APB clock for GPTIMER_CLK_SRC_DEFAULT. ESP32-C2 uses 40MHz PLL but APB_CLK_FREQ was 26MHz. ESP32-C6 uses 80MHz PLL but APB_CLK_FREQ was 40MHz. Implementation now gets the correct frequency from ESP-IDF. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-08-07 16:55:46 +10:00
Angus Gratton	ce109af712	esp32/machine_timer: Enable timer clock source for ESP32C6. ... Otherwise the PLL is not enabled. These changes are adapted from `timer_legacy.h` in ESP-IDF. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-08-07 16:55:23 +10:00
Damien George	d5ecda05eb	ports: Allow MICROPY_PY_MACHINE_I2C_TARGET to be disabled by board cfg. ... Signed-off-by: Damien George <damien@micropython.org>	2025-08-07 10:33:26 +10:00
Damien George	3c9546ea09	esp32/mpconfigport: Disable I2CTarget on ESP32-C6 to reduce code size. ... I2CTarget costs about 8k of flash size on ESP32-S2, and about 11k on ESP32-C6. The ESP32-C6 only has about 8k remaining, so disable I2CTarget on that SoC until more flash can be made available. Signed-off-by: Damien George <damien@micropython.org>	2025-08-02 08:53:36 +10:00
Jonathan Hogg	327655905e	esp32/modules/machine.py: Add Counter and Encoder classes. ... Adds a Python override of the `machine` module, which delegates to the built-in module and adds an implementation of `Counter` and `Encoder`, based on the `esp32.PCNT` class. Original implementation by: Jonathan Hogg <me@jonathanhogg.com> Signed-off-by: Jim Mussared <jim.mussared@gmail.com>	2025-08-01 23:45:18 +10:00
Jonathan Hogg	c3f3339c87	esp32/modesp32: Add esp32.PCNT class. ... Add a new `esp32.PCNT` class that provides complete, low-level support to the ESP32 PCNT pulse counting hardware units. This can be used as a building block to implement the higher-level `machine.Counter` and `machine.Encoder` classes. This is enabled by default on all OG, S2, S3, C6 boards, but not on C3 (as the PCNT peripheral is not supported). Original implementation by: Jonathan Hogg <me@jonathanhogg.com> Signed-off-by: Jim Mussared <jim.mussared@gmail.com> Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-08-01 23:45:18 +10:00
Damien George	7bc83afee2	esp32/machine_i2c_target: Implement I2CTarget class. ... Only soft IRQs are supported. Signed-off-by: Damien George <damien@micropython.org>	2025-08-01 23:03:17 +10:00
Damien George	ac5b1bce99	esp32/machine_i2c: Factor default pin macros to header file. ... So the implementation of I2CTarget can use them. Signed-off-by: Damien George <damien@micropython.org>	2025-08-01 23:03:17 +10:00
Angus Gratton	d4399b3230	esp32: Fix first line ESP32-C2 serial output after reset or deepsleep. ... ESP32-C2 ROM prints at 74880bps (same as ESP8266), so need a newline before first MicroPython output to avoid it being appended on end of a line of noise. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-30 10:51:29 +10:00
Angus Gratton	77c9eb7795	esp32: Add "Free RAM" optimisation config flags. ... This is necessary for ESP32-C2 Wi-Fi & BT to work reliably (and for TLS to work at all). On IDF 5.4.2 the free static RAM goes from 60KB to 100KB, and there will also be a reduction in lwIP & Wi-Fi memory use at runtime. The performance trade-off seems low for most use cases, although it will probably be significant for certain combinations of load (i.e. heavy TCP/IP, heavy BT throughput, and some peripheral driver functions). Added as a set of config flags because this is potentially useful on other SoCs where the goal is to maximise RAM available for MicroPython. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-07-30 10:51:29 +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
Jeff Epler	0c8d35b322	ports: Eliminate define of {U,}INT_FMT where redundant. ... The default definition in `py/mpconfig.h` for 32-bit architectures is `%u/%d`, so these can be removed. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-07-25 10:54:27 +10:00
Damien George	10ef3e4ac2	esp32: Update to use ESP-IDF v5.4.2. ... This is a patch release of the IDF. Comparing with 5.4.1, firmware size is up by about 1.5k on ESP32 and 9k on ESP32-S3. But IRAM usage (of the IDF) is down by about 500 byte on ESP32 and DRAM usage is down by about 20k on ESP32 and 10k on ESP32-S3. Testing on ESP32, ESP32-S2, ESP32-S3 and ESP32-C3 shows no regressions, except in BLE MTU ordering (the MTU exchange event occuring before the connect event). Signed-off-by: Damien George <damien@micropython.org>	2025-07-23 12:52:49 +10:00
Damien George	79b2d4ff22	esp32/machine_uart: Improve sendbreak so it doesn't reconfig the UART. ... Currently, `UART.sendbreak()` on esp32 will reconfigure the UART to a slower baudrate and send out a null byte, to synthesise a break condition. That's not great because it changes the baudrate of the RX path as well, which could miss incoming bytes while sending the break. This commit changes the sendbreak implementation to just reconfigure the TX pin as GPIO in output mode, and hold the pin low for the required duration. Signed-off-by: Damien George <damien@micropython.org>	2025-07-23 12:50:29 +10:00
Yoctopuce dev	df05caea6c	shared/timeutils: Standardize supported date range on all platforms. ... This is code makes sure that time functions work properly on a reasonable date range, on all platforms, regardless of the epoch. The suggested minimum range is 1970 to 2099. In order to reduce code footprint, code to support far away dates is only enabled specified by the port. New types are defined to identify timestamps. The implementation with the smallest code footprint is when support timerange is limited to 1970-2099 and Epoch is 1970. This makes it possible to use 32 bit unsigned integers for all timestamps. On ARM4F, adding support for dates up to year 3000 adds 460 bytes of code. Supporting dates back to 1600 adds another 44 bytes of code. Signed-off-by: Yoctopuce dev <dev@yoctopuce.com>	2025-07-09 11:54:21 +10:00
Daniël van de Giessen	431b79146e	esp32/panichandler: Support building against IDFv5.4.2. ... The IDF panic handler resets the watchdog timeout to prevent the printing of the error message from being cut off by a WDT reset. We use the exact same function call in our wrapper function for the same purpose. In IDFv5.4.2 the function used for this was changed from `esp_panic_handler_reconfigure_wdts` to `esp_panic_handler_feed_wdts`, specifically in this commit: cd887ef59a Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-07-06 00:14:10 +10:00
Garatronic	b4b7c0a003	esp32/boards/GARATRONIC_PYBSTICK26_ESP32C3: Add pybstick26-esp32c3 defn.	2025-06-26 10:44:48 +10:00
Meir Armon	c1196cadb1	esp32/modesp32: Fix access to ext0_pin only if defined. ... In different functions `machine_rtc_config.ext0_pin` is accessed where SOC_PM_SUPPORT_EXT0_WAKEUP is not defined, fix that. Signed-off-by: Meir Armon <meirarmon@gmail.com>	2025-06-17 10:31:41 +10: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
Damien George	fa393feaed	esp32/README: Update README to describe auto filesystem sizing. ... Signed-off-by: Damien George <damien@micropython.org>	2025-06-14 01:06:27 +10:00
Damien George	6201e77999	esp32/boards: Convert all boards to auto detect flash size. ... Remove the "vfs" entry from all partitions-*.csv files, and then remove duplicated files. And remove the ESP32_GENERIC_S3-FLASH_4M variant, because it's no longer needed. Signed-off-by: Damien George <damien@micropython.org>	2025-06-14 01:06:12 +10:00
Damien George	2a0e2b5782	esp32/main: Auto detect the size of flash and auto create vfs partition. ... Currently in the esp32 port the size of the SPI flash must be configured at build time, eg 4MiB, 8MiB, etc. Also, the esp32 partition table must be configured at build time, which depends on the size of the SPI flash. A bigger flash means more can be allocated to the user filesystem. This commit makes it so the SPI flash size is automatically determined at runtime, and the filesystem size is automatically set to take up as much room as possible (a "vfs" partition is created automatically if it doesn't exist). This works by: - Setting the SPI flash size to be 4MiB in the build (or some other value, as long as the firmware app fits). - Removing the vfs partition from the esp32 partition table (only nvs, phy_init and firmware, and maybe romfs, remain in the partition table). - At boot, query the physical size of the SPI flash and use that as the actual size in the code. - If it doesn't already exist, automatically create a "vfs" partition which takes up the flash from the end of all existing partitions to the end of flash. This allows simplifying a lot of board configurations, and removing some board variants that just change the flash size (to be done in a following commit). It's also fully backwards compatible, in the following sense: - Existing boards with MicroPython firmware will continue to work with the same filesystem, ie the filesystem won't be erased when the firmware is updated. - If a user has a custom esp32 partition table and installs MicroPython as a bare app into the app partition, the new MicroPython firmware will honour the esp32 partition table and use either "vfs" or "ffat" partitions as the filesystem. Signed-off-by: Damien George <damien@micropython.org>	2025-06-14 01:03:44 +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
Daniël van de Giessen	2c2f0b292a	esp32: Re-use allocated timer interrupts and simplify UART timer code. ... If the interrupt is not freed but merely disabled, instead of reallocating it every time the timer is enabled again we can instead just re-enable it. That means we're no longer setting the handler every time, and we need to ensure it does not change. Doing so by adding an additional wrapper function does not only solve that problem, it also allows us to remove some code duplication and simplify how machine_uart uses the timer. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-06-05 16:39:13 +10:00
Daniël van de Giessen	bf909303ff	esp32/machine_timer: Do not free interrupt from ISR. ... esp_intr_free is not safe to call from the timer ISR because it requires the current task (the one the ISR interrupted) to be pinned to the same core as the interrupt was allocated on. Merely disabling the ISR however is safe since that only requires that we're currently running on the same core (which the ISR always is), regardless of the current task. This was causing deadlocks in machine_uart when the ISR happened to interrupt a task that was not pinned to a specific core. Signed-off-by: Daniël van de Giessen <daniel@dvdgiessen.nl>	2025-06-05 16:39:13 +10:00
Andrew Leech	d5f2fc239a	extmod/modbluetooth: Add timeout to deinit. ... If the BLE radio stops responding before deinit is called the function can get stuck waiting for an event that is never received, particularly if the radio is external or on a separate core. This commit adds a timeout, similar to the timeout already used in the init function. Updated for nimble, btstack, esp32 and zephyr bindings. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-04 02:21:32 +10:00
Matt Trentini	3e33d0567f	ports: Update board.json files for vendor/product consistency. ... The vendor and product fields in the `board.json` files were somewhat inconsistent. Remove any duplication of the vendor name in the product field so that `f"{vendor} {product}"` reads well. In addition to that, update most of the URL's for `board.json` files that are modified here, and match case and spacing used by the manufacturers for the vendor and product names. Signed-off-by: Matt Trentini <matt.trentini@gmail.com>	2025-06-04 01:47:59 +10:00
Angus Gratton	4781cde4f7	esp32/modsocket: Add optional flags argument for recv and recvfrom. ... Implements MSG_PEEK and MSG_DONTWAIT (both passed through to LWIP sockets API). This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-03 12:52:06 +10:00
Angus Gratton	22f1d76633	shared/tinyusb: Use device event hook to schedule USB task. ... Previously MicroPython ports would linker-wrap dcd_event_handler in order to schedule the USB task callback to run when needed. TinyUSB 0.16 added proper support for an event hook to do the same thing without the hacky linker wrapping. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-05-26 11:15:33 +10:00
Malcolm McKellips	dc1af386a8	esp32/boards/SPARKFUN_IOT_REDBOARD_ESP32: Add SparkFun board. ... Add board definition files for SparkFun IoT RedBoard ESP32. Signed-off-by: Malcolm McKellips <malcolm.mckellips@sparkfun.com>	2025-05-22 10:37:38 +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