►
From YouTube: 20210629 FPGA Standup
Description
29 June 2021 FPGA Stand-up meeting from Open Research Institute.
A
Yes,
I
am,
it's
been
pretty
exciting.
Some
some
great
things
have
happened
and
we're
we're
here
in
huntsville
with
steve
and
we're
waiting
for
the
space
center
to
make
some
time
for
us
so
that
we
can
talk
about
that
big
dish.
C
A
Looking
forward
to
that,
anyway,
hey
thanks
for
showing
up
and
let's
let's
go
ahead
and
and
hear
about
what
you've
done
and
what
you're
planning
on.
And
if
you
have
any
roadblocks.
B
So
I
did
code
for
fpga
gsc
encoder
submitted,
sent
it
to
andre
subato
for
review
and
he
has
got.
He
has
given
some
really
good
comments
and
helped
me
so
I'm
addressing
those
commands
there
is
a.
There
is
a
some
change
in
approach,
how
I'm
streaming
the
packets.
So
I'm
doing
that
change,
and
hopefully
it
should
be
done,
maybe
today
or
tomorrow,
and
then
I
will
start
with
the
testing.
I
will
start
writing
the.
D
A
A
Wow,
no,
it
sounds
exciting,
so
yeah.
I
look
forward
to
hearing
about
the
about
the
stream.
The
streaming
change
that
that
could,
yes,
it's
pretty
cool.
A
I'm
looking
forward
to
hearing
more
about
that
yeah
cool,
okay,
I'll,
tell
you
what
I've
been
up
to
so
my
my
goal
is
to
get
the
hardware
get
things
running
on
hardware
as
quickly
as
possible,
and
so
this
is
means
remoting
into
the
san
diego
lab,
pc
and
that's
where
vms
are
running
on
this
pretty
powerful,
pc
and
and
then
the
boards
are
connected
to
that
particular
computer.
A
And
if
you
read
through
pound
fpga,
you
can
see
it's
it's
real
close,
but
we're
not
not
quite
there.
Yet
the
hardware
server
appears
to
be
up
and
running.
Some
of
it
seems
to
be
working
but
running
the
application
on
the
zinc
and
running
getting
the
bit
streams.
Loaded
hasn't
worked
yet
so
lots
of
things
are
working
and,
and
the
hardware
running
will.
D
A
On
the
I'm,
just
the
learning
how
to
do
better,
fpga
design
again
after
quite
a
while
of
not
doing
it,
I
can
make
prog
make
projects.
I
understand,
sort
of
the
modern
workflow.
A
I
can
make
things
on
the
programmable
logic
and
I
can
connect
them
to
the
the
processor
system
and
that
can
that
kind
of
a
big
step
forward.
Wow
the
ide
has
really
improved,
and
so
that's
that's
coming
along
really
well,
so
until
I
think
we'll
we'll
probably
stop
trying
to
fight
the
the
remote
for
now,
I'm
gonna
call
in
some
help
over
the
next
week
or
so
or
maybe,
when
I
get
back
on
the
7th
of
july,
but
I'm
I
think
what
I'll
focus
on
is
is
maybe
more
simulation.
A
So
so
getting
things
look
can
just
continue
to
learning
and
working
with
the
the
code
bases
that
we
have
and
and
write
some
stuff
to
to
kind
of
come
up
to
speed.
So
you
know,
another
roadblock
is
that
the
new
platform
project
in
vivato
isn't
working
for
me
for
some
reason,
that
seems
to
be
a
separate
problem
and
that's
shared.
B
A
Other
people
littered
across
the
land,
so
that's
probably
some
sort
of
local
local
problem
and
not
not
a
remote
related
problem.
So
that's
it
for
me.
D
If
I,
if
I
can,
I'm
sorry
I'm
just
a
bit
late,
but
with
the
various
versions
of
vivado
business
and
business
hls,
I
mean
it's
fluid,
even
within
the
salix
universe.
But
if,
if,
if
you're
having
issues
in
building
a
tool
chain
depends
upon
which
version
you
started
off
from
because
they
change
from
version
to
version.
What
they're
doing
underneath.
A
Yeah,
I
suspect
that
this
is
probably
a
a
virtual
machine
issue
with
connecting
the
hardware
and
not
a
tool
flow.
The
tool
seems
to
be
behaving
really
well
and
everything
expected
there.
I
I
think
that
the
root
cause
is
probably
the
unraid
server
running
a
vm,
and
even
though
we
mapped
the
usb
drive,
you
know
we
mapped
the
usb
connection
over
correctly
that
there's
something
subtle,
something
that
we've
missed.
A
So
I
think
we're
going
to
back
up
and
use
aperture
instead
of
chunk,
so
that
we're
removing
the
unread
server
and
removing
that
tricky,
trickier
and
more
sophisticated
virtual
machine
and
then
trying
to
remote
in
without
unraid,
and
if
that
works
as
expected,
then
we'll
have
a
lot
more,
we'll
have
a
clue,
so
we're
just
going
to
keep
marching
along
and
do
it.
The
tool
flow,
though
for
the
versions
of
auto
that
we're
using
seems
to
be
behaving
pretty
well.
A
So
I
I
wouldn't
put
that
first,
I
think
I'm
I'm
more
inclined
to
blame
the
virtual
machine
and
unraid
before
the
particular
version
of
nevada.
D
Is
there
is
there
a
readme
about
where
the
fundamentals
are
defined?
I
mean
you've
developed
this.
This
framework
chunk.
I
haven't
heard
it
before
or
unread.
I
haven't
perhaps
heard
before,
because
I
use
real
machines.
You
know
because
I,
like
real
machines,
like
you,
know,
an
ubuntu
machine.
You
know
that's
really
an
ubuntu
bf,
but
I'm
just
wondering
are
these
other
frameworks
necessary
for
your
work
or
they
just
happen
to
be
what
was
in
use.
A
Yeah,
this
is
all
related
to
the
remote
labs,
so
in
order
to
use
the
expensive
evaluation
boards
in
order
to
be
able
to
use
the
trends
gear
in
order
to
be
able
to
bring
up
the
boards
that
we
eventually
will
create,
since
that's
done
remotely,
all
of
this
stuff
has
to
be
sorted
out
and
the
sooner
the
better.
A
A
A
D
A
That's
what
we're
using
it's
linux,
the
unraid
is
just
a
way
to
to
run
virtual
machines.
So
it's
it's
running
ubuntu
on
the
on
the
lab,
pc,
okay,
okay,
yeah!
It's
a
if
you
want
to
learn
more!
It's
all
under
remote
labs
in
in
documents
that
phase
foreground
repo.
So.
D
Yeah
I
haven't
actually
visited
that
section.
I
was
just
focusing
on
just
trying
to
okay,
but
the
the
fpga
thread
that
I
was
just
happening
discussion
last
night.
I
realized
that
okay,
I'm
going
to
shift
to
the
unix
environment
and
just
you
know,
just
dump
everything
there,
because.
A
Yeah,
that's
that's
totally
good.
That's
that's
a
reasonable
way
to
do
it,
so
you
know,
and
you
can
get
the
same
repositories
in
the
same
code
base.
You
don't
have
to
use
remote
labs.
Just
when
you
come
to
the
point
where
you
want
to
run
it
on
hardware,
if
you
don't
have
the
you
know
the
expensive,
dev
boards
or
the
target
we
do
and
and
so
hopefully,
by
the
time
you
have
to
use
it,
it's
oh,
we
have
worked
out
all
of
this.
These
issues
sounds
like
you're
having
a
ripping
week.
D
The
roadblocks
are
our
first
capital
for
buying
all
these
I
mean
you're
sitting
about
a
okay.
We
got
a
picture.
We
picked
up
a
turbo,
vac
chamber,
18
inches
by
24
inches
in
diameter.
The
pump
will
be
down
to.
If
we
pay
for
the
service
of
the
pump,
then
it
would
be
down
to
10
10
10
millitards
10
millitars
0.010
torr.
D
D
It
appropriately,
for
you,
know,
first
round
of
testing.
We
don't
want
to
do
the
propulsion
testing
right
away
because
it
will
contaminate
the
chamber.
We
just
need
to
experience
with
it.
We
want
to
do
it
in
the
air
before
we
do
it
in
the
vacuum,
but
once
we
do
it,
then
the
chamber
will
be
coated.
We
have
to
decide
on
the
mitigation
system
for
coding.
D
A
D
D
A
A
That
sounds
like
a
ton
of
stuff
going
on.
Okay:
let's
talk
a
little
bit
more
then
I'll,
be
back
in
san
diego
on
the
7th
of
july,
and
I
have
a
little
bit
of
time
in
between
here
here
between
today
and
then
yeah
we'll
just
keep
asking
and
we'll
keep
looking
and
digging
and
seeing
seeing
what
we
can
accomplish
and
and
we'll
just
keep
at
it.
D
Fpga
work,
you
know,
I
was
really
trying
to
read
the
documentation
out
and
that's
where
I
found
that
file
name
issue.
I
I
now.
I
understand
that
it's
okay,
I
mean.