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

How to determine bit width of the point-to-point AXI link? #7

Closed
troibe opened this issue Mar 28, 2021 · 3 comments
Closed

How to determine bit width of the point-to-point AXI link? #7

troibe opened this issue Mar 28, 2021 · 3 comments

Comments

@troibe
Copy link
Contributor

troibe commented Mar 28, 2021

I'm trying to run your project on an ULX3S however I'm now wondering what the appropriate bit width would be.
Is there some table with the bit width of all supported litex boards?
Where did you find this information?

@gsomlo
Copy link
Collaborator

gsomlo commented Mar 28, 2021

Hi @developandplay -- thanks for pointing this out!

I just committed cc45c13 which should explain where you can find the correct width to use.

@troibe
Copy link
Contributor Author

troibe commented Mar 28, 2021

Thanks a lot!
Just in case anyone finds this thread and wants to take a shortcut:

INFO:SoCBusHandler:main_ram Region added at Origin: 0x80000000, Size: 0x02000000, Mode: RW, Cached: True Linker: False.
INFO:SoC:Converting MEM data width: 16 to 64 via Wishbone
INFO:ECP5PLL:Config:
clki_div   : 1
clko0_freq : 50.00MHz
clko0_div  : 8
clko0_phase: 0.00°
clko1_freq : 50.00MHz
clko1_div  : 8
clko1_phase: 90.00°
vco        : 400.00MHz
clkfb_div  : 16

So for the ULX3S it seems to be 16bits. That's interesting considering that it's using the same ECP5 chip. Then it's the SRAM that's used on the ULX3S that makes the difference I guess. Since 16 is smaller than the 64 standard which effect does it have?

@gsomlo
Copy link
Collaborator

gsomlo commented Mar 28, 2021 via email

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