Excellent! regards
marc On Mon, Aug 13, 2018 at 10:19 AM, Concu, Raimondo <raimondo.co...@inaf.it> wrote: > Hi Mark, > > I replaced tcpborphserver3 with tcpborphserver3-unmap. > > I have programmed the roach2 100 + 400 times ... without problems > > We had an old version of tcpborphserver3 > > Now we have a SARDARA reconfigurable many times ;-) and then permanently > offered to the astronomers at SRT ... > > Problem solved > > Thanks again! > > 2018-08-13 11:24 GMT+02:00 Concu, Raimondo <raimondo.co...@inaf.it>: >> >> I meant between versions, >> >> but I read that: "New tcpborphserver3: fixes unmap issue when programming >> boffiles" , >> >> could be our case. >> >> It is being tested ... >> >> 2018-08-13 10:59 GMT+02:00 Marc Welz <m...@ska.ac.za>: >>> >>> The one is a symbolic link to the other >>> >>> regards >>> >>> marc >>> >>> >>> On Mon, Aug 13, 2018 at 8:56 AM, Raimondo Concu <raimondo.co...@inaf.it> >>> wrote: >>> > Yes Mark! >>> > >>> > I had already seen this link. >>> > >>> > What is the difference between tcpborphserver3 and >>> > tcpborphserver3-unmap? >>> > >>> > Thank You! >>> > Raimondo >>> > >>> > Il Lun 13 Ago 2018, 10:00 Marc Welz <m...@ska.ac.za> ha scritto: >>> >> >>> >> On Fri, Aug 10, 2018 at 5:51 PM, John Ford <jmfor...@gmail.com> wrote: >>> >> > That depends where the image lives. If it is on an NFS mounted disk >>> >> > somewhere, you have to install the new kernel and file system there. >>> >> > If >>> >> > on >>> >> > the flash, you have to install it on the flash. >>> >> > >>> >> > THe latest stuff ought to be here (Marc is it so?) >>> >> >>> >> Hmm... those look like they are roach1 related. >>> >> >>> >> Rather have a look in >>> >> >>> >> https://github.com/ska-sa/roach2_nfs_uboot/ >>> >> >>> >> In particular the executable boot/tcpborphserver3 >>> >> >>> >> regards >>> >> >>> >> marc >>> >> >>> >> -- >>> >> 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 post to this group, send email to casper@lists.berkeley.edu. >>> > >>> > -- >>> > 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 post to this group, send email to casper@lists.berkeley.edu. >>> >>> -- >>> 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 post to this group, send email to casper@lists.berkeley.edu. >> >> > > -- > 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 post to this group, send email to casper@lists.berkeley.edu. -- 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 post to this group, send email to casper@lists.berkeley.edu.
