Hi Cedric, I also tried to load my .bof or .pfg through casperfpga but I
have not been successful, the way I have been working is by running, if you
have not done so you can try:
import corr
fpga = corr.katcp_wrapper.FpgaClient('ip_roach', 7147)
fpga.upload_program_bof('path_your_design.bof',7174)
although this is only loaded in volatile memory
Regards.
Javier Ulloa
El vie., 6 sept. 2019 a las 4:06, 'Cedric Viou' via
casper@lists.berkeley.edu (<casper@lists.berkeley.edu>) escribió:
> Dear CASPERites,
>
> Thanks again for the very useful CASPER2019 workshop.
> I'm trying to build upon what I've learned there.
>
> I have a ROACH2 board that I want to program and control with casperfpga.
>
> Control is fine when I previously programmed the board through telnet.
>
> But I get this kind of error when attempting to program it (bof or fpg):
> > In [4]: fpga = casperfpga.CasperFpga(roach2)
> > In [5]: fpga.is_connected()
> > Out[5]: True
> > In [6]: fpga.upload_to_ram_and_program(bitstream)
> >
> /home/cedric/anaconda3/envs/2point7/lib/python2.7/site-packages/casperfpga-0.1.2-py2.7-linux-x86_64.egg/casperfpga/casperfpga.pyc
> in upload_to_ram_and_program(self, filename, wait_complete, chunk_size,
> initialise_objects)
> > 312 else:
> > 313 rv = self.transport.upload_to_ram_and_program(
> > --> 314 filename=filename, wait_complete=wait_complete)
> > 315
> > 316 if not wait_complete:
> >
> >
> /home/cedric/anaconda3/envs/2point7/lib/python2.7/site-packages/casperfpga-0.1.2-py2.7-linux-x86_64.egg/casperfpga/transport_katcp.pyc
> in upload_to_ram_and_program(self, filename, port, timeout, wait_complete,
> skip_verification)
> > 569 if request_result != '':
> > 570 raise RuntimeError('progremote request(%s) on host
> %s failed' %
> > --> 571 (request_result, self.host))
> > 572 # start the upload thread and join
> > 573 upload_queue = Queue.Queue()
> >
> > RuntimeError: progremote request(Request to client 192.168.40.96
> failed.) on host 192.168.40.96 failed
>
>
> I believed that my tcpborphserver could be too old (how to get the
> version, btw?) for casperfpga (branch tutorial2019 at the time I installed
> it), even if the Traceback is not exactly what is shown on
> https://www.mail-archive.com/casper@lists.berkeley.edu/msg07451.html.
>
> To check that hypothesis and try a newer tcpborphserver3, I started to
> setup TFTP+DHCP+NFS using "ROACH-2 Production Test Machine Setup"
> documentation and files from
> https://github.com/casper-astro/roach2_nfs_uboot. I merged dnsmask.conf
> from those 2 sources and modified /etc/exports for my needs. You can get a
> glimpse at my configuration here:
> https://github.com/CedricDViou/NRT_2G_channelizer/blob/master/README.md
>
>
> When netbooting, I got TFTP and DHCP to behave properly, but I get stuck
> when mounting the file system from nfs (with or without nolock option):
> > IP-Config: Got DHCP answer from 192.168.40.1, my address is 192.168.40.96
> > IP-Config: Complete:
> > device=eth0, addr=192.168.40.96, mask=255.255.255.0, gw=192.168.40.1
> > host=roach2, domain=acme.pvt, nis-domain=(none)
> > bootserver=192.168.40.1, rootserver=192.168.40.1,
> rootpath=/home/nfs/roach2/current,nolock
> > nameserver0=192.168.40.1VFS: Mounted root (nfs filesystem) readonly
> on device 0:11.
> > Freeing unused kernel memory: 144k freed
> > nfs: server 192.168.40.1 not responding, still trying
> > nfs: server 192.168.40.1 not responding, still trying
>
>
> However, my server actually sees the request and grants it:
> > Sep 4 12:22:17 nanunib rpc.mountd[25828]: authenticated mount request
> from roach2:713 for /home/nfs/roach2/squeeze_root.ppc (/home/nfs)
>
>
> And when I try mounting the filesystem myself after a soloboot (just to
> test my nfs server), I need to add the nolock option to have some success:
> > / # mount 192.168.40.1:/home/nfs/roach2 /mnt
> > svc: failed to register lockdv1 RPC service (errno 111).
> > lockd_up: makesock failed, error=-111
> > mount: mounting 192.168.40.1:/home/nfs/roach2 on /mnt failed:
> Connection refused
> >
> > / # mount -t nfs -o nolock 192.168.40.1:/home/nfs/roach2 /mnt
> > / # ls mnt
> > current squeeze_root.ppc
>
>
> Any ideas about this problem?
>
>
> When this works, I'll probably attempt upgrading the board (romfs at
> least, and u-boot?, kernel?, all of them?) with:
>
> https://casper.ssl.berkeley.edu/wiki/Getting_Started_with_ROACH2#ROACH2_kernel.2C_bootloader_and_romfs_upgrades
> ... if you think it's something I should do with my current configuration:
> > U-Boot 2011.06-rc2-00000-g2694c9d-dirty (Dec 04 2013 - 20:58:06)
> > Linux version 3.9.0-rc1+ (shanly@shanly-HP8710w) (gcc version 4.6.1
> 20110627 (prerelease) (GCC) ) #8 Wed Mar 6 12:54:28 SAST 2013
> > BusyBox v1.19.4 (2012-05-18 14:57:54 SAST)
>
>
> Sincerely Yours,
>
> Cedric
>
>
> --
> Cedric Viou <cedric.v...@obs-nancay.fr>
>
> Ingénieur de recherche
>
> Station de Radioastronomie de Nançay,
> Observatoire de Paris, PSL Research University, CNRS, Univ. Orléans, OSUC,
> 18330 Nançay, France
> http://www.obs-nancay.fr/
>
> phone : +33 (0) 248 51 8609
> fax : +33 (0) 248 51 8318
>
> www.openstreetmap.org/?mlat=47.381848&mlon=2.194415&zoom=18
>
>
>
> --
> 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/30747169-57ae-1c52-c4ff-92a9db484d33%40obs-nancay.fr
> .
>
--
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/CALo%3DeSJikMYR8Rf1zjK479WdL13hPVYFDNCnUOqHz%2B5SbJtcHA%40mail.gmail.com.
