On 7/20/22 03:36, Marc wrote:
So quite a number of people have worked on the katcp protocol specification
over the last decade or so, and everybody has of course had a slightly different
view on it, so what it "meant" to do is fuzzy.
But I always intended it to be plain text where possible
Dear Kiran, others,
The specific problem of tcpborphserver not working on the latest RPis is
solved in the katcp_devel fork on HERA_Team (and the rpi-devel-casperfpga
branch of katcp_devel on casper-astro), if you need it. It’s a matter of
the GPIO address on the Pi having changed.
Aaron
On
Hello
On Tue, Jul 19, 2022 at 10:01 PM Kiran Shila wrote:
> > but there are use cases where multiple GBytes of data are moved through
> > katcp
> This is a crazy to me as clearly the protocol is not meant for this
> purpose.
So quite a number of people have worked on the katcp protocol
It seems like the easiest way to make everybody satisfied is to fix the
above issue, which is a) objectively broken, not "just" non compliant;
b) absolutely cannot possibly be that hard to fix. (Take the snap/pi
version of tcpborphserver, find the "actual" fpga read/write call within
the
Hello
Right - so even more conext will be helpful: tcpborphserver was written for the
ROACH1 board - which is about a decade old. It memory maps the
FPGA into the processor's address space - so accesses were
actually rather quick. tcpboprhserver has since been ported to
number of other platforms
On Tue, 19 Jul 2022, 19:01 Kiran Shila, wrote:
> > ?wordread/?wordwrite was written with maximal human readability in
> > mind. Somebody who has a misbehaving roach deployed somewhere can just
> > telnet/netcat/socat/etc to port 7147 and issue a wordread
> > to see if enough bits are toggling,
?wordread/?wordwrite was written with maximal human readability in
mind. Somebody who has a misbehaving roach deployed somewhere can just
telnet/netcat/socat/etc to port 7147 and issue a wordread
to see if enough bits are toggling, or if some counter is ticking
over, set a debug flag, etc.
I
Hello
Maybe it is helpful to give the reason for having two different
read/write mechanisms in tcpborphserver:
?wordread/?wordwrite was written with maximal human readability in
mind. Somebody who has a misbehaving roach deployed somewhere can just
telnet/netcat/socat/etc to port 7147 and issue
On 7/15/22 08:16, Marc wrote:
So re-reading my first reply it becomes clear that this was much too
terse - sorry.
Here then the longer explanation:
At the lowest level katcp is a line-based protocol consisting out of lines
starting with either '#', '?', '!', followed by one or more words,
So re-reading my first reply it becomes clear that this was much too
terse - sorry.
Here then the longer explanation:
At the lowest level katcp is a line-based protocol consisting out of lines
starting with either '#', '?', '!', followed by one or more words, each
word separated from the
Hello
On Fri, Jul 15, 2022 at 1:51 PM Kiran Shila wrote:
> Actually, the more I think about this - I'm really unsure how this even
> works. What happens if the binary payload contains 0x20 or 0x10 (space
> or newline)? Wouldn't that just break the parser? Is there something
> somewhere that
On 7/1/22 12:13, Kiran Shila wrote:
Hey everyone,
I've been recently working on getting a SNAP up and running and have
been digging into the guts into how all these parts fit together. As I
try to avoid python like the plague, I thought it would useful to start
to write some of the
12 matches
Mail list logo
