Monday, 2020-04-06

*** tpb has joined #litex00:00
*** CarlFK has joined #litex00:03
*** scanakci has joined #litex00:15
*** HoloIRCUser2 has quit IRC00:40
*** Degi has quit IRC00:44
*** Degi has joined #litex00:46
*** futarisIRCcloud has joined #litex01:11
*** FFY00 has quit IRC01:23
*** FFY00 has joined #litex01:23
*** HoloIRCUser has joined #litex01:48
*** HoloIRCUser1 has joined #litex01:49
*** HoloIRCUser has quit IRC01:52
*** FFY00 has quit IRC02:06
*** FFY00 has joined #litex02:09
*** FFY00 has quit IRC02:12
*** FFY00 has joined #litex02:15
*** FFY00 has quit IRC02:19
*** FFY00 has joined #litex02:20
*** FFY00 has quit IRC02:22
*** FFY00 has joined #litex02:25
*** FFY00 has quit IRC02:28
*** FFY00 has joined #litex02:29
*** FFY00 has quit IRC02:40
*** FFY00 has joined #litex02:40
*** FFY00 has quit IRC02:43
*** FFY00 has joined #litex02:44
*** captain_morgan has joined #litex04:06
*** futarisIRCcloud has quit IRC04:18
*** HoloIRCUser has joined #litex06:17
*** HoloIRCUser1 has quit IRC06:21
*** HoloIRCUser1 has joined #litex07:09
*** HoloIRCUser has quit IRC07:13
*** _whitelogger has quit IRC08:06
*** _whitelogger has joined #litex08:08
*** CarlFK has quit IRC09:02
*** fkokosinski has joined #litex09:22
*** SingularitySurf has joined #litex10:12
SingularitySurfHi, could someone give me a hint on how I can add my own code to the BIOS to set up some custom peripherals?10:14
*** SingularitySurf has quit IRC12:05
acathlahttps://github.com/enjoy-digital/litex/wiki/Create-And-Load-Software-To-The-CPU13:07
tpbTitle: Create And Load Software To The CPU · enjoy-digital/litex Wiki · GitHub (at github.com)13:07
acathlait's empty, so yeah, how do I add the bios/program to the .bit file on a spartan6?13:09
acathlaISE complain : INFO:Bitgen:341 - This design is using one or more 9K Block RAMs (RAMB8BWER).13:09
acathla   9K Block RAM initialization data, both user defined and default, requires a13:09
acathla   special bit stream format.13:09
acathlaHum, I have a litex> prompt, may be it's ok finaly13:13
_florent_acathla: yes it's still empty, i created the topics and try to fill things progressively :)13:31
acathlaBon courage!13:31
_florent_:), this can be useful to create a custom firmware and load if to the CPU: https://github.com/litex-hub/fpga_101/tree/master/lab00413:33
tpbTitle: fpga_101/lab004 at master · litex-hub/fpga_101 · GitHub (at github.com)13:33
_florent_There is also this: https://github.com/enjoy-digital/litex/wiki/Tutorials-Resources13:34
tpbTitle: Tutorials Resources · enjoy-digital/litex Wiki · GitHub (at github.com)13:34
somlo_florent_: I've managed to patch litex_soc_ctrl for 64bit, then liteeth and litespi to work on 64bit with litex_soc_ctrl (https://github.com/gsomlo/linux/tree/litex-devel-next)13:48
tpbTitle: GitHub - gsomlo/linux at litex-devel-next (at github.com)13:48
somloI then built a kernel with litespi *and* CONFIG_MMC_SPI=y13:49
somlobut now I am stuck at coming up with the right DT node description13:49
_florent_somlo: nice, sorry i saw your previous progress but haven't answered yet13:52
somloI can do a straightforward "litespi0" node and see the probe function succeed. But setting up a "mmc-spi-slot" on top of that is s13:53
somlo*is still a mystery :)13:53
_florent_somlo: i think you just need to replace the spidev0 part in the dts: https://hastebin.com/konisemomo.makefile14:22
tpbTitle: hastebin (at hastebin.com)14:22
somlo_florent_: https://hastebin.com/isomukivub.xml14:37
tpbTitle: hastebin (at hastebin.com)14:37
somlomaybe I still need to add something to the kernel config (besides SPI, SPI_MASTER, SPI_LITESPI, and MMC_SPI)?14:38
*** fkokosinski has quit IRC14:40
*** fkokosinski has joined #litex14:40
_florent_somlo: sorry, not sure i explained it correctly, i think you need something like this:14:42
_florent_https://hastebin.com/belajicuse.py14:42
tpbTitle: hastebin (at hastebin.com)14:42
_florent_(sorry for the python part, i'm editing json2dts.py)14:42
fkokosinski_florent_hi, i've been trying to reproduce some working setup with litevideo in ycbcr mode. I've tried your https://github.com/enjoy-digital/netv2 design on netv2 board and got this from pattern fb: https://drive.google.com/file/d/1XSO7sElsx-UMvwVAsV6Rp32STnQNCrod/view?usp=sharing. In firmware's source code it states that the white, yellow, cyan,14:43
fkokosinskigreen and so on, so they don't really match. Did it use to be like this when you worked on it, or maybe some recen change to one of the litex cores caused this behavior?14:43
tpbTitle: GitHub - enjoy-digital/netv2: NeTV2 SoC based on LiteX (at github.com)14:43
somlo_florent_: oooh, embed the mmc-slot thing *within* litespi014:44
somlolet me try that :)14:44
somlo_florent_: progress! https://imgur.com/a/7hPahcF14:54
tpbTitle: Imgur: The magic of the Internet (at imgur.com)14:54
somlonow I need to figure out what "unsupported mode bits 4" and "can't change chip-select polarity" actually means, but this is way better than the sound of crickets I was experiencing before :D14:55
_florent_somlo: ok good :)14:59
_florent_somlo: i'm also going to do some tests on the nexys4ddr with Linux-on-LiteX-Vexriscv15:05
somlo_florent_: and (obviously) thanks for getting me unstuck w.r.t. the DT entry! I'll pick this back up later in the afternoon (got some $DAYJOB stuff I kinda have to take care of first) :)15:09
fkokosinski_florent_ ping15:49
*** fkokosinski has quit IRC16:19
mithrosomlo: Is Rocket verilog of systemverilog?16:22
somlomithro: litex-data-cpu-rocket/... is Verilog (upstream Rocket sources are Chisel)16:27
mithrosomlo: Thanks, I think I was getting it confused with Ariane16:28
somloI thought Ariane was also Verilog (not *System*), but don't quote me on that :)16:29
*** CarlFK has joined #litex16:44
somlo_florent_: is the `reg = <x>` value of `mmc-slot@x` relative to that of the enveloping `spi@yyy`, or is it absolute (i.e., x == yyy)?16:49
Findeariane is sv fwiw17:40
*** tucanae47_ has joined #litex18:07
*** tucanae47 has quit IRC18:08
*** tucanae47_ is now known as tucanae4718:08
*** HoloIRCUser has joined #litex18:10
*** HoloIRCUser1 has quit IRC18:13
*** FFY00 has quit IRC18:38
*** FFY00 has joined #litex18:39
somlo_florent_: after some RTFMing, it appears nested nodes' `reg` properties are relative to their parents', so if litespi starts at 0x12004800, and the mmc-slot nested inside should also start at 0x12004800, the latter really *does* need to have `reg = <0>`, i.e. start at parent node's offset18:46
somloat least one fewer things to confuse me :)18:47
mithro_florent_: I'm a bit confused about how the build at https://travis-ci.com/github/enjoy-digital/litex/jobs/315546886 succeeded, given it downloaded a Linux binary on Mac? Is the compiler never actually used as part of the setup.py test command?19:35
tpbTitle: Travis CI - Test and Deploy with Confidence (at travis-ci.com)19:35
somlo_florent_: Still not *the* answer, but for LiteSPI, the example should probably have `litespi,num-cs = <1>`, not 2, here: https://github.com/litex-hub/linux-on-litex-vexriscv/blob/master/buildroot/board/litex_vexriscv/patches/linux/0007-drivers-spi-add-LiteSPI-driver.patch#L2420:54
tpbTitle: linux-on-litex-vexriscv/0007-drivers-spi-add-LiteSPI-driver.patch at master · litex-hub/linux-on-litex-vexriscv · GitHub (at github.com)20:54
somloif this means how many actual `cs` pins there are in the `spisdcard` pads, it's 1 on every set of pads on all platforms in litex[-boards] I could find, not sure why they'd have used 2 for the example...20:55
somloif that makes sense to you, I'll add that to my kernel patch set as part of the litespi driver upgrade20:56
zypwhat's the general opinion on wishbone-tool vs litex_server.py?21:47
zypI'm having some problems getting litescope to work via wishbone-tool - works fine via litex_server.py21:48
_florent_somlo: yes cases where we use 2 or more cs pins are rare, it's only useful on boards where multiple chips are using the same SPI lines21:53
_florent_somlo: i've not been able to test the SDCard in SPI mode with Linux-on-LiteX-Vexriscv, but will do some testing tomorrow21:54
_florent_zyp: litex_server is probably slower and has less features than wishbone-tool, but that's what i'd recommend at first for LiteScope if you don't need specific features from wishbone tool. I've only used wishbone-tool for the specific cases that were not possible with litex_server (ex UART in Crossover mode over Etherbone) and it was working great, but i haven't tested personally LiteScope with it.21:59
zypyeah, I tested the crossover mode earlier, and then I figured I'd keep using it, and found stuff weren't working properly22:03
zypbut I haven't looked too hard into how it's failing yet, so I don't have enough info to properly report it yet22:04
zypI'm also looking forward until ethernet works more stable on the colorlight board, I guess it'll be a lot faster to dump the litescope buffer over etherbone rather than the uart bridge :)22:09

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!