_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://libera.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
bl0x has quit [*.net *.split]
Xesxen has quit [*.net *.split]
hrberg_ has quit [*.net *.split]
geertu has quit [*.net *.split]
Finde has quit [*.net *.split]
sensille has quit [*.net *.split]
trabucayre has quit [*.net *.split]
joseng has quit [*.net *.split]
trabucayre has joined #litex
bl0x has joined #litex
sensille has joined #litex
hrberg has joined #litex
tpb has joined #litex
geertu has joined #litex
Finde has joined #litex
Xesxen has joined #litex
dark_star has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
dark_star has joined #litex
bl0x_ has joined #litex
bl0x has quit [Ping timeout: 252 seconds]
hammdist has joined #litex
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #litex
<hammdist> how would I determine whether a particular board is supported with a FOSS toolchain?
<sensille> hammdist: safest bet is still lattice ECP5 or iCE40 fpga. the board itself is of lesser importance
<sensille> to my knowledge everything else is more or less experimental
<sensille> but for the smaller fpgas most vendor toolchains are also free and run on linux. but compared to yosys they are a pain to handle
indy_ has joined #litex
<MoeIcenowy> yes, just choose a board with ECP5/iCE40
<MoeIcenowy> for iCE40, iCE40UL and iCE5LP is blacklisted
<MoeIcenowy> for ECP5 I am not sure (my only ECP5 board is just Colorlight "LED screen controller"
<MoeIcenowy> by the way the iCE40 vendor toolchain is very weird
<MoeIcenowy> maybe worse than open source one
dark_star has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
FabM has joined #litex
FabM has joined #litex
FabM has quit [Changing host]
genpaku has quit [Remote host closed the connection]
genpaku has joined #litex
dark_star has joined #litex
dark_star has quit [Ping timeout: 272 seconds]
beltzer has joined #litex
<beltzer> isr.c was moved from the bios directory to libbase (884ee45c289e1a1650937355c6356b3f64ee0c3a). Does this not make it harder to add your own interrupt handlers without modifying libbase for your project? Before you could just specify your own isr function, doing that now throws a linker error.
<somlo> hammdist: it shows as "out of stock" at the moment, but I'd recommend trying to find out if/when they're going to do another production run of this board: https://shop.lambdaconcept.com/home/46-2-ecpix-5.html#/2-ecpix_5_fpga-ecpix_5_85f
<tpb> Title: ECPIX-5 (at shop.lambdaconcept.com)
<somlo> (it can run Fedora-riscv64 on bitstream built with yosys/trellis/nextpnr, so IMHO it's the optimal FOSS-all-the-way-down board out there)
<MoeIcenowy> somlo: a full rocket?
<MoeIcenowy> (with this price I can buy a xc7k325t board by QMtech,
<MoeIcenowy> and +50 euros I can buy a STLV7325
<MoeIcenowy> for STLV7325, considering it has a SODIMM slot, it might be able to self-reproduce the gateware someday (but not today, >32bit bus support in LiteX does not exist now
<MoeIcenowy> and 7-series open source toolchain is also not really usable now
<somlo> MoeIcenowy: yeah, a single-core "full" double-wide (128-bit memory bus -- 512MB DRAM) Rocket, with sdcard and ethernet
<tpb> Title: [PATCH] lib: Add Dhrystone benchmark test - Geert Uytterhoeven (at lore.kernel.org)
<geertu> On orangecrab/vexriscv @ 64 MHz, I got 22 DMIPS (0.3 DMIPS/MHz)
<geertu> which is far from the claimed 1.44 or 1.57 on https://github.com/SpinalHDL/VexRiscv
<tnt> geertu: vex is so configurable that it heavily depends on your config. Also highly dependent on your memory system. You'd only reach that with on-chip zero latency memory probably.
<tnt> Also, those numbers would be running benchmark baremetal with no os overhead.
<geertu> tnt: So far, Andestech AX45 (in RZ/Five) is the RISC-V core with the highest DMIPS/MHz I have (2.2)
<tnt> But what fmax do you get with it on the same fpga vs Vex ? :D
<geertu> tnt: ;-)
<somlo> geertu: on a nexys-video with 4 Rocket cores (the "full", a.k.a. FPU-enabled variant), I did `echo y > /sys/module/test_dhry/parameters/run` (i.e., without any additional preparation, paramter settings, etc.)
<somlo> got "CPU3: Dhrystones per Second: 106384 (60 DMIPS)"
<somlo> I should also mention the cpu clock is 50MHz
<somlo> I assume only one core is used by default? (in which case I'd expect similar results on any 50MHz "full" Rocket/LiteX system, regardless of core count)
<geertu> somlo: Thx! 1.2 DMIPS/MHz is not that bad, given that I get 1.5 on U54 and 1.8 on U74 hardcores
<geertu> somlo: Yes, it's per core
<somlo> geertu: is this on its way to official upstream? Once it lands, I should add it to the rocket/litex defconfig in `litex-hub/litex-rebase` :)
hammdist has quit [Quit: Client closed]
<geertu> somlo: That's the plan. But it's really only intended for testing.
<somlo> well, yeah, just like the `litex-rebase` branch itself
<MoeIcenowy> somlo: BTW I did some conditionally-compiled DT at https://github.com/Icenowy/linux-on-litex-openc906
<MoeIcenowy> although initially created for OpenC906, I also use this to run on Rocket now too
<somlo> MoeIcenowy: interesting! Although, long-term, I'd like to take advantage of the `pythondata_cpu_rocket/verilog/generated-src/*.dts` files that are generated by Chisel along with the verilog for each specific variant
<somlo> which should come in handy if we ever manage to get rid of variants and elaborate the verilog from chisel on-demand
hammdist has joined #litex
<jevinskie[m]> <MoeIcenowy> "for STLV7325, considering it has..." <- Yes rebuilding itself from its bootstraps is an interesting prospect :)
<jevinskie[m]> It looks like dynamic timing (e.g. delays) support has been upstreamed from antmicro’s verilator fork to the main repo. I should be able to run litex_sim with Micron DDR3 models now :)
<somlo> yeah, short-term an ECP5 board with a SODIMM slot would be nice :) Medium-term, full yosys/nextpnr support for xilinx 7-series chips (artix/kintex/virtex) would be even more awesome
<geertu> Any open toolchain for mpfs?
TMM__ has joined #litex
amstan1 has joined #litex
alanvgreen_ has joined #litex
Crofton[m]1 has joined #litex
alanvgreen has quit [Ping timeout: 252 seconds]
amstan has quit [Ping timeout: 252 seconds]
TMM_ has quit [Ping timeout: 252 seconds]
Crofton[m] has quit [Ping timeout: 252 seconds]
anuejn has quit [Read error: Connection reset by peer]
alanvgreen_ is now known as alanvgreen
anuejn has joined #litex
hammdist has quit [Quit: Client closed]
hrberg has quit [Ping timeout: 256 seconds]
hrberg has joined #litex
lambda has quit [Quit: WeeChat 3.5]
lambda has joined #litex
FabM has quit [Ping timeout: 260 seconds]
kaaliakahn has joined #litex
joseng has joined #litex