I've not heard back from anyone yet...
One option is to root around the various FPGA, and A/D and D/A vendors' websites. For example, I just took a brief stroll around the Analog Devices (ADI) website and found the following reference design-related links for their JESD204-enabled A/D converters:
1. Product evaluation boards that interface to an FPGA-based data capture board to form a complete evaluation system.
2. ADI’s EngineerZone forum online FPGA reference design resource site
3. FPGA reference design resource page on Analog Devices wiki site.
If anyone knows of other reference designs for other vendors, please post your comments here.
Thanks Steve -- you are correct -- I should have pointed out how many I/O lines are required when doing things the old-fashioned way (grin). When you start to have multiple converters, the savings in I/O when you go serial instead of parallel really mount up
Max, I thought it was a good mix of data converter and FPGA knowledge. I've forwarded it to a few colleagues within Xilinx. You're right that data converters and FPGAs are becoming much more closely joined at the hip. The only piece to the article I would've added would be a little more detail on the data converters' standard parallel outputs requiring 16 or 32 pins and IO lines for a 16-bit ADC, for example. For systems with multiple data converters in parallel, JESD204B could be a lifesaver for routing and getting good data.
-Steve Logan, Xilinx
Thank you for taking the time to comment -- I must admit that when I'm reading something I hate it if it suddenly gets mega-complex -- the thing about this article is that I've recently come to realize that the majority of people who aren't using FPGAs really don't have a clue what's inside them -- so I decided to make it an article that introduced everyone to everyone else ... sort of thing...
Some parts were a bit too simplistic, but in general I think you gave a very good introduction.
The most important thing - there are no boring parts, no too-complex-I'll-just-skim-this parts.
Thank you for the effort, it's useful to know these things :)
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.