请问我的vhdl代码是否有故障？

这是我的VHDL代码，以及我的约束文件。
同样在图中，黄线是SPI_MISO信号，绿色与check1相对应，check1是一个信号，用于检查何时应该读取第一个通道的ADC值:)
哦，而且，我正在VINA和VINB上应用方波信号。
问候！
adc_2.zip 4 KB



以下为原文

And here is my VHDL code, together with my constraints file.
Also in the picture, the Yellow line is the SPI_MISO signal and the green is corresponding with check1, a signal to check when it should read the ADC value of the first channel :)
Oh and also, I'm applying a square wave signal at VINA and VINB together.
greetings!
            adc_2.zip ‏4 KB

我希望嘈杂的绿色信号迹线（通道4）是一个恶劣的探针接地技术的神器。
通过论坛帖子进行技术讨论很困难。
我们只看到您发布的内容，因此请务必细致发布内容。
第三次我试图解决我的问题，让ADC-DAC正常工作。
我注意到，当我运行ADC时，我没有得到正确的答案
SPI_MISO信号，我的vhdl代码中是否有故障，或者它是什么
其他？
你没有提到
你正在使用什么板
你正在使用什么ADC
你正在使用什么DAC
你正在使用什么FPGA
你运行了什么模拟
SPI_MISO信号有什么问题（除了它不是“正确的”）
您检查和验证的其他信号，如果有的话。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

I hope the noisy green signal trace (channel 4) is an artifact of poor scope probe grounding technique.  It is difficult enough carrying on a technical discussion through forum posts.  We see only what you post, so please be meticulous about what you post.

third time I'm trying to solve my problem to get the ADC-DAC working correctly.
I've noticed that when I'm running the ADC, I don't get a correct SPI_MISO signal, is there a fault in my vhdl code, or is it something else?

You haven't mentioned

• what board you are using
  
• what ADC you are using
  
• what DAC you are using
  
• what FPGA you are using
  
• what simulation you have run
  
• what is wrong with the SPI_MISO signal (other than it isn't "correct")
  
• what other signals you have checked and verified, if any.
  

-- 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.

对不起，我忘记了所有:)
我正在使用Spartan 3ES500 Starters套件，板载14位ADC和12位ADC。
SPI_MISO信号的问题在于它应该发送与模拟信号的转换值相对应的位，但它不发送任何信号。
接地可能确实更好，我的错！
我会试着给你一个印象：在绿色高的地方，我应该得到与前置放大器的值相对应的脉冲朝向ADC，但我只在开始时得到一个脉冲，没有其他脉冲..现在我不知道
我知道如何解决这个问题，或者我的VHDL代码是错误的......
不管怎么说，多谢拉！



以下为原文

Sorry, I forget about that all :)
I'm using the Spartan 3ES500 Starters kit, with the onboard 14bits ADC en 12 bits ADC.
The problem with the SPI_MISO signal is that it should send bits corresponding to converted value of the analogue signal, but it sends nothing..
The grounding could be better indeed, my fault!
I will try to give you an impression: where the green is high, I should get pulses corresponding with the value coming from the preamplifier towards the ADC, but I only get a pulse at the beginning, no other pulses.. Now I don't know how to solve this, or is it a mistake in my VHDL-code...
Thanks anyways!

我正在使用Spartan 3ES500 Starters套件，板载14位ADC和12位ADC。
参考设计是否适用于此板？
这将验证电路板硬件是否正常工作，您的注意力应该集中在您的代码上。
你有模拟你的设计吗？
其他SPI设备（如果有）是否按预期工作？
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

I'm using the Spartan 3ES500 Starters kit, with the onboard 14bits ADC en 12 bits ADC.

Does the reference design work on this board?
This would verify that the board hardware functions correctly, and your attention should be focused on your code.
 
Have you simulated your design?
Do other SPI devices (if any) work as expected?
 
-- 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.

啊，永无止境的问题，
我没有得到我期待的输出。
原因是：
a）你没有输入正确的alog信号
b）您没有正确控制ADC
c）你正在查看错误的引脚。
所以你需要分治一下。
adc可以做任何你能观察到的事情， 
如果是这样发送spi代码，
你能看看spi代码吗？ 
它们是正确的代码，正确的顺序，时序和电压电平。
你能看一下adc输入的alog signa吗？ 
它是否在adc cna看到的范围内并且如您所愿？
对不起，它仔细检查设备的数据表， 
探究周围，直到你看到不应该的东西，



