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

Setting DBUS_WB_TYPE = "B3_READ_BURSTING" causes lockup #150

Open
jefferybond opened this issue Apr 11, 2022 · 1 comment
Open

Setting DBUS_WB_TYPE = "B3_READ_BURSTING" causes lockup #150

jefferybond opened this issue Apr 11, 2022 · 1 comment
Assignees

Comments

@jefferybond
Copy link

If I set the DBUS_WB_TYPE parameter to "B3_READ_BURSTING", then the CPU locks up when attempting the first data access.

It seems that the dbwm_we_o output gets asserted, and a valid address is presented on dwbm_adr_o, but the dwbm_stb_o / dwbm_cyc_o outputs remain low, and no bus access happens. CPU locks up from this point on.

Setting DBUS_WB_TYPE="CLASSIC" allows it to work again. Also, setting IBUS_WB_TYPE="B3_READ_BURSTING" causes no issue - only seems to affect the data bus.

@stffrdhrn
Copy link
Member

Hi @jefferybond, I usually run mor1kx with mode B3_REGISTERED_FEEDBACK for both ibus and dbus. Sorry I haven't tried B3_READ_BURSTING so it's very likely there could be issues here.
Would you be able to do further investigation to figure out what is the issue with B3_READ_BURSTING?

@stffrdhrn stffrdhrn self-assigned this Apr 11, 2022
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