I would like to put the XRST pin in high with the following function: CyU3PMipicsiSetSensorControl (CY_U3P_CSI_IO_XRES, CyTrue); but when I call any function that contains Mipi I get the following error:
Does anyone have any idea why? thank you
We want to use CyU3PMipicsiSetSensorControl(CY_U3P_CSI_IO_XRES,CyTrue); in the BootLedBlink example main.c line 83.
We attached also the source code .The result when compile is:
*** Incremental Build of configuration Debug for project BootLedBlink ****
'Building target: BootLedBlink.elf'
'Invoking: Cross ARM C Linker'
arm-none-eabi-gcc -mcpu=arm926ej-s -marm -mthumb-interwork -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall -g3 -T "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_build/boot_fw/cyfx3.ld" -nostartfiles -Xlinker --gc-sections -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/boot_lib/1_3_3/lib" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\ARM GCC\/lib/gcc/arm-none-eabi/4.8.1" -L"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\ARM GCC\/arm-none-eabi/lib" -Wl,-Map,"BootLedBlink.map" -Wl,-d -Wl,-elf -Wl,--no-wchar-size-warning -Wl,--entry,Reset_Handler -o "BootLedBlink.elf" ./I2C.o ./cyfx_gcc_startup.o ./main.o -lcyfx3boot -lcyu3mipicsi -lc -lgcc
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiRegisterRead':
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterRead+0x54): undefined reference to `CyU3PI2cReceiveBytes'
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterRead+0x68): undefined reference to `_tx_thread_sleep'
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiRegisterWrite':
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterWrite+0x50): undefined reference to `CyU3PI2cTransmitBytes'
cyu3mipicsi.c:(i.CyU3PMipicsiRegisterWrite+0x64): undefined reference to `_tx_thread_sleep'
C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/fw_lib/1_3_3/fx3_debug\libcyu3mipicsi.a(cyu3mipicsi.o): In function `CyU3PMipicsiSetSensorControl':
cyu3mipicsi.c:(i.CyU3PMipicsiSetSensorControl+0xbc): undefined reference to `_tx_thread_sleep'
c:/program files (x86)/cypress/ez-usb fx3 sdk/1.3/arm gcc/bin/../lib/gcc/arm-none-eabi/4.8.1/../../../../arm-none-eabi/bin/ld.exe: BootLedBlink.elf: hidden symbol `CyU3PI2cReceiveBytes' isn't defined
c:/program files (x86)/cypress/ez-usb fx3 sdk/1.3/arm gcc/bin/../lib/gcc/arm-none-eabi/4.8.1/../../../../arm-none-eabi/bin/ld.exe: final link failed: Bad value
collect2.exe: error: ld returned 1 exit status
cs-make: *** [BootLedBlink.elf] Error 1
12:55:48 Build Finished (took 2s.213ms)
How can we use this function in bootledblink example?What do we have to include or to configure?
Thanks in advance!
I am developing an oscilloscope in-house. Currently, I am working on the Texas Instrument's ADS54J60evm and TSW14J56evm boards. My end goal is to display and format at least 500K samples captured.
Now, I had been using HSDC GUI to display the captured data from the TSW board; but due to fairly low number of samples displayed on HSDC GUI, I need to switch to a custom based GUI.
So, my first step is to capture the data from the CYUSB301X available on the TSW14J56evm board. Is it possible if you can share with me the python files or the way CYUSB301X is sending the data to the HSDC GUI?
We use FPGA+CYUSB3014 for image capture and the register of camera are controlled by IIC port of CYUSB3014.
Recently we found that the speed of IIC is much lower in WIN 10 system than in WIN 7 system. Maybe more than ten times.
Any experience for this problem, please tell me the reason.
I am interested in using the Cypress FX3 as a mechanism to communicate with our FPGA. I basically need a method for two communication platforms:
1. FPGA will stream data out to an ARM processor connected via USB (through the Cypress FX3)
2. ARM processor needs to be able to read some registers (BRAM) on the FPGA through the same USB link and be able to set some registers (BRAM) to dictate what the FPGA will stream out.
I am following the information in the document AN65974 - Designing with the EZ-USB® FX3™ Slave FIFO Interface (cypress.com) and I can see that there is a pathway for me to do #1. The "FX3 Slave interface" described in an example like below seems to be a way of me to transfer data out of the FPGA using the "EP1_IN" interface.
However, what I am wondering is how to implement #2 - it is certainly possible to do it via some sort of opcode based protocol using EP1_OUT but what I risk doing in that respect is now data in EP1_IN is containing different streams of input data sources that need to be multiplexed in the USB Host (the ARM Core).
Is there perhaps a more elegant solution to do what I am describing? I saw that there is capability for an I2C and SPI interface on the FX3, but I am not too sure what this refers to. Does this appear like a SPI or I2C interface to the FPGA? Something like that could work - so the I2C/SPI interface is used as my #2 requirement.
Thanks for the help!
I want to send Bulk data as well as interrupt data through FX3 device Can i implement it in CYUSB3014?
This may have been placed in the wrong area but I am sure that will get figured out.
As the title says we are developing on a Cypress CX3 chip that we are viewing issues on that has been designed to be used as a camera board with 2 LED's. The board is set up with a USB-C connector. We are attempting to have a powered usb hub connect to the device and allow the host computer to trigger the hub to power up and stream images. However during a specific power up sequence the camera device will get locked into an unknown state and be unable to stream images. However we are able to see the device in the tree and still issue vendor commands.
How to reproduce the problem:
Using a powered hub we are able to 100% reproduce the issue by using the following steps ONLY with usb C to C cables. We cannot reproduce with C to A:
1. plug device into UNPOWERED USB hub w/ usb C to usb C cable
2. plug hub into UNPOWERED laptop w/ usb C to usb C cable
3. plug in power to usb hub
3. power on laptop
Data and information collected:
1. The device appears to get some sort of power to the CX3 chip on the order of 80mV and we have an LED attached to the device reset call that *appears to attempt to start a reset but does not complete*. This is an assumption. During normal operation we would have the laptop turned on. We would plug the device into the laptop and see a full white LED pulse and have the device do its reset.
2. Issuing a hard reset over I2C will reset the device and fix the issue. But we need to find out what is causing the issue and prevent it or understand why it is happening
3. Connecting UART into the device during the initial start up allows me to see the following dma errors:
4. Attempting to manually initialize the device through the API calls for the mipi and device initialization via a vendor command does not fix the issue.
5. Placing delays in the startup of the code does not prevent the initial startup from happening during power up of the hub
Any help or insight into how we could potentially get closer to our solution would be very appreciated. Thank you for your time and please let me know if I can provide any additional information to provide a more clear description of our issue.
I have a basic setup working great with the FX3 when operating in synchronous master mode with internal clock settings. But, my data source always has the clock running from the start, so PCLK is always receiving a clock and data.
(Master/Slave) Either causes crash
The moment the GPIF bus is loaded, the processor freezes. Sometimes it gets as far as calling a `CYU3P_PIB_INTR_DLL_UPDATE` before freezing. It's always after load. I've tried springboarding into a loop of DATA_IN that doesn't actually write the data but nothing I do seems to prevent the device from freezing except discontinuing the clock.
Is there a way to suppress the PCLK pin until everything else is setup and ready to roll, like the state machine is started? Or anything else I can do to prevent the chip from seizing up when unsolicited data is flowing in?
BTW - as soon as I switch around to internal clock writing out, everything works 100% as expected.Show Less
I'm a newbie so my question might sound trivial.
I'm trying to get my ARM-USB-TINY-H to debug through jtag a cypress FX3 on a custom board.
I've succeeded to flash out an example to the FX3 using the USB3 connection, but it doesn't have debug capabilities.
can anyone point me to the right direction on how to get it to work?Show Less
We are working on a MFi (Made For iPhone) product that is embedding during the development phase a Cypress CYUSB3KIT-003 EZ-USB® FX3™ SuperSpeed Explorer Kit (https://www.cypress.com/documentation/development-kitsboards/cyusb3kit-003-ez-usb-fx3-superspeed-exp...). Our final product will use the FX3 chip. We are interested in discussing about your product CY8CKIT-033A PSoC® 3 MFi (Made for iPod® | iPhone® | iPad®) Digital Audio Development Kit for Lightning™ (https://www.cypress.com/documentation/development-kitsboards/cy8ckit-033a-psoc-3-mfi-made-ipod-iphone-ipad-digital-audio) and how you are handling IAP2 protocol on this board.
Thank you for your answer and have a nice day.