你好,
我已经开发了一种设备来读取数据从我们的雷达DAQ底盘,但我有一些潜伏的问题。我正在使用批量传输(EP2四缓冲512字节),我现在试图使用ISO传输代替(EP2双缓冲1024字节)。
我使用GPIF从DAQ中的96KBythFIFO读取,当我使用一个大容量EP时,它工作得很好,但是现在我已经切换到ISO了,它什么也做不了。我的代码触发一个GPIF FIFO读,但是除了GPIF说它很忙之外什么也没有发生。
GPIF FIFO读取是公正的。
//GPIF波形2:FIFO Re///间隔0、1、2、3、4、5、6空闲(7)//α、α、α、α、β、α、α、α、α、α、α、α、α、α、α、α、α、α、α、α、α、β、α、α、β、α、β、α、β、α、β、α、β、α、β、α、β、β、β、氨基酸等。Te//NeXDATA SAMEDATA SAMEDATA SAMEDATA SAMEDATA SAMEDATA SAMEDATA SAMEDATA INT INT INT INT INT INT INT INT INT/INF/等待3等待1等待1等待1等待1 / 1 / /项QTr//LFUNC或/ Term B IntReady / /BANCHCH1空闲/ /分支/0空闲/ /重新执行NO//SNGL/CRC默认违约默认违约默认//Req 0 1 1 1 1 1 1 1 1 //CTL1 0 0 0 0 0 0 //cTL2α,β2,/1,1,1,1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,2,2,2,2,1,2,2,1,2,2,2,1,2,1,2,2,1,2,1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,1,1,2,1,2,2,2,2,1,1,2,1,2,2,2,2,2,2,1,1,2,1,1,2,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1有人有线索吗?
以上来自于百度翻译
以下为原文
Hi,
I have developed a device to read data from our radar DAQ chassis but I am having some latency problems. I was using bulk transfers (EP2 quad buffered 512 bytes) and I am now trying to use iso transfers instead (EP2 double buffered 1024 bytes).
I use the GPIF to read from the 96kbyte FIFO in the DAQ, and this worked fine when I was using a bulk EP, however now that I have switched to iso it doesn't do anything. My code triggers a GPIF FIFO read but nothing happens apart from the GPIF saying it's busy.
The GPIF FIFO read is just.
// GPIF Waveform 2: FIFO Rea // // Interval 0 1 2 3 4 5 6 Idle (7) // _________ _________ _________ _________ _________ _________ _________ _________ // // AddrMode Same Val Same Val Same Val Same Val Same Val Same Val Same Val // DataMode NO Data Ac
tivate Activate Activate Activate Activate Activate // NextData SameData SameData SameData SameData SameData SameData SameData // Int Trig No Int No Int No Int No Int No Int No Int No Int // IF/Wait Wait 3 IF Wait 1 Wait 1 Wait 1 Wait 1 Wait 1 // Term A QTR // LFunc OR // Term B IntReady // Branch1 ThenIdle // Branch0 ElseIdle // Re-Exec No // Sngl/CRC Default Default Default Default Default Default Default // REQ 0 1 1 1 1 1 1 1 // CTL1 0 0 0 0 0 0 0 0 // CTL2 0 0 0 0 0 0 0 0 // CTL3 0 0 0 0 0 0 0 0 // CTL4 0 0 0 0 0 0 0 0 // CTL5 0 0 0 0 0 0 0 0 So there's no decision state to stall on or anything. Anyone have any clues?
0