_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]
tpb has joined #litex
gregd has joined #litex
ewen has quit [Ping timeout: 264 seconds]
ewen has joined #litex
ewen has quit [Quit: leaving]
Degi_ has joined #litex
Degi has quit [Ping timeout: 268 seconds]
Degi_ is now known as Degi
jevinskie[m] has quit [Read error: Connection reset by peer]
dcallagh has quit [Write error: Connection reset by peer]
sajattack[m] has quit [Read error: Connection reset by peer]
Leon[m] has quit [Remote host closed the connection]
shoragan[m] has quit [Write error: Connection reset by peer]
jryans has quit [Read error: Connection reset by peer]
jryans has joined #litex
Leon[m] has joined #litex
shoragan[m] has joined #litex
dcallagh has joined #litex
sajattack[m] has joined #litex
jevinskie[m] has joined #litex
nelgau has joined #litex
Xesxen_ has joined #litex
keesj has quit [Ping timeout: 264 seconds]
Xesxen has quit [Read error: Connection reset by peer]
keesj has joined #litex
nelgau has quit [Ping timeout: 245 seconds]
<cr1901> _florent_: I guess the answer is no, but if I have an old (full) build tree from a litex-boards build, is it possible to get the python command-line I sent back?
<cr1901> Can prob be inferred from the headers, but maybe that's a "nice-to-have"? I'll implement said feature at some point if you accept it
sajattack[m] has quit [*.net *.split]
dcallagh has quit [*.net *.split]
shenki has quit [*.net *.split]
rektide has quit [*.net *.split]
tumbleweed has quit [*.net *.split]
Finde has quit [*.net *.split]
Guest6527 has quit [*.net *.split]
ysionneau1 has quit [*.net *.split]
Stary has quit [*.net *.split]
kbeckmann has quit [*.net *.split]
gruetzkopf has quit [*.net *.split]
sajattack[m] has joined #litex
dcallagh has joined #litex
Finde has joined #litex
Guest6527 has joined #litex
ysionneau1 has joined #litex
gruetzkopf has joined #litex
Stary has joined #litex
kbeckmann has joined #litex
shenki has joined #litex
rektide has joined #litex
tumbleweed has joined #litex
pftbest has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
nelgau has joined #litex
nelgau has quit [Ping timeout: 268 seconds]
<gregd> Is there a recommended sw layer for LiteEth? I see timvideos/hdmi2usb makes use of uIP, so that's probably what I'll try first
<gatecat> gregd: there's also the minimal stack that the BIOS uses for TFTP boot: https://github.com/enjoy-digital/litex/tree/master/litex/soc/software/libliteeth
<tpb> <https://x0.no/4uwzs> (at github.com)
<gregd> gatecat: Thanks. I have seen that, that's currently how I'm doing ARP and sending "raw" UDP packets.
<gregd> I'm intially wanting to support a telnet interface to replace the need for uart for debugging. So something that provides TCP is a requirement.
<gatecat> yeah, uIP probably makes sense but I haven't personally tried it
<gregd> neither, I've had a bit of experience with lwip.
<_florent_> gregd: Contiki/uIP is indeed a good option if you want to go a further than with libliteeth from the BIOS
<_florent_> it's easy to use and you can find very various documentation, I also used it a few years ago for similar reasons (having TCP/Telnet)
<_florent_> Also, just for info, it's possible to have virtual UARTs over Etherbone (+ the UDP/IP Stack)
<_florent_> For this, you just have to use a Crossover UART and use litex_term bridge
<_florent_> It's convenient for some use case, but will probably use more resources than the uIP running on the CPU
<_florent_> It's also not TCP
<_florent_> That's what I'm using for debug/bringup on the SDS1104X-E support: https://github.com/360nosc0pe/scope
<_florent_> cr1901: That would be nice to have this yes (+ also the different parameters of the SoC)
<gregd> Cool! I'm working on a Thermal Camera -> Ethernet interface, So I'm making use of the Hybrid MAC, SoC for admin/overhead, and a hw stream for image data.
<_florent_> Nice, I also used it at some point on the SDS1104X-E: SW stack for the BIOS netboot + Linux driver and HW stack for Etherbone/UDP, it seems to be working fine but hasn't been tested extensively, so feel free to complain if you have troubles :)
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
gregd has quit [Ping timeout: 268 seconds]
nelgau has joined #litex
nelgau has quit [Ping timeout: 245 seconds]
Xesxen_ is now known as Xesxen
acathla has quit [Quit: [Guru Meditation]]
acathla has joined #litex
drraid has joined #litex
drraid has quit [Remote host closed the connection]
gce has joined #litex
gce has quit [Remote host closed the connection]
pftbest_ has joined #litex
pftbest has quit [Ping timeout: 272 seconds]
yorick has quit [Quit: reboot]
yorick has joined #litex
pftbest_ has quit [Remote host closed the connection]
pftbest has joined #litex
gregd has joined #litex
gregd has quit [Quit: Leaving]
nelgau has joined #litex
nelgau has quit [Ping timeout: 272 seconds]