zeptoforth

This release has working SPI, SDHC/SDXC card, and FAT32 support on all supported platforms (note that on STM32 platforms NSS must be turned disabled and SSM needs to be enabled and selected for the SPI peripheral in use when using SDHC/SDXC cards) and adds the words s>d, d>s, s>f, and f>s for converting between single-cell, double-cell, and S31.32 fixed-point values.

This release adds a 'monitor' functionality optionally started with start-monitor in the monitor module which adds the ability to use "attention" (i.e. Control-T or, in zeptocom.js, the Attention button) followed by t to list all running tasks even when the REPL is not active, an ability to set hooks to be called when tasks terminate, task termination reason functionality which is exposed to task termination hooks and to any other tasks that may wish to query a given task, and an expansion of the capabilities of dump-tasks in the task module to dump information on tasks on both cores on the RP2040 (i.e. the Raspberry Pi Pico).

This release adds the ability to send exceptions to tasks with signal in the task module, which can be done within an interrupt handler, and using this adds an "attention" key, mapped to Control-T, which takes a (currently single-character) command even when the console is not being read and acts on it; currently the only "attention" key command is z, which sends an exception to the main task (with the general goal being to return control to the REPL after allowing cleanup to take place). Additionally main-task in the task module has been changed so it always refers to the main task of the first core on the RP2040, whereas previously it would refer to the initial core of the second core when executed within the second core. Last but not least, a fix has been made to a bug where the console would be practically unusable if the second core was booted on the RP2040.

This release adds Control-C support at the console to reboot the microcontroller (which is used by the 'Reboot' button in the latest zeptocom.js), providing it is not severely wedged, adds optimizations for sending and receiving bytes as master over SPI, fixes a lurking bug where the incorrect use of bis! to set NVIC registers in the interrupt module was masking a significant interrupt-handling bug in multicore operation on the RP2040 by incorrectly clearing pending interrupts which would otherwise be unhandled, and fixes the aforementioned RP2040 multicore interrupt bug which was unmasked by fixing the aforementioned incorrect use of bis!.

This patch-level release fixes a number of concurrency bugs, particularly ones affecting multicore operation on the Raspberry Pi Pico.

This patch-level release fixes a couple significant bugs in the multitasker and peripheral support for the Raspberry Pi Pico with regard to multicore operation; booting the second core was incorrectly resetting systick-counter to 0, which was causing problems with other tasks, particularly tasks in the midst of a delay, and interrupts were not being properly initialized when the second core was being booted, which was causing problems with regard to the I2C peripherals of the RP2040 in particular. Also note that interrupts are now being used by the SPI peripherals of the RP2040, whereas previously interrupts had not been properly initialized for such.

This patch-level release adds the capability to create closures with arbitrary numbers of bound values with nbind in the closure module.

This release adds closures which may be created with bind or 2bind in the closure module. These serve to provide a means to produce arbitrary execution tokens which are bound with runtime-specified data at arbitrary addresses, which may be replaced or disposed of as the user sees fit, unlike words defined with <builds and does>, which are permanently defined and can only be disposed of through erasing flash, if compile to flash, or rebooting, if compiled to RAM.

This patch-level release adds word annotations to the fault output, making it easier for the user to identify the location of faults in the codebase.

This release adds best-effort fault recovery, with, if possible, faults in the main task resulting in the user being returned to the REPL, faults in other tasks resulting in those tasks being terminated, and faults in hardware interrupt/exception handlers, with the exception of the hardfault handler, resulting in the user being returned to a REPL in a recovery mode where interrupts (and thus multitasking) is not available. When faults occur, information relating to the state of the system at the time and place of the fault, including the PC, registers, data stack contents, and return stack contents, are output on the console.