Hi Tilak, I’m glad this is resolved. Thank you for reporting back on the solution.
Best, Mitch > On Mar 30, 2026, at 9:26 AM, Tilak Katoch <[email protected]> wrote: > > Hi Mitch, > > The casper image issue of ZCU208 board of status return and tcp server got > resolved. As the soft link of the updated 'tcpborhserver3' was not linked > with the system bin folder. > > After creating a symbolic link, it is now working fine. > > Thanks and regards > Tilak > > > On Fri, 27 Mar 2026 at 18:10, Tilak Katoch <[email protected] > <mailto:[email protected]>> wrote: >> Hi Mitch, >> >> Sorry for the late reply. As you suggested last time. To check the following >> command, >> ========== >> Start a telnet or netcat session with the platform, replacing the IP shown >> below with your board’s IP address. >> >> `nc 192.168.2.100 7147` >> >> =========== >> >> I tried with the ZCU208 board and the following is the output with error >> invalid and unknown command. >> >> <Screenshot from 2026-03-27 18-04-38.png> >> >> Same I tried with the RFSoC 4x2 board and the following is the successful >> output. >> >> <Screenshot from 2026-03-27 18-05-13.png> >> >> Hope this helps you to figure out the issue with the ZCU208 board >> installation. >> >> Let me know if anything else is needed. >> >> Regards, >> Tilak >> >> >> On Mon, 23 Mar 2026 at 21:41, Mitchell Burnett <[email protected] >> <mailto:[email protected]>> wrote: >>> No, I’m still unsure of what the issue is and cannot replicate it. >>> >>> Start a telnet or netcat session with the platform, replacing the IP shown >>> below with your board’s IP address. >>> >>> `nc 192.168.2.100 7147` >>> >>> The response from the server will look something like this: >>> #version-connect katcp-library v0.2.0-295-g5b314db-dirty 2024-01-11T03:34:31 >>> #version-connect katcp-protocol 5.0-M #version-connect kernel >>> 5.4.0-xilinx-v2020.2 #1\_SMP\_Mon\_Aug\_15\_19:08:58\_UTC\_2022 >>> >>> Check the version by sending the command: `?rfdc-driver-ver`. The expected >>> output would look like this: >>> >>> #version-connect katcp-library v0.2.0-295-g5b314db-dirty 2024-01-11T03:34:31 >>> #version-connect katcp-protocol 5.0-M >>> #version-connect kernel 5.4.0-xilinx-v2020.2 >>> #1\_SMP\_Mon\_Aug\_15\_19:08:58\_UTC\_2022 >>> ?rfdc-driver-ver >>> #rfdc-driver-ver version:\_8.100000 >>> !rfdc-driver-ver ok >>> >>> Mitch >>> >>> > On Mar 23, 2026, at 7:13 AM, Tilak Katoch <[email protected] >>> > <mailto:[email protected]>> wrote: >>> > >>> > Hi Mitch, >>> >> >>> >> >>> >> >>> >> >>> >> On Wed, 18 Mar 2026 at 21:59, Mitchell Burnett >>> >> <[email protected] <mailto:[email protected]>> wrote: >>> >> Hi Tilak, >>> >> >>> >> Could you please try downloading and installing the >>> >> `tcpborphserver3_v8.1` file again from the instructions in the readme >>> >> for the zcu208update? >>> > I downloaded and installed the `tcpborphserver3_v8.1` file and followed >>> > the instructions in the readme for the zcu208update as you said. >>> >> >>> >> >>> >> This is strange. I wonder if the file was not installed correctly, or >>> >> the actively running process was not killed before restarting? If the >>> >> same result happens we will need to do some more targeted debugging. >>> > >>> > The file was installed correctly and the actively running process was >>> > killed as per the instruction mentioned in the readme. >>> > But the result was same as mentioned earlier and given below >>> > again<Screenshot from 2026-03-23 18-40-22.png> >>> > >>> > >>> > I am hopeful that this has clarified things for you. >>> > >>> > Let me know if anything else is needed. >>> > >>> > Regards, >>> > Tilak >>> > >>> >> >>> >> Like the updated `tcpborphserver3` executable, `prg_8a34001` also needs >>> >> to be copied from that update package and installed into the `bin/` >>> >> directory. As for `prg_clk104_rfpll` and `reset_rfpll`, the recommended >>> >> way to program the clk104 board, and to reset its PLLs, is by using >>> >> casperfpga’s progpll method for RFSoCs. There are examples of using this >>> >> method in the RFDC tutorial under “Testing the Design". If these >>> >> standalone binary utilities are needed it’s something we can look at >>> >> getting available. >>> >> >>> >> Best, >>> >> Mitch >>> >> >>> >>> On Mar 18, 2026, at 12:11 AM, Tilak Katoch <[email protected] >>> >>> <mailto:[email protected]>> wrote: >>> >>> >>> >>> Hi Mitch, >>> >>> >>> >>> Following the instructions as mentioned in the link >>> >>> https://github.com/casper-astro/tutorials_devel/issues/78, I was trying >>> >>> to install the casper image for the ZCU208. After following it and >>> >>> updating the image as per the zcu208update. I am still not able to get >>> >>> the status return value. As shown below in the issue. >>> >>> ============================================= >>> >>> >>> >>> In [1]: import casperfpga >>> >>> >>> >>> In [2]: fpga = casperfpga.CasperFpga('192.168.1.120') >>> >>> >>> >>> In [3]: fpga.upload_to_ram_and_program('zcu208_tut_rfdc.fpg') >>> >>> Out[3]: True >>> >>> >>> >>> In [4]: zcu = fpga.adcs['rfdc'] >>> >>> >>> >>> In [5]: zcu.init() >>> >>> Out[5]: True >>> >>> >>> >>> In [6]: zcu.status() >>> >>> >>> >>> --------------------------------------------------------------------------- >>> >>> ValueError Traceback (most recent call >>> >>> last) >>> >>> Cell In[6], line 1 >>> >>> ----> 1 zcu.status() >>> >>> >>> >>> File ~/newenv/lib/python3.8/site-packages/casperfpga/rfdc.py:480, in >>> >>> RFDC.status(self) >>> >>> 478 d = {} >>> >>> 479 for s in stat: >>> >>> --> 480 k, v = s.split(' ') >>> >>> 481 d[k] = int(v) >>> >>> 482 status[tile] = d >>> >>> >>> >>> ValueError: not enough values to unpack (expected 2, got 1) >>> >>> >>> >>> ================================================ >>> >>> >>> >>> On checking the bin folder of the casper installed, where the updated >>> >>> "tcpborphserver" is linked. I did not find the following executed files >>> >>> "prg_8a34001", "prg_clk104_rfpll", " reset_rfpll", etc. as the bin >>> >>> was completely empty. >>> >>> >>> >>> Can you suggest what would be the cause of the above error and missing >>> >>> files in the bin. >>> >>> >>> >>> Regards >>> >>> Tilak >>> >>> >>> >>> >>> >>> -- >>> >>> You received this message because you are subscribed to the Google >>> >>> Groups "[email protected] <mailto:[email protected]>" >>> >>> group. >>> >>> To unsubscribe from this group and stop receiving emails from it, send >>> >>> an email to [email protected] >>> >>> <mailto:casper%[email protected]>. >>> >>> To view this discussion visit >>> >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPGD9MnEBWkqbsoPeLVjteYLezNMxkPNfwhY%3DSHq482UmiOZ8g%40mail.gmail.com. >>> >> >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> >> Groups "[email protected] <mailto:[email protected]>" >>> >> group. >>> >> To unsubscribe from this group and stop receiving emails from it, send >>> >> an email to [email protected] >>> >> <mailto:casper%[email protected]>. >>> >> To view this discussion visit >>> >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/F592208C-1C3D-4711-8FD6-CD80D5BD3BD5%40gmail.com. >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> >> Groups "[email protected] <mailto:[email protected]>" >>> >> group. >>> >> To unsubscribe from this group and stop receiving emails from it, send >>> >> an email to [email protected] >>> >> <mailto:casper%[email protected]>. >>> >> To view this discussion visit >>> >> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPGD9MnfDdQJ9ksVmfYkypfmMzM%3D%2BeU2RmeWq4tm7RGwkrMy8g%40mail.gmail.com. >>> > >>> > >>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "[email protected] <mailto:[email protected]>" group. >>> > To unsubscribe from this group and stop receiving emails from it, send an >>> > email to [email protected] >>> > <mailto:casper%[email protected]>. >>> > To view this discussion visit >>> > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/497607F9-67C1-4875-AD24-8555913EF903%40gmail.com. >>> > >>> > -- >>> > You received this message because you are subscribed to the Google Groups >>> > "[email protected] <mailto:[email protected]>" group. >>> > To unsubscribe from this group and stop receiving emails from it, send an >>> > email to [email protected] >>> > <mailto:casper%[email protected]>. >>> > To view this discussion visit >>> > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPGD9MnRFfR%2B%3DvRSQWEGj%3DT9iULbvbWX-_TMHb13gWLbMJGGJg%40mail.gmail.com. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "[email protected] <mailto:[email protected]>" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] >>> <mailto:casper%[email protected]>. >>> To view this discussion visit >>> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/C27FC280-00F1-45B4-97DE-0F9003CC955B%40gmail.com. > > > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion visit > https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPGD9Mk7JzQ1t0BhxNwzt_R%2Ba_h6b_9J_c7T%2B78_1Exw1fMXug%40mail.gmail.com > > <https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/CAPGD9Mk7JzQ1t0BhxNwzt_R%2Ba_h6b_9J_c7T%2B78_1Exw1fMXug%40mail.gmail.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/E86185E4-BAC5-484D-9D76-B0DCA1D73F10%40gmail.com.
