Bloom v0.9.0

Feature release

---

This release includes significant changes to Bloom's internals. Although best efforts have gone into testing the release, users may face some issues as a result of the changes. In the event that you come across any issues, please report them as soon as possible.

Debug tool drivers:

• JTAGICE3, requested by @septatrix and @maximevince

For configuration values, see https://bloom.oscillate.io/docs/configuration#debug-tool-target-config

Custom GDB commands (via the monitor GDB command)

• monitor help - Displays help text, describing the supported monitor commands.
• monitor version - Displays Bloom's version number.
• monitor version machine - Outputs Bloom's version number in JSON format.
• monitor target-info machine - Outputs information on the connected target, in JSON format.
• monitor reset - Resets the target and holds it in a stopped state. See #24 for more.

Other

• --version-machine CLI command - Outputs Bloom's version number in JSON format.

Bug fixes

• Insight was needlessly refreshing GPIO pin states twice, when the user would update a PORT register via the register inspection window.
• The GDB debug server would fail and shutdown (causing the rest of Bloom to follow) when an exception was thrown during the processing of a TargetExecutionResumed event (sending a stop reply packet to the GDB client).
• Bloom wasn't operating correctly when used with CLion 2022.1 (and possibly some other versions proceeding 2021.1) - CLion was configuring GDB to include frames before the entry point, when generating backtraces. This was resulting in GDB requesting memory reads at invalid memory addresses, which Bloom was handling incorrectly. See #37 for more.