On Fri, Mar 27, 2020 at 1:47 PM Davis Hoover <dhoover_at_geontech.com> wrote:
> Brian - please take a look at
> https://gitlab.com/opencpi/opencpi/-/wikis/AD9361-Integration-Guide and
> then let us know any remaining questions. This will give us an opportunity
> to improve that wiki page. Thanks!
>
Thanks for the link. Reading through, I still have a question as to the
runtime programability of the values.
The delay values are built into the HDL, but also provided at runtime to
the RCC initialization struct. Which takes precedence? Or is it always
the hardware one is read and populates the initialization struct?
I am not a fan of the guess-and-check methodology. If things get unwieldy,
with each register being 4 bits, isn't that 65536 potential cores that need
to be generated? I don't want to copy the code around everywhere to modify
the build parameters of a core piece of OpenCPI.
I think this mainly comes back to the question of on-demand customization
and not utilizing NGC/EDIF netlists and just stitching things together
using source code and references?
What is the best methodology going forward?
Sorry for all the questions and confusion.
Brian
Received on Wed Apr 01 2020 - 15:20:31 CDT