Monday, 2022-04-25

*** tpb <[email protected]> has joined #litex00:00
*** Degi_ <[email protected]> has joined #litex00:37
*** Degi <[email protected]> has quit IRC (Ping timeout: 250 seconds)00:37
*** Degi_ is now known as Degi00:37
*** subthreshold <subthreshold!~subthresh@2607:f140:800:1::284> has quit IRC (Quit: Client closed)00:40
*** subthreshold <subthreshold!~subthresh@2607:f140:800:1::284> has joined #litex01:08
*** xenador77 <[email protected]> has joined #litex03:34
xenador77Is there a guide to adding a board to the supported boards list and/or porting litex to an ice40 dev board?03:38
xenador77I'm capable of using google just wanted to know if there was a definitive "official guide"03:39
*** xenador77 <xenador77!~xenador77@user/xenador77> has quit IRC (Remote host closed the connection)03:47
*** xenador77 <[email protected]> has joined #litex03:48
*** subthreshold <subthreshold!~subthresh@2607:f140:800:1::284> has quit IRC (Ping timeout: 252 seconds)03:49
*** FabM <FabM!~FabM@2a03:d604:103:600:4923:d8d3:c661:83e3> has joined #litex06:18
*** subthreshold <[email protected]> has joined #litex06:23
_florent_amstan: The implementation indeed seems very efficient! I may have a good use-case to test it/use it: I have a SDS1104X-E on my desk, that can also be used as a LiteX dev board that I would like to use as an additional screen, but the 100Mbps Ethernet link is a bit limitating, encoding in QOI on the Host and decoding it in the FPGA could be be enough to have something usable. 07:42
_florent_amstan: It's perfectly possible to integrate verilog in LiteX BTW, we are mostly using it for integrating CPUs in the "open-source" part, but it's heavily used to re-integrate other regular Verilog/System-Verilog/VHDL cores in proprietary projects. 07:43
_florent_subthreshold: The controller integration is probably done by add_sdram in your design, the code is here: https://github.com/enjoy-digital/litex/blob/master/litex/soc/integration/soc.py#L1344-L151907:45
_florent_subthreshold: you add the PHY in your target file (since specific) and add_sdram adds the LiteDRAM core + connections to the SoC.07:46
_florent_xenador77: Sorry no, we don't have an official guide. I would recommend starting simple: To get a first version of your SoC running, you just need an input clock and a UART07:48
*** ilia__s0 <[email protected]> has quit IRC (Ping timeout: 276 seconds)07:48
_florent_xenador77: So you can just create a platform file with this. You should then be able to build the simple target on it: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/simple.py07:49
_florent_xenador77: ex when building it for Digilent Arty board: python3 -m litex_boards.targets.simple litex_boards.platforms.digilent_arty --build07:49
_florent_xenador77: Once it's working, you can then progressively add the specific clocking, peripherals, etc... and create a specific target file for your board07:50
*** ilia__s0 <[email protected]> has joined #litex07:51
subthreshold_florent_ thanks so much! That makes sense - for a while i had ignored add_SDRAM as I thought that was adding the memory device model itself. '=(07:53
*** davebee <[email protected]> has joined #litex08:05
davebeeI'm trying to get jtagbone working on litex. I have a vexriscv, on an ECP5 (colorlight i9). Is there anything I need to do other than call soc.add_jtagbone()? Perhaps some clock domain I'm not connecting / providing? Can I bring out the JTAG to io pins, rather than connecting to the internal ECP5 JTAGG?08:13
davebeeThe colorlight i9 extension board has an stm32 device which implements JTAG over USB, 'cmsisdap'. I'm using openFPGALoader.08:16
*** ilia__s0 <[email protected]> has quit IRC (Read error: Connection reset by peer)08:16
*** ilia__s0 <[email protected]> has joined #litex08:18
_florent_davebee: Just adding soc.add_jtagbone should be enough yes08:30
_florent_davebee: then used a .cfg file similar to this: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/prog/openocd_butterstick.cfg08:30
_florent_davebee: when generating your design, add --csr-csv=csr.csv08:30
_florent_davebee: then start litex_server: litex_server --jtag --jtag-config=openocd_butterstick.cfg08:31
davebeeI have the csv file. I wonder what I'm doing wrong then. I don't have direct access to the JTAG pins. They connect via pogo pins to the STM32.08:31
_florent_davebee: then you can try to do a litex_cli --regs that should dump the SoC's registers08:31
davebeeltiex-server is looking for vid 0403, pid 601408:31
davebeeIs there an easy way to bring out the JTAG to io pins?08:32
_florent_here it's using a FT232 chip, you'll have to adapt this to your programmer08:32
_florent_not really for this, some HDL parts will be missing, at least for JTAGBone08:33
_florent_if that's GDB for VexRiscv that you want, it shoud be possible to expose the JTAG pins directly08:33
davebeeI think I'll try that then. Thanks.08:33
_florent_at least for NaxRiscv, Dolu added it recently: https://github.com/enjoy-digital/litex/blob/master/litex/soc/cores/cpu/naxriscv/core.py#L323-L32808:34
davebeegreat, I'll take a look08:42
*** subthreshold <[email protected]> has quit IRC (Quit: Client closed)08:42
xenador77Thanks _florent_09:49
xenador77hopefully Upduino-3.1 will be on the list (:09:49
xenador77will be on the list soon*09:50
*** xenador77 <xenador77!~xenador77@user/xenador77> has quit IRC (Remote host closed the connection)09:58
*** Xenador77 <Xenador77!~river@user/xenador77> has joined #litex10:04
*** Xenador77 <Xenador77!~river@user/xenador77> has quit IRC (Client Quit)10:07
*** xenador77 <xenador77!~xenador77@user/xenador77> has joined #litex10:07
davebeeFirst problem solved : I hadn't set the cpu-variant to "standard+debug". No I have a debug plugin I can see the JTAGG being used and see timing cacls for the jtag interface. But I still can't see the risc-v in a jtag scan.10:09
*** ilia__s0 <[email protected]> has quit IRC (Quit: The Lounge - https://thelounge.chat)10:25
*** somlo <[email protected]> has quit IRC (Remote host closed the connection)12:35
*** somlo <[email protected]> has joined #litex12:55
*** davebee <[email protected]> has quit IRC (Quit: Leaving)14:18
*** ilia__s0 <[email protected]> has joined #litex14:57
*** ilia__s0 <[email protected]> has quit IRC (Quit: The Lounge - https://thelounge.chat)15:20
*** ilia__s0 <[email protected]> has joined #litex15:21
*** ilia__s06 <[email protected]> has joined #litex15:58
*** ilia__s0 <[email protected]> has quit IRC (Ping timeout: 246 seconds)16:00
*** ilia__s06 is now known as ilia__s016:00
*** davebee <[email protected]> has joined #litex16:08
*** davebee <[email protected]> has quit IRC (Quit: Leaving)16:17
*** ilia__s00 <[email protected]> has joined #litex16:32
*** ilia__s0 <[email protected]> has quit IRC (Ping timeout: 272 seconds)16:36
*** ilia__s00 is now known as ilia__s016:36
*** ilia__s0 <[email protected]> has quit IRC (Read error: Connection reset by peer)18:31
*** ilia__s07 <[email protected]> has joined #litex18:31
*** zjason <[email protected]> has quit IRC (Read error: Connection reset by peer)19:08
*** zjason <[email protected]> has joined #litex19:11
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Quit: Leaving)19:51
*** ilia__s0 <[email protected]> has joined #litex20:07
*** ilia__s07 <[email protected]> has quit IRC (Ping timeout: 246 seconds)20:10
*** indy <[email protected]> has quit IRC (Ping timeout: 240 seconds)22:03
*** indy <[email protected]> has joined #litex22:07
*** Melkhior <Melkhior!~Melkhior@2a01:e0a:1b7:12a0:225:90ff:fefb:e717> has quit IRC (Ping timeout: 260 seconds)22:09
*** Melkhior <Melkhior!~Melkhior@2a01:e0a:1b7:12a0:225:90ff:fefb:e717> has joined #litex23:54
*** Melkhior_ <Melkhior_!~Melkhior@2a01:e0a:1b7:12a0:225:90ff:fefb:e717> has joined #litex23:55
*** Melkhior <Melkhior!~Melkhior@2a01:e0a:1b7:12a0:225:90ff:fefb:e717> has quit IRC (Remote host closed the connection)23:56

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