On 3/15/21 11:52 AM, Brian Padalino wrote:
On Mon, Mar 15, 2021 at 11:16 AM Davis Hoover <dhoover@geontech.com> wrote:
Doc:
Also I forgot this link, which is DRC component spec itself (agnostic w/ respect to FMCOMMS/AD9361). It may be oudated... but this is about as well-documented as an API gets.
(perhaps outdated) https://opencpi.gitlab.io/releases/latest/docs/Dig_Radio_Ctrlr.pdf

No offense, but I don't think this documentation is as complete as you might believe.  If I search for tx_rf_port or getRfOutput, I don't get any results in that PDF.  Both of those things were the things I were told to `git grep` earlier in the thread which solved the issue I was having.  I also don't see a mention of the DoSlave structure.

Maybe this level of abstraction is one higher than what I needed, but the DRC also talks to the AD9361, so maybe the thing I needed was actually in the middle and not ultra well documented since it is so very new?

What am I missing?

Brian

_______________________________________________
discuss mailing list -- discuss@lists.opencpi.org
To unsubscribe send an email to discuss-leave@lists.opencpi.org

The current DRC documentation is in 3 places:

1. The briefing

2. The application guide chapter (for users, not implementers)

3. The platform guide (for implementers).

The 9361 code is not really considered a documented thing at this point.

The layer of software in the current DRCs (for pluto, e31x, fmcomm) that use the 9361, do not have "internals" documentation for the layer between the high level DRC worker code and the No-OS ADI library.  Hopefully in 2.2, it will be better since the chip is so ubiquitous.

Jim