| *** tpb has joined #yosys | 19:20 | |
| *** emeb_mac has joined #yosys | 20:52 | |
| *** chris_99 has joined #yosys | 21:05 | |
| *** Sarayan has quit IRC | 22:26 | |
| *** chris_99 has quit IRC | 22:36 | |
| *** peepsalot has joined #yosys | 22:46 | |
| ZirconiumX | What would cause a "Multiple edge-sensitive events found for this signal" error from Yosys? | 23:06 |
|---|---|---|
| mwk | too many posedge * in sensitivity list | 23:07 |
| ZirconiumX | This is coming from nMigen, so it's a bit tricky to check | 23:07 |
| mwk | still | 23:07 |
| mwk | it happens in proc_dff pass for a process that has more than one edge trigger | 23:08 |
| mwk | (asynchronous resets are handled in an earlier pass, proc_arst) | 23:08 |
| mwk | so you'd need to dump the rtlil from nmigen and look for funky processes | 23:08 |
| mwk | it could be a result of a botched async reset | 23:09 |
| ZirconiumX | Wonderful. | 23:09 |
| tnt | does nmigen even have async reset ? | 23:09 |
| ZirconiumX | It has a full reset network by default | 23:09 |
| tnt | yeah. Sync reset. | 23:10 |
| tnt | (AFAIU) | 23:10 |
| ZirconiumX | Mm. Not sure then. | 23:11 |
| tnt | Digging a bit, looks like it does support async reset, but the default is still sync. | 23:14 |
| tnt | from what I read it was omigen that didn't do async without tricks. | 23:14 |
| whitequark | yep | 23:18 |
| whitequark | that was one of the problems I set out to fix with nmigen | 23:18 |
| *** kuldeep has joined #yosys | 23:35 | |
| *** twnqx has quit IRC | 23:35 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!