Releases: forged-org/provisioner-ui
Releases · forged-org/provisioner-ui
Provisioner UI 0.3.4
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
0.3.4
Added
- Added custom flashing support for non-probe-rs chips
- Probe speed can now be set via the command line arguments
Fixed
- The
--help
flag will now properly display CLI help. - Provisioner settings can be saved again
Provisioner UI 0.3.3
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
0.3.3
Added
- Uploaded blocks are now displayed on the report view
Changed
- Cleaned up colors and wording on the UI buttons
- Available updates are not prompted automatically anymore and shown in the settings panel.
- The changelog of the most recent update is shown in nice Markdown instead of just plain text.
- The titlebar now shows the client version.
- The steps display now provide more useful information:
- During programming, which chip and version is displayed
- During command execution, the command label is displayed
- Select the debug probe & provisioner token from the commandline
- Use 2MHz probe speed
- Make it possible to disable chip erase
Provisioner UI 0.3.2
Added
- The UI will now indicate what error is encountered when attempting to run a specific step
Changed
- RTT output is now attached to the run as a file instead of a log
- Attachments for flashing steps and command steps now have unique names to indicate which step
they're from
Fixed
- Fixed an issue where rerunning a device would erroneously create a new device and run
Provisioner UI 0.3.1
Added
- Arm64 builds are now automatically published as debian packages
Changed
- The UI now supports selecting steps to view output during execution
- Users can now return to step output after a run has completed execution
- More robust logging is added with
env_logger
Fixed
- Fixed some minor graphical issues with step listing
Provisioner UI 0.3.0
Changed
- Users are prevented from starting when there are no steps defined.
- Final result display made cleaner
Fixed
- Now only completes steps that are associated with its assigned station.
- No longer crashes sporadically when running custom commands
- Fixed an issue with uploading test logs
Provisioner UI 0.2.0
Changed
- The control flow of runs is now dynamic and controlled by the backend Rust tooling, which prevents
control flow from being interrupted by refreshing or navigating within the user interface. - Probe-rs version bumped to v0.17.0
- RTT may now be used for uploading all block data types
- RTT lines are now prefixed with
forged>
on RTT channel 0 and end with newlines - The provisioner is now driven by Playbooks configured in the project
Fixed
- Initial configuration settings will now properly display data in the settings screen after first setup
- The provisioner now lists the reasons for unsuccessful runs on the report view.
Provisioner UI 0.1.1
Added
-
Added the capability to stream RTT data from the running target to the forged backend during provisioning.
The provisioner scans the first two (0 and 1) channels of RTT on the target.
- Channel 0 is considered UTF8 text and directly translated and displayed in the log as is.
- Channel 1 is considered UTF8 text as well and expects a
<key>:<value>
format with multiple items separated via;
(<v>:<k>;<a>:<b>
).
The RTT transaction stops and the provisioner continues to the test steps once no data was received for longer than 1 second or an
endforged
element is encountered (<v>:<k>;endforged
).
If a badly formatted element is encountered, the run will fail.
Fixed
- Fixed an issue where initial setup would loop infinitely until the app was restarted
- Fixed an issue where the test step status would improperly display when modifying the specified test command
- Log data now sticks to the bottom of the window
Provisioner UI 0.1.0
Initial commit with a README