以下为原文

Ah the never ending question,
 
I'm not getting the output I'm expecting.
 
the reason for that are either :
 
a) you not putting the right alog signal in
b) you are not controlling the ADC correctly
c) you are looking at the wrong pins.
 
so you need to divide an conquer.
 
can the adc do anything else which you can observer, 
    if so send the spi codes for that, 
 
can you look at the spi codes,
     are they the correct codes, in the correct sequence, and timing, and voltage levels.
 
can you look at the alog signa at the adc input ?
    is it in the range the adc cna see and as you expect ?
 
sorry, it's double check the data sheets for the devices, 
     probe around till you see something that should not be,
 

我检查了一些更多的信号，我使用方波作为1.97V AC的模拟输入。
我稍微更改了我的代码，因此在ad_conv从高到低之后，spi-sck时钟周期会更快。
然后我有2个时钟周期然后读数应该开始，在两个补码中我应该得到一个值10011111001111，但我得到01111111111111，这当然不正确。
我尝试发送一个恒定的数字序列，以检查我的代码是否正常并且工作正常。
所以主要的问题是我的SPI_MISO信号没有发送必要的信号，它只是一直保持在相同的值（01111111111111）。只有当我提高输入电压，超过极限（2.9Volts）时我得到
01011111111111序列..
我认为我的计时参数是正确的，任何想法会导致什么问题？
图片是从（从上至下:) adconv信号，SPI_MISO信号和SPI_SCK时钟信号拍摄的照片。
谢谢！



以下为原文

I've checked some more signals, I use a square wave as analogue input of 1.97V AC.
I changed my code a little bit so the spi-sck clockcycles would come faster after ad_conv goes from high to low. then I have 2 clockcycles and then the reading should start, in two's complement I should get a value of 10011111001111, but instead I get 01111111111111, which is off course not correct. 
I tried sending a constant sequence of numbers, to check if my code works correct and that works correct. 
So the main problem is that my SPI_MISO signal doesn't send the necessary bites, it just stays at the same value (01111111111111) all the time.. Only if I raise my input voltage, above the limits (2.9Volts) the I get a 01011111111111 sequence..
I think my timing parameters are correct, any idea what can cause the problems?
The picture is a photo taken from (from up till down:) adconv-signal, SPI_MISO signal and the SPI_SCK clock signal.
Thanks!

嗨
所以你需要检查。
什么是进入ADC的信号？
看看范围， 
你看到了什么。 
交叉检查adc的数据表。 
你有没有正确的信号进入ADC？ 
你有正确的调整吗？ 
你有合适的电压（数字和模拟）



以下为原文

hi
 
So you need to check.
 
what are the signals into the ADC ? look with the scope, 
    what do you see.
 
       cross check with the data sheet for the adc.
          do you have the right signals into the ADC ?
               do you have the right timming ?
                     do you have the right voltage ( digital as well as analog )
 
 

你有那么多的超调+下冲......
这是因为你正在探究的方式，还有你知道或“我不知道”的其他事情？
无论如何，fpga在这种情况下是SPI主控对吗？
你能否将SPI时钟减慢10倍，看看事情是否神奇地改善了？你还可以将fpga输入/输出的压摆率改变为比现在慢的速度。
或者在总线上添加一点R / C滤波器以抑制其中一些尖峰。
不是永久的解决方案，而是更多的故障排除，看它是否突然改善了一些事情。



以下为原文

That's quite a bit of overshoot + undershoot you have there...
 
Is that because of the way you are probing, something other that you know or "I don't know"?
 
Anyways, the fpga is the SPI master in this case right? Can you slow down the SPI clock by a factor of 10, and see if things magically improve? You could also change the slew rates of the fpga input/outputs to something slower than what you have now. Or add a little R/C filter to the bus to supress some of those spikes. Not a permanent solution, but more some troubleshooting to see if it suddenly improves things.
 

