_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://freenode.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
Degi has quit [Ping timeout: 264 seconds]
Degi_ has joined #litex
Degi_ is now known as Degi
avg has joined #litex
<avg> sajattack[m] What are you doing about RAM? Will be external?
<sajattack[m]> in my testing I just gave it a 1k sram
<sajattack[m]> but you could do an external sdram or something for sure
<sajattack[m]> I was able to compile vexriscv minimal into an asic outside of litex
* sajattack[m] uploaded an image: 2020-08-10-180151_570x540_scrot.png (138KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/QytCMUkglTMsCqtASPDLnptI >
<sajattack[m]> I'm not sure if it's a problem with litex or my naive approach to modifying the build script
avg has quit [Remote host closed the connection]
jaseg has quit [Ping timeout: 256 seconds]
jaseg has joined #litex
mntmn has quit [Ping timeout: 256 seconds]
daddesio has quit [Ping timeout: 256 seconds]
mntmn has joined #litex
daddesio has joined #litex
davidcorrigan714 has quit [Remote host closed the connection]
_whitelogger has joined #litex
avg has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 240 seconds]
<futarisIRCcloud> conmega: Which JTAG adapter are you using for the Acorn CLE-215+ ?
<zyp> futarisIRCcloud, you didn't ask me, but I'm just using a generic ft232h breakout
avg has quit [Remote host closed the connection]
kgugala_ has quit [Read error: Connection reset by peer]
kgugala has joined #litex
proteusguy has quit [Ping timeout: 256 seconds]
somlo has quit [Ping timeout: 240 seconds]
somlo has joined #litex
CarlFK has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 264 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 256 seconds]
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 240 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 256 seconds]
st-gourichon-fid has quit [Ping timeout: 260 seconds]
kgugala_ has joined #litex
kgugala has quit [Read error: Connection reset by peer]
<disasm[m]> <sajattack[m] "in my testing I just gave it a 1"> How about https://github.com/VLSIDA/OpenRAM ?
<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)
<avg> sajattack[m] Did you see the Skywater slack? http://join.skywater.tools/
<tpb> Title: Request invite to the skywater-pdk Slack! (at join.skywater.tools)
<lkcl> SDRAM: 131072KiB 16-bit @ 80MHz
<lkcl> Memtest at 0x40000000...
<lkcl> [########################################]
<lkcl> - bus errors: 74/256
<lkcl> [########################################]
<lkcl> - addr errors: 7639/8192
<lkcl> - data errors: 475365/524288
<sajattack[m]> avg: yup I've been asking questions and chatting there
<lkcl> 120 mhz DRAM: also fail :)
<daveshah> Huh, maybe something has broken
<daveshah> Does the default 75MHz system clock work?
<lkcl> daveshah: yes, 75mhz is fine
<lkcl> tried 40mhz clock (160mhz SDRAM), fail too
<lkcl> 48mhz (192mhz SDRAM) _also_ fail. urk
<lkcl> the average DDR3 IC _should_ work fine at around 200 mhz....
<daveshah> The DDR3 clock is only 100MHz
<daveshah> litex is incorrectly reporting the transfer rate not the frequency
<lkcl> ah
<lkcl> SDRAM: 131072KiB 16-bit @ 300MHz
<daveshah> litex disables DLL so low frequencies should be fine
<lkcl> CPU: PicoRV32 @ 75MHz
<daveshah> The problem is probably the various latency magic numbers in the PHY aren't right at such a low frequency
<daveshah> Or, the problem is in the ECP5 IO logic
<lkcl> well, i'm going to cheat and do a manual clock which halves the frequency
<lkcl> nuts.
<lkcl> i need to 1/4 the frequency, don't i? :)
<lkcl> so that's a counter up to 8 (3 bits), test the top bit == true, that's the "clock" to send over the DomainRenamer() new clock domain
m4ssi has joined #litex
m4ssi has quit [Remote host closed the connection]
<lkcl> ah doh i need something a bit more sophisticated than a part-hack
<lkcl> i need to do a level of indirection, add *another* DomainRenamer, sigh.
<lkcl> daveshah: is there any other PLL that i could use to run things from, on the versa_ecp5, do you know?
<daveshah> Yes there are three PLLs and LiteX should only use one of them
<zyp> three?
<lkcl> okaay. so hypothetically i could indeed do a separate sys clock running from that
<lkcl> call it "core clock" or something
<lkcl> however.... mm.... interacting with the wishbone bus is going to get interesting
awordnot has quit [Read error: Connection reset by peer]
awordnot has joined #litex
avg has quit [Remote host closed the connection]
lf has quit [Ping timeout: 244 seconds]
lf has joined #litex