Sunday, 2022-02-13

*** tpb <[email protected]> has joined #litex00:00
*** mikek_Xtrx <[email protected]> has joined #litex02:42
mikek_XtrxHello All:  I have received some critical warnings when compiling the fairwaves_xtrx project. Should I be concerned about this? 02:42
mikek_XtrxWARNING: [Vivado 12-3523] Attempt to change 'Component_Name' from 'pcie_s7' to 'pcie' is not allowed and is ignored.02:42
mikek_XtrxWARNING: [IP_Flow 19-3374] An attempt to modify the value of disabled parameter 'Legacy_Interrupt' from 'NONE' to 'None' has been ignored for IP 'pcie_s7'02:42
mikek_Xtrx# synth_ip $obj02:43
mikek_XtrxCRITICAL WARNING: [Vivado 12-5447] synth_ip is not supported in project mode, please use non-project mode.02:43
mikek_XtrxResolution: Verify the create_clock command was called to create the clock object before it is referenced.02:43
mikek_XtrxINFO: [Vivado 12-626] No clocks found. Please use 'create_clock' or 'create_generated_clock' command to create clocks. [/home/mikek/Documents/Cyclone5_SOC/Litex_New_release_Nov2021/xtrx_julia/build/fairwaves_xtrx_platform/gateware/fairwaves_xtrx_platform.xdc:361]02:43
mikek_XtrxCRITICAL WARNING: [Vivado 12-4739] set_clock_groups:No valid object(s) found for '-group [get_clocks -of_objects [get_nets rfic_clk]]'. [/home/mikek/Documents/Cyclone5_SOC/Litex_New_release_Nov2021/xtrx_julia/build/fairwaves_xtrx_platform/gateware/fairwaves_xtrx_platform.xdc:361]02:43
mikek_XtrxResolution: Check if the specified object(s) exists in the current design. If it does, ensure that the correct design hierarchy was specified for the object. If you are working with clocks, make sure create_clock was used to create the clock object before it is referenced.02:43
mikek_XtrxCRITICAL WARNING: [Vivado 12-4739] set_clock_groups:No valid object(s) found for '-group '. [/home/mikek/Documents/Cyclone5_SOC/Litex_New_release_Nov2021/xtrx_julia/build/fairwaves_xtrx_platform/gateware/fairwaves_xtrx_platform.xdc:361]02:43
mikek_XtrxResolution: Check if the specified object(s) exists in the current design. If it does, ensure that the correct design hierarchy was specified for the object. If you are working with clocks, make sure create_clock was used to create the clock object before it is referenced.02:43
*** bl0x_ <bl0x_!~bastii@p200300d7a746a200cab5aa5fd6830bc4.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 256 seconds)02:44
mikek_XtrxCRITICAL WARNING: [Constraints 18-4427] You are overriding a physical property set by a constraint that originated in a read only source. Your changes will not be saved with a project save. If you wish to make this change permanent, it is recommended you use an unmanaged Tcl file. [/home/mikek/Documents/Cyclone5_SOC/Litex_New_release_Nov2021/xtrx_julia/build/fairwaves_xtrx_platform/gateware/fairwaves_xtrx_platform.gen/sources_1/ip/pcie_s7/source/pcie_s7-P02:44
mikek_XtrxCIE_X0Y0.xdc:117]02:44
mikek_XtrxCRITICAL WARNING: [Constraints 18-4427] You are overriding a physical property set by a constraint that originated in a read only source. Your changes will not be saved with a project save. If you wish to make this change permanent, it is recommended you use an unmanaged Tcl file. [/home/mikek/Documents/Cyclone5_SOC/Litex_New_release_Nov2021/xtrx_julia/build/fairwaves_xtrx_platform/gateware/fairwaves_xtrx_platform.gen/sources_1/ip/pcie_s7/source/pcie_s7-P02:44
mikek_XtrxCIE_X0Y0.xdc:118]02:44
mikek_XtrxI have the "home" version of the vivado software, Do I need to have an upgraded version for clock support?02:44
*** bl0x_ <bl0x_!~bastii@p200300d7a738c50034438ab600b54555.dip0.t-ipconnect.de> has joined #litex02:45
mikek_XtrxAgain, I am not very familar with vivado software.. thanks! MikeK02:46
mikek_Xtrxthe build was successful, and created a Bin file. I just want to make sure it's ok before I program the XTRX device. Thanks.02:47
*** mikek_Xtrx <[email protected]> has quit IRC (Quit: Leaving)02:47
*** mikek_Xtrx <[email protected]> has joined #litex02:48
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:8192:df18:486a:6454> has quit IRC (Quit: Leaving)02:51
*** ilia__s <[email protected]> has quit IRC (Ping timeout: 250 seconds)03:21
*** mikek_Xtrx <[email protected]> has quit IRC (Ping timeout: 256 seconds)03:36
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has joined #litex03:37
*** Degi_ <[email protected]> has joined #litex03:46
*** Degi <[email protected]> has quit IRC (Ping timeout: 256 seconds)03:47
*** Degi_ is now known as Degi03:47
*** cr1901_ <cr1901_!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has joined #litex05:10
*** cr1901_ <cr1901_!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has quit IRC (Remote host closed the connection)05:12
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has quit IRC (Quit: Leaving)05:12
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has joined #litex05:12
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has quit IRC (Remote host closed the connection)05:13
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:f8ef:a9df:2427:39ab> has joined #litex05:29
*** linear_cannon <[email protected]> has quit IRC (Quit: linear_cannon)09:07
*** _franck_ <[email protected]> has quit IRC (Quit: Ping timeout (120 seconds))13:10
*** _franck_ <[email protected]> has joined #litex13:11
*** SpaceCoaster_ <SpaceCoaster_!~derek@user/spacecoaster> has joined #litex13:11
*** SpaceCoaster <SpaceCoaster!~derek@user/spacecoaster> has quit IRC (Read error: Connection reset by peer)13:12
*** SpaceCoaster_ is now known as SpaceCoaster13:12
*** mikek_Xtrx <[email protected]> has joined #litex13:20
*** mikek_ <[email protected]> has joined #litex13:45
*** mikek_Xtrx <[email protected]> has quit IRC (Ping timeout: 256 seconds)13:48
*** mikek_ <[email protected]> has quit IRC (Quit: Leaving)13:51
*** mikek_Xtrx <[email protected]> has joined #litex13:52
mikek_Xtrxyeah got it to work!   Counting LEDS on DECA board!  :)14:30
*** mikek_Xtrx <[email protected]> has quit IRC (Remote host closed the connection)15:20
*** mikek_Xtrx <[email protected]> has joined #litex15:20
*** mikek_Xtrx <[email protected]> has quit IRC (Remote host closed the connection)15:24
*** ilia__s <[email protected]> has joined #litex15:25
*** Martoni <Martoni!~Martoni@2a03:d604:103:600:2ad2:44ff:fe23:2f72> has joined #litex17:19
*** Thanos634 <[email protected]> has joined #litex19:16
Thanos634Hi Litex team, I am trying to create a SoC to test through the openroad toolchain (https://openroad.readthedocs.io/en/latest/user/GettingStarted.html)19:16
Thanos634Do you recommend using litex for asic? Do you have any suggestions/pointers to any related documentation or efforts of other users?19:16
Findeafaik this is being done by efabless for caravel, not sure if this is the right repo but it's what I got from a quick google: https://github.com/efabless/caravel_mgmt_soc_litex19:24
_florent_Hi Thanos634, the best would be to create specific build backend for each specific ASIC flow. I'm also building a generator to ease LiteX SoC generation and use in designs (without using the LiteX build system). This could also be useful for ASIC flow.19:37
Thanos634Thanks a lot  Finde I Am looking into it!19:41
_florent_eFabless indeed seems to use LiteX for Caravel, but I'm not sure I would have done it this way. I'm not sure for example they are using litex_sim or prototyping on hardware through boards available litex_boards. 19:41
Thanos634_florent_ I am not sure what you mean. My initial plan is to create the verilog model and then go thought the available open source tools to end up with a gds.19:43
_florent_Thanos634: The aim of the LiteX SoC generator is to simplify SoC generation (so what you call verilog model)19:45
_florent_Thanos634: For now, you can also generate a simple SoC with: https://github.com/litex-hub/litex-boards/blob/master/litex_boards/targets/simple.py19:46
_florent_and use one of the existing build backend to specialize the code19:47
Thanos634Exaclty. This is why i think it is a good idea to use litex. But as far as I can see it is targeting fpga tho. I just thought to ask in the channel if that should deter me.19:47
Thanos634It looks like it should not :)19:47
_florent_python3 -m litex_boards.targets.simple litex_boards.platforms.digilent_arty --no-compile-software19:49
_florent_python3 -m litex_boards.targets.simple litex_boards.platforms.terasic_de0nano --no-compile-software19:49
_florent_Here it will generate a simple SoC specialized for Xilinx or Altera/Intel19:51
_florent_You can then replace the few FPGA primitives in the code and test with OpenLane19:51
_florent_or create the OpenLane build backend that will allow direct specialization of the code19:52
Thanos634Hm, I see. I like the second idea a lot! Thanks19:52
_florent_I've been using LiteX on small parts of ASIC in the past (and also for verification), but this is not open-source19:53
_florent_it would be nice in the future to support the open-source flows19:53
Thanos634Of course. I am working on this with a friend for his thesis. If it goes well we will provide documentation for sure!19:59
_florent_Thanos634: great, happy to provide specific help if needed20:05
Thanos634Thanks a lot _florent_ !20:30
Thanos634I will keep you posted20:30
*** Martoni <Martoni!~Martoni@2a03:d604:103:600:2ad2:44ff:fe23:2f72> has quit IRC (Ping timeout: 240 seconds)23:04
*** ilia__s <[email protected]> has quit IRC (Ping timeout: 256 seconds)23:39
*** ilia__s9 <[email protected]> has joined #litex23:39
*** yrrapt[m] <yrrapt[m]!~yrraptmat@2001:470:69fc:105::1:2c66> has quit IRC (Ping timeout: 250 seconds)23:39
*** CarlFK <CarlFK!~carlfk@2001:470:69fc:105::5d8> has quit IRC (Ping timeout: 250 seconds)23:40
*** yrrapt[m] <yrrapt[m]!~yrraptmat@2001:470:69fc:105::1:2c66> has joined #litex23:51
*** CarlFK <CarlFK!~carlfk@2001:470:69fc:105::5d8> has joined #litex23:58

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