<tpb>
Title: GitHub - VLSIDA/OpenRAM: An open-source static random access memory (SRAM) compiler. (at github.com)
<disasm[m]>
I'm not sure it's easily embeddable in current flows, but anyway
proteusguy has joined #litex
<sajattack[m]>
It's not ready yet
m4ssi has joined #litex
<conmega>
futarisIRCcloud: I am using a clone J-link at the moment. I only happen to have an FT232R breakout kicking around right now and it doesn't even have all the pins broken out. So I need to order some things. Wasn't really a complaint as more of an observasion on my end :)
<conmega>
Actually, just happened across an amontec jtagkey on eBay for a good price, so grabbed that. FT232H with level shifting from 5V down to 1.4V so that will be nice.
m4ssi has quit [Remote host closed the connection]
lkcl has joined #litex
<lkcl>
hi all, have been setting up libresoc to run under litex. sim works, am just setting up on a versa-ecp5 (LFE5UM)
<lkcl>
as this is a "first iteration ever" i am identifying areas that need improvement
<lkcl>
however i would like to "just get it to work for now"
<lkcl>
currently there's a 37ns routing loop which limits the top clock frequency that this can run at to around 27 mhz
<lkcl>
my question therefore is: how can i set the frequency of the design clock to run at say... 16 mhz?
<lkcl>
or 75/4=18.75 for example
tannewt has joined #litex
<lkcl>
is it as simple as adding "--sys-clk-freq=18.75e6" to the BaseSoC parameters?
<daveshah>
passing it on the command line should work, yeah
<daveshah>
I don't know if you need the '=' though, I always use a space
<lkcl>
daveshah: ok ta
<lkcl>
started building @ 16e6, i'll let it run
* lkcl
waves to daveshah
<daveshah>
hi!
<lkcl>
8mhz clock rate initialisation of versa-ecp5 dram: not quite working, there.
<lkcl>
also, whilst that's an 8mhz clock rate, it's actually a FSM at the moment
<daveshah>
You could see if it works with picorv32 at that rate
<lkcl>
so the actual instruction rate is... 1/8th of that
<lkcl>
ah good idea
<lkcl>
i'd have to bring it down to around 2mhz to be "on par"
<daveshah>
My guess is it is the DRAM interface clock, not the CPU IPS, that is the problem
<daveshah>
Unfortunately, that is fixed at 2x the system clock and not easily changeable
<lkcl>
ahh ok
<lkcl>
oh yes, i noticed that
<lkcl>
well... i could put a "fake" PLL (digital counter/divider) in
<daveshah>
It might be possible to use a faster processor to do DRAM init
<daveshah>
And then provide another AXI port or whatever that you CDC to your slow CPU under test
<lkcl>
i'm leaning towards a manual clock-counter (in nmigen). leave the main clock at 75mhz and fire the cpu clock using a DomainRenamer()
avg has joined #litex
<lkcl>
picorv32 memtest @ 16mhz...
<lkcl>
- bus errors: 98/256
<lkcl>
- addr errors: 7717/8192
<lkcl>
- data errors: 520871/524288
* lkcl
trying 20mhz
<lkcl>
trying with picorv32 is a good idea, it's quite quick to build (a lot faster than libresoc, which is approaching the max LUTs of 45k)