►
From YouTube: FPGA Meetup for 18 October 2022
Description
Encoder update, welcome to new team members, and Remote Labs reports.
A
B
Welcome
everybody
to
the
fpga
standard
meeting
at
open,
Research
Institute
for
Tuesday
October
18th,
so
I'll
invite
everybody
to
talk
about
what
they've
done
over
the
past
week,
what
they
have
to
have
planned
to
do
over
the
next
week
if
there
are
any
resources
that
are
needed
or
if
there's
any
roadblocks
in
the
way
and
I'll
start
out
with
just
a
brief
encoder
update
of
everything
that
I
I
know
and
and
then
turn
it
turn
it
over
to
to
James
and
Sasha
and
and
Everest,
and
anybody
else
that
is
able
to
attend.
B
So
these
are
a
little
bit
of
encoder
Updates.
This
is
the
encoder.
This
is
the
downlink,
and
so
we
have
a
couple
of
problems
that
we've
found
recently.
One
of
them
is
a
problem
in
the
inline
config
adapter,
a
k-switch
for
the
config,
which
is
the
enumerated
Tuple
of
the
frame
type
constellation
and
code
rate,
has
some
combinations
that
aren't
in
the
tables
in
the
spec,
so
I
volunteered
to
write
a
pull
request
for
that
and
then
I
think
we
should
really
start
looking
hard
at
editing.
B
This
is
using.
These
calls
is
a
different
approach
from
from
writing
low-level
dma
code
or
using
the
old
myconus
structures
and
and
systems.
B
So
what's
happening
to
us
with
the
with
the
encoders
that
the
configuration
word
is
getting
corrupted
somehow
along
the
way,
and
that
means
that
it
changes
changes
Behavior,
it
doesn't
understand
what
code
rate
or
modulation
or
frame
type
it
has
anymore,
and
it's
causing
a
transmit
buffer
timeout
in
iio
and
about
that
buffer.
So
we
were
using
iio
buffer
push
which
shoves
out
the
entire
buffer
that
you
set
up
and
every
recommended
to
look
at
the
iio
buffer
push
partial.
B
B
The
the
encoder
puts
out
a
signal
there's
some
problems
with
that
signal
on
the
zc706
which
I'll
mentioned
very
shortly,
but
the
sending
so
sending
single
words
to
the
buffers
filling
up,
the
buffer
and
shoving
of
it
all
out
usually
worked,
but
sending
files
like
BB
frame
files
isn't
yet
working
and
so
help
is
still
needed.
Here
we
have
some
additional
capabilities.
The
mqtt
approach
from
every
student
entroll
is
working
on
the
Pluto,
but
not
yet
working
on
the
zc706.
B
This
will
be
a
really
powerful
way
to
do
things
when
it's
working
for
for
everything.
We
do
have
a
python
notebook
that
takes
a
TS
or
a
TS
file
or
transport
stream
file.
Generally,
you
can
assume
that
this
is
MPEG,
eventually
we're
going
to
do.
Gse
the
generic
stream
and
encapsulation,
but
right
now
we're
working
with
TS
files,
because
the
receivers
are
more
plentiful
easier
to
test,
but
it
takes
a
TS
file,
turns
it
into
BB
frames.
B
It's
a
python
notebook
and
this
matches
the
Block
in
gnu
radio
that
produces
BB
frames
from
a
TS
file.
You
can
use
either
one,
but
if
you
don't
want
to
install
a
good
new
radio
and
you
you're
okay
with
using
a
python
notebook,
then
you
can
get
a
BB
frame
file,
a
BB
frames
from
a
TS
file
and
we've
improved
just
consistently
approved
over
time
the
processor
side
operations.
B
We
now
have
everything
from
bit
file
to
PS
workflow
documented.
We
can
operate
the
station
with.
I
o
calls
on
the
processing
side
and-
and
we've
done
this
multiple
times-
and
you
know
we're
getting
a
lot
better
with
with
essentially
setting
up
the
the
station
from
scratch
to
to
getting
applications
working
on
the
processor
side,
there's
some
updates
on
resources
and
reaching
out
welcome
to
Sasha
and
janani.
These
are
two
new
people
to
the
fpga
team.
Please
look
for
them
and
make
them
feel
welcome.
B
We've
gotten
some
additional
Community
Support,
the
ham
Expo
presentations
about
our
work
went
really
very
well
again.
In
the
past,
Andre
and
others
have
anchovy
have
presented
at
ham
Expo.
We
did
it
again
and
got
additional
good
feedback
and
we've
had
a
pretty
high
level,
wide-ranging
set
of
presentations
to
jamshot.
So
thank
you.
Everyone
for
helping
getting
out
the
word
it
doesn't
happen
without
people
actually
pushing
and
and
saying
things
and
and
going
out
there
and
introducing
it.
B
So
please
help
spread
the
the
good
news
and
then,
in
in
terms
of
Articles
or
papers,
we
we
wrote
an
article
about
the
Forward
Air
correction
on
the
Uplink,
the
offer
opulent
voice.
This
is
very
likely
to
be
published
soon
in
a
national
publication.
We
should
really
follow
that
up
with
one
about
the
multiplexing
and
the
encoder
work
that
we're
doing
here.
B
So
here's
what
the
currently
what
the
encoder
looks
like
this
is
what
the
wrapper
looks
like.
This
is
what
was
gets
placed
in
the
HDL
and
the
two
main
chunks
of
it.
Well,
you
have
input
data
and
output
data,
of
course,
and
in
our
case,
we're
taking
in
data
from
BB
frames.
So
it's
at
the
baseband
frame
level.
B
Data
width
is
is
32
bits
it's
expecting
32
bits
in,
and
so
that's
the
data
mismatch.
The
bus
mismatch
that
we
just
fixed
yet
again.
So
it's
the
default
from
the
from
the
reference
design
is
128
and
we
forgot
to
change
that.
We
thought
maybe
some
of
the
more
recent
problems
were
because
of
that,
but
that
cleaning
that
up
didn't
didn't
fix
it
or
didn't
fix
it
completely.
Once
you
get
into
the
wrapper,
you
have
an
inline
config
adapter.
This
handles
the
the.
When
we
have
a
BB
frame.
B
We
it's
not
just
BB
frames,
it's
one
word,
that
is
the
configuration
word
with
the
frame,
type
constellation
and
code
rate,
and
then
job
of
the
inline
configure
adapter
is
to
figure
out
which
one
of
those
32-bit
words
is
that
particular
special
word
and
then
break
it
down
into
enumerated
types
and
feed
the
encoder.
You
can
see
that
the
encoder
has
these
things
that
go
into
it
and
so
those
two
sub
two
entities
in
there.
That's
that's
what's
in
the
wrapper
and
then
what
comes
out
is
IQ
Data.
B
B
If
you
drill
down,
look
just
look
at
the
encoder:
this
is
what
it
looks
like
so
lots
of
axi,
but
other
than
that,
a
pretty
straightforward.
The
data
comes
in
and
and
the
encoder
frame
type
constellation
code
rate
from
that
one
word
comes
in
as
well
and
then
IQ
out,
and
this
is
backing
up
a
little
bit.
This
is
how
it
fits
so
before
the
txdma
controller
went
directly
to
the
DAC
fifo
we've
gotten
in
the
middle
of
that
with
our
encoder
and
now
we're
just
trying
to
make
it
make
it
work
all
right.
B
So
I'm
going
to
turn
off
sharing
and
then
hey
everybody.
So
that's
kind
of
a
summary
of
of
where
we're
at
from
from
what
I
know,
and
so
I'd
like
to
turn
it
over
to
let's
go
with
with
ever
East,
and
let
us
know
what
you
think
and
what
what
additional
things
we
should
be
working
on.
C
Okay,
I,
don't
know,
I,
don't
know
what
you
mean.
Yes,
you
sound
great
yeah,
so
good
step
forward
as
you
work
a
lot
on
the
on
fixing
all
this
issue,
so
I
I
write
minimal
example,
which
which
should
work
on
on
both
platform.
So
on
Pluto,
which
is
working
right
right
now
and
just
by
Define,
it
should
be
work
on
the
zc706.
C
I
think.
Well,
maybe
there
is
some
HDR
difference
between
the
both.
So
maybe
we
have
to
investigate
the
difference
between
the
twos.
The
both
I
can
also
make
well
make
some
more
truss
on
debug,
which
means
that
we
can,
if
we
can
have
the
register
of
the
encoder
on
the
Pluto
and
on
the
other
platform,
and
we
can
we
can,
we
can
maybe
inspect
what
what
the
what
the
issue
so
I
think
that
I
we
had
a
dump
of
the
register
after
each
right
to
the
encoder.
C
Yes,
so
that's
it.
I
just
have
a
quick
question:
I
try
to
understand
how
to
change
the
sample
rate
on
the
80.
Well,
9371.
C
B
B
We
tried
to
look
for
that
too.
Yesterday,
I,
don't
I,
don't
know
how
yet
it
it
did
not
seem
to
be
obvious.
So
you're
you're,
not
alone,
so.
C
Because
it
seems
that
the
initial,
the
initial
sample
rate
is
about
more
than
100
Megas
yeah.
B
C
Yeah
and
yeah,
and
so
we
we
can't
have-
we
will
receive
a
which
handled
that,
so
we
have
to
figure
out
how
to
how
to
change
the
sample
rate.
My
idea
is,
maybe
that
you
can't
change
the
sample
rate
itself
but
add
some
stages
after
that
to
decimate-
and
this
is
what's
happened
on
the
Pluto
itself,
but
the
io
under
that
so
I
I,
wonder
how
it
is
done
on
this
platform.
B
Right
yeah,
I,
I'm
I'm
with
you
and
understand
I.
We
may
have
to
at
least
the
old
way
of
doing
it
seem
to
be
to
set
it
up
using
the
the
transceiver
evaluation
software
that
Tes
software
and
that
that
you
set
it
all
in
there.
And
then
you
get
this
C
file
or
python
either
way
and
it's
a
export
from
Tes,
and
then
you
put
that
with
that
was
part
of
your
code
for
the
old
way
of
doing
it.
But
now
we
want
to
use
iio.
C
Yeah
progress
yeah
because
normally
IO
is
simplify
the
the
the
the
multi-platform,
which
means
that,
if
I
do
that
on
on
Pluto
with
sample
rates,
I
could
have
the
same
behavior
on
a
on
another
platform.
Just
with
laser
change
and
right
now
it
doesn't
work
anymore.
So
I
I,
don't
know
if
it
is
the
the
I
o
driver
of
the
1971,
which
is
not
finished,
because
the
documentation
is
not
as
detailed
as
the
at
the
90s
61
or
62
3
of
the
of
them.
C
Okay,
that's
maybe
maybe
we
have
to
to
ask
questions
to
ADI,
okay,.
B
Yeah,
that
sounds
like
something
to
ask
them
and
yeah
good
good
observation.
C
The
just
the
last
word
it's
now
very
easy
to
test
for
me
and
going
to
the
zc706
directly
on
SSH
and
I
can
I
think
that
you
have
seen
it
well,
the
the
binary
which
is
on
the
MSD,
yes,
and
so
it's
very
very
convenient
thanks
for
the
for
this
remote
lab.
Oh.
B
B
Awesome
all
right
so
Sasha,
please
welcome,
go
ahead
and
introduce
yourself
if
you'd
like
and
let
us
know
what
you'd
like
to
accomplish.
I
believe
this
is
the
the
first
time
that
you've
made
one
of
the
meetings.
So
please,
please,
you
have
the
floor
is
a
lot
of
audio
work.
Yes,
you
sound
great,
so.
A
Yeah
I
would
like
to
work
on
getting
the
EVPs
to
transmitter
or
working
and
I
guess
I'm.
Just
a
bit
of
background.
I
am
I.
A
friend
startup
does
want
a
dpbs2
transmitter
for
satellite
cues
and
they're
okay
with
paying
me
to
help
make
it
happen,
and
obviously
this
project
seems
to
be
quite
Advanced,
I
I,
don't
think
I
could
I.
Don't
really
think
I
could
do
that.
Much
work
in
the
times
fan
that
they
want
me
to
get
get
a
transmitter
done
and
working
and
test
it.
B
That's
a
good
question
so
right
now,
what
we're
on
is
a
it's
called.
A
zc,
706
or
706
is
what
we
call
it,
but
this
is
706..
This
is
xilinx
fpga
development
station
I'm
you
if
you're
in
fpgas
you're,
probably
familiar
with
it.
So
so
that's
the
the
platform.
B
The
hardware
that
we're
working
with
today
attached
to
it
is
something
called
an
adrv
9371
and
that's
the
9371
RF
SOC
from
Analog
Devices
and
that's
their
development
board,
and
so
these
two
boards
fit
together
and
they
make
a
radio
fpga
radio
development
platform.
So
that's
where
that's
where
we
start
and
and
get
the
hardware
working.
So
it's
a
xilinx
Target.
B
We
also
have
a
Trends
module,
which
is
a
this
drops
a
lot
of
the
peripherals
off
so
that
you're
dealing
just
with
the
fpga.
So
we
have
that
waiting
for
us
to
use
to
take
the
next
step
in
order
to
to
make
our
own
board
set.
So
the
board
set
will
include
everything
that
you
need
in
a
payload,
and
that
includes
the
the
so
the
encoder
is
a
big
part
of
that
for
the
downlink.
Obviously,
and
the
Uplink
receiver
is
the
work
for
that
protocol
is
pretty
far
along.
B
There
still
needs
to
be
some
some
work
done
there
for
the
for
the
Uplink.
You
know
so
that
and
the
hardware
for
that
same
same
development
station,
but
we
do
not
have
any
any
HDL
working.
Yet
that's
just
begun.
So
that's
sort
of
this
Hardware
status
and
the
hardware
path
that
we
have.
So
we
we,
our
goal,
is
to
end
with
actual
custom
boards
for
space.
A
Yeah
I
guess
I'm
specifically,
like
so
I,
understand
the
setup
of
like
an
fpga
dashboard
and
then
board
with
the
80
chip
that
takes
in
IQ
samples
and
outputs
like
RF,
yes
and
I'm.
I'm
wondering
like
my
company
would
like
to
have
something
that
outputs,
x-band
and
I.
Don't
think
that
80
that
80
part
outputs
in
the
x-band
I
think
it
pops
out
at
like
five
or
six
gigahertz.
That's.
B
Correct
what
we're
doing
with
the
dev
board,
what
we
have
today
is
is
making
sure
that
the
baseband
Works,
essentially
the
baseband,
so
we're
testing
at
I
think
what
are
we
testing
out
right
now?
We're
testing
at
2.5
gigahertz
and
there
is
additional
RF
Hardware,
that's
going
to
be
needed
to
get
to
10
gigahertz,
which
is
our
our
particular
goal
for
the
downlink.
So
the
satellite
sub
band
for
amateur
radio
is
what
we
have
targeted
it's
about.
It's.
B
We
have
10
megahertz
there
and
that's
the
that's
the
goal
for
the
hardware,
the
uplink's
on
five
gigahertz,
similar
similar
bands,
similar
sub-band
and
then
the
path
you
know
we're.
Also
looking
at
24
and
47
gigahertz
hardware
for
this,
but
known
by
itself,
the
9371
will
not
do
10
gigahertz
on
its
own
or
anything
higher.
So
that's
true.
B
There's
additional
RF
hardware
needed
there's
some
designs
that
have
been
sketched
out
and
some
some
parts
were
were
picked
and
then
covid
has
really
kind
of
changed
the
schedule
for
a
lot
of
this,
including
fpgas.
As
you
know,
it's
kind
of
tough
to
get
them
we're
very
lucky
that
we
have
the
boards
that
we
have
and
we
can
make
progress
on
all
this
stuff,
but
the
the
building
of
the
the
of
the
10,
essentially
an
up
converter
for
10
gigahertz
kind
of
stalled
out.
B
So
it's
there's
plenty
of
interest
and
and
a
very
slow
amount
of
progress,
but
because
the
a
lot
of
people
were
were
kind
of
scared
away
from
from
doing
part
selection.
What
we
do
have
is
a
lot
of
surplus
parts
and
parts
from
that
have
been
donated,
or
these
are
ones
no
longer
available
for
a
while
right,
so
so
lots
of
silver
boxes
and
and
filters
and
amps
and
things.
So
that's
where
we're
at
on
the
RF
side.
A
B
That's
a
good
question:
let
me
think
about
it
and
get
back
to
you
very
quickly
because
the
the
the
problems
that
we're
having
with
the
HDL
on
the
encoder
May.
Well,
we
think
they.
These
are
probably
problems
with
the
software.
B
B
A
B
That's
the
goal
right
on
all
right,
James
tell
us!
Oh
sorry,
Sasha
I
didn't
mean
to
cut
you
off.
Is
there
anything
else
that
you
wanted
to
talk
about
talk.
A
D
Oh,
it's
going
fairly
well
down
here
in
remote,
lab
South,
we've
finished
moving
one
of
the
really
big
pieces
of
equipment
out
of
the
building
that
we'll
be
using
for
that'll,
be
the
permanent
features
for
remote
Labs
South.
So
we've
got
a
lot
more
space
to
move
more
equipment
in
and
start
getting
a
lot
more
stuff
set
up
down
here.
So
it's
going
to
be
nice,
it's
one
of
our
like
biggest
and
heaviest
pieces
of
equipment.
We
had
to
move
around,
and
so
it
was
nice
to
finally
get
that
done.
D
D
And
you
cut
out
briefly,
but
I
think
you
said
my
name,
nothing
to
report
about
remote
lab
West.
It's
still
there
and
I've
been
using
it
to
develop
these
fpga
tests
and
I've
been
helping
out
working
on
that
with
Michelle
and
that's
pretty
much
what
I've
been
up
to
I,
don't
have
any
new
roadblocks
or
anything
going
on
for
the
meeting
good.
B
All
right-
and
we
have
some
some
interest
in
getting
polar
codes
up
and
running
and
I'm,
hoping
that
we
can
use
at
least
in
for
remote
Lab
at
remote
lab
West.
B
We
do
have
the
zc706,
which
is
not
something
that
we
have
at
remote
lab
South
remote,
Labs
South
has
an
ultrascale
plus
a
zcu
106,
and
we
have
the
same
board
here
in
remote,
lab
West,
and
it's
been
somewhat
underutilized
I'd
like
to
to
start
getting
more
projects
on
that
so
I'm
trying
to
to
build
up
a
small
team
of
people
that
are
interested
in
polar
codes.
So
these
are,
these
are
pretty
tricky.
They
are
arguably
better
than
ldpc,
which
is
essentially
gets
you
up
to
capacity.
B
So
if
you're
listening
to
this-
and
you
want
to
see
more
open
source
work
for
Polar
codes,
which
are
used
in
5G
lots
of
research
activity
around
polar
codes,
they're
great
they're,
complicated,
so
I
can
promise
you
a
pretty
steep
learning
curve,
but
plenty
of
support
and
a
powerful
development
station
to
use
for
fpga
design
and
very
shortly,
we'll
be
kicking
off
our
artificial
intelligence
and
machine
learning.
Handbook
effort
for
forgetting
practical
sort
of
AIML
open
source
work
done.
B
This
may
not
be
exclusively
fpga,
but
if
we
see
anything
that
might
might
be
of
use
or
might
could
be
deployed
using
fpga
stations,
then
the
remote
Labs
will
be
the
place
where
it
will
be
offered
as
a
resource
for
that
all
right.
Any
last
comments
or
questions
before
we
close
for
the
day.
B
All
right,
thank
you.
Everybody
we'll
keep
whacking
away
at
the
the
encoder
problems
and
I'm
highly
confident
that
it's
going
to
be
producing
some
as
just
as
good
Spectrum
as
the
Pluto
did.
Thank
you
so
much
to
everybody
for
for
helping
and
we'll
do
this
again
next
week
and
see
you
on
Slack.