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.

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

Switching from cocotb.fork to cocotb.start_soon breaks _read function #28

Open
cameronweston opened this issue Dec 19, 2023 · 2 comments

Comments

@cameronweston
Copy link

cameronweston commented Dec 19, 2023

The read functional fails to get the last value returned in a sequence of reads. If you request a single address, no data will be returned, if you request n addresses, n-1 values will be returned. Simply replacing start_soon with fork fixes this issues, however, I know fork is deprecated.

This could potentially be fixed by changing cocotb.start_soon(self._read()) to await cocotb.start(self._read()). I wish I knew the difference I guess I should read up on that.

@Kev-J Kev-J mentioned this issue Oct 11, 2024
@Kev-J
Copy link

Kev-J commented Oct 11, 2024

I've run into this bug as well. Here is some fix: #29

@Kev-J
Copy link

Kev-J commented Dec 5, 2024

I've run into this bug as well. Here is some fix: #29

Since this bugfix was merged, I assume we can close this issue.

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

No branches or pull requests

2 participants