I finally got all the information from the camera supplier and filled the 'Image Sensor Configuration' tab in the CX3 MIPI Receiver Configuration.
When I switch to the 'CX3 Receiver Configuration' tab, I get the two following errors :
Min/Max values don't make sense so I don't know how to fix these errors ?
I still tried to use the resulting configuration but I only get black screen.
Any idea how to make this interface work ?
I have been trying to use NetworkManager together with cypress-fmac-v5.4.18-2021_0527 patches on mainline 5.4.18 kernel. Currently nearly all is working correctly except few issues, which were fixed together with little help from Beniamino Galvani of NM RedHat Team. My issue is in here Hotspot WPA3 support - this is the second half of the issue, because first one was solved with upgrading NM from 1.32 branch to 1.33. In brief, together with Beniamino we have discovered, that the driver is not returning RSN_AUTH_KEY_MGMT_SAE. We suspect that the problem is that the SAE AKM is not set in the NL80211_ATTR_AKM_SUITES netlink attribute by the driver. I have used grep to find it and i did not find any. My question is it possible that all suits are defined in the firmware and is it possible that this specific suite is missing? Is it possible for the cypress team to solve this issue because it is needed by the NM to set a wpa3 hotspot.
Hello Team Infineon,
I am here to ask for your recommendation on
the best dev kit or Evaluation Board that comes with touchscreen kit or
Infineon MCU that can control 3.98 inch LCD touchscreen and more features,
in order to develop touch screen device.
kit / MCU Specifications in need :
-supports LCD : 3.98 inch, 320X480, RGB, 40pin
(client considers ILI9488, a-Si TFT LCD single chip driver : https://focuslcds.com/content/ILI9488.pdf )
-supports 2D graphics acceleration
-supports single touch feature (capacitive)
-supports PWM controllers for buzzer feature for audio
-better than Arm Cortex-M0+
-6x USART, timers
-RAM size : 144kB or better
-Flash size : 256kB or 512kB
-compatible to use NAND flash of size 4~8MB
(in order for the device to support user interface in
three different languages(Korean, Chinese, English))
-preferably has easy development environment to develop the LCD touchscreen device.
The client was considering the following ST-micro MCU before,
because of its simple guidance to the sample project guide.
If you can recommend MCU or/and evaluation board that can support above feature with design guidance for LCD touch device project, that would be greatly appreciated to share it with the client.
As always, thank you for your considerations to help and bring our business forward.
The CC pin and VBUS are exposed when viewed from the outside, such as when Type-C is inserted and removed continuously, and when the connector is first inserted, 5V is momentarily applied to the IC or FET.
As a result, there is a question as to whether it will damage over and over again.Also, they want to know if it has the proof stress to withstand noise such as static electricity. Furthermore, there are only capacitors on the CC pin and VBUS lines.
Q) What is the durability of CYPD3177 regarding the above concerns?
I am trying to use the CYPD3177 over I2C to control a USB-PD SRC. After connecting a USB-PD 100W supply:
- FLIP signal rises from 0 to 3v3
- USBPD Bus rises from 0 to 5V
- Activity on CC pins (assuming successful negotiation)
The hardware seems happy. But i am getting strange results from the I2C reads:
DEVICE_MODE returns 0x95 instead of quoted "always returns 0x92". I've attached the bus transaction.
Other registers such as status, silicon ID return 0 over successful I2C reads. It's like my IC has been disabled for I2C mode.
I've followed the tutorial in the link below to export my configuration to MDK, but when opening the gpdsc file, it said "Cannot read project file 'Project_name.gpdsc'!" in MDK's prompt window.
What should I do next?
MDK version: V188.8.131.52
DAVE version: V4.5.0
Many thanks.Show Less
We are upgrading the communication interface of our peripheal from USB2 to USB3 with an FX3 development kit CYUSB3KIT-003.
This peripheal will be connected to a Windows computer.
In our application, the peripheal must receive packets (size below 512Bytes) at the lowest latency possible (<200us).
Is this latency figure achievable with this configuration?Show Less
I am designing a circuit that uses the CY7C68013A as a USB peripheral controller.
I have a question below.
1. What is the minimum and maximum time from when the reset is released until the D+ pull-up is enabled?
According to "4.2 Enabling Pull-up on D+" in the PDF file at the URL below, it says "the FX2LP enables the pull-up on the D+ once the RESET is deasserted".
What is the minimum and maximum time from reset release until D+ pull-up is enabled?
I'm using CX3(CYUSB3065).
When test using Stremer Program, the USB hub Operates normally.
But Fail occurs when connecting directly to PC.
How can I fix the problem?