USB low-full-high speed peripherals Forum Discussions
Hi,I'm using cy68013-56pvxc on my circuit board with a MAXIM1316 analog-digital chip.I separate the AGND and DGND net and connect them together with a 0 ohm resisitor.recently i have received my circuit board and have check it that everything is ok.But After I welded cy68013-56pvxc on board (no other component on board)i found that the AGND and DGND was connected.I check the single chip and the board carefully and nothing is wrong except that pin 13 and pin 17 were not internally connected(the datasheet declares that these two pins are all AGND pins).My circuit is attached below.Please help me.
Show LessHi everyone,
I'm using CyUSB .NET DLL to interact with a device that contains a FX2 chip. The device continuosly sends data upstream through endpoint 6, which I am continuosly polling from a dedicated thread to fetch and process the afore mentioned data.The problem is that when I use the synchronous methods BeginDataXfer( ), WaitForXfer( ) and FinishDataXfer( ) after a while .NET Framworks throws a FatalExecutionEngineError exception. The thread's code is shown bellow:
inEP = myCyDevice.EndPointOf(0x86) as CyBulkEndPoint;
int BufSz = inEP.MaxPktSize * 245;
int QueueSz = 6;
inEP.XferSize = BufSz;
while (canContinue)
{
byte[][] cmdBufs = new byte[QueueSz][];
byte[][] xferBufs = new byte[QueueSz][];
byte[][] ovLaps = new byte[QueueSz][];
unsafe
{
for (int i = 0; i < QueueSz; i++)
{
cmdBufs = new byte[CyConst.SINGLE_XFER_LEN];
xferBufs = new byte[BufSz];
ovLaps = new byte[CyConst.OverlapSignalAllocSize];
fixed (byte* tmp0 = ovLaps)
{
OVERLAPPED* ovLapStatus = (OVERLAPPED*)tmp0;
ovLapStatus->hEvent = PInvoke.CreateEvent(0, 0, 0, 0);
}
}
int len = BufSz;
for (int i = 0; i < QueueSz; i++)
inEP.BeginDataXfer(ref cmdBufs, ref xferBufs, ref len, ref ovLaps);
int failures = 0;
for (int i = 0; i < QueueSz; i++)
{
fixed (byte* tmp0 = ovLaps)
{
OVERLAPPED* ovLapStatus = (OVERLAPPED*)tmp0;
if (!inEP.WaitForXfer(ovLapStatus->hEvent, 500))
{
inEP.Abort();
PInvoke.WaitForSingleObject(ovLapStatus->hEvent, CyConst.INFINITE);
}
}
if (inEP.FinishDataXfer(ref cmdBufs, ref xferBufs, ref len, ref ovLaps))
chunks.Process(xferBufs);
else
failures++;
}
}
}
The problem goes away if I use synchronous XferData( ) instead, but this method is not enought for the bandwidth requirements.
Show Lessi read the doc "AN73609",about how to develop example on linux.
but,i can`t find bulkloopapp which is mentioned in the doc.
anyone know where can i find that?tell me please.
Or anyone just has one,send me please.
thanks a lot ^ ^ .
Show LessHi,all,
the first word of the first time transfer is uncertain.
I set the EP2 as the auto in mode. I set the all FIFOPINPOLARs as active high, and the FIFOPINPOLARs pins are pulldown with a resistor. I carefully checked the source code that generates SLWR signal. I'm sure it doesn't generate extra active SLWR signal.
Even I reset the fifo at the beginning of transfer, the first word is till uncertain. I don't know why it is .
So I Think if I can reset the fifo pointer the problem might be solved. So dose anybody knows how to reset the fifo pointer?
Show Lesshi all,
im a new user of CY7C67300 cotroller provided in the ML605 kit.Though i have downloaded the necessary softwares and drivers from the CYPRESS website but nothing seems to work.I want to send data from PC to FPGA through CY7C67300.Is there any documentation available for the same
Show LessWe have a controller built around the old Anchor chips AN2131QC. Once it was functioning with the monitor running we compiled a driver using the ezloader method to download the firmware to the board, the board executes the firmware then renumerates, and a communications driver is loaded.
Up until now we have been able to generate new .sys files whenever we revised the firmware and the customer only had to copy the .sys file to the system32\drivers directory and reboot to have the controller running new firmware.
I am trying to find a way to compile a 64 bit version of the firmware and would appreciate any information available for doing that.
Thank you,
Rex Peterson
Show LessDear Sir/Madam,
I have recently purchased the NX2LP-Flex Development board (which comes with a seperate CY3684 board with the FX2LP chip for development purposes) and have issues with getting started. I am running Windows 7 x64 on an intel I7 computer. I began to follow the instructions in the dev kit getting started guide, plugged in the FX2LP board (with NX2LP board mounted on-top) and all the status LEDs (1-5) were lit. THe board was configured with EEPROM ON and LARGE EEPROM. Windows detected the USB as an unkown device and I proceeded the install the drivers. I used the windows vista x64 driver, but it resulted in a "Cypress NX2LP - Unprogrammed USB Device" to appear in Device manager, so I thought the installation of drivers was sucessful. However upon connecting the RS232 cable and loading Keil, the Green LED D7 remained unlit and the PC did not mount my device as a drive letter, as suggested by the getting started guide. The Nandmfg.exe program could not find the device either.
I wanted to get this to work, so uninstalled the drivers and tried reinstalling the windows 7 drivers x64 for CY7C68013. Now the device was detected as cypress fx2lp dev kit. But i still could not detect the device using Nandmfg.exe. In order to try to get the whole thing working I ended up following a forum support note which suggested that I should flash the NAND chips on my NX2LP board with firmware.. So on USB Control Centre I flashed the 4k page file.iic file using the ProgramFX2>64kb eeprom menu , (as I had a 4k NAND chip installed in U4 and U8 on the NX2LP board as it came shipped with these). The operation completed sucessfully, but now my device does not appear in the device manager at all, even with view hidden devices setting on. I am worried that I may have made the EEPROM inaccesiblle.
Furthermore when I switch to small eeprom the device is detected under Other devices as an unkown device, but I can't install any of the drivers successfully. The PID and VID are as follows in this case: \VID_04B4&PID_0082&REV_0000.
When I switch the eeprom off, the device, after installation of drivers installs sucessfully as FX2LP Development Kit in device manager. But again I can't seem to detect the device on Nanmfg.exe, although the device is found in the Cypress USB suite control centre. This time the PID and VID are as follows: USB\VID_04B4&PID_8613&REV_:001.
Can you please help me to get the kit back to factory settings and help me get started to mount the device as a drive (which your kit promises comes out the box!)?
Your help is much appreciated.
Many Thanks,
Sach
Show LessDoes someone have the TD_Init() code for autoout?
I configure the antoout mode as follows:
^&^&^&^&^&^&^&^&^&^&^&&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&
Typically, a FIFO is configured for Auto-Out mode as follows:
1. Configure bits IFCONFIG[7:4] to define the behavior of the interface clock.
2. Set bits IFCFG1:0=11.
3. Reset the FIFOs.
4. Set bit EPxFIFOCFG.4=1.
^&^&^&^&^&^&^&^&^&^&^&&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&^&
however,I send 1024 bytes with Cyconsole.exe , the out transfer are failed.
I remember that in the AUTO-IN mode ,i set the AUTOINLENH:L. But in the AUTO-OUT mode, i can't find the relevant register.
anyhow, does someone have the TD_Init() code for autoout?
Show LessStop me if you're heard this one before. I need to fix a hardware issue in software. <G>
I need to wiggle the SCK signal on a FX2 while the SDA line is being held low. I am assuming that SDA being held low results in BERR error status bit being set and no I2C data transfer occurs, thus no clocking to clear the stuck I2C peripheral. Since SDA and SCK are not also GPIO pins there seems no way to do this. Is there some double secret handshake way of getting SCK to give me some edges?
TIA,
Neal
Show Less