_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
Degi_ has joined #litex
Degi has quit [Ping timeout: 265 seconds]
Degi_ is now known as Degi
hrberg has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
hrberg has joined #litex
mtretter has joined #litex
FabM has joined #litex
FabM has joined #litex
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
<_florent_> sensille: When using add_ethernet, you can specify phy_cd: https://github.com/enjoy-digital/litex/blob/master/litex/soc/integration/soc.py#L1626
<_florent_> sensille: if you are not using add_ethernet, have a look at how the clock domain renaming is done in it to see how to apply it to LiteEthMAC
<_florent_> (but that's something that should be improved)
<sensille> i spent quite some time there yesterday reading the code. i think phy_cd does not do the trick, it only applies to bus width != 32. but anyway, i also found that the device has not enough resources to handle an additional interface just for debugging purposes
<_florent_> ah OK... you could eventually add a second UART + UARTBone if that's possible/convenient on your system.
<sensille> i tried uartbone, but that's too slow on my system, mainly because the usb uart dongle add to much latency
<sensille> although echo 1 > /sys/bus/usb-serial/devices/ttyUSB0/latency_timer improved it a lot
<sensille> i now have a somewhat working dev environment. my current problem ist that i can't increase integrated_main_ram_size above 0x1000. synthesis works, but the BIOS-ram-test fails
<_florent_> sensille: strange, which FPGA board are you using?
<sensille> linsn_rv901t, spartan6
<_florent_> OK, strange. And what's the test behavior? do you only get errors for addr >= 0x1000 or even for < 0x1000?
<sensille> even for the base 0x40000000. write does nothing, read gives data from an address in the middle of the ROM. like offset 7758 in ROM
<sensille> even stranger, 40000004 give the next word from rom
<sensille> address decoding can't be that wrong
<_florent_> hmm, can your provide the generated software/include/generated/mem.h?
<sensille> dump 0x40000000 show data starting at 0x7910. mem.h: https://dpaste.org/gEv4n
<tpb> Title: dpaste/gEv4n (C) (at dpaste.org)
<_florent_> sensille: OK, I don't see anything specific, do you have another board to similar test? (and see if it could be an issue with ISE?)
<sensille> no other spartan6 board, only artix 7 and lattice ecp5
<sensille> i should also learn how to simulate the design and see if it works in simulation
<_florent_> Just tested litex_sim --integrated-main-ram-size=0x2000 and memtest pass fine
FabM has quit [Ping timeout: 260 seconds]
cr1901 has joined #litex
cr1901 has quit [Remote host closed the connection]
cr1901 has joined #litex
<sensille> maybe litescope can sched some light onto this
<sensille> i read the same values with mem_read from the bios and via etherbone
<sensille> and what i read is always around 0x100 from the top of the bios. when the bios shrinks, the offset changes with it
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
embargo has quit [Ping timeout: 246 seconds]
embargo has joined #litex