I've got some code I've been writing that I now want to convert over to be able to upgrade Over The Air.

The code has the BLE component set up as a Client and Server profile.  The Client profile is configured with a Current Time Service, to enable syncing of the time in my code whenever it is accessed via a central device.  In the Server profile, I've got various custom services along with all the normal ones (Device Information, Generic Attribute, Generic Access, etc).

The Server profile is also set up to stuff some data into the Scan Response Packet, to make it easier to get data across to the Client without requiring a connection.  Connection is reserved for firmware updates (if I can get this to work!)

The code, as a non-OTA arrangement, compiles and works fine.  Until I attempt to convert it over to an OTA Fixed Stack Bootloadable version.  I've done this before, just not with the CTS functionality included, and its always worked.  I've followed all the steps outlined in the OTA Guide (AN97060), but I'm still not getting the Bootloadable code to compile.  Its throwing up a bunch of errors associated with the CTS functionality, even though I've made sure I've included the appropriate header files, etc.

The particular things its getting errors on are:

• CyBle_GetClientState()
• CYBLE_CLIENT_STATE_DISCOVERED
• cyBle_ctsc

I can see that these are all defined in the Bootloader source code (in BLE_eventHandler.h & BLE_cts.c and BLE_cts.h), but for whatever reason, my Bootloadable code isn't seeing them.

Any ideas what I'm doing wrong??

Cheers,

Mike

I made a custom board consisting of a CYPD3125 controller.

The board shall be the preferred power supply to a tablet connected via USB type-c. In case the boards external supply is down the tablet shall power the board. So the board with the CYPD3125 must be either source or sink.

The firmware is based on the notebook project that has already all main functions.

Now the problem is that the producer FET is never turned on. I only measure ~150mV.

Does anyone have an idea?!

Please find the attached screenshot of the schematic.

Hi

   I found a strange problem. The ifclk pin of cy7c68013A has output working with the driver of CY3684 EZ-USB FX2LP Developmeng kit(the chip VID is 04B4 PID is 8614, same as in inf file), while ifclk pin has no output when I install the driver of cyusb3.sys(the VID and PID is modified as 04B4 8614 in cyusb3.inf).

  Is appears that the iclk pin has output when the chip is powered on(VID 04B4 PID 8614), and no installing cyusb3.sys, if the driver of cyusb3.sys is installed, the output will be disappeared after a few seconds. Is there any limition in cyusb3.sys? How to fix it?

I have a Windows 10 machine and am logged in as Administrator, and I get to the end of what appears to be the complete installation of the ModusToolbox, pressing finish, but I get an error message:  Unable to execute file.  ShellExecuteEx failed: code 5, access denied

Hi,

Could you please help me with Schematic and firmware design support to drive Segment LEDs using the PSoC 5LP chip?
We have to drive a seven-digit seven segment display with various segment current from 16-bit serial input.

Regards,

Mari 

Hi Gents,

 This question is in reference to https://www.cypress.com/documentation/application-notes/an60317-psoc-3-and-psoc-5lp-i2c-bootloader

When I try and run the provided API it errors on the Bootloader Version replied back by the PSOC3 we use.

The PSOC3 is replying back with the bytes 60,1,1. Whereas, the API is looking for 0x000000 :

int CyBtldr_StartBootloadOperation_PSoC3(unsigned long expSiId, unsigned char expSiRev, unsigned long* blVer)
{
const unsigned long SUPPORTED_BOOTLOADER = 0x000000;

[...]
}


Why is the API looking for 0x000000 when the PSOC3 bootloader is hardcoded with 60,1,1 ?!

Hi,

I worked through the UVC example and got video streaming working.  I then worked through the GpifToUsb example and got data read out working.  Now I am trying to merge them and continuously read out data from an ADC without dropping data.  To do this, I began with the GpifToUsb example and added a simple GPIF project with two threads (0,1):

Next, I added a MANY_TO_ONE auto DMA channel to GpifToUsb:

    //try creating a many to one dma channel
    CyU3PDmaMultiChannelConfig_t dmaMultiConfig;
    CyU3PMemSet ((uint8_t *)&dmaCfg, 0, sizeof (dmaMultiConfig));
    dmaMultiConfig.size           = CY_FX_DMA_BUF_SIZE;
      dmaMultiConfig.count          = CY_FX_DMA_BUF_COUNT;
      dmaMultiConfig.validSckCount  = 2;
      dmaMultiConfig.prodSckId [0]  = (CyU3PDmaSocketId_t)CY_U3P_PIB_SOCKET_0;
      dmaMultiConfig.prodSckId [1]  = (CyU3PDmaSocketId_t)CY_U3P_PIB_SOCKET_1;
      dmaMultiConfig.consSckId [0]  = (CyU3PDmaSocketId_t)(CY_U3P_UIB_SOCKET_CONS_0);
      dmaMultiConfig.prodAvailCount = 0;
      dmaMultiConfig.prodHeader     = 0;                 /* 12 byte UVC header to be added. */
      dmaMultiConfig.prodFooter     = 0;                  /* 4 byte footer to compensate for the 12 byte header. */
      dmaMultiConfig.consHeader     = 0;
      dmaMultiConfig.dmaMode        = CY_U3P_DMA_MODE_BYTE;
      dmaMultiConfig.cb 			= NULL;
      dmaMultiConfig.notification   = 0;
      //dmaMultiConfig.notification   = CY_U3P_DMA_CB_CONS_SUSP; // CY_U3P_DMA_CB_PROD_EVENT | CY_U3P_DMA_CB_CONS_EVENT;
      //dmaMultiConfig.cb             = GpifToUsbDmaCallbackMulti;
     
      	  apiRetStatus = CyU3PDmaMultiChannelCreate (&glDmaChHandleMulti, CY_U3P_DMA_TYPE_AUTO_MANY_TO_ONE,
              &dmaMultiConfig);
      if (apiRetStatus != CY_U3P_SUCCESS)
      {
          /* Error handling */
          CyU3PDebugPrint (4, "DMA Channel Creation Failed, Error Code = %d\n", apiRetStatus);
          CyFxAppErrorHandler (apiRetStatus);
      }

The result is:

USB event: 11 0
About to connect to USB host
USB event: 0 1
CY_U3P_USB_EVENT_CONNECT detected
CyFxApplnInit complete
USB event: 8 0
USB event: 5 1
setting up dma
              DMA Channel Creation Failed, Error Code = 64

Any idea what I'm doing wrong?  

About CX3 Control center

Hi,

I'm using ADC component of CYBLE-416045-02 MCU. I have 4 analog pins which needs to be attached on 4 separate ADC channels but its showing me analog internal routing error. For the time being I'm using an internal mux like shown in the picture, but i want to use 4 different  channels of the ADC and not through internal mux.Please help.