| *** tpb has joined #litex | 00:00 | |
| *** CarlFK has quit IRC | 00:18 | |
| *** rohitksingh has joined #litex | 00:43 | |
| *** CarlFK has joined #litex | 01:59 | |
| *** rohitksingh has quit IRC | 02:15 | |
| *** rohitksingh has joined #litex | 03:28 | |
| *** CarlFK has quit IRC | 04:49 | |
| *** rohitksingh has quit IRC | 04:52 | |
| *** rohitksingh has joined #litex | 04:53 | |
| *** CarlFK has joined #litex | 05:32 | |
| *** rohitksingh has quit IRC | 07:46 | |
| *** m4ssi has joined #litex | 07:55 | |
| *** freemint has joined #litex | 07:59 | |
| *** karol is now known as kgugala | 08:43 | |
| *** freemint has quit IRC | 11:39 | |
| *** freemint has joined #litex | 12:07 | |
| *** freemint has quit IRC | 12:23 | |
| *** freemint has joined #litex | 14:07 | |
| *** freemint has quit IRC | 14:13 | |
| *** m4ssi has quit IRC | 14:15 | |
| *** m4ssi has joined #litex | 14:15 | |
| *** freemint has joined #litex | 14:19 | |
| *** freemint has quit IRC | 16:42 | |
| *** m4ssi has quit IRC | 17:10 | |
| somlo | daveshah: does a 'nextpnr_ecp5::assertion_failure' with the following message "what(): Assertion failure: closest != BelId() (/builddir/build/BUILD/nextpnr-85f4452b0a3bd47ccb25be023859542ffef888f7/ecp5/pack.cc:2588)" ring any immediate bells? | 17:44 |
|---|---|---|
| somlo | trying to build latest LiteX with Rocket for the trellisboard (or for the versa5g, same issue) | 17:45 |
| somlo | I am currently using yosys d448483, trellis 30ee6f2, and nextpnr 85f4452 | 17:45 |
| daveshah | There was a LiteX change relating to ECLKBRIDGECS | 17:45 |
| daveshah | a while ago | 17:46 |
| daveshah | I did fix a nextpnr issue related to it but that was also a month or so ago | 17:46 |
| somlo | daveshah: it gets weirder -- it builds fine (latest LiteX sources) on the development VM I've been using for a few months and updating | 17:46 |
| somlo | but I just built a new VM this morning for a "mobile demo", with the same software (as far as I can tell), and it fails on that one :) | 17:47 |
| somlo | so if I had to guess, it's something the whole setup depends on *implicitly* in some way, but I can't for the life of me figure out what | 17:47 |
| somlo | at least yosys/trellis/nextpnr/migen/abc/iverilog/verilator are the very same RPMs I've installed on the old (working) VM... :) | 17:49 |
| somlo | so if this assertion thing isn't immediately obvious, don't worry about it. It's gotta be some weird quantum Heisen-bug with my setup... :) | 17:51 |
| somlo | the downside of having had this happen is that now I'm scared to even breathe too hard in the general direction of my *working* VM :D | 17:52 |
| daveshah | It could be to do with an old prjtrellis version being used to build nextpnr | 17:53 |
| daveshah | Can you sha256 nextpnr-ecp5 to double check it is the same binary? | 17:53 |
| somlo | daveshah: they're different :( Now I gotta figure out how they ended up that way, but this is definitely helpful -- thanks! | 17:57 |
| daveshah | It's possible one is built against libtrellis from before libtrellis had ECLKBRIDGECS in it (probably November ish?) | 17:58 |
| somlo | oh, I think I know -- I pushed both trellis and nextpnr updates into Fedora to resolve their request to prep for python 3.9 | 18:01 |
| somlo | and nextpnr must have pulled in the old trellis dependency | 18:02 |
| somlo | RPMs on my dev machine are from my local builds, the ones on the new machine are from upstream fedora (which -- good to know -- has a broken nextpnr package, so I should probably rebuild that and push it out again :) | 18:03 |
| somlo | also, note to self: in the future, always build trellis first, and wait for it to be published before requesting a nextpnr build :) | 18:08 |
| *** rohitksingh has joined #litex | 18:25 | |
| acathla | Is there a common reason for the litex builder to never finish a build and stay forever in loop? | 19:04 |
| *** rohitksingh has quit IRC | 19:04 | |
| *** rohitksingh has joined #litex | 19:33 | |
| *** freemint has joined #litex | 19:46 | |
| Xiretza | _florent_: fyi, liteeth CI is pretty red due to new_soc | 20:00 |
| *** rohitksingh has quit IRC | 20:03 | |
| _florent_ | Xiretza: thanks, i'll look at that | 20:05 |
| *** freemint has quit IRC | 20:07 | |
| *** freemint has joined #litex | 20:08 | |
| _florent_ | Xiretza: it's green again :) | 20:34 |
| *** _whitelogger has quit IRC | 20:37 | |
| *** rohitksingh has joined #litex | 20:37 | |
| _florent_ | Xiretza: ah no, not completely | 20:38 |
| Xiretza | _florent_: wasn't it green already? weird | 20:40 |
| *** _whitelogger has joined #litex | 20:40 | |
| _florent_ | it was green, but has not been re-triggered with litex changes | 20:50 |
| Xiretza | ah, makes sense. oh my, such a pretty log, I like it! | 20:57 |
| _florent_ | thanks, that's really green again now | 21:02 |
| _florent_ | btw, i'm fine your improvements in #33, do you have others changes you want to do or should i merge? | 21:04 |
| Xiretza | _florent_: I'm currently still trying to get customizable mem/csr/interrupt mappings in there somehow, but that's more of a litex thing anyway | 21:56 |
| Xiretza | the depths of argparse are not a pretty place | 21:56 |
| _florent_ | Xiretza: the generator should probably use a .yml config file as the others generator (litedram/litepcie), defining the mem/csr/interrupt map would also be easy this way | 22:10 |
| Xiretza | _florent_: yeah, that'd probably be the sanest solution. I'll have a look around. | 22:11 |
| _florent_ | Xiretza: i could do the skeleton if you want and you could add the configurable mapping? | 22:12 |
| Xiretza | sure, if you feel like it, that'd be great. shouldn't be too much trouble to cobble it together myself, but you know your design preferences best :) | 22:14 |
| *** CarlFK has quit IRC | 23:03 | |
| _florent_ | Xiretza: done with https://github.com/enjoy-digital/liteeth/commit/fcadd60ceaa4ac06b2b3ec5c902c8201eebe5cb9, feel free to add parameters if you want to customize the mapping | 23:22 |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!