Re: [casper] RA Instruments using CASPER hardware and tools
Another LMT Instrument using CASPER hardware is WARES - Wideband Array ROACH enabled Spectrometer - a 32-pixel spectrometer system based on ROACH2s and ADC5Gs. Gopal On Wed, Aug 31, 2022 at 9:40 AM Sam Rowe wrote: > Ciao Morag, > > You can add MUSCAT and TolTEC (both at the LMT-50m) to the list of MKID > instruments that have been built using CASPER hardware and tools. > > Cheers, > > Sam > > > On Wed, 31 Aug 2022, 11:53 Morag Brown, wrote: > >> *External email to Cardiff University - *Take care when replying/opening >> attachments or links. >> *Nid ebost mewnol o Brifysgol Caerdydd yw hwn - *Cymerwch ofal wrth >> ateb/agor atodiadau neu ddolenni. >> >> Ciao dalla Sardegna, collaborati! >> >> I'm hoping to put together a more up-to-date list of instruments that >> have been built using CASPER hardware and tools. The most current list was >> compiled in 2016 for the "A Decade of Developing Radio-Astronomy >> Instrumentation using CASPER Open-Source Technology" paper by Jack et al, >> so it could probably use updating. >> >> The list is currently as follows: >> >> *Spectrometers and packetizers -* >> Fly’s Eye >> GUPPY >> CASPER >> BPSR >> GAVRT >> SERENDIP V.v >> HiTREKS >> NUPPI >> Skynet >> RATTY >> cycSpec >> C-BASS >> HIPSTER >> KuPol >> VEGAS >> ALMA Phasing Project >> Leuschner >> R2DBE >> DSN Transient Observatory >> VGOS >> AVN-Ghana >> COMAP >> >> *MKID readout systems -* >> Columbia MKID >> Mustang2 >> DARKNESS >> MEC >> BLAST-TNG >> HOLMES >> >> *Correlators and beamformers -* >> KAT7 >> PAPER >> ATA >> LEDA >> ARI >> MAD >> pocketcorr >> Medicina FFTT >> GMRT >> Meteor >> AMI >> MeerKAT AR-1 >> FLAG >> BIRALES >> Starburst >> AMiBA >> EOVSA >> SWARM >> MeerKAT >> HERA >> >> If you are not (or know of any instruments that are not) on this list, >> please reach out to me for it to be added? >> >> Grazie! >> Morag >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "casper@lists.berkeley.edu" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to casper+unsubscr...@lists.berkeley.edu. >> To view this discussion on the web visit >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%2BWym%2BZiiE_A%40mail.gmail.com >> <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fa%2Flists.berkeley.edu%2Fd%2Fmsgid%2Fcasper%2FCAGH-0TcON2s8K2JqXe0OAWWMeUeuKrnGSzhfRJS%252BWym%252BZiiE_A%2540mail.gmail.com%3Futm_medium%3Demail%26utm_source%3Dfooter=05%7C01%7Csam.rowe%40astro.cf.ac.uk%7C08d0ff8d28c1483b0f7d08da8b3f020f%7Cbdb74b3095684856bdbf06759778fcbc%7C1%7C0%7C637975399971406476%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=FRvK0DN7ZIp4q1KH1qcH7ioE1ox0My%2BbiTgl%2FWUUsDs%3D=0> >> . >> > -- > You received this message because you are subscribed to the Google Groups " > casper@lists.berkeley.edu" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to casper+unsubscr...@lists.berkeley.edu. > To view this discussion on the web visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAHsow4zE4DFvXNy1hE8hhf%3DpnBK7Cz16QV-%3DLdzx4t%3D%3D7tw4RQ%40mail.gmail.com > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAHsow4zE4DFvXNy1hE8hhf%3DpnBK7Cz16QV-%3DLdzx4t%3D%3D7tw4RQ%40mail.gmail.com?utm_medium=email_source=footer> > . > -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 Pronouns: he/him/his -- You received this message because you are subscribed to the Google Groups "casper@lists.berkeley.edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to casper+unsubscr...@lists.berkeley.edu. To view this discussion on the web visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CACboPVErFJ96iVP-ViGwoVZDOOxNUK7MYyBgE-Mku4%3D-kzWYaw%40mail.gmail.com.
Re: [casper] katcp python client.
Ramesh I find this line a bit suspicious in your routing table. Given that your gateway is in a different subnet, you might need to set the netmask to 255.255.0.0 instead of 255.255.240.0 134.104.16.00.0.0.0 255.255.240.0 U 0 00 eth0 Also, are you sure that you are running katcp client from the same machine that you are telneting to the roach? And have you set the port of FpgaClient class to 7147? Gopal On Mon, Jul 14, 2014 at 10:05 AM, Ramesh Karuppusamy ram...@mpifr-bonn.mpg.de wrote: Hi Danny, I did check this as the first thing - here is what I see. root@majestix:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 134.104.29.23 0.0.0.0 UG0 00 eth0 134.104.16.00.0.0.0 255.255.240.0 U 0 00 eth0 192.168.2.0 0.0.0.0 255.255.255.0 U 0 00 eth1 Cheers, Ramesh On 14 Jul 2014, at 15:54, Danny Price dpr...@cfa.harvard.edu wrote: Hi Ramesh Could this be a problem with routing tables? You can check with the route tool: http://manpages.ubuntu.com/manpages/precise/man8/route.8.html You should see eth1 as the only route for the 192.168.2.0 network Cheers Danny Ramesh Karuppusamy mailto:ram...@mpifr-bonn.mpg.de July 14, 2014 at 9:24 AM Hello list, I have a weird situation with our setup - can someone help me solve this issue? Our head node has two network interfaces - the first on the institute network and the interface eth1 is assigned 192.168.2.1. I assigned a static IP of 192.168.2.100 to our ROACH2 and eth1 above are connected to a simple D-Link unmanaged switch. From the head node, I can ping ROACH2 or ‘telnet 192.168.2100 7147’ to connect to tcpborphserver. But the katcp python client simply doesn't connect to ROACH2, as it tries to use the first interface on the head node. Is it possible to force katcp to use the eth1 (or ip 192.168.2.1) on the head node? Thanks! Cheers, Ramesh -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Problem using the ASIAA 5Gsps chip in design
Hi Dave I tried your suggestion to reset back to the commit at hand. I tried recompiling the simple ASIAA ADC design alone. I get further along this time, but I get the following error: XPS% Loading xmp file system.xmp ERROR:EDK - This project was created with EDK version 14.6, but the installed version of EDK tools is 14.5 ERROR:EDK - while running revup So my Xilinx tool set is indeed 14.5. I even tried to create a whole new project from scratch with a XSG config object, a System generator and the ASIAA ADC. But it still produces the same error. Perhaps this is a simpler fix? Looks like the EDK version is hard-coded somewhere in the mlib-devel area. Do you have suggestions on what to do here? Thanks! Gopal On Sat, May 10, 2014 at 2:15 PM, David MacMahon dav...@astro.berkeley.eduwrote: Hi, Gopal, It doesn't look like there are any relevant changes for you since (and including) the suspect commit, so you could just reset your local mlib_devel back to the commit just prior to commit e419ce2 with this command: $ git reset --hard e419ce2^ Note the '^' at the end, that's very important. Dave On May 10, 2014, at 8:43 AM, Gopal Narayanan wrote: Dave, Is there a simple fix to xps_library/detokenize.m in the SKA mlib_devel repository? Should I just use the detokenize.m script from the SMA git branch? Should the calculation not be based on app_clk_rate but rather on 100 MHz? Thanks! Gopal On Fri, May 9, 2014 at 4:53 PM, David MacMahon dav...@astro.berkeley.edu wrote: I think Gopal's problem with the ska-sa mlib_devel is due to commit e419ce2. This commit changed the calculation of the clock factors in xps_library/detokenize.m to be based on app_clk_rate (250 MHz in Gopal's case) rather than 100 MHz. These clock factors are passed to the roach_infrastructure HDL via parameters that get defined in system.mhs. Dave -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Problem using the ASIAA 5Gsps chip in design
Charles, Thanks. This patch worked fine. Gopal On Mon, May 12, 2014 at 1:23 PM, Charles Coldwell coldw...@gmail.comwrote: On Mon, May 12, 2014 at 11:52 AM, Gopal Narayanan go...@astro.umass.edu wrote: Hi Dave I tried your suggestion to reset back to the commit at hand. I tried recompiling the simple ASIAA ADC design alone. I get further along this time, but I get the following error: XPS% Loading xmp file system.xmp ERROR:EDK - This project was created with EDK version 14.6, but the installed version of EDK tools is 14.5 ERROR:EDK - while running revup I had to work around this problem for version 14.4 targeting ROACH2 $ git show 39a088449a2e0261cd84740014b313f704b55ded commit 39a088449a2e0261cd84740014b313f704b55ded Author: Charles M. Coldwell coldw...@gmail.com Date: Tue Apr 29 13:08:42 2014 -0400 Change the ISE version number to the one we have. diff --git a/xps_base/XPS_ROACH2_base/system.xmp.sx475t b/xps_base/XPS_ROACH2_base/system.xmp.sx475t index 88706c5..0c6922e 100644 --- a/xps_base/XPS_ROACH2_base/system.xmp.sx475t +++ b/xps_base/XPS_ROACH2_base/system.xmp.sx475t @@ -1,5 +1,5 @@ -XmpVersion: 14.6 -VerMgmt: 14.6 +XmpVersion: 14.4 +VerMgmt: 14.4 IntStyle:default MHS File:system.mhs MSS File:system.mss Since this file is copied verbatim when building your XPS project (no variable substitution or whatnot), I couldn't think of a better way to do it. -- Charles M. Coldwell, W1CMC Belmont, Massachusetts, New England Turn on, log in, tune out -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Problem using the ASIAA 5Gsps chip in design
Dave, Is there a simple fix to xps_library/detokenize.m in the SKA mlib_devel repository? Should I just use the detokenize.m script from the SMA git branch? Should the calculation not be based on app_clk_rate but rather on 100 MHz? Thanks! Gopal On Fri, May 9, 2014 at 4:53 PM, David MacMahon dav...@astro.berkeley.eduwrote: I think Gopal's problem with the ska-sa mlib_devel is due to commit e419ce2. This commit changed the calculation of the clock factors in xps_library/detokenize.m to be based on app_clk_rate (250 MHz in Gopal's case) rather than 100 MHz. These clock factors are passed to the roach_infrastructure HDL via parameters that get defined in system.mhs. Dave -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Problem using the ASIAA 5Gsps chip in design
Hi Rurik I have been mostly using the SKA mlib branch until now. When I saw the problem of compiling ROACH2 and ASIAA ADC, I tried to switch to SMA mlib to see if the problem was there as well (my assumption was that since you guys are using the ASIAA ADC actively, you must not have this issue). And indeed while it solved the MMCM clock issue, the fi dependence on Fixed-Point toolbox is a show-stopper there. So I might spend some time cherry-picking the fi dependency out of the SMA branch. I'll let you know the success of this effort. Thanks Gopal On Fri, May 9, 2014 at 3:47 PM, Primiani, Rurik rprimi...@cfa.harvard.eduwrote: Hi Gopal, Your XSG core config parameters look fine to me. I do not understand how the adc0_clk clock frequency should affect the sys_clk-generating MMCM in any way. Can you send me the full output log of your compile? Also, can you send me the XPS_ROACH2_base/system.mhs file from your design directory? As for the fixed point toolbox, I see that commits 1b13e3d, 617ba13, and b3d63ce remove the fi dependence from the FFT blocks. This was after the most recent time I merged with ska-sa and so the sma-wideband FFT still depends on the fixed-point toolbox. You can try cherry-picking those commits to remove the dependence for now. I have tried this but I have not tested it. Unfortunately merging the two forks at this point would require quite a bit of careful thought since there are many conflicts that would need to be worked out. I will give this a shot since this needed to be done eventually. Best, Rurik On Fri, May 9, 2014 at 2:37 PM, Gopal Narayanan go...@astro.umass.edu wrote: Rurik For the MMCM error, here are my XSG core config mask parameters: Hardware platform: ROACH2:sx475t User IP Clock Source: adc0_clk User IP Clock Rate: 250 MHz Sample Period: 1 Synthesis Tool: XST Yes, I normally use the ska-sa branch, and I have compiled the tutorial 3 spectrometer using other boards (KatADC or iADC) successfully without needing the Fixed point Toolbox. Thanks! Gopal On Fri, May 9, 2014 at 2:24 PM, Primiani, Rurik rprimi...@cfa.harvard.edu wrote: Hi Gopal, The MMCM error you pasted above has nothing to do with the ADC5g block. It is instead coming from the roach_infrastructure pcore which generates the sys_clk signal. What are your XSG core config mask parameters set to? I'm not sure how the sma_wideband repository differs from ska-sa in terms of the FFT and fixed point toolbox. The two forks have diverged quite a bit and should probably be merged. Perhaps one of the divergences is that the fixed point blocks have been replaced in ska-sa but I am unaware of such a change. Have you tried building your FFT module using the ska-sa fork (without the ADC5g if need be)? Thanks, Rurik On Fri, May 9, 2014 at 2:09 PM, Gopal Narayanan go...@astro.umass.edu wrote: Hi Casperites, I am trying to use the ASIAA ADC chip in a simulink design. To start with all I have in my design is the chip operating in two channel (AC mode), with 1:1 demux on ZDOK 0 with a clock rate of 2 GSps. I just terminated all outputs of the ADC just for this design. I am using a ROACH2 board in my design. I get the following error when compiling: ERROR:LIT:667 - Block 'MMCM_ADV symbol physical_group_infrastructure_inst/infrastructure_inst/sys_clk_fb_int/infrastructure_inst/infrastructure_inst/MMCM_BASE_sys_clk' has its target frequency, FVCO, out of range. Valid FVCO range for speed grade -1 is 600MHz - 1200MHz. The computed FCVO is a function of the input frequency CLKIN1_PERIOD, the division factor DIVCLK_DIVIDE, and the CLKFBOUT_MULT_F attribute (FVCO = 1000*CLKFBOUT_MULT_F/(CLKIN1_PERIOD*DIVCLK_DIVIDE)). The CLKIN_PERIOD attribute may have been set by ngdbuild based on the user specified PERIOD constraint. The current calculated FVCO is 400.00 MHz. Reference the V6 architecture Users Guide or search the Xilinx Answer Records database for the error code. Errors found during logical drc. I am using Matlab R2012b and XSG 14.5. This is when I am using the SKA mlib-devel branch. Here are the details of the mlib git branch: $ git rev-parse --short HEAD b2d72d4 $ git remote -v origin https://github.com/ska-sa/mlib_devel.git (fetch) origin https://github.com/ska-sa/mlib_devel.git (push) I tried to use the SMA mlib_devel branch instead. Here are the details on the SMA mlib branch I used: $ git rev-parse --short HEAD d4954fd $ git remote -v origin https://github.com/sma-wideband/mlib_devel.git (fetch) origin https://github.com/sma-wideband/mlib_devel.git (push) With the SMA mlib devel I am able to compile the simple ASIAA chip design mentioned above. However, for more complicated designs (I'm trying to put
[casper] Problem using the ASIAA 5Gsps chip in design
Hi Casperites, I am trying to use the ASIAA ADC chip in a simulink design. To start with all I have in my design is the chip operating in two channel (AC mode), with 1:1 demux on ZDOK 0 with a clock rate of 2 GSps. I just terminated all outputs of the ADC just for this design. I am using a ROACH2 board in my design. I get the following error when compiling: ERROR:LIT:667 - Block 'MMCM_ADV symbol physical_group_infrastructure_inst/infrastructure_inst/sys_clk_fb_int/infrastructure_inst/infrastructure_inst/MMCM_BASE_sys_clk' has its target frequency, FVCO, out of range. Valid FVCO range for speed grade -1 is 600MHz - 1200MHz. The computed FCVO is a function of the input frequency CLKIN1_PERIOD, the division factor DIVCLK_DIVIDE, and the CLKFBOUT_MULT_F attribute (FVCO = 1000*CLKFBOUT_MULT_F/(CLKIN1_PERIOD*DIVCLK_DIVIDE)). The CLKIN_PERIOD attribute may have been set by ngdbuild based on the user specified PERIOD constraint. The current calculated FVCO is 400.00 MHz. Reference the V6 architecture Users Guide or search the Xilinx Answer Records database for the error code. Errors found during logical drc. I am using Matlab R2012b and XSG 14.5. This is when I am using the SKA mlib-devel branch. Here are the details of the mlib git branch: $ git rev-parse --short HEAD b2d72d4 $ git remote -v origin https://github.com/ska-sa/mlib_devel.git (fetch) origin https://github.com/ska-sa/mlib_devel.git (push) I tried to use the SMA mlib_devel branch instead. Here are the details on the SMA mlib branch I used: $ git rev-parse --short HEAD d4954fd $ git remote -v origin https://github.com/sma-wideband/mlib_devel.git (fetch) origin https://github.com/sma-wideband/mlib_devel.git (push) With the SMA mlib devel I am able to compile the simple ASIAA chip design mentioned above. However, for more complicated designs (I'm trying to put together a spectrometer with the ASIAA chip) when using FFT modules, the SMA mlib branch seems to need the Matlab Fixed-Point toolbox, which I don't have a license for. I came across the following thread in the casper mailing lists about the Fixed Point toolbox: https://www.mail-archive.com/casper@lists.berkeley.edu/msg04488.html Anybody have some ideas on what may be causing the MMCM_ADV error seen above or to circumvent the need for a FP toolbox license? Thanks! Gopal -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Problem using the ASIAA 5Gsps chip in design
Rurik For the MMCM error, here are my XSG core config mask parameters: Hardware platform: ROACH2:sx475t User IP Clock Source: adc0_clk User IP Clock Rate: 250 MHz Sample Period: 1 Synthesis Tool: XST Yes, I normally use the ska-sa branch, and I have compiled the tutorial 3 spectrometer using other boards (KatADC or iADC) successfully without needing the Fixed point Toolbox. Thanks! Gopal On Fri, May 9, 2014 at 2:24 PM, Primiani, Rurik rprimi...@cfa.harvard.eduwrote: Hi Gopal, The MMCM error you pasted above has nothing to do with the ADC5g block. It is instead coming from the roach_infrastructure pcore which generates the sys_clk signal. What are your XSG core config mask parameters set to? I'm not sure how the sma_wideband repository differs from ska-sa in terms of the FFT and fixed point toolbox. The two forks have diverged quite a bit and should probably be merged. Perhaps one of the divergences is that the fixed point blocks have been replaced in ska-sa but I am unaware of such a change. Have you tried building your FFT module using the ska-sa fork (without the ADC5g if need be)? Thanks, Rurik On Fri, May 9, 2014 at 2:09 PM, Gopal Narayanan go...@astro.umass.edu wrote: Hi Casperites, I am trying to use the ASIAA ADC chip in a simulink design. To start with all I have in my design is the chip operating in two channel (AC mode), with 1:1 demux on ZDOK 0 with a clock rate of 2 GSps. I just terminated all outputs of the ADC just for this design. I am using a ROACH2 board in my design. I get the following error when compiling: ERROR:LIT:667 - Block 'MMCM_ADV symbol physical_group_infrastructure_inst/infrastructure_inst/sys_clk_fb_int/infrastructure_inst/infrastructure_inst/MMCM_BASE_sys_clk' has its target frequency, FVCO, out of range. Valid FVCO range for speed grade -1 is 600MHz - 1200MHz. The computed FCVO is a function of the input frequency CLKIN1_PERIOD, the division factor DIVCLK_DIVIDE, and the CLKFBOUT_MULT_F attribute (FVCO = 1000*CLKFBOUT_MULT_F/(CLKIN1_PERIOD*DIVCLK_DIVIDE)). The CLKIN_PERIOD attribute may have been set by ngdbuild based on the user specified PERIOD constraint. The current calculated FVCO is 400.00 MHz. Reference the V6 architecture Users Guide or search the Xilinx Answer Records database for the error code. Errors found during logical drc. I am using Matlab R2012b and XSG 14.5. This is when I am using the SKA mlib-devel branch. Here are the details of the mlib git branch: $ git rev-parse --short HEAD b2d72d4 $ git remote -v origin https://github.com/ska-sa/mlib_devel.git (fetch) origin https://github.com/ska-sa/mlib_devel.git (push) I tried to use the SMA mlib_devel branch instead. Here are the details on the SMA mlib branch I used: $ git rev-parse --short HEAD d4954fd $ git remote -v origin https://github.com/sma-wideband/mlib_devel.git (fetch) origin https://github.com/sma-wideband/mlib_devel.git (push) With the SMA mlib devel I am able to compile the simple ASIAA chip design mentioned above. However, for more complicated designs (I'm trying to put together a spectrometer with the ASIAA chip) when using FFT modules, the SMA mlib branch seems to need the Matlab Fixed-Point toolbox, which I don't have a license for. I came across the following thread in the casper mailing lists about the Fixed Point toolbox: https://www.mail-archive.com/casper@lists.berkeley.edu/msg04488.html Anybody have some ideas on what may be causing the MMCM_ADV error seen above or to circumvent the need for a FP toolbox license? Thanks! Gopal -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] KatADC vs ASIAA ADC
Hi Dan Thanks for your input. For 800 MHz BW, I am looking for 2048 spectral channels. If that is a tall order, we could settle for 1024. I am hoping to double the number of channels for halving the BW. For eg. BW NumChannels 8002048 4004096 2008192 I see why you are suggesting the ASIAA dual adc card for the 800 MHz mode. But I would prefer if we could use the same ADC for all modes. If I were to use the ASIAA ADC sampling at 1.6 GHz (FPGA clock ~ 200 MHz), and use all 8 parallel streams of the ADC for PFB and FFT then I satisfy that mode. For the 400 MHz mode, if I leave the sampling clock at 1.6 GHz, but terminate 4 outputs of the 8 parallel streams from the ADC, am I not effectively sampling at 800 MHz? Can a similar argument not be applied for 400 MHz sampling? What are the downsides to taking this approach? Am I missing something obvious? Cheers, Gopal On Thu, Mar 20, 2014 at 3:43 PM, Dan Werthimer d...@ssl.berkeley.eduwrote: hi gopal, how many spectral channels do you need? for 800 MHz bandwidth, you can use a pair of asiaa dual adc's at 2Gsps, and get four signal inputs per roach2, and clock the fgpa at 250 MHz. . for 400 MHz bandwidth, i suggest you use a pair of adc16 boards in quad input mode (sample at 960 Msps, four inputs per board), so you can get 8 signal inputs per roach2. fpga clock of 240 MHz. we might have a design for this you can use if you'd like. for 200 MHz bandwidth, i suggest you use a pair of adc16 boards in octal input mode (sample at 480 Msps, eight inputs per board), so you can get 16 signal inputs per roach2. fpga clock of 240 MHz. best wishes, dan On Thu, Mar 20, 2014 at 10:08 AM, Gopal Narayanan go...@astro.umass.eduwrote: Hello Casperites I'm looking for advice. We are at the point of launching into a wideband spectrometer project for building ROACH-2 based spectrometers to handle 32 independent front-end inputs. This is a conventional spectrometer (no cross-correlations needed). Our maximum bandwidth needed is 800 MHz. We are also interested in modes of bandwidth 200 and 400 MHz. I should note that legacy IF processors with band-limiting filters for the above BWs already exist, and we are building our spectrometer to these bandwidths. I am debating between the KatADC board and the wideband ASIAA 5GSPS ADC based boards. I ran some preliminary Simulink designs with the KatADC boards, and I run into timing issues when I use ADC sampling rate 1200 MHz. For 1.5 GSPS sampling, the FPGA clock gets up to 375 MHz with the KatADC, so perhaps this is the issue. I would like to squeeze 4 pixels into one ROACH-2 if possible. Has anyone run the KatADC close to its maximum sampling rate with the ROACH-2s? Are plan-ahead and other more advanced techniques needed for this? Alternatively, we could use the ASIAA ADC board, which has a divided-by-8 for the FPGA clock from the ADC sample rate. Keeping FPGA clock rates at nominal values might be easier with the ASIAA board, especially when we are only interested in relatively low sample clocks to 1.6 GHz. We are considering the 8-bit DMUX 1:1 version of the ASIAA board. Any pointers/advice/suggestions in choosing an appropriate ADC board is appreciated! Thanks Gopal -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
[casper] Patch for windows with cygwin
Hello,
I am not sure who to send this patch to since there are multiple
mlib_devel github repositories, so I thought a general email would be
better.
The latest version of CASPER tools fail in the last stages with a
cryptic error message. I have tracked it down to a problem in
gen_xps_files.m wherein if you have a windows system with Cygwin
installed, it assumes it is a unix-like OS, and then fails to run some
bat files.
Attached is a simple patch to gen_xps_files.m. Hope this helps someone.
Gopal
--
Gopal Narayanan Ph #: (413) 545 0925
Department of Astronomy e-mail: go...@astro.umass.edu
University of Massachusetts Amherst MA 01003
--- gen_xps_files.m.old 2012-08-22 13:34:45.0 -0400
+++ gen_xps_files.m 2012-08-22 13:33:57.0 -0400
@@ -91,9 +91,14 @@
disp(sprintf('Detected Linux OS'));
system_os = 'linux';
else
- slash = '/';
- disp(sprintf('Detected Unknown Unix-like OS'));
- system_os = 'linux';
+ if ~isempty(regexp(w, 'windows'))
+disp(sprintf('Detected Cygwin-like Windows OS'));
+system_os = 'windows';
+ else
+slash = '/';
+disp(sprintf('Detected Unknown Unix-like OS'));
+system_os = 'linux';
+ end
end
xps_blks= find_system(sys,'FollowLinks','on','LookUnderMasks','all','RegExp','on','Tag','^xps:');
Re: [casper] Patch for windows with cygwin
Glenn, Thanks for the pointer. So far, outside of this issue with gen_xps_files.m, I have not seen any problems with having cygwin installed on my windows machine. I run Xilinx ISE 13.4, perhaps some of the issues you mention are solved for this version? Gopal On 08/22/2012 02:18 PM, G Jones wrote: Hi, I strongly recommend not having cygwin installed on a windows system with the toolflow. Xilinx EDK includes its own version of cygwin and the two will conflict with inexplicable errors and failures. Glenn On Wed, Aug 22, 2012 at 1:44 PM, Gopal Narayanan go...@astro.umass.edu wrote: Hello, I am not sure who to send this patch to since there are multiple mlib_devel github repositories, so I thought a general email would be better. The latest version of CASPER tools fail in the last stages with a cryptic error message. I have tracked it down to a problem in gen_xps_files.m wherein if you have a windows system with Cygwin installed, it assumes it is a unix-like OS, and then fails to run some bat files. Attached is a simple patch to gen_xps_files.m. Hope this helps someone. Gopal -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Matlab crashes with tutorial 3
Hi Jack, Thanks to you and Danny Price for suggesting this. I copied over the pcores in the zip file mentioned in the CASPER wiki to my mlib_devel/xps_lib/XPS_ROACH_base/pcores directory, then I deleted the previous r_spec_2048_r106 build directory, and then ran the compile again. It fails with similar results. Here is the error message in the matlab window: Format revision of project to EDK 13.3 completed ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 ERROR:EDK - IPNAME: opb_v20, INSTANCE: opb0 - cannot find MPD for the pcore 'opb_v20_v1_10_c' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 99 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_odd - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 461 ERROR:EDK - IPNAME: opb_v20, INSTANCE: opb0 - cannot find MPD for the pcore - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 99 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_odd - cannot find MPD for the pcore - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 461 ERROR:EDK - while loading XMP file XPS% Evaluating file run_xps.tcl ERROR:EDK - Load a MHS or XMP file first Error using == gen_xps_files at 686 XPS failed. I am attaching the r_spec_2048_r106/XPS_ROACH_base/system.mhs file with this. Why is it not finding these pcores? There are some details described in http://www.xilinx.com/support/answers/34778.htm But I am not sure which of those is applicable to my case. Also, which directory should I copy the pcores from the http://dl.dropbox.com/u/2832602/pcores_for_ise13.zip zipfile: 1) mlib_devel/xps_lib/XPS_ROACH_base/pcores or 2) mlib_devel/xps-lib/pcores I did (1) Thanks! Gopal On 05/10/2012 10:27 AM, Jack Hickish wrote: Well, you wouldn't want things to be too easy now, would you? :) Your missing pcore problem occurs because you are compiling with ISE 13.3, which removed support for some of the cores that we still use. The design should compile fine with 11.x (which is what I tested it on), but you can fix the error relatively easily -- see https://casper.berkeley.edu/wiki/CASPER_With_ISE_13.1 Hopefully that will be the only hurdle, Jack On 10 May 2012 15:05, Gopal Narayanan go...@astro.umass.edu mailto:go...@astro.umass.edu wrote: Compilation of the MDL file for tutorial 3 in Jack's git repository failed. The last few lines in the Matlab window after the failure are: - Format revision of project to EDK 13.3 completed ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 WARNING:EDK - IPNAME: opb_v20, INSTANCE: opb0 - Superseded core for architecture 'virtex5sx' - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 99 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_odd - cannot find MPD for the pcore 'opb_bram_if_cntlr_v1_00_a' in any of the repositories - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 461 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_even - cannot find MPD for the pcore - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 373 ERROR:EDK - IPNAME: opb_bram_if_cntlr, INSTANCE: r_spec_2048_r106_odd - cannot find MPD for the pcore - /home/gopal/engineering/roach/myroach/r_spec_2048_r106/XPS_ROACH_base/system. mhs line 461
Re: [casper] Matlab crashes with tutorial 3
Hi Jack, Indeed, I can open tutorial 3 from your forked github location successfully without causing segfaults. I'll post if compilation of the simulink model fails. So where exactly is the problem? In mlib_devel or incompatible changes in Xilinx System Generator? Thanks! Gopal On 05/09/2012 03:58 PM, Jack Hickish wrote: Hi all, After a fair bit of tutorial related pain on the mailist recently, I've just forked the tutorial-devel repo to https://github.com/jack-h/tutorials_devel and recompiled tutorials 1-3 with Sysgen 11.5 and the libraries in the main casper github repo. The tutorials in the 2011 directory *should* work (along with their python counterparts). Feel free to give those a go and give me a shout if you still have problems. Cheers, Jack On 9 May 2012 20:49, John Ford jf...@nrao.edu mailto:jf...@nrao.edu wrote: Hi all. Rich Lacasse at NRAO in Charlottesville has the same problem. I also tried it on our machine in Green Bank, with the same bad results. That's three separate machines and users with the same problem. Something's wrong with this tutorial, or it is incompatible with the latest mlib_devel. Could someone have a look at it? Thanks! John Hey Gopal, One thing you can try is to start matlab without loading the yellow blocks, open the model file and add them in fresh from the library, save and return to normal usage. This will require you comment out the load xps_library portion of your matlab startup script. Start matlab, and open the desired model file. Doing this, you may be able to see the yellow blocks show up as bad links with red dashes around them. From there you can delete them, and manually add them back in from the xps library. You may need to consult the tutorial, or look at the original model .mdl file in a text editor, to make sure you set the parameters appropriately. From there you should be able to save the .mdl file, close matlab, go back to the startup file and uncomment back to the regular usage. Hopefully it opens up fine this time. If this solution works, perhaps I can write something more detailed to the wiki page for the Tutorials. Would that be an appropriate edit for the wiki? I think something stated on that page would help - we have seen several new roach users encounter this issue. Gopal, I was also strongly advised when I started out to use 11.5 and the stable release of the tools. This solution fixed the problem on that setup, hopefully it does on 13 as well. --Laura On Mon, May 7, 2012 at 12:44 PM, Gopal Narayanan go...@astro.umass.edu mailto:go...@astro.umass.eduwrote: Hello All, I am running Matlab R2011A on a 64-bit Debian Linux System. I also have tested this issue in two other machines, one running Ubuntu (64 bit as well), and the other running Windows XP-64 with similar results. The Xilinx System Generator version in all cases is 13.3.4175. I have successfully created, compiled and programmed our ROACH board with tutorials 1 and 2. I am able to download the tutorial model files from the CASPER website and open Tutorials 1 and 2, and compile/simulate them. However, when I download the r_spec_2048_103.mdl or the r_spec_2048_105.mdl (both are tutorial 3 files) from the CASPER git site, and open within simulink, immediately I get a segfault crash in matlab. I attach the crash dump for my ubuntu machine with this. I contacted Matlab technical support, but after looking at it, they blame Xilinx System Generator for this problem even indicating an url that apparently show memory leaks in sysgen: http://www.xilinx.com/support/answers/34287.htm I thought I would write to you all to find if anyone has had issues like mine. And if you have some helpful tips to fix the issue. Alternatively, if someone could send me an updated saved version of the tutorial 3 file saved with a more recent system generator version, I would appreciate it! Maybe I could try with this updated version. Thanks a bunch. Gopal -- Gopal Narayanan Ph #: (413) 545 0925 tel:%28413%29%20545%200925 Department of Astronomy e-mail: go...@astro.umass.edu mailto:go...@astro.umass.edu University of Massachusetts Amherst MA 01003 -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003
Re: [casper] Matlab crashes with tutorial 3
Hi Laura, Thank you for your suggestions. I made progress with your suggestions, but there are still some problems. I commented out the xps_library portion of my matlab startup script. Indeed, now I am able to open the tutorial 3 model file without a segfault. I see the yellow blocks show up as bad links. I can delete them. I looked at the original .mdl file in a text editor and saw what I need to add. I addpath the xps_library area to the matlab path. This next step took me a while to figure out (maybe it is obvious to others). Inside the simulink library browser I had to go to View-Refresh Tree View (or F5) to have simulink catch the newly added xps_library. I add appropriate yellow blocks. I can save this new model file. But when I edit back the xps_library into the startup script and restart sysgen, and open the newly saved tutorial 3 file, I segfault again! So I decide it is a pain in the neck, but I can go through adding the xps_library path by hand each time to be able to open this model. So I commented out the xps_library in startup, manually addpath and refresh tree view after opening model. The model is all there now. So I want to compile the model, and I run bee_xps, and press the Run XPS button, it fails with the following message: Detected Linux OS Warning: The fourth output, VERSN, of FILEPARTS will be removed in a future release. In fileparts at 35 In gen_xps_files at 121 In bee_xpsrun_Callback at 150 In bee_xps at 82 # ## System Update ## # config = source: @pipeline_init_xblock config = source: @pipeline_init_xblock config = source: @pipeline_init_xblock config = source: @pipeline_init_xblock config = source: @pipeline_init_xblock Error using == gen_xps_files at 199 Error due to multiple causes. Any ideas? Gopal On 05/07/2012 04:12 PM, Laura Vertatschitsch wrote: Hey Gopal, One thing you can try is to start matlab without loading the yellow blocks, open the model file and add them in fresh from the library, save and return to normal usage. This will require you comment out the load xps_library portion of your matlab startup script. Start matlab, and open the desired model file. Doing this, you may be able to see the yellow blocks show up as bad links with red dashes around them. From there you can delete them, and manually add them back in from the xps library. You may need to consult the tutorial, or look at the original model .mdl file in a text editor, to make sure you set the parameters appropriately. From there you should be able to save the .mdl file, close matlab, go back to the startup file and uncomment back to the regular usage. Hopefully it opens up fine this time. If this solution works, perhaps I can write something more detailed to the wiki page for the Tutorials. Would that be an appropriate edit for the wiki? I think something stated on that page would help - we have seen several new roach users encounter this issue. Gopal, I was also strongly advised when I started out to use 11.5 and the stable release of the tools. This solution fixed the problem on that setup, hopefully it does on 13 as well. --Laura On Mon, May 7, 2012 at 12:44 PM, Gopal Narayanan go...@astro.umass.edu mailto:go...@astro.umass.edu wrote: Hello All, I am running Matlab R2011A on a 64-bit Debian Linux System. I also have tested this issue in two other machines, one running Ubuntu (64 bit as well), and the other running Windows XP-64 with similar results. The Xilinx System Generator version in all cases is 13.3.4175. I have successfully created, compiled and programmed our ROACH board with tutorials 1 and 2. I am able to download the tutorial model files from the CASPER website and open Tutorials 1 and 2, and compile/simulate them. However, when I download the r_spec_2048_103.mdl or the r_spec_2048_105.mdl (both are tutorial 3 files) from the CASPER git site, and open within simulink, immediately I get a segfault crash in matlab. I attach the crash dump for my ubuntu machine with this. I contacted Matlab technical support, but after looking at it, they blame Xilinx System Generator for this problem even indicating an url that apparently show memory leaks in sysgen: http://www.xilinx.com/support/answers/34287.htm I thought I would write to you all to find if anyone has had issues like mine. And if you have some helpful tips to fix the issue. Alternatively, if someone could send me an updated saved version of the tutorial 3 file saved with a more recent system generator version, I would appreciate it! Maybe I could try with this updated version. Thanks a bunch. Gopal -- Gopal Narayanan Ph #: (413) 545 0925 tel:%28413%29%20545%200925 Department of Astronomy
[casper] Matlab crashes with tutorial 3
Hello All, I am running Matlab R2011A on a 64-bit Debian Linux System. I also have tested this issue in two other machines, one running Ubuntu (64 bit as well), and the other running Windows XP-64 with similar results. The Xilinx System Generator version in all cases is 13.3.4175. I have successfully created, compiled and programmed our ROACH board with tutorials 1 and 2. I am able to download the tutorial model files from the CASPER website and open Tutorials 1 and 2, and compile/simulate them. However, when I download the r_spec_2048_103.mdl or the r_spec_2048_105.mdl (both are tutorial 3 files) from the CASPER git site, and open within simulink, immediately I get a segfault crash in matlab. I attach the crash dump for my ubuntu machine with this. I contacted Matlab technical support, but after looking at it, they blame Xilinx System Generator for this problem even indicating an url that apparently show memory leaks in sysgen: http://www.xilinx.com/support/answers/34287.htm I thought I would write to you all to find if anyone has had issues like mine. And if you have some helpful tips to fix the issue. Alternatively, if someone could send me an updated saved version of the tutorial 3 file saved with a more recent system generator version, I would appreciate it! Maybe I could try with this updated version. Thanks a bunch. Gopal -- Gopal Narayanan Ph #: (413) 545 0925 Department of Astronomy e-mail: go...@astro.umass.edu University of Massachusetts Amherst MA 01003 Segmentation violation detected at Fri May 4 14:55:20 2012 Configuration: Crash Decoding : Disabled Current Visual : 0x21 (class 4, depth 24) Default Encoding: UTF-8 GNU C Library : 2.13 stable MATLAB License : 59778 MATLAB Root : /usr/local/MATLAB/R2011a MATLAB Version : 7.12.0.635 (R2011a) Operating System: Linux 3.0.0-19-generic #33-Ubuntu SMP Thu Apr 19 19:05:14 UTC 2012 x86_64 Processor ID: x86 Family 6 Model 7 Stepping 10, GenuineIntel Virtual Machine : Java 1.6.0_17-b04 with Sun Microsystems Inc. Java HotSpot(TM) 64-Bit Server VM mixed mode Window System : The X.Org Foundation (11004000), display :0 Fault Count: 1 Abnormal termination: Segmentation violation Register State (from fault): RAX = 7f77 RBX = RCX = 7f77ba312f50 RDX = 0014 RSP = 7f7808336e40 RBP = 7f7808336f50 RSI = 7f77ba314520 RDI = 7f77ba313d78 R8 = R9 = 7f78166abd10 R10 = 7f78166a7e90 R11 = 7f77ce46ea50 R12 = R13 = 7f77ba22a5a0 R14 = 7f77ba3137b0 R15 = 0014 RIP = 7f77e152152e EFL = 00010246 CS = 0033 FS = GS = Stack Trace (from fault): [ 0] 0x7f7818da6f49 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwfl.so+00474953 fl::sysdep::linux::unwind_stack(void const**, unsigned long, unsigned long, fl::diag::thread_context const)+09 [ 1] 0x7f7818d5cdc1 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwfl.so+00171457 fl::diag::stacktrace_base::capture(fl::diag::thread_context const, unsigned long)+000161 [ 2] 0x7f7818d660dd /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwfl.so+00209117 [ 3] 0x7f7818d66364 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwfl.so+00209764 fl::diag::terminate_log(char const*, fl::diag::thread_context const, bool)+000100 [ 4] 0x7f7817dd2be5 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00420837 fl::diag::terminate_log(char const*, ucontext const*, bool)+85 [ 5] 0x7f7817dcfb54 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00408404 [ 6] 0x7f7817dd103d /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00413757 [ 7] 0x7f7817dd1197 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00414103 [ 8] 0x7f7817dd1b1d /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00416541 [ 9] 0x7f7817dd2435 /usr/local/MATLAB/R2011a/bin/glnxa64/../../bin/glnxa64/libmwmcr.so+00418869 [ 10] 0x7f781692a060 /lib/x86_64-linux-gnu/libpthread.so.0+00065632 [ 11] 0x7f77e152152e /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+16213294 [ 12] 0x7f77e0d1d115 /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+07807253 [ 13] 0x7f77e0d1d797 /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+07808919 [ 14] 0x7f77e0e86597 /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+09287063 [ 15] 0x7f77e1521438 /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+16213048 [ 16] 0x7f77e0d1d115 /usr/local/MATLAB/R2011a/bin/glnxa64/libmwsimulink.so+07807253 [ 17] 0x7f77e0d1d797 /usr/local
