USB low-full-high speed peripherals Forum Discussions
Hi,
I am using CYUSBS236 USB-serial development Kit.
When I run the example UART code given in the ISO file from "www.cypress.com/go/CYUSBS236" the function "CyGetDeviceInfoVidPid" returns a device type "5" which corresponds to a device in "Manufacturing mode"
typedef enum _CY_DEVICE_TYPE {
CY_TYPE_DISABLED = 0, /*Invalid device type or interface is not CY_CLASS_VENDOR*/
CY_TYPE_UART, /*Interface of device is of type UART*/
CY_TYPE_SPI, /*Interface of device is of type SPI */
CY_TYPE_I2C, /*Interface of device is of type I2C */
CY_TYPE_JTAG, /*Interface of device is of type JTAG*/
CY_TYPE_MFG /*Interface of device is in Manufacturing mode*/
} CY_DEVICE_TYPE;
I would like to configure the development board (CY7C65215) in UART mode (I have already configured SCB0 in UART mode) to be able to use UART specific functions.
/*
Summary
This API is used to retrieve the information of all devices with specified Vendor ID and Product ID.
Description
For a given VID and PID, the API returns deviceIdList and deviceInfoList.
The deviceIdList contains the device numbers of all the devices with specified VID and PID.
Using deviceInfoList application can identify the device of interest.
Information that is provided includes interface number, string descriptor, deviceType and deviceClass.
Return Value
* CY_SUCCESS on success else error codes as defined in the enumeration CY_RETURN_STATUS.
* CY_ERROR_REQUEST_FAILED on if library is not initialized (Only for Linux and Mac)
* CY_ERROR_INVALID_PARAMETER if the input parameters are invalid.
* CY_ERROR_DEVICE_INFO_FETCH_FAILED if failed to fetch device information.
* CY_ERROR_ACCESS_DENIED if access is denied by operating system.
* CY_ERROR_DEVICE_NOT_FOUND if specified device number is invalid.
See Also
* CY_DEVICE_INFO
* CY_DEVICE_CLASS
* CY_DEVICE_TYPE
* CyGetListofDevices
* CyGetDeviceInfo
* CyOpen
* CyClose
*/
CYWINEXPORT CY_RETURN_STATUS CyGetDeviceInfoVidPid (
CY_VID_PID vidPid, /*VID and PID of device of interest*/
UINT8 *deviceIdList, /*Array of device ID's returned*/
CY_DEVICE_INFO *deviceInfoList, /*Array of pointers to device info list*/
UINT8 *deviceCount, /*Count of devices with specified VID PID*/
UINT8 infoListLength /*Total length of the deviceInfoList allocated
(Size of deviceInfoList array)*/
);
Thank you for your help.
Show LessHello,
In my company, we are producing keyboards using CY7C63413C controler.
Until now, we programmed them with CYPRESS USB PROGRAMMER FOR STARTER (CY3649). Unfornately it seems to don't work anymore and I can't find where to buy a new one online.
Do you know if I can buy a new one ? Or maybe which new programmer can I use ?
Many thanks for your quick reply, we are actually blocked du to this failure,
Best Regards,
Benjamin Recoules
Show LessHello
After programming the program using the USB "Control Center",
Could you tell me how to check that the program was correctly rewritten by Control Centor?
Best Regards
Arai
Show LessHello,
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 Less