I lack a little understanding in the no-os solution that we offer for the AD9371. In the no-os solution, do the common.h and common.c files get compiled with the .hdl code and then combined into the .bit file for the FPGA?
In all the supported cases - there is some sort of CPU involved, either a hard-core ARM, or some soft-core Microblaze or NIOS. These CPU's either run a OS or No-OS. In the No-OS scenario you simply compile your drivers and test code against a C library with some minimal runtime. Then the FPGA is configured with the bitstream generated from the HDL. And the CPU is loaded with an ELF sort of binary.
'common.c' and 'common.h' are part of software API and not part of HDL.
You need to generate a bit file from HDL and then create a software project using this file in Xilinx SDK.
Please follow steps in below link to create a complete No-OS build. You need to copy API source code into expected directory structure
Yes, I understand all of this. However, I have customers who want to use Mykonos but are confused about the difference between the Linux and the no-OS builds. They are looking for the details of what is going on deep within the software. I'll try to ask this a different way. If you are trying to compile a .c and a .h file, yet there is no operating system defined, where are these files being compiled to?
Do you understand what I'm asking?
I think I understand. There is still some minimal run time engine running in the CPU, the code is compiled with that CPU as the target. I think this is what's generally referred to as a bare metal application. Is the use of bare metal applications like this documented in depth anywhere at ADI, or am I better searching the web for information, or Xilinx or Altera?
That's the typical use case for Xilinx SDK. Start looking there for documentation.
Retrieving data ...