在Spartan 6上读取16通道的CMOS矩阵是否可以在SP605板上实现此任务？

您是否打算通过GbE IP实时发送处理过的图像？
如果是这样，请考虑源数据速率与GbE输出通道的有效数据速率之间的差异。
与其要求我们为您设计解决方案，您应该开发自己的顶级框图，其中包含您设计的每个功能块（或流程）。
然后弄清楚每个块的实现方式
在FPGA硬件中（如果适用）
互连（电缆，连接器等）
板级硬件（内存，电源）
在算法（数据压缩，图像处理等）
这将帮助您组织您的想法，识别技术问题，并识别缺少的知识或专业知识。
然后，您应该能够提出更具体的问题，更好地了解需求和依赖关系以及上下文。
- 鲍勃埃尔金德
签名：新手的自述文件在这里：http：//forums.xilinx.com/t5/New-Users-Forum/README-first-Help-for-new-users/td-p/219369总结：1。
阅读手册或用户指南。
你读过手册了吗？
你能找到手册吗？2。
搜索论坛（并搜索网页）以寻找类似的主题。
不要在多个论坛上发布相同的问题。
不要在别人的主题上发布新主题或问题，开始新的主题！5。
学生：复制代码与学习设计不同.6“它不起作用”不是一个可以回答的问题。
提供有用的详细信息（请与网页，数据表链接）.7。
您的代码中的评论不需要支付额外费用。
我没有支付论坛帖子的费用。
如果我写一篇好文章，那么我一无所获。



以下为原文

Do you intend to send processed images via GbE IP in real time?  If so, consider the difference in source data rate vs. the effective data rate of the GbE output channel.
 
Rather than ask us to design your solution for you, you should develop your own top-level block diagram with each of the functional blocks (or processes) of your design represented.  Then figure out how each block might be implemented

• in FPGA hardware (if applicable)
  
• in interconnect (cables, connectors, etc.)
  
• in board-level hardware (memory, power supplies)
  
• in algorithms (data compression, image processing, etc.)
  

This will help you to organise your thoughts, identify technical problems, and identify missing bits of knowledge or expertise.  Then you should be able to ask more specific questions, with a better understanding of requirements and dependencies and context.
 
-- 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.

336699写道：
你好。
我是FPGA上图像处理的新手。
我的任务是简单读取CMOS矩阵CMOSIS CMV2000（附件中的数据表）并通过IP协议发送此图像。
对于我的任务，我使用的是SP605开发板和Xilinx ISE / EDK 13.4。
我正在创建新的microblaze项目（这用于IP协议）。
现在我正在研究用于读取CMOS矩阵到DDR内存的自定义外设，然后将其发送到我的笔记本电脑。
在16个并行通道LVDS中读取矩阵。
CLK 480 MHz。
是否可以在SP605板上实现此任务？
如果可能如何使其成为最佳？
对于读取矩阵，我想使用AXI_DMA +我的自定义外设。
我创建测试项目并在内存中写入测试数据，然后将其传输到计算机。
是正确的方法吗？
谢谢。
你所描述的不是初学者的任务。
说真的。您是否考虑过传感器以及SPI配置端口所需的偏置，更不用说高速DDR数据输出？
----------------------------是的，我这样做是为了谋生。



以下为原文

336699 wrote:
Hello.
I'm newcomer in image processing on FPGA.
My task is simple read read CMOS matrix CMOSIS CMV2000 (datasheet in attach) and send this image over IP protocol.
For my task I'm using SP605 development board and Xilinx ISE/EDK 13.4.
I'm create new microblaze project (this use for IP protocol).
Now I'm working on custom peripheral for read CMOS matrix to DDR memory and then send it to my laptop.
The matrix is read in 16 parallel channels LVDS. The CLK 480 MHz.
Is it possible to implement this task in SP605 board?
Is if it possible how to how to make it an optimal?
While for read matrix I guess to use AXI_DMA+my custom peripheral. I create test project and write in memory test data and then transmit it to computer. Is correct way?
 
Thanks.



 

What you're describing is no beginner task. Seriously.
Have you considered the biasing required by the sensor, as well as the SPI configuration port, not to mention the very high speed DDR data outputs?
----------------------------Yes, I do this for a living.

只是一个背后的计算：
CMOSIS输出= 480 Mbps x 16
SP605 DDR3 RAM = 667 Mbps x 16
因此，只需编写图像就需要大约72％的内存带宽。
明显
您无法使用此路径以全速实时流式传输图像。
如果你只是去
为了拍摄偶然的图像并离线处理，SP605应该足够了。
确保为传感器提供服务的内存端口具有高优先级以避免
丢失图像数据。
祝你好运，
-  Gabor
-  Gabor



以下为原文

Just a back-of-the-envelope calculation:
 
CMOSIS output = 480 Mbps x 16
 
SP605 DDR3 RAM = 667 Mbps x 16
 
