On 14/08/2024 03:52, Brajesh wrote:


That's great.
If possible, request your time for interactive session. This request is to understand codebase ( https://github.com/EttusResearch/fpga/commit/78eab419fdcdc18f4da8fd33f267af6c4d0494f6 )  and get starting point to start for data rate modifications.
You should go through the official support channels--the e-mail you got from "supp...@ettus.com" will have given you a URL.

But unless you've purchased a higher-level support package, you aren't going to get an engineer to sit down with you and   tell you where to put modified code, and how that code is best structured, etc.

Every new purchase includes a "initial bringup" level of support, which absolutely DOES NOT include detailed hand-holding
  through modifying the FPGA code.

Even if you *could* get that level of support, I would *NOT* be the person doing it.  I didn't write that FPGA code, and I'm
  not primarily an FPGA developer.


    I'm not sure what you're looking for apart from what you've
    already found, and I've already pointed you to. The FPGA source-code
      is freely available.  There are documents that describe the
    work-flow for making custom mods to the N2xx FPGA images.
      The FPGA "architecture" is common between (obsolete) USRP2 and
    N2xx hardware.  The follow-on architecture is referred
      to in the FPGA codebase as "usrp3", but that's just the naming
    of the FPGA architecture.

    Like I have said previously, there is no "structured walk-through"
    document that describes, in a high-level way, the architecture
      of the FPGA codebase.  The codebase is the document. The same is
    basically true for the host-side UHD library. The architecture
      changes often-enough that by the time a "structured
    walk-through" document could be considered "complete", the
    architecture
      underneath it, at least the details, would have changed.  Such
    is the nature of an evolving code-base.

    Now, for the "usrp2" FPGA architecture, THAT codebase has been
    relatively static for many years.  But a goodly chunk of it
      was written by people who have long-since departed the company. 
    Occasional maintenance is done on it, but for the
      most part, it has been the same for many years.  Again, though,
    the codebase IS the documentation.


Thanks again for shared details.

_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to