| *** tpb <[email protected]> has joined #yosys | 00:00 | |
| *** killjoy <[email protected]> has joined #yosys | 00:02 | |
| *** sugarbeet <[email protected]> has quit IRC (Ping timeout: 252 seconds) | 13:09 | |
| *** sugarbeet <[email protected]> has joined #yosys | 13:11 | |
| *** somlo_ is now known as somlo | 15:49 | |
| somlo | playing with the nextpnr-himbaechel xilinx blinky, I noticed that if I try to use the green LEDs ([15:12], T10, T9, J5, H5, currently commented out in the example arty xdc file), I get an "unipmemented" assertion failure in nextpnr/himbaechel/uarch/xilinx/fasm.cc:326 | 15:50 |
|---|---|---|
| somlo | After some clumsy poking around, it looks like tile_type/src/dst are RIOI3_SING / RIOI_OLOGIC0_OQ / RIOI_O0 (none of that means anything to me, yet... :) ) | 15:50 |
| somlo | Wondering if this is worth pursuing as a n00b project to slowly gather situational awarenes w.r.t. the way things hang together, or if maybe something else (easier) would make more sense :) | 15:50 |
| somlo | gatecat, lofty: ^^^^; any other ideas/clues much appreciated :) | 15:50 |
| lofty | somlo: might be useful, yes | 15:51 |
| *** mewt <[email protected]> has quit IRC (Ping timeout: 248 seconds) | 17:13 | |
| *** mewt <[email protected]> has joined #yosys | 17:13 | |
| *** FabM <FabM!~FabM@2a03:d604:108:3f00:493f:31b2:3ae:4ec5> has joined #yosys | 19:31 | |
| somlo | guess I need to detour into reading up on FASM, and also all the information encoded in the tile, src, and dst names... | 19:38 |
| *** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 244 seconds) | 19:45 | |
| somlo | ok, FASM as a file format is fairly straightforward, the magic is in the name of the various entries. And, the method I'm studying (write_pip() in himbaechel/uarch/xilinx/fasm.cc) seems to be doing a bit of "sed"-like editing of the tile name, src, and dst, so I'm guessing the "unimplemented" assertion is more sed-like rules being needed to write out the "correct" FASM ? | 20:11 |
| somlo | so what I really need is a quick and efficient way to come up to speed on the PIP nomenclature. Do I go straight to the firehose (prjxray) for that, or is there a better/smarter way to start digging ? | 20:12 |
| lofty | somlo: probably prjxray; every project has its own naming rules | 20:13 |
| somlo | I guess this is very much specific to xilinx fpga layout, and their feature naming scheme. fingers crossed for some comprehensible documentation :D | 20:17 |
| *** mewt <[email protected]> has quit IRC (Ping timeout: 248 seconds) | 20:32 | |
| *** mewt <[email protected]> has joined #yosys | 20:34 | |
| *** tecepe <tecepe!~tecepe@2603:7080:2af0:7eb0::111e> has joined #yosys | 21:47 | |
| *** tecepe <tecepe!~tecepe@2603:7080:2af0:7eb0::111e> has quit IRC (Client Quit) | 21:50 | |
| *** tecepe <tecepe!~tecepe@2603:7080:2af0:7eb0::111e> has joined #yosys | 21:50 | |
| tecepe | Hello, I am having trouble using the VTR container. When running `vtr_flow/scripts/run_vtr_task.py vtr_flow/tasks/regression_tests/vtr_reg_basic/basic_timing`, what I get as answer is a bunch of errors related to "yosys failed". I then realized that yosys as a command is not available in $PATH. I was wondering what I am missing. Please feel free to | 21:58 |
| tecepe | point me out to a different forum if this is not the right one to ask this. | 21:58 |
| lofty | tecepe: for problems in a container, you should probably go to the VTR people | 22:00 |
| tecepe | Thank you, I'll try to find their forum | 22:12 |
| *** nonchip <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 22:35 | |
| *** nonchip <[email protected]> has joined #yosys | 22:35 | |
| *** krispaul <[email protected]> has joined #yosys | 23:08 | |
| *** kristianpaul <kristianpaul!~paul@user/kristianpaul> has quit IRC (Ping timeout: 244 seconds) | 23:08 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!