Thanks Andrew for clarifying. Could you please update the Wiki page here: https://casper.berkeley.edu/wiki/MSSGE_Setup_with_Xilinx_14.5_and_Matlab_2012bwith this?
Also, a very minor point, could you please also modify 'casper_xps.m' to support "14.5" (switch statement)? Thanks, Nimish On Mon, Sep 23, 2013 at 6:47 PM, Andrew Martens <[email protected]> wrote: > Hi > > https://github.com/casper-astro/mlib_devel contains the official stable > CASPER libraries. > > There are other repos that contain more bleeding-edge versions of the > libraries but I would advise using the standard libraries if possible. > > Regards > Andrew > > Hello, > > It is my understanding that the latest mlib directory can be found at > https://github.com/ska-sa/mlib_devel. > > -- Louis P. Dartez > (956) 372-5812 > Arecibo Remote Command Center Scholar > Center for Advanced Radio Astronomy > University of Texas at Brownsville > > > On Mon, Sep 23, 2013 at 5:37 PM, Weiwei Sun <[email protected]> wrote: > >> Hi Nimish, >> >> I'm Laura's colleague. I'm new to the roach design. I have a question as >> to the library I should install. I'm trying to install the latest version >> of casper libraries which is based on xilinx version 11.5: >> https://casper.berkeley.edu/git/ >> >> It has not been updated since two years ago, which makes me worried a >> little bit. Can you help me confirm if it's the right one that I should >> install? It might be a silly question. I'm appreciated of your time and >> help. >> >> Best, >> >> Weiwei >> >> Folllowing are the past conversations on this topic: >> >> >> Message: 1 >> Date: Thu, 19 Sep 2013 14:00:47 -0400 >> From: Nimish Sane <[email protected]> >> Subject: Re: [casper] Report of experience with KatADC >> To: "Vertatschitsch, Laura E." <[email protected]> >> Cc: "Gary, Dale E." <[email protected]>, casper list >> <[email protected]> >> Message-ID: >> <CA+VQD= >> [email protected]> >> Content-Type: text/plain; charset="utf-8" >> >> Sounds reasonable. We persisted with 11.5 for ROACH2 so far, but we feel >> that it is high time we migrate to latest tools. So instead of 13.x, we >> are >> going for the latest 14.5. Others can comment if there are any red flags >> in >> using latest commit with 11.5. >> >> Thanks, >> >> Nimish >> >> >> On Thu, Sep 19, 2013 at 1:54 PM, Vertatschitsch, Laura E. < >> [email protected]> wrote: >> >> > Nimish, >> > >> > Thanks. My colleagues are planning on doing exactly what you mentioned: >> > programming ROACH2 KatADCs with the 11.5 tools we had used to previously >> > and successfully program ROACH1. >> > >> > The advice I would give them after hearing this discussion is as >> follows: >> > >> > [*] build the design with their current toolflow, make sure it compiles, >> > and then observe the internal KatADC snaps to see if the error Dale's >> error >> > is recreated. >> > >> > [*] If so, update the mlib_devel to the latest (simple, fast, may work). >> > >> > [*] If error persists, upgrade to Xilinx 14.x toolflow which should >> yield >> > success (extrapolated from the 13.x success presented in the initial >> email). >> > >> > Is that the correct summary? I can have them try and report back on >> this >> > issue as to where they exited this "if/then" statement. >> > >> > --Laura >> > >> > PS - my sincere apologies, Dale, for calling you Gary, earlier, I am >> just >> > jealous of nice, short last names that are human-readable >> > >> > >> > On Thu, Sep 19, 2013 at 1:35 PM, Nimish Sane <[email protected]> >> wrote: >> > >> >> Hi Laura, >> >> >> >> No. The one with 11.5 used an old commit >> >> 1c2035ed9e4f4bcc98e9f08f2722d3 >> 4dd4f10872 (Nov 12, 2012) from ska-sa. >> >> >> >> I believe Dave M used the latest one from casper-astro (waiting for his >> >> answer). >> >> >> >> So, as a caveat to what Dale has mentioned in his email, the problem >> >> could be between yellow blocks and not necessarily the toolflow, >> though I >> >> do not know if yellow block has changed significantly. >> >> >> >> Thanks, >> >> >> >> Nimish >> >> >> >> >> >> On Thu, Sep 19, 2013 at 1:03 PM, Vertatschitsch, Laura E. < >> >> [email protected]> wrote: >> >> >> >>> Gary, >> >>> >> >>> Can you confirm the same mlib_devel checkout was used for both >> compiles? >> >>> >> >>> --Laura >> >>> >> >>> >> >> > >
