_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
CarlFK has quit [Quit: Leaving.]
CarlFK has joined #litex
freemint has quit [Ping timeout: 256 seconds]
CarlFK has quit [Ping timeout: 272 seconds]
<Finde> awesome scanakci
CarlFK has joined #litex
<sajattack[m]> this was fun to play with https://github.com/tomtor/rust-litex
<tpb> Title: GitHub - tomtor/rust-litex: Running Rust on the (Linux) Litex VexRiscv FPGA SOC (at github.com)
<sajattack[m]> while I wait for someone to help with my vga issues
_whitelogger has joined #litex
CarlFK has quit [Read error: Connection reset by peer]
<levi> What vga issues are you having?
<sajattack[m]> I'm not really sure, I'm trying to get it to build on an altera board, I did what florent suggested, and linux hangs when it starts the framebuffer
<sajattack[m]> it's probably a clock issue
<levi> Just how much of the system is "hung"? Do you have a way of getting a debug dump of processor registers via jtag or some wishbone bridge?
<sajattack[m]> I have uart and usb blaster
<sajattack[m]> not sure how to get a debug dump from usb blaster
<sajattack[m]> if possible
<levi> I am pretty new to litex so I'm not entirely sure, but I know there's a debug option for the CPU cores and a number of "wishbone-to-X" bridges where X includes ethernet and I think uart. You'd have to poke at the example programs.
<sajattack[m]> where can I find the examples?
<levi> There's generally a directory in each of the litex module repos with examples in it.
<levi> https://github.com/timvideos/litex-buildenv/wiki/Debugging could give you some pointers too.
<tpb> Title: Debugging · timvideos/litex-buildenv Wiki · GitHub (at github.com)
<sajattack[m]> thanks
<scanakci> thanks @Finde
<sajattack[m]> ok I can confirm the clock is running via dasblinkenlightsen
<sajattack[m]> * ok I can confirm the clock is running via das blinkenlightsen
<sajattack[m]> either that or I made a python mistake that has the same effect
<sajattack[m]> no, I'm pretty sure the clock is alive
<sajattack[m]> does the pixel clock need to be phase shfited?
<sajattack[m]> the openocd recommended on that debugging wiki page doesn't compile
<levi> Alas, it is the nature of wikis to be out-of-date
<sajattack[m]> indeed
rohitksingh has joined #litex
rohitksingh has quit [Ping timeout: 240 seconds]
<_florent_> scanakci: thanks for the update and great for the LiteDRAM integration. I just merged your PR to allow you to go further, i'll probably do small changes in the next days but it will only be cosmetic changes
<_florent_> sajattack[m]: sorry i need to look at the code to be able to help but i'm not able to it now, i'll have more time for it after the weekend. At least you don't need a specific phase for the pixel_clock. It's possible that the Linux kernel has some parts hardcoded for 7-series, to ease your work, maybe you could look at how it was done before when the video out was initialized in bare metal: before
<tpb> Title: Add litevideo driver · litex-hub/linux-on-litex-vexriscv@9a9f01b · GitHub (at github.com)
<_florent_> you could try to look at framebuffer.h/framebuffer.c and skip the part related to the clocking since it's already initialized at a fixed frequency on your board
<dkozel> _florent_: I was just about to ask if a C example for LitePCIe exists, but noticed litepcie_util in the software directory.
<_florent_> You should be able to have something on the screen (garbage data) by just initializing the DMA
<dkozel> Would it be useful for me to add a description of that util to the top level examples folder README?
<_florent_> dkozel: yes, there is also a new version of the driver/utils in https://github.com/enjoy-digital/netv2/tree/master/software
<tpb> Title: netv2/software at master · enjoy-digital/netv2 · GitHub (at github.com)
<_florent_> dkozel: yes sure, contributions on documentation are welcome
<dkozel> _florent_: Great. I'll look at both of those and contribute back where things aren't obvious to a new user
<dkozel> Is the plan to merge back the netv2 PCIe driver in the future?
<_florent_> dkozel: it's not decided yet, we could keep both for now
<_florent_> dkozel: the one in LitePCIe is the original one created in 2014, the one in netv2 is a new one that has a different architecture and can be used to do DMA TX/R/X onmultiple channels in //
<_florent_> dkozel: both are compatible with the gateware. For a new design, i would probably recommend using the one in netv2
freemint has joined #litex
freemint has quit [Remote host closed the connection]
freemint has joined #litex
freemint has quit [Ping timeout: 256 seconds]
CarlFK has joined #litex
keesj has quit [Ping timeout: 240 seconds]
freemint has joined #litex
freemint has quit [Ping timeout: 256 seconds]
CarlFK has quit [Quit: Leaving.]
freemint has joined #litex
vup has quit [Quit: vup]
anuejn has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
anuejn has joined #litex
vup has joined #litex
<scanakci> _florent_: thanks for the merge. I think my next PR will come once I integrate LiteETH.
freemint has quit [Ping timeout: 256 seconds]
freemint has joined #litex
CarlFK has joined #litex
freemint has quit [Ping timeout: 256 seconds]
freemint has joined #litex
freemint has quit [Ping timeout: 256 seconds]
<sajattack[m]> update: made it past framebuffer initialization after 20000 seconds, but still nothing on screen
<sajattack[m]> longest boot ever?
<sajattack[m]> I should probably mention I'm using linux prebuilt, could that be the issue? When I build it myself it doesn't boot at all
<sajattack[m]> I see that framebuffer change is newer than linux prebuilt
<sajattack[m]> I got linux building and running but hangs at the same spot
<CarlFK> karol: mithro handed me a Opsis booster gizmo....
<CarlFK> when I plug in usb, I get Product: Tomu Bootloader (5) v2.0-rc7
<CarlFK> but no tty
freemint has joined #litex
freemint has quit [Ping timeout: 256 seconds]
tpb has quit [Remote host closed the connection]
tpb has joined #litex