[问答]

FX3 GPIFtoUSB示例丢失GPIF数据

问答对人有帮助，内容完整，我也想知道答案 0 你好，从EZ-USB FX3 SDK 1.3固件 BooToFFGPIFTUSOB的例子接近我的应用需求-连续采样GPIF数据，并将其传输到PC。但在测试过程中，我正在经历从GPIF接口收集的缺失数据。测试是在FX3超高速探索者工具箱上进行的。GPIF接口的数据是由FPGA连接到KIT的。这是一个简单的14位计数器在38兆赫时钟。示例中的DMA被设置为自动模式（MualalSoDMA定义禁用）。为了最小化我这边的错误，为了收集数据，我使用USB控制中心实用程序-传输文件的功能。要传输的字节设置为2MB，结果在文件中。但是每个16KB（0x4000）都有缺失的数据。就像下一张照片：在这种情况下，大约有26个丢失的FPGA时钟。有时它会导致超过400的FPGA时钟丢失。由于USB 3连接，我期待连续的数据流。通过设置CLKDIV＝8来减缓GPIF接口是没有帮助的。有什么暗示我忽略了什么，或者如何改进它？最好的问候，斯拉沃米尔以上来自于百度翻译以下为原文 Hello, example from EZ-USB FX3 SDK1.3firmwareboot_fwgpiftou*** fit close to my application demands - continuously sample GPIF data, and transfer it to PC. But during tests, i am experiencing missing data collected from GPIF interface. Tests was performed on FX3 Superspeed Explorer kit. Data for GPIF interface are produced by FPGA connected to kit. It's a simple 14 bit counter at 38MHz clock. DMA in the example is set to AUTO mode (MANUAL_DMA definition disabled). To minimize errors on my side, for data collecting i use USB control center utility - transfer file-in function. Bytes to transfer is set to 2MB, and result is in the file. But each 16kB (0x4000) there are missing data. Like in the next picture: In this case it's approximately 26 missing FPGA clocks. Sometimes it rise to more than 400 missing FPGA clocks. Because of USB 3.0 connection i am expecting continuous data flow. Slowing down GPIF interface by setting clkDiv=8 doesn't help. Any hint what am i overlook, or how can improve it? Best regards, Slavomir 0
2018-12-27 15:48:52　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × 36切53 该类别下有 65 个回答。邀请回答 hnui2002 该类别下有 50 个回答。邀请回答细水爱长流该类别下有 33 个回答。邀请回答不cdvdhgdh 该类别下有 31 个回答。邀请回答 iwuwjgj 该类别下有 26 个回答。邀请回答 cslb2000 该类别下有 25 个回答。邀请回答珠海易胜该类别下有 23 个回答。邀请回答 ggfx 该类别下有 23 个回答。邀请回答 h1654155958.0210 该类别下有 22 个回答。邀请回答 hrtuoyu 该类别下有 22 个回答。邀请回答 ncmza 该类别下有 21 个回答。邀请回答 shaoye88 该类别下有 21 个回答。邀请回答瑾年Invader 该类别下有 20 个回答。邀请回答望望Ll 该类别下有 20 个回答。邀请回答 april_yu 该类别下有 20 个回答。邀请回答 zkzk196599 该类别下有 19 个回答。邀请回答 lucas_songlea 该类别下有 18 个回答。邀请回答 nvwuwy 该类别下有 18 个回答。邀请回答 zhan81411 该类别下有 17 个回答。邀请回答 cmh22 该类别下有 17 个回答。邀请回答举报张坤相关推荐 • 如何将数据发送到FX3 2489 • FX3软件GPIF II设计器在哪里可以下载？ 1201 • FX3与FPGA的连接线中是否可以省略地址线？ 194 • FX3中断捕获发现会有帧丢失 2719 • 请问GPIF最大速度是多少？ 1781 • 需要12 GPIF数据总线 910 • 设计柏树FX3突破板问题该怎么解决？ 1245 • 如何在GPIF中使用输入PCLK？如何配置代码？ 940 • 怎么使用FX3 GPIF-II的同步从设备FIFO写模式 2152 • FX3接口在100MHz的ADC接口 3092 2个回答

答案对人有帮助，有参考价值 0 你好， GPIFTUSOB示例主要用于测试最大吞吐量。为了进行可靠的数据传输，这个例子不能这样使用。正如您可能知道的，来自GPIF的数据由FX3接收并存储在其DMA缓冲器中，然后将其发送到USB。假设您的示例具有4个DMA缓冲区，每个大小为16K字节。一旦数据传输开始，来自GPIF的字节开始填充第一缓冲器。一旦第一个缓冲区被填充，FX3的DMA引擎就需要一些有限的时间（很少的US）使第二个缓冲区就绪。在此期间，来自GPIF的数据将丢失。因此，您报告丢失的字节可能会到达这个缓冲区切换时间。因此，我们建议在FPGA和GPIF之间以旗子的形式进行握手。详情请参阅以下申请须知。（特别参阅标志A和标志B部分）。AppNoSE还附带示例项目。 AN6974-用EZ-USB®FX3从FIFO接口设计CyPress半导体当做， - Madhu Sudhan 以上来自于百度翻译以下为原文 Hi, The GpifToU*** example is mainly used for testing the maximum throughput. For doing reliable data transfers, this example cannot be used as such. As you may be aware the data from the GPIF is received by FX3 and stored in its DMA Buffers before sending it to the USB. Assume that your example has 4 DMA Buffers, each of size 16K Bytes. Once the data transfer starts, the bytes from GPIF Start filling the 1st Buffer. Once the 1st buffer is filled, FX3's DMA engine takes some finite time (few uS) to make the second buffer ready. In that meantime the data coming from the GPIF will be lost. So the bytes you have reported to be lost may would have arrived in this buffer switching time. So we recommend to have a handshake between the FPGA and GPIF in the form of flags. Please refer to the below application note for more details. (Refer to Flag A and Flag B parts especially). The AppNote also comes with example project. AN65974 - Designing with the EZ-USB® FX3™ Slave FIFO Interface \| Cypress Semiconductor Regards, -Madhu Sudhan

2018-12-27 15:54:11 评论举报刘辉

答案对人有帮助，有参考价值 0 梓木鱼之子发表于 1970-1-1 08:00 你好，我认为，在缓冲区之间切换所需的时间是问题所在。这些芯片是为了无缝地切换缓冲器而设计的，所以如果需要握手的话，使用这些芯片是没有意义的。事实上，减慢数据率是无济于事的，这证明了这一点。我有一个类似的数据丢失问题之前，转让通过，下一个是： CY7C68013流光输入传输ISOC丢失数据你已经解决了这个问题了吗？你可以把其他答案标记为正确答案，这样也许有人来看看问题。在这个问题上有“回答”标签可以帮助潜在的帮助者离开。当做，弗兰克以上来自于百度翻译以下为原文 Hi, I don't think that the time needed to switch between buffers is the problem. These chips are designed for seamlessly switching the buffers around, so it would make no sense to use these chips at all if you need handshake anyways. The fact that slowing down the data rate does not help, kind of proves this. I have a similar data loss issue right before the transfer is through and the next one is started: Cy7C68013 Streamer input transfer ISOC loses data Have you been able to solve the problem, yet? You can unmark the other answer from being the correct answer so that maybe someone else is coming and looking at the problem. Having the "answered" tag on the question keeps potential helpers away. Regards, Frank

2018-12-27 15:59:29 评论举报李星星