So just writing the image requires about 72% of your memory bandwidth.  Obviously
you can't stream images in real-time at full speed using this path.  If you're only going
to snap an occasional image and process it off-line, then the SP605 should be adequate.
 
Make sure that the memory port that serves the sensor has high priority to avoid
losing image data.
 
Good Luck,
 
-- Gabor
-- Gabor

“我的任务很简单”不，不是！
（正如其他人所指出的那样）我最近被一个类比打动了（别担心，瘀伤并不严重）：你的第一个木工项目不会是避暑别墅或华丽的餐具柜。
这将是一个画框，然后可能是一个小桌子。
然后，您将逐渐走向结构性或非常复杂的状态。
------------------------------------------“如果它不起作用
模拟，它不会在板上工作。“



以下为原文

"My task is simple "

No it isn't! (As others have pointed out)

I have recently been struck by an analogy (don't worry, the bruising wasn't severe):
Your first wood-working project would not be a summer-house or ornate sideboard. It would be a picture-frame, then perhaps a small table. You would then gradually progress towards something structural or very complicated.

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

336699写道：
我的任务描述：1）从矩阵到内存读取数据;
听起来很简单，不是吗？
但事实并非如此。
a）配置传感器，使其输出格式符合您的预期，换句话说，输出抽头的数量。
b）在传感器的输出上训练输入解串器，以便正确识别数据字框。
c）最后，将反序列化的数据字写入帧存储器。
对这三个问题进行长期和艰苦的思考。
您是否已连接SPI配置端口并验证其功能？
你正在开始训练吗？
踢球者：传感器一次给你16个像素。
但那些16个像素并不相邻。
想象一下，将传感器分成16个垂直“条纹”。
你从每个“条纹”中得到一个像素。
那么你以什么顺序将它们写入帧存储？
更有趣的是：如何将时钟域从反序列化像素数据时钟（传感器输出时钟/数据输入时钟除以5）桥接到DDR3存储器时钟域？
你还担心吗？
我敢打赌：你应该是。
2）通过IP协议将读取数据发送到计算机。这不是实时读取任务。
读取矩阵后我发送数据，发送数据后我再次读取矩阵。
我需要5-10 fps。
您打算在帧缓冲区中存储多少帧？
你如何管理触发传感器读出？
如何管理帧缓冲区，以免覆盖以前的帧？
你怎么知道何时停止读取传感器并开始从FPGA板传输到主机？
现在我有自定义外设将数据传输到AXI DMA（使用AXI4 Stream 5.00a）。
但令我困惑的是，轴的最大传输速度为344.4 MBytes / sec
我不知道“AXI”是什么，但肯定它必须有一些连接到帧存储的机制。
是否有替代AXI DMA用于从外设写入DDR而不是从C代码读取写入数据？
我？
我会做Camera Link。
比千兆以太网更快，让帧抓取器处理它。
使用硬件状态机完成所有操作。
将C代码保留给编写处理帧抓取器的人。
----------------------------是的，我这样做是为了谋生。



以下为原文

336699 wrote:

My task description:

1) Read data from matrix to memory;
 
Sounds simple, doesn't it? But it's not.
 
a) Configure the sensor so its output format is what you expect, in other words, the number of output taps.
b) Train your input deserializers on the sensor's output so you get the data word framing correct.
c) Finally, write the deserialized data words to the frame store memory.
 
Think long and hard about all three of these. Do you have the SPI configuration port connected and verified as functional? Are you initiating the training? 
And the kicker: the sensor gives you 16 pixels at a time. But those 16 pixels aren't adjacent. Imagine dividing the sensor into 16 vertical "stripes." You get one pixel from each "stripe." So in what order do you write them to the frame store?
More fun: how do you bridge the clock domain from the deserialized pixel data clock (which is the sensor output clock/data input clock divided by 5) to the DDR3 memory clock domain?
 
Are you worried yet? My bet is: you should be.
 
 
2) Send read data to computer over IP protocol.
This's no real time read task. After read matrix I'm send data, after send data I read matrix again. I need 5-10 fps.
 
How many frames do you intend to store in the frame buffer?
How do you manage triggering the sensor to read out?
How do you manage the frame buffer so you don't overwrite previous frames?
How do you know when to stop reading the sensor and start transferring from the FPGA board to the host computer?


 
Now I' m having custom peripheral that transmit data to AXI DMA (use AXI4 Stream 5.00a). But it confuses me that maximal transmit speed in axi dma 344.4 MBytes/sec<480Mbit/s*16. I think use 16 128K BRAM (write from matrix to BRAM) and then transmit from BRAM to DDR and than transmit it to computer. Is correct way?
 
I don't know what an "AXI" is, but surely it must have some mechanism to connect to the frame store.
 
 
Is exist alternative AXI DMA for write from peripheral to DDR and than read write data from C code?

Me? I'd do Camera Link. Faster than Gigabit ethernet, and let the frame grabber deal with it.  Do it all with hardware state machines. Leave the C code to the guy who writes the stuff to deal with the frame grabber.
 
----------------------------Yes, I do this for a living.