USB superspeed peripherals Forum Discussions

Hi,

I'm trying to add C++ files to the sample projects and am getting a linker error when compiling.  In "Tool Settings" there is:

"ARM Sourcery Windows GCC C++ Compiler" (additional Compiler setting)

"ARM Sourcery Windows GCC C++ Linker" (replaces "ARM Sourcery Windows GCC C Linker)

I've tried to copy all the linker settings from the sample C projects, but must still be missing something.

Here is the error:

'Building target: AFProfileSensor.elf'
'Invoking: ARM Sourcery Windows GCC C++ Linker'
arm-none-eabi-gcc -T"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/common/fx3.ld" -nostartfiles -Xlinker --gc-sections -Wl,-Map,AFProfileSensor.map -Wl,-d -Wl,--no-wchar-size-warning -Wl,--entry,CyU3PFirmwareEntry "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyu3lpp.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyfxapi.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyu3threadx.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/arm-none-eabi/lib/libc.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/lib/gcc/arm-none-eabi/4.5.2/libgcc.a" -mcpu=arm926ej-s -mthumb-interwork -o "AFProfileSensor.elf"  ./af_analyze.o ./cyfx_gcc_startup.o ./cyfxtx.o ./cyfxusbenumdscr.o ./cyfxusbspiregmode.o   
./cyfxusbspiregmode.o: In function `main':
cyfxusbspiregmode.c:(.text.main+0xa8): undefined reference to `CyU3PDeviceConfigureIOMatrix'
cyfxusbspiregmode.c:(.text.main+0xb4): undefined reference to `_tx_initialize_kernel_enter'
collect2: ld returned 1 exit status
cs-make: *** [AFProfileSensor.elf] Error 1

**** Build Finished ****

Here is the original good build with only C files:

'Building target: UsbSpiRegMode.elf'
'Invoking: ARM Sourcery Windows GCC C Linker'
arm-none-eabi-gcc  ./cyfx_gcc_startup.o ./cyfxtx.o ./cyfxusbenumdscr.o ./cyfxusbspiregmode.o    -T"C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/common/fx3.ld" -nostartfiles -Xlinker --gc-sections -Wl,-Map,UsbSpiRegMode.map -Wl,-d -Wl,--no-wchar-size-warning -Wl,--entry,CyU3PFirmwareEntry "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyu3lpp.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyfxapi.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/firmware/u3p_firmware/lib/fx3_release/cyu3threadx.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/arm-none-eabi/lib/libc.a" "C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/lib/gcc/arm-none-eabi/4.5.2/libgcc.a" -mcpu=arm926ej-s -mthumb-interwork -o "UsbSpiRegMode.elf"
'Finished building target: UsbSpiRegMode.elf'
' '
cs-make --no-print-directory post-build
'Generate boot-loadable binary image'
'C:\Program Files (x86)\Cypress\EZ-USB FX3 SDK\1.3\/util/elf2img/elf2img.exe' -i UsbSpiRegMode.elf -o UsbSpiRegMode.img
Note: 256 bytes of interrupt vector code have been removed from the image.
      Use the "-vectorload yes" option to retain this code.

' '
'Invoking: ARM Sourcery Windows GNU Print Size'
arm-none-eabi-size  --format=berkeley UsbSpiRegMode.elf
   text       data        bss        dec        hex    filename
  82536        660      11588      94784      17240    UsbSpiRegMode.elf
'Finished building: UsbSpiRegMode.siz'
' '

**** Build Finished ****

Which .a file contains CyU3PDeviceConfigureIOMatrix?

Thanks for any help.

Hello

Thank you for all your help.

We are going to use the CYUSB2014 part.  Now Pins A2 and B5 were previously USRXVDDQ and USTXVDDQ in the CYUSB301X parts.  Now in the CYUSB2014 part these pins are VDD so they just hook up to the core Voltage, 1.2V correct?

Now in the app note AN70707 the USRXVDDQ and USTXVDDQ had an individual inductor for each pin and a 22uF and .1uF for each pin.  Do I still need this for the A2 and B5 pins for the CYUSB2014?  I would think not but wanted to check with you.

Thank you
Gary

Sorry if this is a repeat question as I could not find the answer here.

I guess this is one easy thing to fix but I didn't get the clue...

My FX3 board works perfect when using stand alone but using it with my evaluation board (Xilinx Kintex Ultrascale, KCU-105) Both "USB Serial" Interfaces are available at the Control Center but not the programmable interface. In Addition the reset Switch (SW1) didn't seem to work anymore.

So I programmed the SRAM example (SRAM FX3.img) into RAM and I2C Eeprom but no changes so I guess it's not a problem with some initialization or wrong code.

Maybe someone know what's wrong with this situation or at least why my FX didn't work? The KCU-105 starts up with the default firmware that makes some LED animations. It looks like the programmable part of the FX3 board is held in reset somehow but I have no idea why.

Hello, 

As the Subject, I've checked the FX3 datasheet,TRM,... but couldn't find the the maximum operating current of CVDDQ line. 

Please tell me if you got any documents to check out the I (CVDDQ)

Best Regards,

Tran.

Hi:

What's the relationship between the exposure value and gain value  for OV5640 in manual exposure mode? Is the  gain value independent of the exposure value if I turn off AEC/AGC?

If  I want to get best SNR for image ,that is reduce the gain value  and increase the exposure time manually,what should I do?

I understand I set the requested USB power levels in the configuration descriptors.

My FX3 has a requirement to turn on some additional hardware once the requested power levels are granted: how do I tell when that has happened?

Are there events/callbacks for that, or can I read certain registers for it?

Dear all,

My project is about communication between PC and FPGA. Previously, all things works well. However, this afternoon, the system broke down suddenly. When debugging, I found that I cannot implement loopback example (from AN65974) any more, which always succeeded previously. However, when I connect FX3 to USB2.0 ports, it still works.

Then I wonder if a certain pin of USB3.0 failed. So I test the bulkloopauto example via USB3.0 port. It still works. I have no idea where is the problem, could someone give me some suggestions to narrow down the problem.?

Thank you very much.

Best Regards

Zoe

Hi,

We currently have e-con systems board with CX3 and OV5640. We are interested in switching to another Omnivision sensor, preferably OV4689. Has anyone done that before and can give me some pointers, especially on the coding/firmware side.

Thanks,

What should I do when I want to use some other still image capture methods for OV5640?

How many  Still image capture methods can be  supported for OV5640?

Can I use an gpio signal(hardware method) to trigger a still image capture?

Thanks for help.

Richy