USB low-full-high speed peripherals Forum Discussions
Hello,
The customer wants to distribute the USB-UART (CY7C65213) driver installer (CypressDriverInstaller_1.exe) to the end user.
Is it possible to sell the customer's products including Cypress's driver software on a recording medium such as CD-R?
Does Cypress allow redistribution of driver software?
Best Regards,
Naoaki Morimoto
Show LessHello
Regaring the CY7C68013A-56PVXC.pdf Japanese version (document number: 001 - 63322 Rev. D).
They are checking both Figure 18 on page 46 and Figure 20 on page 48.IFCLK in the figure should be supplied internally.
The clock to be supplied seems to be able to select the phase with the program of FX2 (below)
● Clock phase selection (Phase can be selected when selecting internal supply)
1) Make the phase of IFCLK in phase with IFCLKi inside FX2.
2) Make the phase of IFCLK inverse to IFCLKi inside FX2.
Q)
They are programming it with reverse phase of 2) mentioned above.In this case, what about the standards in Figures. 18 and 20?
They are undrstanding that Figures 18 and 20 as charts of the same phase (above selection 1) ).
Is there a chart or standard when IFCLK is in reverse phase?
Best Regards
Arai
Show Lesshello.
this is Akira.
we long time used a product which uses cy7c63001.
but this product is discontinued, since cy7c63991 was already finished.
so, now we are looking for another device which has same protocol as cy7c63001 which means we do not want to change software on the Windows.
does anybody have an Idea? or information?
thanks in advance.
Show LessHi we need to impliment the "lock" function on an SD kaart partition.with the Card’s "Internal Write Protection" mechanism.
I am not sure if it's been handeled inside the Cy driver or firmware of the FX3S
Is there anybody that implimented this ?
Help would very much be appreciated.
According to the SD card associasion manual :
"
The entire card may be permanently write
protected by the manufacturer or content provider by setting the permanent or temporary write protect
bits in the CSD. For cards which support write protection of groups of sectors by setting the
WP_GRP_ENABLE bit in the CSD, portions of the data may be protected (in units of
WP_GRP_SIZE sectors as specified in the CSD), and the write protection may be changed by the
application. The SET_WRITE_PROT command sets the write protection of the addressed write protect group,
and the CLR_WRITE_PROT command clears the write protection of the addressed
write-protect group. "
I assume the firmware needs to handle the low level interface while the driver needs to inrefcae between the firmware and User interface and/or file write/read handler.
Show LessI'm using the USB Serial SDK to build a USB-I2C bridge with the CY7C65211 broken off a CY8CKIT-049-42XX. As a first step I'm reading some "who am i" registers, and on the face of it that works fine, so far.
However, on the logic analyzer I see a long delay of 3-8ms between the I2C write and the read. (The two rather randomly chosen test devices, INA219 and MPU6050, require to first set the register pointer with a 1-byte write followed by a 1-byte read.)
It is clearly the master who is responsible for this, because in the 3-8ms waiting period the clock is low - which I find a bit strange, too.
Those 3-8ms equate to 125-333Hz, which is quite slow given the capabilities of the device and USB itself.
What is the reason for this delay? Can it be avoided or is there anything to watch out for?
The C program is absolutely straightforward: Open device, write, read, close. The CY7C65211 has the default configuration, just with the switch to I2C.
Show LessHi,
I plan to connect the CF to CY7C68300C-56LTXC.
So, I just want to make sure whether CY7C68300C-56LTXC have limitation of CF density.
I plan to use 8GB and 32GB of CF.
Let me know your advice.
BR,
Shohei
Show LessHi All,
I am using USB CY7C65215 for my usb projector connection , here is my visual c++ sample code as well as attached cyusbserial.dll so please have a look it
BYTE *writeBuffer = new BYTE[1];
ZeroMemory(writeBuffer, (sizeof(BYTE) * 1));
writeBuffer[0] = (BYTE)83;
CY_RETURN_STATUS num1 = Write((BYTE)27, writeBuffer, len1);
*************** Write Function Code
CY_RETURN_STATUS Write(UCHAR byteSlaveAddres7bit, UCHAR *buf, UINT32 len)
{
CY_I2C_DATA_CONFIG* dataConfig = NULL;
CY_DATA_BUFFER* writeBuffer = NULL;
UCHAR *pszWriteBuffer = NULL;
try
{
dataConfig = new CY_I2C_DATA_CONFIG();
CHECK_NULL(dataConfig)
writeBuffer = new CY_DATA_BUFFER();
CHECK_NULL(writeBuffer)
pszWriteBuffer = new UCHAR[len];
CHECK_NULL(pszWriteBuffer)
memset(pszWriteBuffer, 0, len);
memcpy(pszWriteBuffer, buf, len);
dataConfig->slaveAddress = byteSlaveAddres7bit;
dataConfig->isStopBit = (BOOL)TRUE;
writeBuffer->length = (UINT32)len;
writeBuffer->buffer = pszWriteBuffer;
CY_RETURN_STATUS cyReturnStatus = LTWrite(mHandle, dataConfig, writeBuffer, 5000U);
SAFE_DELETE(pszWriteBuffer)
SAFE_DELETE(dataConfig)
SAFE_DELETE(writeBuffer)
return cyReturnStatus;
}
catch(std::exception &e)
{
SAFE_DELETE(pszWriteBuffer)
SAFE_DELETE(dataConfig)
SAFE_DELETE(writeBuffer)
throw LTException(e.what());
}
};
** CY_RETURN_STATUS cyReturnStatus = LTWrite(mHandle, dataConfig, writeBuffer, 5000U);
Above line always return CY_ERROR_I2C_DEVICE_BUSY and please find attached cyusbserial.dll which I am using for read/write operation.
When I have checked the same thing from Cypress SDK -> Cypress\USB-Serial SDK\examples\usbserialexample\i2cmaster then also I am getting the same error.
Thanks In Advance.
Shailesh Vora.
Show LessWe are developing with the Cypress EZ-USB FX2LP USB Microcontroller and we have to change the .inf file which needs to be re-certified. but there seems to be no good help on the subject we have the .inf, .spt and wdfCoinstaller01011.dll files. I am using visual studio to recompile your drivers, but when we go to the target machine it will not load because they aren't digitally signed. We can run the drivers if we by-pass the digital signature by using the Windows disable of digital signature check. We would not like to do this do very computer we have here and every time we reboot the machine. This driver will only be used in-house.
Show Less