17143 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Alessandro Gatti	901c96dc55	py/emitnative: Remove redundant RV32 Viper int-indexed code. ... This commit removes redundant RV32 implementations of certain int-indexed code generation operations (32-bit load/store and 16-bit load). Those operations were already available as part of the native emitter API but were not exposed to the Viper code generator. As part of the introduction of more specialised load and store API calls to int-indexed Viper load/store generator bits, the existing native emitter implementations are reused, thus making the Viper implementations redundant. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 11:29:02 +10:00
Alessandro Gatti	84ad2c6cd0	py/asmxtensa: Extend existing specialised load/store operations range. ... This commit updates the existing specialised implementations for int-indexed 32-bit load and store operations, and adds a specialised implementation for int-indexed 16-bit load. The 32-bit operations relied on the fact that their applicability was limited to a specific range, falling back on a generic implementation otherwise. Introducing a single entry point for each int-indexed load/store operation size would break that assumption. Now those two operations contain fallback code to generate working code by themselves instead of raising an exception. The 16-bit operation instead simply did not have any range check, but it was not exposed directly to the Viper emitter. When a 16-bit int-indexed load entry point was introduced, the existing implementation would fail when accessing memory outside its 0..255 halfwords range. A specialised implementation is now present, performing fewer operations than the existing Viper emitter equivalent. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 11:29:02 +10:00
Alessandro Gatti	1f5ba6998b	py/asmthumb: Extend load/store generators with ARMv7-M opcodes. ... This commit lets the Thumb native code generator backend emit ARMv7-M specific opcodes for indexed load/store operations if possible. Now T3 opcode encodings are used if the generator backend is configured to allow emitting ARMv7-M opcodes and if the (unsigned) scaled index fits in 12 bits. Or, in other words, LDR{B,H}.W and STR{B,H}.W opcodes are now emitted if possible. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 11:29:02 +10:00
Alessandro Gatti	78ee1bac60	py/emitnative: Let Viper int-indexed code use appropriate operands. ... This commit extends the generic ASM API by adding the rest of the ASM_{LOAD,STORE}[size]_REG_REG_OFFSET macros whenever applicable. The Viper int-indexed load/store code generator was changed to use those API functions if they are available, falling back to backend-specific implementations if possible and ultimately to a generic implementation. Right now all backends except for x64 implement load16, load32, and store32 operations (x64 only implements load16). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 11:29:02 +10:00
Jeff Epler	e43a3849d9	lib/berkeley-db-1.xx: Update submodule to latest. ... Fixes a memory leak in the case lseek fails when creating the mpool. Signed-off-by: Jeff Epler <jepler@gmail.com>	2025-06-10 11:24:50 +10:00
Andrew Leech	fffaf8a41f	extmod/modnetwork: Consolidate definition of common drivers. ... Most extmod network drivers were being defined on a per-port basis, duplicating code and making enabling a driver on a new port harder. This consolidates extmod driver declarations and removes the existing per-port definitions of them. This commit has been verified to be a no-op in terms of firmware change. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-10 11:20:38 +10:00
Andrew Leech	95203ab88b	tools/boardgen.py: Ensure board pin locals_dict has consistent order. ... `tools/boardgen.py` is used by the `make-pins.py` scripts in many ports to generate the pin definitions for the machine module. In #17391 it was found that this is currently generating the C structs for board pin definitions with inconsistent ordering (across different build runs), which makes it sometimes impossible to get a consistent binary file even for no change in source files. This commit fixes that by sorting the board pin names alphabetically. Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-10 11:09:14 +10:00
Alessandro Gatti	b8e56a17b1	github/workflows: Split QEMU/Arm builds into separate entries. ... This commit takes the QEMU/Arm CI build and test step and splits it into three separate steps (bigendian, sabrelite, thumb), to allow them to run in parallel. Currently the QEMU/Arm CI build step would take up to 16 minutes, often being the last step blocking a full test run. With this commit, when the steps run in parallel the time it takes to complete the QEMU/Arm build and test procedure is cut in half - taking between 8 to 9 minutes depending on the CI runner load. The existing `ci_build_and_test_arm` function has been removed, in favour of having three separate functions - one per configuration. They are called `ci_build_and_test_arm_bigendian`, `ci_build_and_test_arm_sabrelite`, and `ci_build_and_test_arm_thumb`. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-10 10:57:32 +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
Damien George	5b340b12b8	tests/run-tests.py: Remove filename arg from prepare_script_for_target. ... It's no longer used. Signed-off-by: Damien George <damien@micropython.org>	2025-06-05 15:18:30 +10:00
Damien George	229104558f	tests/run-tests.py: Automatically skip tests that are too large. ... Some tests are just too big for targets that don't have much heap memory, eg `tests/extmod/vfs_rom.py`. Other tests are too large because the target doesn't have enough IRAM for native code, eg esp8266 running `tests/micropython/viper_args.py`. Previously, such tests were explicitly skipped on targets known to have little memory, eg esp8266. But this doesn't scale to multiple targets, nor to more and more tests which are too large. This commit addresses that by adding logic to the test runner so it can automatically skip tests when they don't fit in the target's memory. It does this by prepending a `print('START TEST')` to every test, and if a `MemoryError` occurs before that line is printed then the test was too big. This works for standard tests, tests that go via .mpy files, and tests that run in native emitter mode via .mpy files. For tests that are too big, it prints `lrge <test name>` on the output, and at the end prints them on a separate line of skipped tests so they can be distinguished. They are also distinguished in the `_result.json` file as a skipped test with reason "too large". Signed-off-by: Damien George <damien@micropython.org>	2025-06-05 15:15:31 +10:00
Damien George	4c55b0879b	tools/ci.sh: Allow errors in code-size build to fail the CI. ... It was possible for CI to pass even if the bare-arm port fails to build. This commit fixes that. Signed-off-by: Damien George <damien@micropython.org>	2025-06-05 14:57:23 +10:00
Alessandro Gatti	193603dbac	tools/ci.sh: Clean the correct MPY files when batch compiling. ... This commit fixes a small yet harmless issue that occurs when invoking `ci_native_mpy_modules_build` on a persistent environment, as only X64 MPY files would be removed by the cleaning process. Now the correct architecture is passed at all times when cleaning before building a natmod for a particular architecture, forcing a full build of all files to better simulate the CI environment (where there's no state persisted between runs for this step). Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:40 +10:00
Alessandro Gatti	e8c92240e2	tools/ci.sh: Remove natmod build restrictions for Xtensa. ... This commit lets the CI pipeline build all natmods for the Xtensa target, now that ROM symbols can be used in the linking process. The restriction was put in place due to build failures on certain natmods for Xtensa, as ROM symbols would not be used, causing undefined symbol errors at build time. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	e4c0e2b73d	esp8266/main: Print error information on crash-induced reboots. ... This commit adds an optional configuration option for the ESP8266 port that, if the board rebooted due to a crash, will print to stdout some information about the error that triggered the issue. It is not possible using regular SDK functions to intercept errors and print information at that stage, and the only error response from the board is to reboot itself. This is the next best thing, print some error information just once at boot time after the crash - the least invasive option given the situation we're in. This is disabled by default, and can be enabled by enabling MICROPY_HW_HARD_FAULT_DEBUG in the port configuration - obviously with a small increase in the firmware code footprint. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	4227654d42	examples/natmod/btree: Fix build for Xtensa. ... This commit provides the appropriate external symbol addresses to let the "btree" example natmod build for the Xtensa platform. On the ESP8266, unsigned integer division code isn't provided as part of libgcc.a, libm.a, or libc.a, but it is instead provided by the ROM. Regular builds inject the appropriate symbol addresses as part of the linking process (see eagle.rom.addr.v6.ld), but natmods need this information brought in from somewhere else. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	887125fc58	examples/natmod/deflate: Fix build for Xtensa. ... This commit provides the appropriate external symbol addresses to let the "deflate" example natmod build for the Xtensa platform. Unlike other natmods that require an external symbol list to build without bringing in the whole runtime libraries set, this natmod is referencing the `__modsi3` symbol which was removed from the ESP8266's SDK but not present in ROM. The latter only has a `__umodsi3` implementation that only operates on unsigned values, and thus unable to handle this natmod. Thus, the extended library resolution process is enabled for this natmod as a `__modsi3` implementation is made available that way (still using ROM symbols whenever possible). This also means that symbols that appear in both ROM and external libraries sort of co-exist in the final MPY file, with ROM symbols being used by natmod code but the implementation from the library still exists in the final MPY file, unused. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	462ee12d3c	examples/natmod/framebuf: Fix build for Xtensa. ... This commit provides the appropriate external symbol addresses to let the "framebuf" example natmod build for the Xtensa platform. On the ESP8266, integer division code isn't provided as part of libgcc.a, libm.a, or libc.a, but it is instead provided by the ROM. Regular builds inject the appropriate symbol addresses as part of the linking process (see eagle.rom.addr.v6.ld), but natmods need this information brought in from somewhere else. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	0bf2fd7ad0	examples/natmod/random: Fix build for Xtensa. ... This commit provides the appropriate external symbol addresses to let the "random" example natmod build for the Xtensa platform. On the ESP8266, signed integer division code isn't provided as part of libgcc.a, libm.a, or libc.a, but it is instead provided by the ROM. Regular builds inject the appropriate symbol addresses as part of the linking process (see eagle.rom.addr.v6.ld), but natmods need this information brought in from somewhere else. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +10:00
Alessandro Gatti	9ef7322a5d	tests/run-natmodtests.py: Allow injected code customisation. ... This commit introduces a mechanism to customise the code that is injected to the board when performing a native module import. A new argument, "-b"/"--begin", is added so regular Python code can be inserted in the injected fragment between the module file creation and the effective module import. This is needed for running natmod tests on ESP8266 as that board does not have enough memory to fit certain modules unless additional configuration is performed. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-06-04 22:35:39 +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	9174cffc47	mpy-cross/main: Document emit=host option in help. ... Signed-off-by: Damien George <damien@micropython.org>	2025-06-04 12:07:30 +10:00
Damien George	e869dae31e	mpy-cross/main: Exit with error if arch not specified with emit=native. ... Currently, mpy-cross will crash if called as: mpy-cross -X emit=native foo.py because it tries to use the native emitter with no target architecture set. Fix that by checking that an architecture is set when `-X emit=native` or `-X emit=viper` is used. Signed-off-by: Damien George <damien@micropython.org>	2025-06-04 12:06:12 +10:00
Andrew Leech	820485358d	unix/coverage: Add coverage test for mp_sched_schedule_node. ... Test modified to reschedule itself based on a flag setting. Without the change in the parent commit, this test executes the callback indefinitely and hangs but with the change it runs only once each time mp_handle_pending() is called. Modified-by: Angus Gratton <angus@redyak.com.au> Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-04 11:31:12 +10:00
Angus Gratton	7f274c7550	py/scheduler: Only run scheduler callbacks queued before run started. ... Without this change, a scheduler callback which itself queues a new callback will have that callback executed as part of the same scheduler run. Where a callback may re-queue itself, this can lead to an infinite loop. With this change, each call to mp_handle_pending() will only service the callbacks which were queued when the scheduler pass started - any callbacks added during the run are serviced on the next mp_handle_pending(). This does mean some interrupts may have higher latency (as callback is deferred until next scheduler run), but the worst-case latency should stay very similar. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-04 11:31:12 +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
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
Andrew Leech	17898f8607	stm32/machine_adc: Enable ADC re-read errata handling for STM32WB55. ... Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-04 02:11:23 +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	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
Angus Gratton	d23fb86934	tests/multi_net: Add test coverage for socket recv flag MSG_DONTWAIT. ... Adding multi_net case for UDP only, as TCP timing is hard to test reliably. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-03 12:52:25 +10:00
Angus Gratton	73d4ddce6c	tests/multi_net: Add test coverage for socket recv flag MSG_PEEK. ... Adds TCP and UDP multi_net test cases. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-03 12:52:22 +10:00
Angus Gratton	0b224048ef	unix/modsocket: Expose MSG_PEEK flag for recv & recvfrom. ... 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	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	e8447768ef	extmod/modlwip: Add optional flags argument for recv and recvfrom. ... Implements MSG_PEEK and MSG_DONTWAIT. This work was funded through GitHub Sponsors. Signed-off-by: Angus Gratton <angus@redyak.com.au>	2025-06-03 12:52:02 +10:00
Damien George	4dff9cbf1a	tests/run-tests.py: Change _results.json to have a combined result list. ... The `_results.json` output of `run-tests.py` was recently changed in 7a55cb6b36 to add a list of passed and skipped tests. The way this was done turned out to be not general enough, because we want to add another type of result, namely tests that are skipped because they are too large. Instead of having separate lists in `_results.json` for each kind of result (pass, fail, skip, skip too large, etc), this commit changes the output form of `_results.json` so that it stores a single list of 3-tuples of all tests that were run: [(test_name, result, reason), ...] That's more general and allows adding a reason for skipped and failed tests. At the moment this reason is just an empty string, but can be improved in the future. Signed-off-by: Damien George <damien@micropython.org>	2025-06-03 10:07:29 +10:00
Andrew Leech	c0111e63b3	lib/libhydrogen: Update to latest release. ... Signed-off-by: Andrew Leech <andrew.leech@planetinnovation.com.au>	2025-06-02 21:28:51 +10:00
Damien George	dea3035b88	tools/pyboard.py: Add write_timeout and catch errors in enter_raw_repl. ... If the USB serial device locks up, then writes to that device can hang forever. That can make the test runner `tests/run-tests.py` lock up, among other problems. This commit introduces a 5 second write-timeout, and catches any OSError's raised during `enter_raw_repl()`. Now, if a USB serial device locks up, `enter_raw_repl()` will eventually raise an exception. Signed-off-by: Damien George <damien@micropython.org>	2025-06-02 17:02:59 +10:00
Damien George	b1c947ab45	tools/pyboard.py: Introduce timeout_overall for read_until(). ... This applies the mpremote commit 03fe9c55ea to pyboard.py. The `timeout_overall` is used in `enter_raw_repl()`. It prevents waiting forever for a serial device that does not respond to the Ctrl-C/Ctrl-D/etc commands and is constantly outputting data. Signed-off-by: Damien George <damien@micropython.org>	2025-06-02 17:02:30 +10:00
Damien George	aaedd59b7c	tools/pyboard.py: Avoid initial blocking read in read_until(). ... This applies the mpremote commit 0d46e45a1f to pyboard.py. If the target does not return any data then `read_until()` will block indefinitely. Fix this by making the initial read part of the general read look, which always checks `inWaiting() > 0` before reading from the serial device. Also added the UART timeout to the constructor. This is not currently used but may be used as an additional safeguard. Signed-off-by: Damien George <damien@micropython.org>	2025-06-02 17:02:30 +10:00
Alessandro Gatti	f5d10c322e	py/asmxtensa: Emit prologue jump only when constants table is in use. ... This commit simplifies native functions' prologue code by not emitting a jump opcode that goes over the function's constants pool if the pool is empty. The original code assumed the constants pool is never empty as large 32-bits constants are commonly used, but for inline assembler functions that may not be the case. This meant that inline assembler functions may start with an unneeded jump (along with its alignment byte), using four bytes more than necessary. This commit is limited to the "xtensa" target, as "xtensawin" doesn't support inline assembler functions yet, so native functions' constant pools are almost always guaranteed to hold one or more values. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-29 12:12:39 +10:00
Alessandro Gatti	1006ed69f0	py/emitinlinextensa: Add the rest of LX3 opcodes to the assembler. ... This commit expands the Xtensa inline assembler to support most if not all opcodes available on the ESP8266 and LX3 Xtensa cores. This is meant as a stepping stone to add inline assembler support for the ESP32 and its LX6 core, along to windowed-specific opcodes and additional opcodes that are present only on the LX7 core (ESP32-S3 and later). New opcodes being added are covered by tests, and the provided tests were expanded to also include opcodes available in the existing implementation. Given that the ESP8266 space requirements are tighter than ESP32's, certain opcodes that won't be commonly used have been put behind a define to save some space in the general use case. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-29 12:12:39 +10:00
Alessandro Gatti	555f1cf488	py/asmxtensa: Make the generated code dumper work on mpy-cross. ... This commit fixes compilation errors occurring when enabling the Xtensa code dumper inside mpy-cross. The original code was meant to dump the code from an Xtensa device itself, but for debugging the inline assembler this functionality was also needed off-line. The changes involve solving a signed/unsigned mismatch that was not much of a problem for the 8266's gcc version but made modern compilers complain, and using the printf formatter for pointers when it comes to printing code addresses. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-29 12:12:39 +10:00
Alessandro Gatti	eccd23feb6	py/asmxtensa: Replace printf messages with exceptions. ... This commit removes old raw printf calls happening inside certain branch opcode emitters, indicating the target label is out of range for the opcode. They have been replaced with a RuntimeError being raised in these cases, using a parameterised qstr instead. Whilst this technically breaks runtime behaviour expectations, the generated code would not have worked anyway so it's better to catch those cases early. This should be updated to always emit long jumps unless jumps are backwards and short enough, following the other ports, but that's something coming later. This is actually needed because there are test files that do not work when processed through mpy-cross and entirely converted to native code. The original implementation would still generate mostly-valid code that was bound to crash on the device, whilst this change would prevent invalid code to even be emitted in the first place. Signed-off-by: Alessandro Gatti <a.gatti@frob.it>	2025-05-29 12:12:39 +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