tpb has joined #litex
_whitelogger has joined #litex
Dolu has joined #litex
freemint has joined #litex
rohitksingh has joined #litex
nrossi has quit [Remote host closed the connection]
synaption[m] has quit [Remote host closed the connection]
xobs has quit [Read error: Connection reset by peer]
john_k[m] has quit [Remote host closed the connection]
nrossi has joined #litex
synaption[m] has joined #litex
xobs has joined #litex
john_k[m] has joined #litex
_franck_ has joined #litex
freemint has quit [Ping timeout: 252 seconds]
freemint has joined #litex
freemint has quit [Ping timeout: 245 seconds]
freemint has joined #litex
CarlFK has joined #litex
<mithro> _florent_: Could you give me access to ?
<tpb> Title: GitHub - enjoy-digital/minerva-verilog (at
<tpb> Title: cpu/minerva: elaborate from nmigen sources during build, enable hardw… · enjoy-digital/litex@ab8af28 · GitHub (at
<mithro> _florent_: still needed until I update litex-buildenv
ironsteel has joined #litex
<tpb> Title: LiteX BuildEnv Support - Google Sheets (at
<somlo> PSA: Rocket currently hates yosis:
<tpb> Title: commit #f31e21b5b breaks yosys synthesis · Issue #2168 · chipsalliance/rocket-chip · GitHub (at
freemint has quit [Ping timeout: 276 seconds]
<mithro> somlo: Yosys :-P
<somlo> mithro: sorry, didn't mean no disrespect (I'm just not good at spelling in real time) :D
<somlo> at least I got it right in #riscv, apparently :)
CarlFK has quit [Ping timeout: 276 seconds]
<mithro> _florent_: Could we move rocket-litex-verilog to litex-hub?
<_florent_> yes
<_florent_> mithro: we could also move minerva-verilog/vexriscv-verilog to litex-hub
ironsteel has quit [Remote host closed the connection]
ironsteel has joined #litex
ironsteel has quit [Remote host closed the connection]
<mithro> _florent_: Where did get_memory_regions() go?
<tpb> Title: Where did soc.get_memory_regions() go? · Issue #290 · enjoy-digital/litex · GitHub (at
rohitksingh has quit [Ping timeout: 264 seconds]
<mithro> _florent_: Now I need to figure out how to fix
<mithro> ValueError: Memory region conflict between spiflash and rom
<mithro> _florent_: I think I want "add_linker_region" ?
<_florent_> mithro: you need to use type="cached+linker" when adding memory region
<tpb> Title: [RFC] Linker region concept by mateusz-holenko · Pull Request #285 · enjoy-digital/litex · GitHub (at
<mithro> Looks like the CSR region moved?
<mithro> ValueError: cas region (0x60006800-0x60006fff) is not located in an IO region.
<mithro> - 0x80000000-0xffffffff
<mithro> Available IO regions:
<_florent_> mithro: where is the code generating this error?
<tpb> Title: litex-buildenv/ at 96ab220b0f60e3d509ca0a66dcfb81676ef294d9 · timvideos/litex-buildenv · GitHub (at
<_florent_> ok, we no longer have shadow_base, so you need to make sure your CSR is in a io region (ie not cached)
<tpb> Title: litex-buildenv/ at 96ab220b0f60e3d509ca0a66dcfb81676ef294d9 · timvideos/litex-buildenv · GitHub (at
<_florent_> and remove the shadow comments
<mithro> Why 0xe0000000 rather than 0x80000000 ?
<_florent_> you can also use 0x80000000, that's was just to use the same addressing as your previous code
<somlo> _florent_, mithro: for what it's worth, I've switched rocket over to csr/mmio below 0x80000000, and cached RAM above
<somlo> so that I can grow the RAM to whatever size the hardware provides, without any MMIO region getting in the way
<tpb> Title: Fix broken LPDDR support. by mithro · Pull Request #94 · enjoy-digital/litedram · GitHub (at
<tpb> Title: Fix file names for the mor1kx processor. by mithro · Pull Request #293 · enjoy-digital/litex · GitHub (at
<somlo> trellisboard running LiteX/Rocket, using the full 1GB RAM:
<tpb> Title: Imgur: The magic of the Internet (at
<daveshah> Very nice!
Dolu has quit [Ping timeout: 240 seconds]
<somlo> daveshah: there's some "hidden slack" in nextpnr's timing analysis, it's usually rated at 52MHz tops, but feels pretty solid at 65MHz
<daveshah> Yes, that's because it's based on Diamond's default model
<somlo> some of the lingering weirdness includes passing memtest on svf push via openocd, but failing upon hitting the reset switch
<somlo> pushing via openocd gets it to pass again (same bitstream)
<daveshah> Which itself is worst process, minimum Vcc, 85 degrees C
<somlo> but the latter is related to litedram, not timing, afaict, for the record...
<daveshah> Have you tried another board yet? It does seem like something is marginal
<somlo> not yet, will try that tomorrow
<daveshah> I seem to remember a minimum frequency for the ECP5 DDRDLL
<daveshah> that was around the 70MHz ish mark
<daveshah> This was in my experiments before litedram
<daveshah> It is possible something misbehaves in a way that varies between boards and chips below this
<daveshah> Unfortunately I don't think it's actually documented anywhere
<somlo> so maybe the versa has more slack than the trellisboard, since the former works OK at 55MHz (with rocket, that is), and the latter pretty consistently at 65, both of which are lower than the "official" number you quoted :)
<daveshah> But a DDRDLL issue would explain why either it works or doesn't after a reset
<daveshah> A typical "marginal" issue would likely not change after a reset and just be odd errors here or there, including in Linux
<somlo> ok, so I'll add "unboxing a secontr trellisboard" to my agenda for tomorrow, then maybe adding sdcard support, so I can boot fedora or debian from there similarly to how LowRISC does it
<somlo> as an alternative to a diskless NFS setup, which might be painful for other reasons... :)
<mithro> somlo / daveshah: antmicro + kgugala are working on LiteSDCard support for both Linux and testing on hardware
<mithro> Does the trellisboard have a sd card connector?
<daveshah> Yes, it does
<mithro> daveshah: What would we need to do to get antmicro a trellis board?
<daveshah> I can't really encourage anyone to build more given there is an unknown DDR3 reliability issue
<daveshah> Along with a few other rev 1.0 niggles
<daveshah> I don't know if forksand or somlo would be able to part with one of theirs
<mithro> daveshah: How similar is the versa board?
<daveshah> mithro: smaller fpga, less ddr, no HDMI, only x1 pcie, less IO
<daveshah> somlo: FYI, this patch was to get nfs boot working on a previous litex lnux project
<tpb> Title: Comparing master...nfs · daveshah1/litex-linux-riscv · GitHub (at
<daveshah> Although fairly slow, it was pretty painless
<mithro> daveshah: Can you log an issue somewhere for someone to clean that up?
<daveshah> Yeah, sure
<mithro> daveshah: I mean -- if you log an issue somewhere with that, I'll see if someone at antmicro has time to clean that up and make it work
<tpb> Title: Add support for NFS rootfs · Issue #54 · litex-hub/linux-on-litex-vexriscv · GitHub (at
_franck_ has quit [Remote host closed the connection]
freemint has joined #litex
Dolu has joined #litex
CarlFK has joined #litex
tpb has quit [Remote host closed the connection]