PSoC™ 4 Forum Discussions

1. Preference

- Windows10

- PSoc Creator 4.1 ~ 4.2

- MCU : CY8C4247LQI-BL473, CY8C4248LQI-BL583 (CY8CKit-042-BLE-A Pioneer board)

   ( Selected correctly in Device Selector depending on MCU at PSoc Creator)

- Example Source : BLE_FindMe (PSoc Example source)

- bluetooth Android APP : CySmart

2. Problem : "CY8C4247LQI-BL473" board Bluetooth not working ( I make pcb board for PSoc4 MCU -> CY8C4247LQI-BL473 assembled )

- "CY8C4248LQI-BL583" bluetooth working good (CY8CKit-143A Board)

3. PCB Bluetooth antenna test : Bluetooth antenna works well

4. Schematic

5. "CY8C4247LQI-BL473" board's function working well except bluetooth (IO, Timer, UART, Input Interrupt )

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

thanks

Hello all-

I have technial question regarding Cypress semiconductors.  That I hope I can get some clarity on. 

I was given a custom made device supporting Bluetooth 4 standard BLE.  The device has the Cypress BLE semiconductor built in and we are  have a Cypress USB dongle for accessing and connecting to it, this one:

http://www.cypress.com/documentation/development-kitsboards/cy5670-cysmart-usb-dongle

The connection and communcation is setup up with Bluetooth 4.0. 

The device is programmed in central mode and the dongle is configured in peripheral mode.  The connection between the processor and BLE module is a universal "pass-through" type of link (RS232).

I have been asked to build a mobile application (Android & iOS) that can be programmed as a peripheral to replicate the actions of the dongle.  My question is what are some of the minimal requirements needed to pass with my peripheral advertisments? And how will the connection will be made. I have an app developed and advertising but I am not sure what advertising data needs to be discovered by the device for the semiconductor. 

I have some screenshots of the Profile and GAP settings that the USB dongle was programmed in.  I also have PSOC programmer and CySmart installed along with the actual dongle.  I am trying to replicate the same settings within my mobile application but I cannot tell if the device is discovering it.  Here is a look at the data I passing for Advertisement:

{

      service: "CDD0",

      name: "BLE_Serial",

      characteristics: [

        {

          uuid: "CDD1",

          permissions: {

            read: true,

            write: true,

            //readEncryptionRequired: true,

            //writeEncryptionRequired: true,

          },

          properties : {

            read: true,

            writeWithoutResponse: true,

            write: true,

            notify: true,

            //indicate: true,

            //authenticatedSignedWrites: true,

            //notifyEncryptionRequired: true,

            //indicateEncryptionRequired: true,

          }

        },

        {

          uuid: "CDD2",

          permissions: {

            read: true,

            write: true,

            //readEncryptionRequired: true,

            //writeEncryptionRequired: true,

          },

          properties : {

            read: true,

            writeWithoutResponse: true,

            write: true,

            notify: true,

            //indicate: true,

            //authenticatedSignedWrites: true,

            //notifyEncryptionRequired: true,

            //indicateEncryptionRequired: true,

          }

        }

      ]

    }

Overall, is this effort actually feasible or is there limitations with the semiconductor that would prevent this from working?  And have anything similar to this been done before?   Any information anyone can provide would be greatly appreciated.  I feel this is possible but I also dont want to keep spinning my wheels.

Thanks all in advance.

Ron

I have a project that's based on the Upgradable Stack Example. Everything is working fine and dandy, but now I need to write project data (password hashes, configuration data, etc) in the flash that would be outside the OTAble range and would be retained in FW update.

How can I modify the areas of the bootloader images? There seems to be some kind of project data section in the example (page 4 of the example doc pdf), but I cannot find any references to it in the example project or in the linker script.