| *** tpb has joined #symbiflow | 00:00 | |
| *** rj has quit IRC | 00:03 | |
| *** rj has joined #symbiflow | 00:08 | |
| *** Degi_ has joined #symbiflow | 00:10 | |
| *** Degi has quit IRC | 00:13 | |
| *** Degi_ is now known as Degi | 00:13 | |
| *** gsmecher has quit IRC | 00:21 | |
| *** rj has quit IRC | 00:33 | |
| *** rj has joined #symbiflow | 00:40 | |
| *** kgugala has joined #symbiflow | 00:41 | |
| *** adjtm has quit IRC | 00:51 | |
| mithro | cjearls: Do you have a github issue? | 01:04 |
|---|---|---|
| *** rj has quit IRC | 01:05 | |
| sf-slack1 | <cjearls> I haven't made one yet, it fell back to the Python script, so everything was still working. When I get the chance, I'll submit one | 01:06 |
| mithro | cjearls: I think I got distracted with other stuff -- I was working on getting it packaged up all properly in https://github.com/SymbiFlow/fasm/pull/64 | 01:10 |
| mithro | cjearls: I forget where I got up to, I think I went yak shaving... | 01:12 |
| mithro | cjearls: I ended up getting https://github.com/SymbiFlow/symbiflow-rr-graph/commits/master packaged and published on PyPi | 01:13 |
| mithro | cjearls: https://github.com/SymbiFlow/actions#examples | 01:15 |
| mithro | cjearls: Not enough hours in the day apparently.... | 01:31 |
| sf-slack1 | <cjearls> I see. So is it fixed, or will it be fixed soon? | 01:32 |
| mithro | cjearls: I think it was more "I was in the process of fixing it but got distracted and can't remember were I got too..." | 01:34 |
| sf-slack1 | <cjearls> Ok, that makes sense | 01:36 |
| mithro | Looks like Mac + Linux were mostly working | 01:37 |
| mithro | but Windows seems unhappy -> https://github.com/SymbiFlow/fasm/pull/64/checks?check_run_id=2055039242#step:8:3346 | 01:37 |
| mithro | cjearls: It looks like past me actually logged some github issues about various things -> https://github.com/SymbiFlow/fasm/issues | 01:39 |
| mithro | I'm going to call it a night | 01:40 |
| sf-slack1 | <cjearls> Alright, thanks for your help | 01:41 |
| *** citypw has joined #symbiflow | 02:25 | |
| *** proteusguy has quit IRC | 03:15 | |
| *** citypw has quit IRC | 04:34 | |
| *** citypw has joined #symbiflow | 05:22 | |
| *** gromero has quit IRC | 05:45 | |
| *** gromero has joined #symbiflow | 05:46 | |
| *** calphool has joined #symbiflow | 06:18 | |
| *** calphool has quit IRC | 06:33 | |
| sf-slack1 | <acomodi> mithro: prjxray-db update looks fine, apart from an unrelated minor instability to the PCIE pips which is straightforward to fix, I'll open an issue about that | 07:13 |
| -_whitenotifier-3- [prjxray] acomodi opened issue #1665: PCIE interface PIPs instability - https://git.io/J3rth | 07:17 | |
| *** TMM has quit IRC | 10:44 | |
| *** TMM has joined #symbiflow | 10:44 | |
| *** adjtm has joined #symbiflow | 10:44 | |
| *** gromero_ has joined #symbiflow | 11:09 | |
| *** gromero has quit IRC | 11:11 | |
| *** kraiskil has joined #symbiflow | 11:51 | |
| mithro | acomodi / cjearls: I reverted the PCIE PIPs file and pushed it to master | 12:02 |
| *** proteusguy has joined #symbiflow | 12:14 | |
| *** kraiskil has quit IRC | 13:07 | |
| *** adjtm has quit IRC | 14:00 | |
| *** rj has joined #symbiflow | 14:29 | |
| *** rj has quit IRC | 14:29 | |
| *** rj has joined #symbiflow | 14:30 | |
| *** rj has quit IRC | 14:30 | |
| *** adjtm has joined #symbiflow | 14:48 | |
| *** citypw has quit IRC | 15:11 | |
| *** gsmecher has joined #symbiflow | 16:09 | |
| *** kraiskil has joined #symbiflow | 16:29 | |
| *** adjtm_ has joined #symbiflow | 16:36 | |
| *** adjtm has quit IRC | 16:39 | |
| sf-slack1 | <cjearls> Ok, the issue appears to be fixed. I'm following the prjxray build instructions, but when I run settings/artix7.sh, I'm getting an error `AssertionError: Mapping file /home/cjearls/prjxray/settings/artix7/resources.yaml does not exists` . Any idea what could be going wrong? | 16:46 |
| sf-slack1 | <acomodi> @cjearls i think you need to run the database prepare step before sourcing the settings file | 16:48 |
| sf-slack1 | <cjearls> I've been following every step o fthe Quickstart Guide here https://symbiflow.readthedocs.io/en/latest/prjxray/docs/db_dev_process/readme.html Is there something I am supposed to do before this? | 16:49 |
| tpb | Title: Project X-Ray SymbiFlow (at symbiflow.readthedocs.io) | 16:49 |
| sf-slack1 | <acomodi> Try to run step 7 and than step 6 | 16:50 |
| sf-slack1 | <acomodi> I think the readme needs an update | 16:51 |
| sf-slack1 | <cjearls> It looks to be doing something, I think that was the answer | 16:52 |
| sf-slack1 | <cjearls> Thanks | 16:52 |
| *** kraiskil has quit IRC | 16:56 | |
| sf-slack1 | <cjearls> Yep, it's working | 16:57 |
| *** kraiskil has joined #symbiflow | 17:09 | |
| sf-slack1 | <cjearls> How can I know if a package is fully bonded? I'm trying to add xc7a35tftg256-1, but the guide to add a new device to an existing family says to choose a fully bonded package. Is that just the package in the resources.yaml with the most pins listed under it? | 17:11 |
| *** jokus_malus[m] has joined #symbiflow | 17:15 | |
| *** kgugala_ has joined #symbiflow | 17:31 | |
| *** kgugala has quit IRC | 17:32 | |
| *** kgugala has joined #symbiflow | 17:48 | |
| *** kgugala_ has quit IRC | 17:50 | |
| *** TMM has quit IRC | 18:08 | |
| *** TMM has joined #symbiflow | 18:08 | |
| *** gromero_ has quit IRC | 18:19 | |
| *** kraiskil has quit IRC | 18:38 | |
| *** kraiskil has joined #symbiflow | 18:52 | |
| *** ayazar has quit IRC | 19:12 | |
| *** ayazar has joined #symbiflow | 19:13 | |
| *** gromero_ has joined #symbiflow | 19:19 | |
| *** kraiskil has quit IRC | 20:22 | |
| *** calphool has joined #symbiflow | 23:37 | |
| calphool | mithro -- you replied to my questions about timing analysis by mentioning that the place and route process honors SDC files, but that's not quite what I was asking, related, but not quite the same thing. In Quartus (and I assume other proprietary suites), you specify your SDC constraints, and it uses those as it's doing place and route, but then | 23:47 |
| calphool | it *also* reports anywhere where it was unable to guarantee those constraints due to things that aren't really observable (generally we think of temperature, but I think it could be anything that the chip manufacturer wanted to put in the silicon that could cause variability). In other words, although I might say "this net must have 5ns response | 23:47 |
| calphool | time" or whatever, only the silicon producer would know if the route selected can accomplish that across the chip's entire rated temperature range... or at least that's what I always thought -- I didn't think that that "manufacturing variability" was public. Of course you guys know a lot more about this stuff than I do, but if I was going to try | 23:47 |
| calphool | to advocate that my team switch to the Symbiflow pipeline, I suspect that'll be one of the things that I'll get asked: "what about timing/temperature analysis after place and route?" | 23:47 |
| mithro | calphool: For Xilinx parts we support pulling designs back into Vivado so you can double check the timing in Vivado | 23:48 |
| calphool | Oh, okay. So the "response" to that "concern" would be "quit worrying about timing analysis until you're closer to delivery, and then you can import your design into Quartus for final checks" or something like that. | 23:52 |
| calphool | ...I should say timing/temperature analysis. I get that basic timing is guaranteed by the place and route. | 23:52 |
| calphool | I'll have to try using the tool chain a bit on my own for a while... what I would really like to see is parity between what the software guys do in their dev pipelines and what we're doing on the hardware side -- all kinds of quality checks, linters, enforced unit tests, and so on, every time they change *anything*. The Symbiflow projects seem | 23:57 |
| calphool | like they could take us closer to that direction. It just feels weird that hardware engineering is so manual compared to what they do on the software side. | 23:57 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!