_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
lf_ has quit [Ping timeout: 240 seconds]
lf has joined #litex
key2 has quit [Read error: Connection reset by peer]
key2 has joined #litex
Degi has quit [Ping timeout: 240 seconds]
Degi has joined #litex
shorne has quit [Ping timeout: 260 seconds]
KSmith has quit [Quit: Leaving]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 260 seconds]
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 240 seconds]
shorne has joined #litex
shorne has quit [Ping timeout: 240 seconds]
shorne has joined #litex
[Matt] has quit [Ping timeout: 272 seconds]
Melkhior has joined #litex
[Matt] has joined #litex
Melkhior has quit [Remote host closed the connection]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 268 seconds]
kgugala has quit [Read error: Connection reset by peer]
kgugala has joined #litex
<_florent_> KSmith, Melkhior: the Kernel panic was due to a csr_data_width mismatch between the gateware and linux drivers (default csr_data_width changed recently to 32-bit), this is solved with https://github.com/litex-hub/linux-on-litex-vexriscv/commit/7b0c212b8051eb7416bbbd3c8826cf6625a4f80a
<_florent_> Krickit: i just tried building ./versa_ecp5 --cpu-type=picorv32 on my machine and it builds correctly but Yosys/Nextpnr is a but outdated, i'll do another test with a recent version.
Melkhior has joined #litex
<Melkhior> _florent_ Indeed with the 'working' commit from buildroot (88a268354d) and HEAD you just committed, it works fine :-)
<Melkhior> Thanks :-)
Melkhior has quit [Remote host closed the connection]
<powergraphic[m]> Are there any examples using litesata as part of a soc? I would like to access a data drive through Linux.
peeps has joined #litex
peeps[zen] has quit [Remote host closed the connection]
scientes_ is now known as scientes
scientes has joined #litex
scientes has quit [Changing host]
<kbeckmann> is it ok to ask netv2 questions here? can't seem to find a dedicated channel for it. anyway, i am wondering if there is a LiteX project setup where PCIe is enabled for netv2?
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 264 seconds]
kgugala_ has quit [Read error: Connection reset by peer]
kgugala has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 240 seconds]
kgugala has joined #litex
kgugala_ has quit [Ping timeout: 265 seconds]
<st-gourichon-fid> zyp, regarding unaligned read, I'm just writing C code. Booting then reading 32-bit word at 0x80070001 works and provides expected value. Looks like it is supported, then. But: booting then reading 32-bit word at 0x80070000 (works) then 32-bit word at 0x80070001 crashes.
<st-gourichon-fid> 0x8007xxxx is flash.
<st-gourichon-fid> Reading only 8-bit bytes from addresses and assembling them with a C macro works always.
<st-gourichon-fid> #define READ32_LE(p) ( (((p)[3]) << 24 ) | (((p)[2]) << 16 ) | (((p)[1]) << 8 ) | (((p)[0]) ) )
<st-gourichon-fid> READ32_LE(0x80070000) followed by READ32_LE(0x80070001) works.
<st-gourichon-fid> printf("%p", *((uint32_t *)0x80070000) ) printf("%p", *((uint32_t *)0x80070001) ) prints only one value
<st-gourichon-fid> Smells like a bug in flash-handling logic? Anyone experienced this kind of behavior? zyp, _florent_ ?
captain_morgan has quit [Quit: The Lounge - https://thelounge.chat]
captain_morgan has joined #litex
CarlFK has quit [Quit: Leaving.]
acathla has quit [Ping timeout: 240 seconds]
acathla has joined #litex
<kbeckmann> another pcie question.. has someone managed to instantiate two or more PCIe PHYs on Artix-7 with LiteX? i'm giving it a go but it seems i get stuck on using multiple refclk/IBUFDS_GTE2, which I guess isn't physically supported (need to check the datasheet here). i'm asking here in case someone has already attempted this and can nudge me in the right direction. I guess sharing one refclk between the
<kbeckmann> links is preferrable.
<kbeckmann> for context i want to build something that intercepts a PCIe link, forwarding TLPs between one uplink and one downlink. so sharing one refclk for both tx ports shouldn't be a problem if i understand things correctly.