So the fpg file is in some ways just a set of commands issued to port 7147 of the roach, one of them includes uploading the bitstream. There are two things to try, either perform these steps manually or use another piece of software to perform the upload.
Manual upload involves isssuing an ?uploadbin 7777 on the 7147 port, and then (quickly, before it times out) on another terminal using netcat to stream in the bitstream $ nc -q 2 -w 2 IP.OF.ROA.CH 7777 < your.bitstream Note that what you are streaming in is *not* the fpg file, but the bitstream, usually in system.bin (IIRC?). Once you have done that and it succeeds, you can paste in the ?register sys_board_id 0x0 0x4 commands, followed by a ?finalise at which point the roach should be programmed, and wordreads should succeed. There is C utility which performs all these steps in one go, which is called kcpfpg. it is part of katcp_devel to be found at https://github.com/casper-astro/katcp_devel or https://github.com/ska-sa/katcp_devel, use $ make -k to build it once you have cloned it, then # make -C fpg install to install it. It understands the -h option and can upload .fpg files regards marc On Mon, Apr 29, 2019 at 8:47 AM 'Nikita Rathore' via casper@lists.berkeley.edu <casper@lists.berkeley.edu> wrote: > > Still I am getting the same issue even I kept the connection open to port > 7147. > > Trying 192.168.100.196... > Connected to 192.168.100.196. > Escape character is '^]'. > #version memcpy-88-g38ad77a-dirty > #build-state 2013-04-11T11:50:43 > #log info 114991 raw new\_client\_connection\_192.168.100.1:46250 > #client-connected 192.168.100.1:46250 > > In [1]: import casperfpga > > In [2]: fpga = casperfpga.CasperFpga('192.168.100.196') > WARNING:casperfpga.transport_katcp:192.168.100.196: no ._stream instance > found. > > In [3]: fpga.upload_to_ram_and_program('pocov64_2019_Apr_04_1337.fpg') > --------------------------------------------------------------------------- > RuntimeError Traceback (most recent call last) > <ipython-input-3-6c690f66cd1e> in <module>() > ----> 1 fpga.upload_to_ram_and_program('pocov64_2019_Apr_04_1337.fpg') > > /usr/local/lib/python2.7/dist-packages/casperfpga/casperfpga.pyc in > upload_to_ram_and_program(self, filename, port, timeout, wait_complete) > 200 """ > 201 rv = self.transport.upload_to_ram_and_program( > --> 202 filename, port, timeout, wait_complete) > 203 if filename[-3:] == 'fpg': > 204 self.get_system_information(filename) > > /usr/local/lib/python2.7/dist-packages/casperfpga/transport_katcp.pyc in > upload_to_ram_and_program(self, filename, port, timeout, wait_complete) > 462 if request_result != '': > 463 raise RuntimeError('progremote request(%s) on host %s > failed' % > --> 464 (request_result, self.host)) > 465 # start the upload thread and join > 466 upload_queue = Queue.Queue() > > RuntimeError: progremote request(Request to client 192.168.100.196 failed.) > on host 192.168.100.196 failed > > On Mon, Apr 29, 2019 at 1:11 PM Marc <m...@ska.ac.za> wrote: >> >> I suppose the next step would be to keep a telnet connection open to >> port 7147 and attempt the upload again - there should be an error >> message telling you why it failed. It might be a bit cryptic though. >> >> On earlier tcpborphserver revisions, the system didn't unmap the fpga, >> and so ran out of address space after a dozen or so uploads, if there >> was no reboot, but that has been fixed quite a while ago. >> >> regards >> >> marc >> >> On Mon, Apr 29, 2019 at 7:10 AM 'Nikita Rathore' via >> casper@lists.berkeley.edu <casper@lists.berkeley.edu> wrote: >> > >> > Following fpg file I am using. Yes I can ping the IP of the roach board, >> > and port 7147 also works fine. >> > >> > Regards >> > Nikita Rathore >> > >> > On Thu, Apr 25, 2019 at 4:25 PM Marc <m...@ska.ac.za> wrote: >> >> >> >> Is the fpg file empty, if not do a less on the file - the first couple >> >> of lines should be human readable register definitions, followed by >> >> the bitstream to check that it looks reasonble. Also see if you can >> >> ping the IP of the roach board, and see if telnet to its port 7147 >> >> works >> >> >> >> regards >> >> >> >> marc >> >> >> >> On Thu, Apr 25, 2019 at 9:27 AM 'Nikita Rathore' via >> >> casper@lists.berkeley.edu <casper@lists.berkeley.edu> wrote: >> >> > >> >> > I am using MATLAB R2012b, Xilinx 14.7 and Roach2 board. Yes, I have >> >> > .fpg file and I am trying to burn fpga with the generated .fpg file >> >> > using casperfpga but in that case I am getting following issue: >> >> > >> >> > import casperfpga >> >> > > >>> fpga=casperfpga.katcp_fpga.KatcpFpga('192.168.100.192') >> >> > > >>> fpga.upload_to_ram_and_program('pocov64_2017_Aug_17_1600.fpg') >> >> > > Traceback (most recent call last): >> >> > > File "<stdin>", line 1, in <module> >> >> > > File >> >> > > "/usr/local/lib/python2.7/site-packages/casperfpga/katcp_fpga.py", >> >> > > line 358, in upload_to_ram_and_program >> >> > > raise RuntimeError('progremote request(%s) on host %s failed' % >> >> > > (request_result, self.host)) >> >> > > RuntimeError: progremote request(Request to client 192.168.100.192 >> >> > > failed.) on >> >> > > host 192.168.100.192 failed >> >> > >> >> > I also tried mkbof command to generate bof file from bit file but in >> >> > that case I had following error: >> >> > mkbof: command not found >> >> > >> >> > I run it like this >> >> > XPS_ROACH2_base# mkbof -o system.bof –s core_info.tab -t 3 >> >> > pocov64_2017_Aug_17_1600.bit >> >> > >> >> > >> >> > >> >> > On Thu, Apr 25, 2019 at 1:09 PM Marc <m...@ska.ac.za> wrote: >> >> >> >> >> >> Not sure what hardware you are working on, but your system might have >> >> >> generated a newer .fpg file ? If this isn't the case, maybe the mkbof >> >> >> executable isn't built for your build machine architecture (x86 vs >> >> >> amd64) or c/linker revision ? See if you can run the mkbof executable >> >> >> manually ? >> >> >> >> >> >> regards >> >> >> >> >> >> marc >> >> >> >> >> >> On Thu, Apr 25, 2019 at 5:59 AM 'Nikita Rathore' via >> >> >> casper@lists.berkeley.edu <casper@lists.berkeley.edu> wrote: >> >> >> > >> >> >> > Hello, >> >> >> > >> >> >> > I started working on 2 element pocket correlator. Simulink design >> >> >> > compiled successfully but the bof file generated is completely blank >> >> >> > (0 bytes). >> >> >> > It would be grateful if someone could help me solve this issue. >> >> >> > >> >> >> > -- >> >> >> > Thanks & Regards >> >> >> > Nikita Rathore >> >> >> > >> >> >> > -- >> >> >> > 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. >> >> > >> >> > >> >> > >> >> > -- >> >> > Thanks & Regards >> >> > Nikita Rathore >> >> > >> >> > -- >> >> > 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. >> > >> > >> > >> > -- >> > Thanks & Regards >> > Nikita Rathore >> > >> > -- >> > 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. > > > > -- > Thanks & Regards > Nikita Rathore > > -- > 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.
