One page for TopDesign.cysch ist too small for my project. The properties of the file (right mouse click)gives me page count of 1. I can not change this value by typing a  "2" nor + or anything else. Is it possible to have a bigger page or two pages for the schematic ? 

Hi, 

I made my custom board(FX3 and Camera Module).

I connected it and wrote my custom source code.

The black screen was printed in AMCAP, so I checked the debug message with wireshark.

The Wireshark confirmed that the data was output.

The resolution is 340(W) x 260(H), 30fps and 12bit data output.

You can see data in wireshark log.

• wireshark log  => ((16380 * 10) + 13292=177,092     
• resolution  =>  340*260*2 = 176,800
• difference => 177,092 - 176,800 = 292
• As above, additional buffers are entered, and it is necessary to check if there is a problem with the code.

I tried to change DMA Buffer size(CY_FX_EP_BULK_VIDEO_PKT_SIZE and CY_FX_EP_BULK_VIDEO_PKTS_COUNT ) in uvc.h

If i change buffer size, the buffers in the data packet are output differently.

Regards,

Jay

Hi

I am developing a firmware that streams data  at 1080p@30 fps, I have  attached the parameters given I am not able to do streaming , the project is also attached , Is there any wrong configuration setting.

Thanks in Advance

Hello,

in my application, I have a lithium battery.

the system is powered when USB is pluging in and a specific IC charge the battery?

the IC charger has two differents set up: 1:  limit the current at USB specifications (100 mA and 500mA after enumeration) and 2 :boost current more than 500mA (max 1800mA) when the USB cable is connect to a wall adapter.

I need to kown, when  this two different stage happen

_ when enumeration is ok and USB port can send 500mA

_when the USB cable is connect to a wall adapter.

is there fonctions in the API of the USBFS component that can handle that.

Our firmware is monitoring a fault gpio line from a load switch that is asserted when a connected device is faulting and pulling too much current. If fault condition does not clear within certain time I call app_disable_pd_port() to disable further activity on the port. 

After a delay and when the fault flag has cleared I want to enable the port again. What is the correct way to do this? There is no symmetric API call to enable the port.

We're using CYPD5225-96BZXI. Source mode only.

Hello all,

I have a custom FX3 board with S25FS064S. I programmed the spi flash via control center. I changed the PMODE[0:2] 11F to 1F0 to enable boot from spi flash. When i program a new flash, FX3 can boot from the flash. But when i want to change the img file in the flash, FX3 can't be programmed anymore. I tested the img files with a evaluation board and it worked well with both of the img files. What could be the problem?

Best Regards 

Hello

in my application the charger IC always feed the system and "disconnect" the battery when the charging process is finish.( ofr keeping a long life battery with less cycle)

So for my understanding, when a USB cable is plug into my device, my system is ALWAY bus powered.

Do I have to set my USB device as a self powered device, and just after the configured state, change into bus powered device ? or directly as a bus powere device ?

What about the hardawe configuration ? do i need external resistance for pull up or I just use the internal pull up resistance on D- and d+

Hello,

I am trying to read data from ADC. If I probe signal lines with a logic analyzer, I can see actual samples (with their respective headers). If I look at data read by SPI slave peripheral using a debugger, I just see some meaningless numbers. Do I have a mismatch on CPOL/CPHA?

CY_ISR_PROTO(RxC1);
CY_ISR_PROTO(RxC2);
void SendData();

uint8_t Data1[32] = {0};
uint8_t Data2[32] = {0};
uint8_t Ptr1 = 0;
uint8_t Ptr2 = 0;
volatile uint8_t Ready1 = 0;
volatile uint8_t Ready2 = 0;
uint32_t Channels[10] = {0};
uint8_t Usb[40] = {0};

void ADCData_Init()
{
    Data1_RxC_StartEx(RxC1);
    Data2_RxC_StartEx(RxC2);
    SpiData1_Start();
    SpiData2_Start();
}

CY_ISR(RxC1)
{
    while(SpiData1_ReadRxStatus() & SpiData1_STS_RX_FIFO_NOT_EMPTY)
    {
        uint8_t dummy;
        if(Ptr1 < 32)
        {
            Data1[Ptr1++] = SpiData1_ReadByte();
        }
        else
        {
            dummy = SpiData1_ReadByte();
            if(dummy < 0xFF)
            {
                Data1[0] = dummy;
                Ptr1 = 1;
            }
        }
        if(Ptr1 == 32)
        {
            Ptr1++;
            Ready1 = 1;
            if(Ready2)
            {
                Ready1 = 0;
                Ready2 = 0;
                SendData();
            }
        }
    }
}
CY_ISR(RxC2)
{
    while(SpiData2_ReadRxStatus() & SpiData2_STS_RX_FIFO_NOT_EMPTY)
    {
        uint8_t dummy;
        if(Ptr2 < 32)
        {
            Data2[Ptr2++] = SpiData2_ReadByte();
        }
        else
        {
            dummy = SpiData2_ReadByte();
            if(dummy < 0xFF)
            {
                Data2[0] = dummy;
                Ptr2 = 1;
            }
        }    
        if(Ptr2 == 32)
        {
            Ptr2++;
            Ready2 = 1;
            if(Ready1)
            {
                Ready1 = 0;
                Ready2 = 0;
                SendData();
            }
        }
    }
}

We have a product that uses the CYBLE-012011-00 with EZ-Serial 1.1.1 that is experiencing issues when sending data over CYSPP.

We are seeing an intermittent issue where it seems the module stops forwarding the data sent to it over UART while in CYSPP mode when connected to an Android Phone (OnePlus 7T Android 10).  Usually, the first 2 or 3 packets sent over UART after sent over BLE but after that, there are no more packets. The module is not completely non-responsive, when the phone doesn't respond to the CYPSS packets, we enter API mode to disconnect which works and then we reenter CYSPP mode awaiting connections. Following connection attempts from the phone do not work either.  I have verified that we are sending the same data over UART for the working and failing cases.

I have captured Wireshark logs a successful connection attempt and failing attempt and nothing stood out to me, an example of both is attached taken using the nRF sniffer firmware. See attached images (couldn't attach pcapng)

We do not see this issue when an nRF product connects to our Cypress module. Sometimes after the nRF product has connected, sent data and disconnected, the following phone connection works.

Is this issue related to 274727 mentioned here?

We are in the process of testing this on other Phones.