| *** tpb <[email protected]> has joined #symbiflow | 00:00 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 00:25 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:bc3c:53c:d96a:be86> has quit IRC (Quit: Leaving) | 01:36 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:bc3c:53c:d96a:be86> has joined #symbiflow | 01:37 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 02:10 | |
| sf-slack | <cjearls> In the SymbiFlow examples, under "Download architecture definitions", it doesn't look like there's an option to download architecture definitions for any of the xc7k325t parts. Is this because no such definitions exist? | 03:08 |
|---|---|---|
| *** rvalles <rvalles!~rvalles@user/rvalles> has quit IRC (Read error: Connection reset by peer) | 03:42 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:bc3c:53c:d96a:be86> has quit IRC (Quit: Leaving) | 03:50 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:bc3c:53c:d96a:be86> has joined #symbiflow | 03:50 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has joined #symbiflow | 04:00 | |
| sf-slack | <torsten.reuschel> @cjearls: Correct, the bitstream is yet to be documented, hence no examples at this time. Are you interested in working with xc7k325t as well? | 04:09 |
| sf-slack | <cjearls> I was curious if SymbiFlow tools worked with a Kintex7 dev board | 04:13 |
| sf-slack | <torsten.reuschel> From my understanding, it does not yet work with the Kintex7. There is a working stub for the Kintex7 in the prjxray-db at this time, but I am not sure of its working condition. I am working with a Digilent Genesys2 board which uses the package xc7k325tffg900-2. For this package, I am working on updating fuzzers and scripts so that the bitstream documentation can be generated. | 04:21 |
| sf-slack | <cjearls> That is the board I was curious about | 04:23 |
| sf-slack | <torsten.reuschel> ok, great :) You can find my updated fuzzers and scripts here: https://github.com/unbtorsten/prjxray/tree/add_xc7k325t However, the script that generates the node tree demands more than 30GByte RAM which I don't have at my disposal right now. Am looking to optimizing the Python script to be more memory efficient... | 04:25 |
| *** abhiSK <[email protected]> has joined #symbiflow | 07:48 | |
| *** abhiSK <[email protected]> has quit IRC (Client Quit) | 07:49 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 09:01 | |
| *** TMM_ <[email protected]> has joined #symbiflow | 09:01 | |
| sf-slack | <fahrenkrog> I will have a look during the week and let you all know. Cheers! | 12:04 |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Remote host closed the connection) | 13:43 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 13:45 | |
| sf-slack | <tmichalak> Hmm, there are also two bits 10 and 9 responsible for spi_buswidth, but I am not sure which ones are actually responsible for QUAD mode. It would be good to see what is the setting of the BSPI register from the Vivado bitstream. | 13:54 |
| sf-slack | <fahrenkrog> I also tried writing 0x26B, assuming 0-> 1bit, 1-> 2 bits and 2->4 bits without success, that is, same load speed as before, about 10 seconds. At what byte address is the register located? | 14:21 |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 15:05 | |
| sf-slack | <tmichalak> Yeah, this sequence makes sense, since 30 02 00 01 is the WBSTAR register which is inline with the C++ code snippet you pasted | 15:15 |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 16:11 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 16:20 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 16:27 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 16:45 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 16:46 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 17:14 | |
| *** TMM_ <[email protected]> has joined #symbiflow | 17:14 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 276 seconds) | 20:31 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:bc3c:53c:d96a:be86> has quit IRC (Quit: Leaving) | 21:06 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has joined #symbiflow | 21:06 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has quit IRC (Quit: Leaving) | 21:13 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has joined #symbiflow | 21:14 | |
| sf-slack | <mithro> @nelson - What is the name of your group at BYU again? IE What is the CPE in the byu-cpe in https://byu-cpe.github.io/ComputingBootCamp/pages/schedule/ | 21:21 |
| tpb | Title: Schedule • Immerse Computing Bootcamp (at byu-cpe.github.io) | 21:21 |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has quit IRC (Quit: Leaving) | 21:56 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has joined #symbiflow | 21:56 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has quit IRC (Remote host closed the connection) | 21:56 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has joined #symbiflow | 21:57 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has quit IRC (Client Quit) | 22:01 | |
| *** cr1901 <cr1901!~cr1901@2601:8d:8600:911:49b1:beb0:6d15:e932> has joined #symbiflow | 22:01 | |
| sf-slack | <nelson> We are the Computer Engineering group - CPE stands for Computer Engineering… | 22:33 |
| *** lkcl <[email protected]> has quit IRC (Ping timeout: 268 seconds) | 23:00 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #symbiflow | 23:19 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Quit: ec) | 23:25 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!