| *** tpb <[email protected]> has joined #symbiflow | 00:00 | |
| *** emilazy <emilazy!~emilazy@user/emilazy> has quit IRC (Ping timeout: 268 seconds) | 00:36 | |
| *** gatecat <[email protected]> has quit IRC (Ping timeout: 268 seconds) | 00:36 | |
| *** gatecat_ <[email protected]> has joined #symbiflow | 00:36 | |
| *** emilazy <emilazy!~emilazy@user/emilazy> has joined #symbiflow | 00:48 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 01:24 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 01:25 | |
| *** zyp <[email protected]> has quit IRC (Ping timeout: 256 seconds) | 02:08 | |
| *** zyp <[email protected]> has joined #symbiflow | 02:18 | |
| *** bl0x_ <bl0x_!~bastii@p200300d7a70e7c009652b8da135cd16a.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds) | 02:23 | |
| *** bl0x_ <bl0x_!~bastii@p200300d7a7172200fba0d562efa7c9cd.dip0.t-ipconnect.de> has joined #symbiflow | 02:25 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 03:11 | |
| sf-slack | <kgugala> @bl0x_ did the desing meet timings? | 08:18 |
|---|---|---|
| bl0x_ | kgugala: Still trying to figure out, but report_timing*.rpt tells slack(MET) for all reported paths. Anything else I should grep for in the output? | 10:26 |
| sf-slack | <acomodi> @bl0x_ Can you please open a GH issue on symbiflow-examples with instructions on how to reproduce the same results you are seeing, alongside with the various versions of the tools and of the symbiflow arches? | 10:34 |
| bl0x_ | @acomodi, will do. thx. | 10:36 |
| sf-slack | <acomodi> @bl0x_: for reference, I am trying the latest linux-on-litex-vexriscv with the latest symbiflow packages. From the arty board config (https://github.com/litex-hub/linux-on-litex-vexriscv/blob/master/make.py#L72) I have removed some of the soc capabilities as some of them are not yet supported/tested: spiflash, sdcard, spi, i2c, xadc and icap_bitstream | 10:47 |
| sf-slack | <acomodi> And also tried to reduce the clock frequency to 75 MHz by adding the following `soc_kwargs = {"sys_clk_freq": int(75e6)}` | 10:47 |
| sf-slack | <acomodi> Ah, I misread the board name though and I am currently testing this for the arty 35t, and I just verified that Linux is booting correctly | 11:04 |
| bl0x_ | @acomodi I've tried with the default clock frequency of 48e6 that's used in the cmod_a7. I understand that the arty boards have seen much more testing than the cmod. | 11:11 |
| bl0x_ | Also I've tried both vexriscv and femtorv quark. Same result. Vexriscv appears to be the standard/reference here, though? | 11:12 |
| sf-slack | <acomodi> So, for a 48 MHz clock timing should be easily met, and I think that either CPU variant should be fine (if it works on Vivado as well). There might be a missing configuration of some IOs done by symbiflow, but it is hard to tell at the moment | 11:27 |
| *** adjtm <adjtm!~adjtm@2a0c:5a80:3a17:7800:d1f9:3a6a:2c35:84e> has quit IRC (Quit: Leaving) | 13:52 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 15:52 | |
| *** gatecat_ is now known as gatecat | 18:29 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 20:11 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 20:13 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Remote host closed the connection) | 21:10 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 21:11 | |
| sf-slack | <timo.callahan> bl0x_: I have a cmod A7 35T on order, so I might be able to help cross-check when it arrives. | 23:48 |
| sf-slack | <timo.callahan> Different topic: my understanding is that the Xilinx XADC is supported in prjxray, symbiflow-arch-defs, and yosys, but not vtr --- is that accurate? | 23:50 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!