可以在不使用EDK的情况下将ADC连接到FPGA吗？

一点也不。
我改编了一个免费提供的SPI内核，可能来自OpenCores.org，并从一台简单的状态机中驱动它。
如果您已经计划在设计中使用MicroBlaze，那么如果存在合适的MicroBlaze SPI外设，可能会使生活更轻松。
我现在可能会使用PicoBlaze，因为我对它更熟悉并且它可供WebPACK用户使用。
现在我考虑一下，如果你不想被SPI打扰，你也可以使用它的一些引脚来配置LTC217x。
但是，我个人发现在调试ISERDES代码时能够编程测试模式序列非常有用，还有一些其他的东西，比如只能使用引脚配置的东西。
在原帖中查看解决方案



以下为原文

Not at all. I adapted one of the freely available SPI cores, possibly from OpenCores.org, and drove it from a simple state machine. If you were already planning to use MicroBlaze in your design, it would probably make life easier to use that if a suitable MicroBlaze SPI peripheral exists. I would probably use PicoBlaze now as I'm more familiar with it and it's available to WebPACK users.
 
Now that I think about it, you can also configure the LTC217x using a few of its pins if you don't want to be bothered with SPI at all. However, I personally found it very useful to be able to program a test pattern sequence while debugging the ISERDES code, and there are a few other things like that which you can't configure using only the pins.
View solution in original post

如果要使用FPGA和一些外部组件实现ADC，则使用xps_delttasigma_adc。
如果您使用的是LTC2171-14，则无法使用此内核并且必须设计自定义接口。
我在接口LTC217x器件方面有相当多的经验，并建议如下：
如果可以，请使用Spartan-6
使用Spartan-6的ISERDES块。
阅读XAPP1064。
如果在16位模式下使用ADC，解码逻辑会变得容易一些，因为您可以使用FR（帧时钟）输出按照XAPP1064为bitlip状态机供电，并寻找8'b11110000模式。
这不是什么大不了的事。
您不需要MicroBlaze与ADC通信，只需要一个SPI控制器来设置寄存器和ISERDES。
无论如何，MicroBlaze可能无法在全倾斜状态下跟上这个ADC。
通常，您将反序列化的数据运行到某种数字滤波器，FFT核心，高速存储器等。
如果您遇到Spartan-3并且必须在结构中进行反序列化（请参阅XAPP485），那么请注意，您将受限于相当慢的采样率。
如果这比更改为Spartan-6更容易，您可以考虑使用外部反序列化器。
如果您对这些部分有任何其他疑问，请与我们联系。
有一些关于我通过博客分散的所有麻烦的信息 - 也许是搜索“ADC”。
以下是我所做的总结：
为ADC设计了双层板，将其连接到Spartan-3A板上的低速连接器。
来自FPGA的时钟ADC。
在高于约10 MHz的采样率下，这是非常不可靠的。
将其连接到Spartan-3E板上的更高速连接器。
来自振荡器模块的时钟ADC，在板上死机。
这非常不可靠。
我没有尝试过各种各样的振荡器模块，但它肯定不能在48 MHz下工作。
使用四层PCB重新设计的ADC板。
将其连接到Spartan-6板（Digilent Atlys）上的高速，阻抗控制，走线长度均衡连接器。
来自板载振荡器的时钟ADC（SMA连接器更智能）。
这很棒！
无论如何，这是一个不错的ADC。



以下为原文

xps_delttasigma_adc is used if you want to implement an ADC using the FPGA and a couple of external components. If you're using the LTC2171-14, you can't use this core and must design a custom interface.
 
I have a fair bit of experience with interfacing the LTC217x parts and would suggest the following:
 

• Use a Spartan-6 if you can
  
• Use Spartan-6's ISERDES blocks. Read XAPP1064.
  
• If you use the ADC in 16-bit mode, the decoding logic becomes a bit easier because you can use the FR (frame clock) output to power the bitslip state machine as per XAPP1064 and look for a 8'b11110000 pattern. This is not a big deal though.
  

You don't need MicroBlaze to talk to the ADC, just an SPI controller to set up the registers and the ISERDES stuff. MicroBlaze probably won't be able to keep up with this ADC at full-tilt anyway. Generally you'd run the deserialised data into some sort of digital filter, an FFT core, high speed memory, etc.
 
If you're stuck with a Spartan-3 and have to do deserialisation in the fabric (see XAPP485), then be aware that you will be limited to fairly slow sample rates. You might consider using an external deserialiser if this is easier than changing to a Spartan-6.
 
Let me know if you have any other questions about these parts. There's a bit of information about all the hassles I had with it scattered through my blog - perhaps search for 'ADC'. Here's a summary of what I did:
 

• Designed two layer board for the ADC, connected it to low speed connector on a Spartan-3A board. Clocked ADC from FPGA.
  
• This was very unreliable at sample rates above about 10 MHz.
  
• Connected it to a higher speed connector on a Spartan-3E board. Clocked ADC from an oscillator module, dead-bugged on board.
  
• This was pretty unreliable. I didn't have a large range of oscillator modules to try, but it most certainly did not work at 48 MHz.
  
• Redesigned ADC board using a four layer PCB. Connected it to high speed, impedance controlled, trace length equalised connector on Spartan-6 board (Digilent Atlys). Clocked ADC from on-board oscillator (an SMA connector would have been smarter).
  
• This works great!
  

It's a nice ADC, anyway.
 

哇，多谢这么全面的回复，Joel：笑脸：
还有一个关于SPI的问题。
CoreGenerator中的SPI很少：SPI-3物理层接口，SPI-3链路层接口和SPI-4.2。
据我所知，在我的情况下最适合SPI-3物理层接口。
我对么？
我瞥见了你的博客，我可以说那里有很多信息。
问候，
Ignas



