I was able to use CyUsb.dll in C# project and successfully communicate with FX2LP device.
I would like to know the steps to communicate with FX2LP device using Python.
This communication is required for some test automations.
I found a similar question asked in below thread.
Our charger product is using the Cypress USB-Serial communication module to connect charger to PC for communication. We used the Cypress drivers and added USB PID/VID info into the drivers files in order for PC to recognize our chargers.
We are facing intermittent PC getting Blue Screen of Death (BSOD) when disconnecting USB cable from PC. The issue happened especially if the charger is connecting through a USB hub (Belkin).
Please advise any solution to solve the issue?
My PC is running on Windows 10 Professional.
AN15456-Guide to a Successful EZ-USB® FX 2LP ™ Hardware Design for 3.3 testing below
They are thinking of checking the operation on the board equipped with FX2LP according to the following test items, but could you please tell me the detailed test procedure for each test item?
Any USB reset circuit should be thoroughly tested. The following tests are recommended:
▪ Cold power up, plugged into USB
▪ Cold power up, unplugged from USB
Q1) There is a Cold power up in the state at the time of the above test, but please tell me specifically what kind of state it should be before plugged and unplugged.is it ok to think that it mean that only the FX2LP board is powered off before plugged/unplugged?
Q2) Also, please tell me specifically what to check after plugged and unplugged.
▪ Hibernate / resume, plugged into USB
Q3) Please tell me the specific test procedure for the above.
▪ Power cycle, plugged into USB
Q4) Please tell me the details about Power cycle. Also, please tell me the specific test procedure above.
Best RegardsShow Less
We are use CY7C65211 on our system.
But our system has low power requirement for USB ports.
Does CY7C65211 meet below mention of LPM & BESL support?
我从8051发了数据到PC，在EP6IN看到的数据是对的，但是我在PC看到的是ffffffff... ； 我重新从8051再发一次相同数据到PC后，EP6IN和PC的数据就都是对的了，也就是说我需要发两次请求才可以得到想要的数据。于是我就想了一个方法，第一次先arm一个不使用的EP（比如EP2IN）,再arm真实需要的EP6IN就可以在PC只得到想要的数据了（不会有第一次的ffffff数据）。能帮忙分析一下是因为什么问题吗？如果可以的话麻烦留个邮件地址以便及时和您沟通，谢谢。Show Less
As per KBA89285 I found these register address 0xE507 to 0xE50C holds unique id but I am getting same id for each Cypress FX2LP controller . I have used following methods to declare in header file and these variable are used in main file used directly
// Unique ID
EXTERN xdata volatile BYTE UNIQUEID1 _AT_ 0xE507; // UID1
EXTERN xdata volatile BYTE UNIQUEID2 _AT_ 0xE508; // UID2
EXTERN xdata volatile BYTE UNIQUEID3 _AT_ 0xE509; // UID3
EXTERN xdata volatile BYTE UNIQUEID4 _AT_ 0xE50A; // UID4
EXTERN xdata volatile BYTE UNIQUEID5 _AT_ 0xE50B; // UID5
EXTERN xdata volatile BYTE UNIQUEID6 _AT_ 0xE50C; // UID6
is it right method?
- or Any other methods are available for reading unique id in fx2 ??
I need to program CY7C64315 using just USB connector (D+ and D-).
Is it possible to connect ISSP DATA (P1_0) and ISSP CLOCK (P1_1) to USB line D+ and D-?
Any suggestion to do that?
I didn't connect for fear of chip damage.
I'll not use ISSP DATA (P1_0) and ISSP CLOCK (P1_1) as I/O in my project. They will be used only to program the chip.
Any advices are welcome.
Is there any USB microcontroller Full Speed at Cypress family where I can use the D+ and D- to program the firmware into the chip?
I need just 4 digital GPIO for my project, but its important to program the chip using USB conector (D+ and D-) as I did with Low Speed Encore II microcontroller.
We intended to configure CY7C65213 as self-powered mode. Other than the schematic connection shown below, the datasheet also says
"Using the configuration utility, the configuration descriptor in the
CY7C65213/CY7C65213A flash should be updated to indicate
that it is self-powered."
My question is: Can the internal flash be accessed and set after the circuit is connected this way? Especially the default power mode in the flash is bus-powered. Thanks.
How does the power mode in the flash affect the chip behavior? Is it just for information purpose, or it changes the chip's function?