Re: [casper] Unconnected output block warnings when compiling with dac_mkid

Hi Richard, I've just modified the dac yellow blocks so that they don't try to call the initialisation script for the now non-existent parallel_to_serial block. The interface should still work -- essentially it's now frozen with the parameters originally set by the dac yellow block, which I

Re: [casper] Unconnected output block warnings when compiling with dac_mkid

T. From: Jack Hickish <jackhick...@gmail.com> Sent: Monday, September 28, 2015 10:49 AM To: G Jones; Tubbesing, Richard G Cc: casper@lists.berkeley.edu Subject: Re: [casper] Unconnected output block warnings when compiling with dac_mkid Hi Richard, I'v

[casper] Unconnected output block warnings when compiling with dac_mkid

Hello, I am a graduate student at ERAU using ROACHs for my research project. I have been trying to use the toolflow for some time now and I have run in to many issues. Currently, I have the latest mlib_devel from the casper-astro git. When I compile a design that includes the dac_mkid

Re: [casper] Unconnected output block warnings when compiling with dac_mkid

Regarding the parallel to serial converter, so far I haven't experienced a need to set the configuration registers on the DAC, so I just deleted that block inside the yellow block and tied the output ports to constants. Obviously not a good solution if you do need the configuration registers. Not