davidlattimore has quit [Remote host closed the connection]
davidlattimore has joined #litex
kgugala_ has joined #litex
kgugala has quit [Ping timeout: 246 seconds]
davidlattimore has quit [Ping timeout: 245 seconds]
kgugala has joined #litex
kgugala_ has quit [Read error: Connection reset by peer]
awordnot has quit [Ping timeout: 265 seconds]
awordnot has joined #litex
m4ssi has joined #litex
CarlFK has quit [Read error: Connection reset by peer]
CarlFK has joined #litex
peepsalot has quit [Read error: Connection reset by peer]
peepsalot has joined #litex
Bertl_zZ is now known as Bertl
Dolu_ has joined #litex
kgugala has quit [Quit: -a- Connection Timed Out]
kgugala has joined #litex
m4ssi has quit [Remote host closed the connection]
<joseng>
Hi all, can someone give me a hint how to get the litex_server/litex_sim and litescope_cli working? First I tried to put in the UARTWishboneBridge in my SoC and start the litex_server over uart and then just run the litescope_cli in another terminal window, but I get a timeout when uploading/starting (I see the connection from litescope_cli in the
<joseng>
litex_server output)
<joseng>
Then I wanted to run the litex_sim as in the litescope wiki page, but when I run this with "litex_sim --with-etherbone --with-analyzer" and then "litex_server --udp --udp-ip=192.168.10.113" (ip of my ubuntu VM), I get a timeout from litex_server
<joseng>
Hi florent, yes exactly these two articles
<joseng>
Am I missing something how to get started with the tools? Or missed something in my setup of litex?
<_florent_>
maybe you can do a test in simulation first
<_florent_>
if you do litex_sim --with-etherbone
<_florent_>
when the SoC is running, are you able to ping 192.168.1.51?
<_florent_>
if so, you can then do: litex_server --udp --udp-ip=192.168.1.51 (you need to provide the IP of the simulation, not your VM)
<_florent_>
and do litex_cli --ident
<_florent_>
it should return the identifier of the simulation
Bertl is now known as Bertl_oO
<joseng>
After dinner if came now to testing
<joseng>
Ping works, connecting with the litex_server also. When I connect, I see the output "Error trying to write data to TAP device" in the litex_sim window
<somlo>
daveshah: with the new(er) yosys (2116c58) I can once again fit a linux (mmu) capable rocket chip and LiteEth on my versa5g board
<somlo>
100% utilization without "-nowidelut", 97% with the option turned on
<somlo>
only tested the latter, fails to actually tftp anythong over ethernet, but passes DRAM testing :)
<joseng>
But when I run litex_client --ident, I get the error "File "litex_client.py", line 96, in dump_identifier
<joseng>
c = chr(wb.read(wb.bases.identifier_mem + 4*i) & 0xff)
<joseng>
AttributeError: 'RemoteClient' object has no attribute 'bases'"
<somlo>
I'll try again without nowidelut, see if that improves LiteETH behavior
<somlo>
but whoo, it's back to where it fits, which is great!
<joseng>
_florent_ After starting the litex_server again several times, now litex_cli --ident works and also litescope_cli runs successful
<joseng>
with the simulator
<joseng>
Seems running the setup script again fixed something?! Now I can also connect with the litex_server and uart to my SoC in the FPGA. With litex_cli --ident I get a result :)
<joseng>
Only litescope_cli does not come back from "[running]"
<joseng>
Ok, newby error. I ran litescope_cli in the wrong folder, where it found the analyzer.csv from the simulator and not in the build folder where the correct file from the SoC is....
<joseng>
Sorry for spamming around...
d_olex has quit [Read error: Connection reset by peer]