proteusguy has quit [Remote host closed the connection]
proteusguy has joined #litex
lindemer has joined #litex
<lindemer>
Can anyone tell me how to debug LiteX/VexRiscv with GDB on an Arty FPGA? The best instructions I can find are https://github.com/timvideos/litex-buildenv/wiki/Debugging but running "load firmware.elf" from GDB once connected returns communication errors and doesn't boot the image
lindemer has quit [Remote host closed the connection]
lindemer has joined #litex
lf has quit [Quit: No Ping reply in 180 seconds.]
lf has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 256 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 256 seconds]
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
kgugala has quit [Quit: -a- Connection Timed Out]
kgugala has joined #litex
<_florent_>
somlo: nice!
keesj has quit [Ping timeout: 272 seconds]
keesj has joined #litex
Bertl_zZ is now known as Bertl
Dolu has joined #litex
futarisIRCcloud has joined #litex
CarlFK has quit [Quit: Leaving.]
lindemer has quit [Remote host closed the connection]
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 260 seconds]
kgugala_ has quit [Read error: Connection reset by peer]
kgugala has joined #litex
kgugala has quit [Read error: Connection reset by peer]
kgugala has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 260 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 260 seconds]
SpaceCoaster has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
SpaceCoaster has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 272 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 246 seconds]
<mithro>
somlo: I'm somewhat excited about "linux-on-litex-rocket"
<mithro>
somlo / _florent_: I really think that the two repositories will kind of end up trending towards, linux-on-litex-vexriscv --> linux-32bit-on-litex and linux-on-litex-rocket --> linux-64bit-on-litex direction (I don't think we should rename them however)
<_florent_>
mithro: I see things differently. There is an history behind linux-on-litex-vexriscv, linked to VexRiscv and to the collaboration with @Dolu @daveshah Antmicro, etc... so this project is not going to support other CPUs
<_florent_>
mithro: same for linux-on-litex-rocket, that is in fact just a name for the work done by @somlo during the last year and that was already available at http://www.contrib.andrew.cmu.edu/~somlo/BTCP/
<tpb>
Title: A Trustworthy, Free (Libre), Linux Capable, Self-Hosting 64bit RISC-V Computer (at www.contrib.andrew.cmu.edu)
<mithro>
I would say that BlackParrot for example is more similar to Rocket than VexRISCV
Bertl is now known as Bertl_oO
<leons>
_florent_: I'm personally equally interested in VexRiscv (which is awesome) and ibex (because it has more mature than VexRiscv) in the OS I'm working on
<mithro>
_florent_: Generally I have found that optionality tends to lead to both options being better than either one by itself
<mithro>
leons: I'm sure that #695 will happen at some point, but it will probably be zephyr / microcontroller targetted rather than Linux
<leons>
_florent_: Or was that only referring to Linux support?
<mithro>
_florent_: But we can keep the linux-on-litex-vexriscv specific repository to VexRISCV
<leons>
mithro: Ah, that makes sense (and conveniently is exactly what I want :) )
<mithro>
It might get a bit silly when we end up having linux-on-litex-vexirscv, linux-on-litex-rocket, linux-on-litex-blackparrot, linux-on-litex-microwatt, linux-on-litex-XXXX
<_florent_>
@leons yes that's the way I see thing, linux-on-litex-vexriscv, linux-on-litex-rocket are applications projects for both LiteX/Vexriscv/Rocket
<mithro>
I do wonder if Dolu will end up looking into an VexRISCV which is 64bit capable but more efficient than rocket
<leons>
And there's nothing stopping anyone from putting in the work to make Linux run on LiteX with these CPUs, right? Just not an official project?
<somlo>
mithro, _florent_: with luck (and I'm personally pretty optimistic about that) we can ensure upstream Linux drivers (and support in general) can be done in a way that works out-of-the-box for both 32 and 64 bit CPUs, without too much in the way of special-case hackery
<mithro>
leons: There isn't really any "official" project here -- everything is mostly driven by what people are interested in
<_florent_>
somlo: that's indeed the direction we are going I think thanks to your work (BTW linux-on-litex-vexriscv is now also using your litex-rocket-rebase branch)
<somlo>
speaking of LiteX vs. linux-on-litex-vexriscv: one of my highest priorities for linux-on-litex-rocket was to use unmodified upstream LiteX, with no customizations in terms of gateware :)
<somlo>
_florent_: I *thought* I saw something about Antmicro's LiteX soc controller landing upstream yesterday (not 100% sure, haven't had time to check)
<_florent_>
somlo: re no customization: that's indeed nice, that also the direction I'd like to go with linux-on-litex-vexriscv
<_florent_>
there are still some customization but I think we could remove it easily
<somlo>
I think that'd be the 8-bit-csr-data-width version that's been winding its way through reviews, so my next priority (next week I hope) is to rebase "litex-rocket-rebase" on top of that work, and to submit upstream the "works with both 8-bit and 32-bit CSRs" portion of that ASAP, before anyone gets too attached to what just got committed :D
<daveshah>
somlo: I've got one if you want me to test anything
<daveshah>
Almost as hot as new GPUs, it seeme
<somlo>
daveshah: nothing immediately earth-shattering -- I was going to get one for myself as a Christmas present, and putter around with LiteX+Rocket (maybe look into whether the sata port would come in handy)
<somlo>
but I can wait for the next production run for all that, no big deal
<somlo>
maybe the next version will come with a heatsink ;)
<chrisps>
i recently got a vcu1525 cheap despite having no ee experience to use as an accelerator for some projects of mine. did i make a mistake?
<Finde>
chrisps: well I'm jealous at least :)
<mithro>
somlo: Antmicro went with mor1k as a start as Stafford could help with getting it upstream and there is less politics
<mithro>
somlo: LiteX + Rocket is probably easier than LiteX + VexRISCV in Linux because Linux 32bit RISC-V has a lot of haters (and there is increasing moment behind the "drop 32bit in Linux all together" idea).
<mithro>
I would really like to figure out getting CI working which shows that Linux will boot on key hardware in linux-on-litex-vexriscv
<somlo>
mithro: interesting to know, thanks for the context! I will probably collapse the litex-vexriscv-rebase and litex-rocket-rebase branches into a single litex-rebase branch that applies cleanly on the current stuff upstream
<somlo>
then we get to bicker about upstreaming the accessors that handle all corner cases some more, but once that's done, additional device drivers should have a much easier time
<mithro>
somlo: I was hoping that the microwatt people would help with Linux on LiteX upstream work but that didn't seem to pan out
<somlo>
imho, device drivers have no business *knowing* whether the CSR data width is 8 or 32, or whether the underlying cpu is 32 or 64 bits :)
<somlo>
we have to encapsulate that magic somewhere (i.e. in the accessors), in a way that can be cleaned up to everyone's satisfaction without further disturbing the way device drivers are written
<mithro>
somlo: if you ever want / need a Nexys Video or Gensys 2 boards, I would happily send you one as long as you promise to continue to support this stuff on small devices like Arty :-)
<mithro>
Specially if you wanted to help make sure LiteX + Rocket works with Yosys + VPR + Prj X-Ray flows
<somlo>
mithro: thanks, but I don't have an arty :) smallest device I do have is nexys4ddr
<mithro>
I'm happy to send you an Arty too
<somlo>
in the xilinx category, at least
<somlo>
In the Xilinx category I was waiting for the dust to settle on the vpr vs. nextpnr-xilinx vs prj-xray situation, and stick with ecp5 for the turtles-all-the-way-down-FOSS self-hosting ideal
<somlo>
but maybe it's time to re-evaluate that at some point... Personally, my first priority is getting something that can mount and read/write an ext2 filesystem in a not-too-slow way
<somlo>
so I can boot Fedora on it, and run yosys/trellis/nextpnr and/or vpr on the "self-hosting" thing itself
<acathla>
"<somlo> hmmm, apparently the 85k version of the ECPIX-5 is out of stock... :("
<acathla>
It seems both versions are out of stock. That's a good news, it means the business is good :)
<daveshah>
Or the AMD/NVIDIA trick of not making enough to create an illusion of popularity ;)
<zyp>
I'm not sure whether I'm more excited for the ECPIX-5 or the butterstick
<zyp>
I ordered one of each the other day
FFY00 has quit [Read error: Connection reset by peer]
FFY00 has joined #litex
<acathla>
I'm not sure they had a clue about how many the were going to sell, so they probably prefered to produce just a few.
<acathla>
Who's behind lambdaconcept? I'm sure they are hiding here :)
<_florent_>
acathla: key2 probably know them :)
<key2>
We really sold out
<key2>
what pisses me off is companies buying sometimes 5 unit making the batch go fast
<acathla>
Like pasta or toilet paper in France during lockdown :)
<futarisIRCcloud>
Is there another batch in the queue?
<felix_>
just had a look in my desk drawers and found a digilent atlys board with corresponding i/o breakout board and a numato opsis in there; if someone wants those and actually has the time to do something useful with those, i cold ship you those; preferrably in germany or at least europe due to shipping cost. it's been quite some time that i did something with the boards, so i'm not sure how functional those still