| *** tpb <[email protected]> has joined #f4pga | 00:00 | |
| *** jacobk <[email protected]> has quit IRC (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) | 02:32 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 04:11 | |
| *** TMM_ <[email protected]> has joined #f4pga | 04:11 | |
| *** F4PGASlackBridge <[email protected]> has joined #f4pga | 07:02 | |
| *** kgugala <[email protected]> has joined #f4pga | 07:06 | |
| F4PGASlackBridge | <kgugala> @me1 it should be working now | 07:06 |
|---|---|---|
| kgugala | yep, it is | 07:07 |
| F4PGASlackBridge | <acomodi> Yeah, nextpnr is able to handle the Interchange, and from it RapidWright can generate the dcp and open it in the Vivado viewer. There are a set of tests up until a LiteX design capable of running Linux that you can find here: https://github.com/chipsalliance/fpga-interchange-tests | 08:11 |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Read error: Connection reset by peer) | 08:44 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 08:45 | |
| *** jn <jn!~quassel@user/jn/x-3390946> has quit IRC (Remote host closed the connection) | 09:04 | |
| *** jn <jn!~quassel@2a02:908:1065:960:20d:b9ff:fe49:15fc> has joined #f4pga | 09:05 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 11:00 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 11:00 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 11:01 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 11:01 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 15:49 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC (Remote host closed the connection) | 15:50 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has joined #f4pga | 15:54 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 16:10 | |
| *** TMM_ <[email protected]> has joined #f4pga | 16:10 | |
| *** littlebobeep <littlebobeep!~alMalsamo@gateway/tor-sasl/almalsamo> has quit IRC (Ping timeout: 268 seconds) | 17:00 | |
| lambda | so uh, nextpnr-xilinx is somehow reversing two pins on my Arty A7 board - U12 and V12 should be PMOD JC[0] and JC[1], respectively, but they're connected to JC[1] and JC[2] | 17:53 |
| lambda | all other PMOD pins are fine | 17:54 |
| lambda | the prjxray-db definitions match up at least with digilent's schematics (U12 is IO_L20P_T3_A08_D24_14, V12 is IO_L20N_T3_A07_D23_14) | 17:56 |
| lambda | oh, my first message should read "they're connected to JC[1] and JC[0]", sorry | 17:56 |
| lambda | I can't find anything about this issue on google, so I doubt it's a board layout issue | 18:02 |
| lambda | ah. https://github.com/gatecat/nextpnr-xilinx/issues/42 | 18:07 |
| lambda | extremely weird that it's only one specific pin pair | 18:07 |
| *** jtf <jtf!~jtf@2601:285:8000:87::5c4> has joined #f4pga | 21:07 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!