_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
ilia__s has joined #litex
bl0x_ has quit [Ping timeout: 240 seconds]
bl0x_ has joined #litex
<bl0x_> _florent_: I've tried a few things, changing clock speed and in general looking about the cmod_a7 related code. Also tried sending serial.tx to another pin as suggested. I can't see any serial output. I see that litex_buildenv claims to have working support for cmod_a7, so I might try that as well. Shouldn't the LEDs also blink a pattern by default? I only see the RGB LEDs at ~30% brightness.
C-Man has quit [Ping timeout: 256 seconds]
Degi_ has joined #litex
Degi has quit [Ping timeout: 256 seconds]
Degi_ is now known as Degi
<sajattack[m]> so this is probably a dumb question, but could litesata be used for ide/pata? is it backwards compatible?
FabM has joined #litex
FabM has quit [Changing host]
FabM has joined #litex
<tnt> with an external sata -> pata you mean ?
<_florent_> bl0x_: I merged your PRs, by default the LedChaser should be blinking and only requires a valid clock/reset to do so. The issue could also be related to Symbiflow, if you have Vivado install it could be interesting to test with it. (Or I could generate a bitstream for you)
<_florent_> sajattack[m]: LiteSATA has a specific user interface and I'm not very familiar with ide/pata. Some chips are doing bridge between SATA and other interfaces, so this could also be an option if such chips exists for ide/pata. With a client on a design we for example used LiteSATA to interface with a SDCard through a DB300 chip: http://www.d-broad.com/db300_eg.html
<tpb> Title: d-broad Inc. (at www.d-broad.com)
<sajattack[m]> I was just looking at the ide controller here https://github.com/MiSTer-devel/ao486_MiSTer/blob/master/rtl/soc/ide.v and found it rather incomplete, and was curious if litesata could be used as a replacement, sounds like not without external hardware. tnx.
<bl0x_> _florent_: Thanks for the merge. I don't have Vivado on my laptop, only on a Windows machine. Tried to install litex there, but that turned out to be a rabbit hole. I might be able to set up an environment with Vivado on a more capable machine, but that'll take a couple of days. Which version of Vivado is currently preferred with litex? ... Generate bitstream for me: Only if it is quick for you to
<bl0x_> do.
TMM_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
TMM_ has joined #litex
C-Man has joined #litex
SpaceCoaster has quit [Ping timeout: 256 seconds]
<leons> Just to confirm my understanding of the LiteDRAM native ports / DMA frontend: LiteDRAM itself does not provide any mechnism to prevent data races, right? I have multiple ports accessing a shared chunk of memory, so I'm wondering what types of guarantees LiteDRAM can give me vs. what protections I need to implement myself.
<_florent_> leons: LiteDRAM doesn't provide a mechanism for this. The only guarantee currently is that there is no write data buffering internally, so the write order will be the similar to the order it accepts the data on the user ports
<_florent_> bl0x_: I'm going to generate a bitstream
<bl0x_> _florent_: thx
<leons> _florent_: Thanks, that already helps me a lot. I have a small hazard detection component which is suboptimal but constant-size and time, exactly what I need for my usecase.
<_florent_> result of ./digilent_cmod_a7.py --build
<leons> _florent_: The only thing which would be really helpful to know is the latency which an accepted `wdata` transaction takes until it is committed to memory and can be read again. Is that latency known somehow?
SpaceCoaster has joined #litex
<bl0x_> _florent_: I get nice blinking lights now! And a litex prompt when using lxterm. great! Now, the question is what's going wrong with symbiflow?
<_florent_> leons: this latency is fixed yes (the reason is still similar: there is no buffering, the data is accepted one it is emitted). If you want to measure it, you could put a LiteScope instance in your design and observe the ready from the wdata port and some internal control path signals of the PHY: https://github.com/enjoy-digital/litedram/blob/master/litedram/phy/s7ddrphy.py#L490-L502
<leons> Thanks for the pointers! I'll look into that :)
<_florent_> bl0x_: You should probably report this to the symbiflow project, since you had to do some adaptation to the LiteX build backend, I imagine it's something that hasn't been tested with LiteX
<bl0x_> _florent_: Will do. Thanks again
tpb_ has joined #litex
tpb has quit [Killed (NickServ (GHOST command used by tpb_))]
tpb_ is now known as tpb
Coldberg has joined #litex
kbeckmann1 is now known as kbeckmann
C-Man has quit [Ping timeout: 256 seconds]
Guest48 has joined #litex
<Wolfvak> I just noticed that on the orangecrab, the linux project uses a spi driver to interface with the SD card rather than the dedicated controller, is there any reason for that?
Guest48 has quit [Ping timeout: 256 seconds]
Martoni has joined #litex
FabM has quit [Ping timeout: 250 seconds]
Guest48 has joined #litex
<Guest48> Hi there, I hope this is the right place to seek help. Im trying to send bits to ttyACM from fomu with litex. These bits are generated from migen code, so in hardware, not from a programm running on the cpu. Currently litex seems to be using its own fork of valentyusb, however I have trouble to understand where exactly I can send the bits, meaning
<Guest48> how the valentyusb api works. A snippet would be greatly appreciated. Or can I not use valentyusb in this manner? So far I've been trying with the serv cpu, because it fit. And when I tried --cpu-type=None it gave me csr collision errors, which I didnt know how to resolve. For my design I dont actually need a cpu though (I think). Help is greatly
<Guest48> appreciated. And thanks for the work in litex it seems quite awesome, although I only understand a fraction of it.
Guest48 has quit [Quit: Client closed]
C-Man has joined #litex
Coldberg has quit [Ping timeout: 256 seconds]
Guest48 has joined #litex
Guest48 has quit [Client Quit]
C-Man has quit [Ping timeout: 240 seconds]
Martoni has quit [Ping timeout: 240 seconds]
<bl0x_> I'm wondering what the cd_sys4x is used for. Looking around litex I find that this is mostly associated with litedram? Boards without DRAM would not need these clock, or am I wrong?
<bl0x_> Perhaps that is just a general thing to always have a CD ready for serdes?