_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
toshywoshy has quit [Remote host closed the connection]
toshywoshy has joined #litex
Degi_ has joined #litex
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
peeps[zen] has joined #litex
peepsalot has quit [Ping timeout: 252 seconds]
nrossi[m] has joined #litex
FabM has joined #litex
FabM has joined #litex
FabM has quit [Changing host]
cr1901_ has joined #litex
cr1901 has quit [Read error: Connection reset by peer]
Wolf0 has quit [Ping timeout: 265 seconds]
Wolf0 has joined #litex
<tcal> tnt: that fixed it!!!
<tnt> tcal: \o/
jeffdi1 has quit [Quit: Leaving.]
essele has joined #litex
<leons> I've got to say, compared to how crazy running a bit-bang memory mapped I2C over wishbone over UART through a TCP connection tunneled through two SSH sessions with a latency of ~10ms sounds like, it works surprisingly well. Essentially doing the thing outlined here https://twitter.com/enjoy_digital/status/1382032355351801861. Thanks _florent_ for providing the infrastructure for that!
<leons> _florent_: Would you mind placing https://gist.github.com/enjoy-digital/e40d296a852335acfcab89a686147272 under a free license? That way I can vendor it into my repository proper 🙂
* geertu found "secret" code ;-)
zjason` is now known as zjason
<zyp> leons, if you like, you can have this: https://paste.jvnv.net/view/oEaWv
<tpb> Title: JVnV Pastebin – View paste – Untitled (at paste.jvnv.net)
<zyp> consider it public domain, I wrote it
<leons> zyp: Awesome, thanks! It works like a charm and is also significantly faster than the other one (presumably because of the microsecond-sleep delays which really aren't needed when you bitbang over wishbone-uart-tcp-ssh :D)
<zyp> it's not needed for bitbanging over wishbone-usb either
<zyp> i2c is usually doing 400 kHz without issue, where a half clock is 1.25us, good luck getting latency below that from a python script running on a regular OS :)
cr1901_ is now known as cr1901
<leons> yeah i figure 🙂
<leons> oh my, I just found out I can tell Element to stop replacing my plain-text smileys with unicode emojis... not exactly a great idea to have that enabled by default :/
jeffdi1 has joined #litex
FabM has quit [Quit: Leaving]
jersey99 has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
<bjonnh> doesn't have the Z7-20
<bjonnh> will it just require me to tweak some configs?
<tpw_rules> i just cannot get lxterm to work properly. i'm trying linux-on-litex-vexriscv on my butterstick and i can use openocd to program the svf just fine. but lxterm just prints garbage. some letters on the keyboard echo a different letter back but it doesn't really make sense
<tpw_rules> i get a blue pattern on the LEDs until lxterm starts then they shut off
<bjonnh> (XC7Z020-1CLG400C)
<bjonnh> I see that there are some XC7Z020 supported
<tpb> Title: litex (liteDRAM, liteVideo, liteEth) Supported boards & Interfaces - Google Tabellen (at docs.google.com)
<bjonnh> does that mean that the DDR is on the ARM and not accessible directly from the FPGA?
<tpw_rules> not entirely sure if ethernet isn't working either or i don't have the network configured correctly
<tpw_rules> how did you get this to work? https://twitter.com/FlUxIuS/status/1461632857814749192
<tpw_rules> i did change the RAM because my board only has the 2gbits
<tpw_rules> is the jtag uart just generally broken? i never got it to work right with my acorn either
<tpw_rules> the design does instantiate a JTAGG block
<tpw_rules> so it must be in there
<_florent_> tpw_rules: here is how I tested JTAG UART on the butterstick recently:
<tpw_rules> ah hah, it needs --jtag-chain 49 . how am i supposed to know that?
<tpw_rules> i guess that's how the hardware works out. it should certainly be documented somewhere
<_florent_> We need to document it yes, for now it was in this issue :)
<_florent_> for the test over Etherbone, the build command is the one at 12-13s of the video
<tpw_rules> hmm, it seems the surgery to downgrade the ram did not work properly
<_florent_> tpw_rules: I just created https://github.com/enjoy-digital/litex/issues/1120 to look at it later
<_florent_> and https://github.com/litex-hub/litex-boards/issues/298 to look at the Butterstick DRAM
<tpw_rules> _florent_: i replaced this line: https://github.com/litex-hub/litex-boards/blob/bf8b23c19f4299638f75274ee2d346ec99bf7572/litex_boards/targets/gsd_butterstick.py#L114 with MT41K64M16 but it did not work. do i need to change the second parameter too?
<tpw_rules> the first 2 bytes work, the next 2 bytes don't, and the 2 bytes after that cause the bios to hang
<tpw_rules> the bios does only say it has 131072KiB
<tpw_rules> but i would expect to see 256MB
<tpw_rules> can litex only use one chip?
<_florent_> Just changing to MT41K64M16 should be enough
<tpw_rules> _florent_: https://pastebin.com/66cjLdpS
<tpb> Title: Warn : gdb services need one or more targets defined __ _ __ - Pastebin.com (at pastebin.com)
<_florent_> tpw_rules: and it was OK with the MT41K256M16?
<_florent_> Can you try to increase the sys_clk_freq to 75MHz?
<tpw_rules> idk, i didn't try it with that. my board only has the MT41K64M16 chip
<tpw_rules> let me try with just the commands you listed
<_florent_> ok, I'm just trying to understand, but on my side I was testing with a 8gb version
<tpw_rules> hm, the problem is with linux-on-litex-vexriscv specifically
<tpw_rules> (which runs at 60MHz)
jersey99 has quit [Quit: Client closed]
<tpw_rules> ok, i tried rebuilding the linux-on-litex-vexriscv at 75MHz and it didn't help
<_florent_> tpw_rules: you could eventually try to build by adding this: https://github.com/litex-hub/linux-on-litex-vexriscv/blob/master/make.py#L377 (we saw issue with DM support on ECP5, which is used by SMP, using the l2 cache avoid using DM and could solve the issue if this the same thing we saw on OrangeCrab/ECPIX-5)
<tpw_rules> does the l2 cache size make a difference?
<tpw_rules> i'm trying it for experiments' sake but unless i am mistaken it is already defined here: https://github.com/litex-hub/litex-boards/blob/bf8b23c19f4299638f75274ee2d346ec99bf7572/litex_boards/targets/gsd_butterstick.py#L115
<tpw_rules> huh, sure enough it works with 2048
<tpw_rules> but not 8192
<tpw_rules> hm, now the --boot is failing with [LXTERM] Got unexpected response from device 'b'E''
ewen has joined #litex
<tpw_rules> i can't get tftp to work either but i think that's a network config issue
<tpw_rules> i see ARP packets in wireshark but i guess the board is not receiving the replies?
<tpw_rules> _florent_: how do you get bits onto this thing
<tpw_rules> i resorted to writing all the images to flash then recompiling with flash support
<tpw_rules> but it works!! https://pastebin.com/sr6k9LC4
<tpb> Title: boot 0x40f00000 - Pastebin.com (at pastebin.com)