hi
     CyU3PI2cPreamble_t works well if the i2c address is only 2-4 bytes width. but if the register address width is longer than 8 bytes, it is hard to use this structure.
    who know how configure CyU3PI2cPreamble_t if the register length longer then 8 bytes.
for example, if i want to read register address 0x123456789acbde1234,  the value with is 10byes, how to configure?

i tried to separate write/read sequence using following two functions. but cannot work seems due to clock-stretching. who can help here?

CyU3PReturnStatus_t

GW5200_SensorReadNB(uint8_t SlaveAddr, uint8_t *buf, int n)

{

    CyU3PReturnStatus_t apiRetStatus=CY_U3P_SUCCESS;

    CyU3PI2cPreamble_t preamble;

    int i = 0;

  preamble.buffer[0] = SlaveAddr;//0x21;

  preamble.length = 1;

  preamble.ctrlMask = 0x0000;//After the second byte,need to restart the I2C communication

  apiRetStatus = CyU3PI2cReceiveBytes (&preamble, buf, n,0);

  if (apiRetStatus == CY_U3P_SUCCESS)

  {

  IMX390_GW_delay(800);

  }

  else

  CyU3PDebugPrint (4, "GW5200_SensorReadNB failed Error Code = %d\n",apiRetStatus);

#if 1

  CyU3PDebugPrint (4, "read:");

  for(i = 0; i < n; i++)

  {

  CyU3PDebugPrint (4, "0x%x ", buf);

  }

  CyU3PDebugPrint (4, "\r\n");

#endif

  return apiRetStatus;

}

CyU3PReturnStatus_t

GW5200_SensorWriteNB(uint8_t SlaveAddr,uint16_t count, uint8_t *buf)

{

    CyU3PReturnStatus_t apiRetStatus=CY_U3P_SUCCESS;

    CyU3PI2cPreamble_t preamble;

    int i = 0;

  preamble.buffer[0] = SlaveAddr; /* Slave address: Write operation */

  preamble.length = 1;

  preamble.ctrlMask = 0x0000;

  apiRetStatus = CyU3PI2cTransmitBytes (&preamble, buf, count, 0);

  if (apiRetStatus == CY_U3P_SUCCESS)

  {

  IMX390_GW_delay(800); /* known issue for SDK I2C */

  }

  else

  {

  CyU3PDebugPrint (4, "GW5200_SensorWriteNB error!\r\n");

  }

#if 0

  CyU3PDebugPrint (4, "write:");

  for(i = 0; i < count; i++)

  {

  CyU3PDebugPrint (4, "0x%x ", buf);

  }

  CyU3PDebugPrint (4, "\r\n");

#endif

  return apiRetStatus;

}

thanks
xingxing

I have inherited some firmware code for our CX3 chip, which is connected to an OV4689 sensor and streaming video over USB 3 to the PC. The person who wrote the firmware code originally needed to send/receive (3K worth of) camera calibration data over USB, and couldn't figure out how to do that. So, they created separate dma channels to send and to receive "side-band data" to/from the PC. I don't understand this code very well. I would have thought ONE dmachannel, bi-directional, would be enough, but this person created two...

The way it's supposed to work is by handshake. The PC sends a request to the firmware, the firmware processes the request, and sends a reply. The firmware never issues a DMA request to the PC first. This should make it straight-forward.

When the PC sends a request to the CX3, I get notified in the DMA callback. For whatever reason, the programmer wrote it so there is a background, application thread, and when the callback gets called that a DMA buffer was received, an event is set, and the background thread goes and reads the event and does what is necessary (like send calibration data).

The DMA "produced" callback calls DMAChannelGetBuffer( RecvStream ), then reads the packet, then calls DmaChannelDiscardBuffer( ), then sets the event for the background thread. The background thread then calls DmaChannelGetBuffer ( SendStream ), copies the calibration data, then calls DmaChannelCommitBuffer( ).

On the PC side, I've opened up an overlapped IO file handle and am sitting there waiting for reads from the sideband USB channel. No rocket science there.

NOW WHAT IS WEIRD:

If anywhere in the background thread, I call CyU3PThreadSleep(), even with a timeout of just 1, the DMA transfer won't happen. DmaChannelGetBuffer( SendStream ) will sit there and time out! A timeout would seem to imply the send buffer is "busy", but since this is the first packet I'm sending over DMA, I don't see how it could be busy. There is something else weird at work here.

Anybody have any good advice, thoughts?

Hi,The PMODE[2:0] pin is Z11(USB boot)：can find bootload on PC.

    But after I download the img file to the USB RAM,PC can't find usb device.I check the clock,voltage are OK.Is CYUSB3014 chip has system on chip?I buy chip from device vendor.

Hello,

We are using FX3S cypress device (CYUSB3025) which is connected with our Host processor at USB 3.0 interface. The application running on Cypress FX3S device is MSC (mass storage). An eMMC and sd card are connected at the storage ports  of cypress device.

We are getting an random issue with the cypress device.

At few power ups, Host processor do not not detect the cypress device and ultimately no access to eMMC. The issue is observed for 1 out of every 10 power ups.

for debugging, we have seen the UART prints of Cypress device, i have attached the logs of CYPRESS UART for passing and failing case.

The above observation is with firmware version 1.3.1.

We have also updated the Cypress boot image with firmware 1.3.4, but the problem is still there with problem frequency 1 out of 15 power ups.

Please look at the UART pass/fail logs and suggest us that what can be the issue and also how can we debug this issue?

Thanks and Regards

Tarang Jindal

I am using a lauterbach JTAG model LA-3500 DEBUG-USB3 for ARM9 with Denebola board based on CX3.

When I flash my own bootloader in SPI, It is not possible to debug with JTAG  using the following command:

D.LOAD D:\Dev\SmileFW\Bootloader_v2\CX3\Bootloader_v2\Release\Bootloader_v2.elf /NOCODE

On the other hand if the spi is empty (full of 0xff) It is possible to step , put break point .

I don't figure out why it is not possible to debug with SPI flash loaded ?

Hello,

I'm currently trying out the "UsbSpiDmaMode" example and when i try so send data to my sensor, the CYUSB3KIT-003 keep sending data over spi and doesn't stop.

Also the LED2 (the Blue one) keep glowing, but i think that's because SSN is connected to the led.

best regards,

Matthias

Here are questions about FX3 and need Cypress' advice.

-------------------------------------

1. Could  FX3 support line buffer for Streaming Frame? Ex: receive 10 line input via ISP , then output 10 line data directly. Or FX3 need wait a full Frame for output ?

2. If FX3 is frame base buffer (need wait full frame) , what is the output latency ? 1/fps second ?

3. If FX3 could support line buffer , what is the minimum output latency (or how many line)?

4. For FX3 ISO mode, the Throughput(bandwidth) is 82700KBps , around 3GBps. Does it mean the max bandwidth is “streaming  resolution x fps x bit/pixel”? ex: 4656x3496(16M) x 4~5fps x 16bit/pixel (please refer to the attachment, there is a table inside it)

5. Could FX3 support add frame count information for each frame ?

-------------------------------------

Regards,

Kyle