说实话，超调，“我不知道”......一些教授告诉我它的触发，但我想不是，我告诉他们我认为这是接地，因为我的探头只有一个接地，
与其他探测器不同，但这对他们告诉我的内容也有很大帮助。
我降低了时钟频率，但仍然没有任何变化。
我也检查了输入，只是一个2.21V的方波，频率为271Hz。
应用正弦波或其他波浪不会改变它..
有什么想法吗？



以下为原文

To be honest, the overshoot, "I dont know" ... some professors came by telling me its the triggering, but I guess it's not, I told them I thought it was the grounding, because only one of my probes is grounded, and the others not, but that helped a lot to ground the other probes as well, contrary to what they told me..
I've lowered the clockfrequency, but still nothing changes.
Also I checked my input, just a square wave of 2.21V at 271Hz..
Applying sinuswaves or other waves don't change it..
Any thoughts?

施加恒定的模拟电压，检查adc输入引脚。
什么看到的串行信号，范围和看起来？
debug就是把问题分成小块， 
这个问题是错的，
你无法猜出答案，特别是在你学习的时候， 
30年的时间，你将有一种直觉，



以下为原文

apply a constant analog voltage, check it through to the adc input pins.
 
what do see for the serial signals , scope them and look ?
 
debug is all about dividing the problem into small bits,
    the bit thats wrong is the problem,
 
you can't guess the answer , especialy when your learning,
    30 years time, you will be able to have a gut feeling,
 
 
 

mrflibble写道：
你有那么多的超调+下冲......
这是范围探测技术不佳的结果。
----------------------------是的，我这样做是为了谋生。



以下为原文

 

mrflibble wrote:
That's quite a bit of overshoot + undershoot you have there...
 

That's the result of poor 'scope probing technique.
 
----------------------------Yes, I do this for a living.

wouterdevriese写道：
说实话，超调，“我不知道”......一些教授告诉我它的触发，但我想不是，我告诉他们我认为这是接地，因为我的探头只有一个接地，
与其他探测器不同，但这对他们告诉我的内容也有很大帮助。
所有'示波器探头都需要一个接地参考，总是（除非它是一个花哨的差分探头，可能不是）。
如果您的一位教授告诉您“范围探测器不需要接地，请寻找另一所大学。
----------------------------是的，我这样做是为了谋生。



以下为原文

 

wouterdevriese wrote:
To be honest, the overshoot, "I dont know" ... some professors came by telling me its the triggering, but I guess it's not, I told them I thought it was the grounding, because only one of my probes is grounded, and the others not, but that helped a lot to ground the other probes as well, contrary to what they told me..

all 'scope probes need a ground reference, always (unless it's a fancy differential probe which might not).
 
If one of your professors tells you that a 'scope probe doesn't need to be grounded, look for another university.
----------------------------Yes, I do this for a living.

wouterdevriese写道：
......有些教授告诉我它是触发器
错误！
我告诉他们我认为这是接地
正确答案！
Bassman59写道：
所有'示波器探头都需要一个接地参考，总是（除非它是一个花哨的差分探头，可能不是）。
同意。
这很容易证明。
尝试它（有和没有探针接地）并在示波器显示屏上看到差异。
如果您的一位教授告诉您“范围探测器不需要接地，请寻找另一所大学。
这听起来有点贵。
有许多工程师和教授需要学习正确使用示波器，它们可以在许多办公室和大学中找到。
尝试教他们而不是离开他们，你将使世界变得更美好。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

wouterdevriese wrote:

 ... some professors came by telling me its the triggering

wrong!

I told them I thought it was the grounding

correct answer!

Bassman59 wrote:

all 'scope probes need a ground reference, always (unless it's a fancy differential probe which might not).

agreed.  This is easy enough to demonstrate.  Try it (with and without probe ground) and see the difference on the scope display.

If one of your professors tells you that a 'scope probe doesn't need to be grounded, look for another university.

That sounds a bit expensive.  There are lots of engineers and professors who need to learn proper use of a scope, they are found in many offices and universities.  Try teaching them instead of leaving them, and you will have made the world a better place.
 
-- 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.

改变大学不是一个选择，因为我是一个伊拉斯谟学生（欧洲交换项目）。
:)
关于SPI_MISO信号如何发送正确数据的任何其他想法？
我尝试了所有信号的范围，但它看起来只有SPI_MISO信号很难..
是否有其他迹象我可以检查我不知道？
谢谢！



以下为原文

