7
31
Fork
You've already forked blackmagic
23

Fix: Reorder editing RISC-V triggers *after* the halting #2218

Merged
dragonmux merged 1 commit from ALTracer/blackmagic:fix/riscv-triggers-clear1 into main 2026年03月27日 11:29:30 +01:00
Contributor
Copy link

Detailed description

  • This is a small bugfix.
  • The existing problem is CSR access failed: 4 in new code in #2194
  • The PR solves that by reordering the clearing of triggers to happen after the halt in riscv_attach(). Detach is fine.

Tested on blackpill-f411ce against Icebreaker v1.0e (Hazard3 rv32ic) running Hazard3-minimal semihosting test in SPRAM, and
on BMDA via d6e7:3507 Sipeed Slogic Combo8 CMSIS-DAP against Sipeed Longan Nano (GD32VF1 rv32imac) running some default demo (likely badapple).

Your checklist for this pull request

Closing issues

## Detailed description * This is a small bugfix. * The existing problem is `CSR access failed: 4` in new code in https://codeberg.org/blackmagic-debug/blackmagic/pulls/2194 * The PR solves that by reordering the clearing of triggers to happen after the halt in `riscv_attach()`. Detach is fine. Tested on `blackpill-f411ce` against Icebreaker v1.0e (`Hazard3 rv32ic`) running Hazard3-minimal semihosting test in SPRAM, and on BMDA via d6e7:3507 Sipeed Slogic Combo8 CMSIS-DAP against Sipeed Longan Nano (`GD32VF1 rv32imac`) running some default demo (likely badapple). ## Your checklist for this pull request * [x] I've read the [Code of Conduct](https://codeberg.org/blackmagic-debug/blackmagic/src/CODE_OF_CONDUCT.md) * [x] I've read the [guidelines for contributing](https://codeberg.org/blackmagic-debug/blackmagic/src/CONTRIBUTING.md) to this repository * [x] It builds for hardware native (see [Building the firmware](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-the-firmware)) * [x] It builds as BMDA (see [Building the BMDA](https://codeberg.org/blackmagic-debug/blackmagic?tab=readme-ov-file#building-black-magic-debug-app)) * [x] I've tested it to the best of my ability * [x] My commit messages provide a useful short description of what the commits do ## Closing issues
riscv_debug: Reorder editing triggers *after* the halting
Some checks failed
ci/woodpecker/pr/build-firmware/15 Pipeline was successful
ci/woodpecker/pr/build-firmware/19 Pipeline was successful
ci/woodpecker/pr/build-firmware/20 Pipeline was successful
ci/woodpecker/pr/build-firmware/16 Pipeline was successful
ci/woodpecker/pr/build-firmware/18 Pipeline was successful
ci/woodpecker/pr/build-linux/2 Pipeline was successful
ci/woodpecker/pr/build-windows Pipeline was successful
ci/woodpecker/push/build-firmware/3 Pipeline was successful
ci/woodpecker/push/build-firmware/1 Pipeline was successful
ci/woodpecker/push/build-firmware/8 Pipeline was successful
ci/woodpecker/push/build-firmware/6 Pipeline was successful
ci/woodpecker/push/build-firmware/7 Pipeline was successful
ci/woodpecker/push/build-firmware/2 Pipeline was successful
ci/woodpecker/push/build-firmware/4 Pipeline was successful
ci/woodpecker/push/build-firmware/5 Pipeline was successful
ci/woodpecker/push/build-firmware/10 Pipeline was successful
ci/woodpecker/push/build-firmware/15 Pipeline was successful
ci/woodpecker/push/build-firmware/9 Pipeline was successful
ci/woodpecker/push/build-firmware/16 Pipeline was successful
ci/woodpecker/push/build-firmware/13 Pipeline failed
ci/woodpecker/push/build-firmware/11 Pipeline was successful
ci/woodpecker/push/build-firmware/14 Pipeline was successful
ci/woodpecker/push/build-firmware/12 Pipeline was successful
ci/woodpecker/push/build-linux/1 Pipeline was successful
ci/woodpecker/push/build-linux/2 Pipeline was successful
ci/woodpecker/push/build-firmware/17 Pipeline was successful
ci/woodpecker/push/build-firmware/19 Pipeline was successful
ci/woodpecker/push/build-firmware/18 Pipeline was successful
ci/woodpecker/push/build-firmware/20 Pipeline was successful
ci/woodpecker/push/build-windows Pipeline was successful
5cec517f0c
* Any CSR access is only possible on a halted hard
* Violating the order results in 4 (wrong state)
dragonmux left a comment
Copy link

LGTM, thank you for fixing this bug, merging. Thanks for the contribution!

LGTM, thank you for fixing this bug, merging. Thanks for the contribution!
ALTracer deleted branch fix/riscv-triggers-clear1 2026年04月14日 23:51:09 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
BMD App
Black Magic Debug App (aka. PC hosted) (not firmware)
BMP Firmware
Black Magic Probe Firmware (not PC hosted software)
Bug
Confirmed bug
Build system
Build system
Can't reproduce
Maintainers can't reproduce this problem
CI
Continuous Integration System
Contribution wanted
User contributions welcome
Documentation
Project documentation
Draft
Work in progress draft
Duplicate
This issue or pull request already exists
Enhancement
General project improvement
Feedback wanted
Requires additional submitter feedback
Foreign Host Board
Non Native hardware to runing Black Magic firmware on
GDB
Issue/PR related to GDB
Good first issue
Good for newcommers
HwIssue Mitigation
Solving or mitigating a Hardware issue in Software
Information Needed
Maintainers need more information
NativeHardware
Official Black Magic Debug Hardware
New Host Board
New hardware to run Black Magic firmware on
New Target
New debug target
Off Topic
Something that does not involve the project in any way
Potential Bug
A potential, unconfirmed or very special circumstance bug
Regression
Bug caused by a regression
User Interest Needed
More user interest required before consideration
User Testing Needed
Looking for user testing reports
Won't fix
Outside of the project scope or works as intended
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
blackmagic-debug/blackmagic!2218
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "ALTracer/blackmagic:fix/riscv-triggers-clear1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?