Bloom v0.11.0

Feature release

---

Project configuration

• Project configuration files are now expected to be in YAML format.
• The init command will now produce a YAML configuration file (bloom.yaml).
• To minimise disruption for current users, JSON configuration is still accepted. In the absence of a bloom.yaml file, Bloom will fall back to bloom.json.
• Renamed the updateDwenFuseBit AVR8 config param to manageDwenFuseBit. The old param is still supported but will be removed in a later release.

Insight

• Memory inspection panes
  • Can now be detached from the main Insight window
  • Auto-refresh is disabled by default (can be enabled by right-clicking the refresh tool button)
  • Individual bytes can be selected in the hex viewer and copied to the clipboard
  • Address labels in the hex viewer can be configured to display absolute or relative addresses (via a context menu presented when right-clicking any address label). This setting is persisted through debug sessions.
  • Added endianness/first-byte indicator on value annotations of focused memory regions, in the hex viewer.
  • Stale memory indicator
• Some minor style tweaks to the bitset widget on the register inspection window.

SVD generation via GDB monitor command

• monitor svd - Generates SVD and outputs to a file in the project directory.
• monitor svd --out - Generates SVD and sends the output to GDB, to display as command output. GDB front-ends (IDEs) can utilise this without requiring any user action.
• The monitor target-info machine command has been removed.

Other

• Upgraded Qt dependency to 6.2.4 LTS
• Verifying AVR8 physical interface configuration
  • Before activating the AVR8 target, Bloom will now confirm the selected physical interface is supported by the selected target. Upon confirmation failure, Bloom will warn the user and provide a list of the physical interfaces supported by the selected target.
  • Bloom will not abandon the startup routine upon confirmation failure, due to the possibility of false-positives.
  • Bloom can only perform this check in environments where the specific AVR8 target name has been provided in the environment configuration. Use of the generic avr8 target name will disable Bloom's ability to perform this check.

Bug fixes

• Widgets on the Insight window were overlapping on KDE Plasma desktops, due to the minimum window size being ignored. This was fixed by moving away from fixed minimum sizes on the memory inspection panel widget. See #48 for more.
• Bloom was failing to program some UPDI targets due to some buffers from GDB being misaligned, along with the lack of grouped flash writes. This was affecting targets such as the Atmega4809 on the Xplained Pro evaluation board.
• Bloom wasn't resetting the target after programming.
• Long memory reads issued by the Insight GUI were occupying the TargetController for too long, preventing it from servicing commands from the GDB debug server, resulting in GDB timeouts (which GDB would report as packet errors). These memory reads have now been split into batches, so that the TargetController can service other commands in-between, reducing the likelihood of timeouts when servicing a GDB command.
• Some instances of the error dialogue were displaying escaped characters.
• When using CLion's 'Embedded GDB Server' configuration, CLion was not allowing Bloom any opportunity to shutdown safely. As a result, the connected hardware was being left in an unknown state, which sometimes resulted in startup failures upon the user starting a new debug session. For information on how this was fixed, see #53.