Changing university is not directly an option, as I am an erasmus student ( european exchange program). :)
Any other thoughts on how it is possible that the SPI_MISO signal is not sending the correct data? I tried scoping all the signals but it looks only the SPI_MISO signal is acting difficult..
Are there perhaps other signas I can check that I'm not aware of?
thanks already!

你好
101关于调试。
它要么
a）芯片/电路板坏了
b）信号是外部的，因此无法驱动
c）你给出的控制信号是错误的
所以，
a）非常不可能，尝试董事会附带的referance设计来改变这一点。
b）再次不太可能，取决于你的代码，所以电路板附带的eval软件将再次回答这个问题，
c）最有可能的。 
调试c） 
尝试电路板的referance代码，看看你感兴趣的信号是做什么的， 
对比并与你的信号比较，



以下为原文

Hi
 
101 on debugging.
 
it either
 
a) the chip / board is broken
b) the signal is pulelled externaly so it can't drive
c) the control signals you are giving it are wrong 
 
 
so, 
 
a) very unlikely, try the referance design that comes with the board to priove this.
 
b) again unlikely, depends upon your code, so again the eval software that came with the board will answer this,
 
c) the most likely.
 
      to debug c)
          try the referance code for the board, see what the signals your interested in are doing, 
                 contrast and compare to your signals,
 
 

关于SPI_MISO信号可能如何的任何其他想法
没有发送正确的数据？
我尝试了所有信号的范围，但它
看起来只有SPI_MISO信号很难。
是否有其他迹象我可以检查我不知道？
我重复3天前为您发布的建议和问题。
参考设计是否适用于此板？
这将验证电路板硬件是否正常工作，您的注意力应集中在您的代码上。
你有模拟你的设计吗？
其他SPI设备（如果有）是否按预期工作？
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

Any other thoughts on how it is possible that the SPI_MISO signal is not sending the correct data? I tried scoping all the signals but it looks only the SPI_MISO signal is acting difficult.  Are there perhaps other signas I can check that I'm not aware of?

I repeat the suggestions and questions I posted for you, 3 days ago.

Does the reference design work on this board?
This would verify that the board hardware functions correctly, and your attention should be focused on your code.
 
Have you simulated your design?
Do other SPI devices (if any) work as expected?

-- 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.

看来参考设计只适用于32位计算机，因为它不想工作......
是否可以在64位笔记本电脑上运行32位文件？
再次感谢！



以下为原文

It seems the reference design is only for 32bits computers, possible, because it doesn't want to work...
Is it possible to run 32bit files on a 64 bit laptop?
Thanks again!

看来参考设计只适用于32位计算机，因为它不想工作......
由于您可能只需要运行一次参考设计，以验证电路板硬件是否正常运行，也许您可​​以借用32位Windows XP计算机。
当然，你认识的人有一台4年前的Windows机器吗？
是否可以在64位笔记本电脑上运行32位文件？
我不知道这是否适用于你想到的（未命名的）应用程序。
你在这个论坛上搜索过吗？
也许Xilinx Boards and Kits论坛可能会提供一些信息或指导。
想想看，整个线程可能会在Xilinx Boards and Kits论坛中吸引更多（更有用）的响应。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

It seems the reference design is only for 32bits computers, possible, because it doesn't want to work...

Since you possibly need to run the reference design only once, to verify that the board hardware is functioning correctly, perhaps you can borrow a 32-bit Windows XP machine.  Surely someone you know has a 4-year old Windows machine?

Is it possible to run 32bit files on a 64 bit laptop?

I dont know if that will work for the (unnamed) application you have in mind.  Have you searched the forums on this?  Perhaps the Xilinx Boards and Kits forum might have some information or guidance.
 
Come to think of it, this entire thread might attract more (and more useful) responses in the Xilinx Boards and Kits forum.
 
-- 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.

好吧，在实验室里发现了一台旧电脑，我觉得因为风扇损坏我有一些听力损伤，但参考设计工作正常，所以电路板应该没问题。
它是否在PDF中提供了代码，董事会使用的确切代码是什么？



以下为原文

Allright, found some old PC in the lab, I think I have some hearing damage because of a broken fan, but the reference design works fine, so the board should be OK.
Is ithe code provided in the PDF, the exact code the board uses?