Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Keep target halted after activation #98

Open
navnavnav opened this issue Dec 3, 2023 · 1 comment
Open

Keep target halted after activation #98

navnavnav opened this issue Dec 3, 2023 · 1 comment
Assignees
@navnavnav
Labels
enhancement New feature or request
Milestone
v2.0.0

Comments

@navnavnav
Copy link
Member

Currently, Bloom will automatically reset and resume target execution shortly after establishing a connection with the target. This can be undesirable.

There should be an option to keep the target halted after reset and activation.

Hoping to include this in the next feature release, v1.1.0.
@navnavnav navnavnav added the enhancement New feature or request label Dec 3, 2023
@navnavnav navnavnav added this to the v1.1.0 milestone Dec 3, 2023
@navnavnav navnavnav self-assigned this Dec 3, 2023
@navnavnav navnavnav changed the title Halt target on activation Keep target halted after activation Dec 3, 2023
@navnavnav
Copy link
Member Author

Development work for this is complete. Bloom will keep the target halted by default, unless the new resume_on_startup target config param is set to true.

These changes will be included in v2.0.0. Will close this ticket once that release is live.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@navnavnav navnavnav

Labels
enhancement New feature or request
Milestone
v2.0.0
Development

No branches or pull requests
1 participant
@navnavnav