Hi Nitika,
Are you determining from this message alone that it is not started?
Have you manually checked if `tcpborphserver3` is running with something like
`ps aux | grep tcpborphserver` When logged into the RP? Or you have verified
you cannot connect to the RP with a client like `casperfpga`? Because from
this message alone, it may not be enough to determine that the server is not
running. For example, comparing your output with output from an RFSoC running
tcpborphserver3 (sorry, I don’t have a RP turned on)
```
casper@alpaca-3:~$ sudo systemctl start tcpborphserver
casper@alpaca-3:~$ sudo systemctl status tcpborphserver
● tcpborphserver.service - TCPBorphServer allows programming and communication
with the FPGA
Loaded: loaded (/etc/systemd/system/tcpborphserver.service; enabled;
vendor preset: enabled)
Active: inactive (dead) since Sun 2021-06-06 05:10:24 MDT; 7s ago
Process: 28809 ExecStart=/bin/tcpborphserver3 -b /lib/firmware
(code=exited, status=0/SUCCESS)
Main PID: 28809 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4414)
Memory: 604.0K
CGroup: /system.slice/tcpborphserver.service
└─28802 /bin/tcpborphserver3 -b /lib/firmware
Jun 06 05:10:24 alpaca-3 systemd[1]: Started TCPBorphServer allows programming
and communication with the FPGA.
Jun 06 05:10:24 alpaca-3 tcpborphserver3[28809]: /bin/tcpborphserver3: about to
go into background
Jun 06 05:10:24 alpaca-3 systemd[1]: tcpborphserver.service: Succeeded.
```
The only real difference here is the is the final `systemd` output messsage.
That could possibly be explained because a newer version of Ubuntu is used for
RFSoC. But if I run
```
casper@alpaca-3:~$ ps aux | grep borph
root 28802 0.0 0.0 3704 1708 ? Ss 05:10 0:00
/bin/tcpborphserver3 -b /lib/firmware
casper 28871 0.0 0.0 5964 748 pts/1 S+ 05:21 0:00 grep
--color=auto borph
```
The tbs server is running if using something like `netcat` from another machine
a client connection to tcpborphserver is successful.
```
[mcb@chewpaca ~]$ nc alpaca-3 7147
#version-connect katcp-library v0.2.0-292-ga1ff49f-dirty 2022-03-15T19:37:48
#version-connect katcp-protocol 5.0-M
#version-connect kernel 5.4.0-xilinx-v2020.2
#1\_SMP\_Thu\_Jul\_15\_16:49:16\_UTC\_2021
```
If you do use netcat to test the connection the above output will be different
because the kernel and katcp versions are different, but if you get this output
the server should be working properly.
You could also just go ahead and try `casperfpga` right away if you already
have set that up.
Hope this helps,
Mitch
> On Mar 30, 2022, at 5:18 PM, Yadlapalli, Nitika <[email protected]> wrote:
>
> Hi all!
>
> I've been setting up a new 10 bit red pitaya according to these instructions:
> https://casper-toolflow.readthedocs.io/projects/tutorials/en/latest/tutorials/redpitaya/red_pitaya_setup.html
>
> I'm not able to activate the tcpborphserver3. The command "systemctl status
> tcpborphserver" always shows this issue:
>
> ● tcpborphserver.service - TCPBorphServer allows programming and
> communication with the FPGA
> Loaded: loaded (/etc/systemd/system/tcpborphserver.service; enabled;
> vendor preset: enabled)
> Active: inactive (dead) since Sat 2017-09-02 13:53:08 UTC; 2s ago
> Process: 3003 ExecStart=/bin/tcpborphserver3 (code=exited, status=0/SUCCESS)
> Main PID: 3003 (code=exited, status=0/SUCCESS)
> CGroup: /system.slice/tcpborphserver.service
> └─2762 /bin/tcpborphserver3
>
> Sep 02 13:53:08 rp-f07179 systemd[1]: Started TCPBorphServer allows
> programming and communication with the FPGA.
> Sep 02 13:53:08 rp-f07179 tcpborphserver3[3003]: /bin/tcpborphserver3: about
> to go into background
>
> Does anyone have any insight into this? I've set the board up to have a
> static IP address, hopefully that isn't causing an issue.
>
> Best,
> Nitika
>
> Nitika Yadlapalli (she/hers)
> PhD Candidate | Astronomy
> California Institute of Technology
>
> --
> 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 on the web visit
> https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/BYAPR03MB3752D923F2642E45E590AF12DA1F9%40BYAPR03MB3752.namprd03.prod.outlook.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].
To view this discussion on the web visit
https://groups.google.com/a/lists.berkeley.edu/d/msgid/casper/27F56572-D8FA-43C3-B030-BE82FDFE09A9%40byu.edu.