以下为原文

Wow, thanks A LOT for such a comprehensive reply, Joel :smileyhappy:
One more question about SPI then. There are few SPI in CoreGenerator: SPI-3 Physical Layer Interface, SPI-3 Link Layer Interface and SPI-4.2. As I understand in my situation best suits SPI-3 Physical Layer Interface. Am I correct?
 
I had a glimpse of your blog and I can say there is quite much info there.
 
Regards,
Ignas

CoreGenerator中的SPI很少：SPI-3物理层接口，SPI-3链路层接口和SPI-4.2。
据我所知，在我的情况下最适合SPI-3物理层接口。
我对么？
你不对。
“SPI”有两个截然不同的含义。
这是您应该感兴趣的SPI。
串行外设接口。
另外，请阅读这里一个很棒的学习网站。
以下是列出的CoreGenerator IP的高带宽SPI。
系统包接口。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

There are few SPI in CoreGenerator: SPI-3 Physical Layer Interface, SPI-3 Link Layer Interface and SPI-4.2. As I understand in my situation best suits SPI-3 Physical Layer Interface. Am I correct?
 
You are not correct.  "SPI" has two very different meanings.
 
Here is the SPI in which you should be interested.  Serial Peripheral Interface.  Also, read here, a great site for learning.
 
Here is the high-bandwidth SPI for which the listed CoreGenerator IPs are intended.  System Packet Interface.
 
-- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

无论谁决定使用“系统数据包接口”这个名称，都应该因为（已经有些令人困惑的）“串行外设接口”而感到困惑。
------------------------------------------“如果它不起作用
模拟，它不会在板上工作。“



以下为原文

Whoever decided on the name "System Packet Interface" should have been slapped for the confusion with (the already somewhat confusing) "Serial Peripheral Interface".

------------------------------------------
"If it don't work in simulation, it won't work on the board."

我的上帝，最初我甚至没有注意到这种差异，直到你们在这里发布它！
那么，回到SPI和ADC  - 我现在有点困惑：是否必须使用EDK来创建MicroBlaze处理器以使用串行外设接口？



以下为原文

My GOD, initially I didn't even notice that difference until you guys posted it right here!
So, back to the SPI and ADC  -  I'm a little bit confused now: is it necessarily to use EDK to create MicroBlaze processor for the use of Serial Peripheral Interface?

一点也不。
我改编了一个免费提供的SPI内核，可能来自OpenCores.org，并从一台简单的状态机中驱动它。
如果您已经计划在设计中使用MicroBlaze，那么如果存在合适的MicroBlaze SPI外设，可能会使生活更轻松。
我现在可能会使用PicoBlaze，因为我对它更熟悉并且它可供WebPACK用户使用。
现在我考虑一下，如果你不想被SPI打扰，你也可以使用它的一些引脚来配置LTC217x。
但是，我个人发现在调试ISERDES代码时能够编程测试模式序列非常有用，还有一些其他的东西，比如只能使用引脚配置的东西。



以下为原文

Not at all. I adapted one of the freely available SPI cores, possibly from OpenCores.org, and drove it from a simple state machine. If you were already planning to use MicroBlaze in your design, it would probably make life easier to use that if a suitable MicroBlaze SPI peripheral exists. I would probably use PicoBlaze now as I'm more familiar with it and it's available to WebPACK users.
 
Now that I think about it, you can also configure the LTC217x using a few of its pins if you don't want to be bothered with SPI at all. However, I personally found it very useful to be able to program a test pattern sequence while debugging the ISERDES code, and there are a few other things like that which you can't configure using only the pins.

brilas写道：
我的上帝，最初我甚至没有注意到这种差异，直到你们在这里发布它！
那么，回到SPI和ADC  - 我现在有点困惑：是否必须使用EDK来创建MicroBlaze处理器以使用串行外设接口？
不，这不对。
SPI的基础是一个简单的移位寄存器。
----------------------------是的，我这样做是为了谋生。



以下为原文

brilas wrote:
My GOD, initially I didn't even notice that difference until you guys posted it right here!
So, back to the SPI and ADC  -  I'm a little bit confused now: is it necessarily to use EDK to create MicroBlaze processor for the use of Serial Peripheral Interface?

No, it's not. SPI is, at its base, a simple shift register.
----------------------------Yes, I do this for a living.

是否必须使用EDK创建MicroBlaze处理器以使用串行外设接口？
正如贝斯曼所写，SPI只不过是一个移位寄存器和状态机。
你看过我推荐的网站了吗？
源代码在那里！
另外，请阅读这里一个很棒的学习网站。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

is it necessarily to use EDK to create MicroBlaze processor for the use of Serial Peripheral Interface?
 
As bassman wrote, SPI is little more than a shift register and state machine.  Have you taken a look at the website I recommended? Source code be there!
 
Also, read here, a great site for learning.
 
- Bob Elkind
SIGNATURE:
README for newbies is here: http://forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369

Summary:
1. Read the manual or user guide.  Have you read the manual? Can you find the manual?
2. Search the forums (and search the web) for similar topics.
3. Do not post the same question on multiple forums.
4. Do not post a new topic or question on someone else's thread, start a new thread!
5. Students: Copying code is not the same as learning to design.
6 "It does not work" is not a question which can be answered. Provide useful details (with webpage, datasheet links, please).
7. You are not charged extra fees for comments in your code.
8. I am not paid for forum posts.  If I write a good post, then I have been good for nothing.

是的，谢谢Bob的链接。
我知道这个网站，但不知怎的，我忘了它。
看起来有很多好东西需要学习！



以下为原文

Yeah, thanks for the link Bob. I've known this site, but somehow I forgot it. It looks like there are many good things to learn!