Hello again,
Thank you everyone for your help and tips. I'll try the new yellow block soon to make sure everything is ok. Now I have to figure out why my design wasn't working, haha. I am sure I will have other questions/issues in the future. Thanks again for the quick support! -Richard 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'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 assume are right -- but I don't have hardware to test on. I also added terminators to the gateways in the yellow block which should suppress "unconnected output" warnings. Pushed to github.com/casper-astro/mlib_devel.git<http://github.com/casper-astro/mlib_devel.git> master branch [https://avatars2.githubusercontent.com/u/1156539?v=3&s=400]<http://github.com/casper-astro/mlib_devel.git> casper-astro/mlib_devel Contribute to mlib_devel development by creating an account on GitHub. Read more...<http://github.com/casper-astro/mlib_devel.git> Let me know if you have any problems. Cheers, Jack PS: There doesn't appear to be any pcore for the mkid_dac_4x in the repository, does anyone have this in their mlib_devel? If so can you raise a pull request against casper / point me at your repository. Failing that, I'll copy/paste the code from here -- https://github.com/argonnexraydetector/RoachFirmPy/tree/master/ANLYellowBlocks/mkid_dacadc_4x On Mon, 28 Sep 2015 at 00:20 G Jones <glenn.calt...@gmail.com<mailto:glenn.calt...@gmail.com>> wrote: 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 sure about the warning. Glenn On Sep 27, 2015 7:02 PM, "Tubbesing, Richard G" <tubbe...@my.erau.edu<mailto:tubbe...@my.erau.edu>> wrote: 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 yellow block, I am having two issues: 1) If the yellow block is placed fresh from the library into the model and then the model is compiled, I get an error related to initializing mask parameters on the "parallel_to_serial" block that is in a subsystem of the dac_mkid block. I can fix this if I replace the "parallel_to_serial" with one from the library or simply copying it and pasting itself back in to the model. Is there anyway to fix this? I have a work around but it is rather annoying to go in and replace those to blocks whenever I use the dac_mkid yellow block. 2) I am getting many warnings when I compile. They look like the following two: Warning: Output port 1 of 'adc_to_dac_test/dac_mkid1/adc_to_dac_test_dac_mkid1_dac_data_i1' is not connected. > In > /opt/Xilinx/14.6/ISE_DS/ISE/sysgen/bin/lin64/xlCompileGenerateMdl.p>xlCompileGenerateMdl > at 203 In /opt/Xilinx/14.6/ISE_DS/ISE/sysgen/bin/lin64/xlGenerateButton.p>xlGenerateButton at 302 In gen_xps_files at 323 In casper_xps>run_Callback at 158 In casper_xps at 88 In @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) Warning: Output port 1 of 'adc_to_dac_test/dac_mkid1/adc_to_dac_test_dac_mkid1_dac_data_q0' is not connected. > In > /opt/Xilinx/14.6/ISE_DS/ISE/sysgen/bin/lin64/xlCompileGenerateMdl.p>xlCompileGenerateMdl > at 203 In /opt/Xilinx/14.6/ISE_DS/ISE/sysgen/bin/lin64/xlGenerateButton.p>xlGenerateButton at 302 In gen_xps_files at 323 In casper_xps>run_Callback at 158 In casper_xps at 88 In @(hObject,eventdata)casper_xps('run_Callback',hObject,eventdata,guidata(hObject)) Can anyone shed some light on this? The model will compile successfully but I think these warnings are preventing the actual design from working on the ROACH. Thank you, -Richard T.
