►
From YouTube: 20210921 FPGA Standup
Description
Welcome to the weekly ORI FPGA Standup meeting!
Visit https://openresearch.institute/getting-started to find out how to get involved.
A
What
we
do
is
we
talk
about
what
we've
done
over
the
past
week,
what
we
have
planned
for
the
next
week,
if
there's
any
resources
that
are
needed
and
any
roadblocks
that
we
have,
that
I
can
help
with
and
what
we'll
do
is
give
these
reports.
And
then,
if
someone
hasn't
spoken,
please
go
ahead
and
pick
them
as
the
next
person
so
that
we
can
can
move
down
the
list
and
let
everybody
have
a
chance
to
talk
so
I'll,
go
ahead
and
start
very
briefly.
A
A
So
hopefully
this
will
help
better
support
the
work
that
we're
doing,
because
the
lessons
learned
from
doing
implementing
a
risk,
five
core
and
and
doing
a
formal
verification
of
it.
The
goal
is
to
have
verified
work
for
phase
four
plenty
of
other
things
like
that
going
on.
But
that's
the
main
thing
that's
been
done
over
the
past
week,
the
pedal
linux
class
from
xylinx
that
I'm
taking
really
good
stuff.
A
But
it's
progressing
so
looking
forward
to
doubling
our
capacity
for
remote
labs
and
to
have
one
that
is.
That
is
also
open
to
doing
interferometry
work
with
a
large
dish,
installation
and
and
that
will
also
be
working
with
the
the
big
dish
at
the
huntsville
space
and
rocket
center.
So
that's
going
to
be
another
opportunity
for
a
lot
of
fpga
work
that
we
have-
and
I
I
it'll
be
many
months
from
now
all
right
and
a
special
welcome
to
aaron
alvarez.
B
Sure,
thank
you.
My
name
is
aaron
olivares
and
my
call
sign
is
ki
5
bab
and
I'm
a
new
member
of
the
fpga
team,
I'm
just
getting
spun
up
and
I'm
also
a
maintainer
for
open
cpi
and
opencpi
sounds
stands
for
open
component
portability
infrastructure.
So
it's
a
framework
that
helps
design
applications
that
target
both
the
general
purpose:
processor,
the
arm
and
the
fpga.
B
B
A
support
project
for
the
zc706
with
an
open
cpi,
because
that's
one
of
the
platforms-
I
know
you
guys
are
working
with.
I
have
that
working
in
hardware
acceleration
mode,
I
was
able
to
gain
access
to
the
remote
labs.
Thank
you.
Paul
and
I've
also
built
pedal
linux
for
the
versions
you're
using
the
2020.2
and
also
2019.2,
which
is
a
version
that
opencpi
supports.
I
got
familiar
with
the
booting
over
jtag
on
the
remote
labs
and
then
I
was
also
able
to
get
andre's
dvd
fpga
docker
container
running
his
test.
B
As
a
good
starting
point,
I
did
start
investigating
the
axi
for
light
register
maps.
It
was
really
neat
to
see
the
I
hadn't
come
across
it
before
the
air
hdl
and
how
they
were
doing
the
register
accesses
on
the
f
pga
and
that
paired
up
with
opencpi
and
that's
what
I'll
continue
working
on
this
week,
I'm
not
going
to
use
andres
right
off
the
bat
I
plan
on
creating
a
simple
register
and
just
just
to
read
a
d
word
and
then
write
it
to
start
and
then
integrating
the
work.
B
C
D
A
A
C
C
C
To
trigger
on
ship
scope,
so
I
can
see
you
know,
there's
transactions
being
sent,
but
I'm
not
expert
by
any
means
in
the
software
side.
So
still
a
long
way
to
go.
Maybe
aaron
can
catch
up
and
you
know
I
can
just
use
that
so
I
don't
mentioned
using
so
specific
components
in
open
cpi.
So
I
I
put
them
all
together
in
the
encoder
and
put
some
sort
of.
C
Oxy
debug
stuff
in
between
and
that
sort
of
shows,
sort
of
the
limitation
of
vhdl
and
actually
very
long
as
well
as
in
it's
starts
to
get
hard
to.
You
know,
put
a
lot
of
stuff
together
and
with
a
register
map,
and
all
of
that,
so
maybe
open
cpi
can
actually
instantiate.
You
know
things
in
do
the
higher
level
thing
you
know
just
connect
the
blocks,
and
apart
from
that
I
got
a
so.
I
have
an
r67
card
that
I'm
not
using.
I
actually
got
a
as
an
sbc.
C
A
E
Okay,
very
good
it'll
be
a
short
report
because
I
haven't
done
anything
in
the
remote
lab,
except
provide
a
little
bit
of
support
here
and
there
this
week,
and
I
don't
have
anything
immediately
going
on.
So
I'm
just
here
in
case
anybody
needs
any
help
with
the
remote
lab
or
if
I
can
learn
what's
going
on
to
further
expedite
that,
so
that
leads
to
luck.
I
think
please
go
ahead.
D
A
D
A
Cool
yeah
paul,
you
will
be
needed,
I
think,
with
both
the
remote
lab
south
set
up
and
also
there's
a
lot
of
interest
in
leveraging
anything
that
we
know
how
to
do
for
remote
labs
with
m17
project
when
they
get
their
lab
up
and
running.
So
I
think
your
your
documented
lab
access
procedures
are
going
to
be
reused
by
at
least
two
other
sites.