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

Fix numato csr headers #24

Merged
merged 2 commits into from
Dec 14, 2019
Merged

Fix numato csr headers #24

merged 2 commits into from
Dec 14, 2019

Conversation

dkozel
Copy link
Contributor

@dkozel dkozel commented Dec 14, 2019

Commit enjoy-digital/litex@8be5824 simplified the handling of csr regions and constants. These target files need to be updated to the new API.

They also still use the with_shadow_base parameter to get_csr_header which was removed/deprecated in enjoy-digital/litex@a4ef9b2. I'm nearly positive that the new default behavior matches the previous behavior that the Numato targets were using.

Longer discussion in #25

litex commit 8be5824e258b84df240d34636aaa539124b92c65 simplified the handling
of csr regions and constants.
get_csr_header parameter with_shadow_base
removed/deprecated in litex 2a8d8c8f. New default
behavior matches the desired behavior in these targets.
@mithro
Copy link
Contributor

mithro commented Dec 14, 2019

@rohitk-singh do you still have access to boards to test?

@enjoy-digital enjoy-digital merged commit c49693f into litex-hub:master Dec 14, 2019
@rohitk-singh
Copy link
Contributor

@mithro, Not with me here. But I can ask someone in the team at Numato to test this PR. From the looks, it should work though.

@enjoy-digital
Copy link
Member

Thanks @dkozel, @rohitk-singh, the PR was fine yes and i merged it. I also fixed the gateware/software builld directory with 7184032, it should now be fine.

@rohitk-singh
Copy link
Contributor

Great! Thanks @enjoy-digital!

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.

None yet

4 participants