I ran into this same issue as well - on Ubuntu 20.04, Rocky 8, and with
hacked-together PKGBUILDs on my arch machine. I found a useful blog post
that also discusses the debugging procedure for haphazardly-vendored
tools such as Vivado:
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
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
?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
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,
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
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 functionality in Rust.
I followed the
7 matches
Mail list logo
