Skip to content

Conversation

@en-sc
Copy link
Collaborator

@en-sc en-sc commented Oct 28, 2025

Restarting the program buffer memory write pipeline when the write of the last element resulted in the busy response triggers an extra memory wrtite, that is cought by an assertion:

src/target/riscv/riscv-013.c:5048: write_memory_progbuf_inner: Assertion
`next_addr_on_target - args.address <= (target_addr_t)args.size *
args.count' failed.

Change-Id: I0f27145cad24686cf539aebfea7f6578b7cd78ab

Restarting the program buffer memory write pipeline when the write of
the last element resulted in the busy response triggers an extra memory
wrtite, that is cought by an assertion:
```
src/target/riscv/riscv-013.c:5048: write_memory_progbuf_inner: Assertion
`next_addr_on_target - args.address <= (target_addr_t)args.size *
args.count' failed.
```

Change-Id: I0f27145cad24686cf539aebfea7f6578b7cd78ab
Signed-off-by: Evgeniy Naydanov <[email protected]>
@tom-van
Copy link
Contributor

tom-van commented Oct 28, 2025

@en-sc Fantastic speed of fixing!

gd32vf103:
:::::::::::::::::::::::::::[ ran 73 tests in 142s ]:::::::::::::::::::::::::::
25 tests returned not_applicable
48 tests returned pass

I confirm the fix works. Thanks!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants