PSoC™ 4 Forum Discussions

Hi. I am working with the CY8CKIT-042-BLE kit using PSOC 4 and 4.1 but what I see is that my kit has a BLE 4.1 whereas I cannot find a BLE 4.1 module either PSOC 4 or 4.1. All I see is either a BLE Smart Module or a BLE Smart 4.2 module. So, how do I add the BLE 4.1 module in my design ?

Hi everyone,

in my project i use two generic event handler create from myself and the DIS service.

In my main.c , i start with CyBle_Start(MygenericEventHandler1).

I want to register MygenericEventHandler2 and the Dis Service.

How can i do that ?

I see the function "CyBle_DisRegisterAttrCallback" but what do i put in ()?

Thanks for your advice.

For the fixed stack OTA bootloader it seems like if I don't use a BLE API function in the 'loader' project, it gets removed and is not available in the 'loadable' project, is this correct? We're using a 128k device and if I set 'remove unused sections = false' I get a ROM overflow condition.  My workaround is to just put the BLE functions I need in a block that won't execute in the 'loader' project, then they will be available in the 'loadable'.  Is this the right approach or am I missing something here?

Thanks,

Eric

The definition of this structure is: 

typedef struct

{

/** Advertisement event type

    - Connectable undirected advertising = 0x00

    - Connectable directed advertising = 0x01

      - Scannable undirected advertising = 0x02

      - Non connectable undirected advertising = 0x03

      - Scan Response = 0x04

    */

CYBLE_GAPC_ADV_EVENT_T eventType; 

/** bd address type of the device advertising.

- CYBLE_GAP_ADDR_TYPE_PUBLIC

- CYBLE_GAP_ADDR_TYPE_RANDOM

- CYBLE_GAP_ADDR_TYPE_PUBLIC_RPA

- CYBLE_GAP_ADDR_TYPE_RANDOM_RPA

    */

    uint8      peerAddrType;

/** Public Device Address or Random Device Address for

   each device which responded to scanning. */

    uint8*     peerBdAddr;

/** length of the data for each device that responded to scanning */

    uint8        dataLen;

/** Pointer to advertising or scan response data */

    uint8*     data;

/** Rssi of the responding device.

* Range: -85 <= N <= 0

* Units: dBm */

    int8     rssi;

} CYBLE_GAPC_ADV_REPORT_T;

For the data section, no distinction is made between a scan response packet or an advertising packet.  data seems to lump the two together.   Does this mean the data length can be 31 * 2 = 62?   Should I expect advertising data to be in the first 31 bytes (0 .. 30) and the Scan Response Data to be in the second 31 bytes (31 .. 61)?  How are the two discriminated in this structure? 

I am configuring a system and trying to decide whether this device can be plugged into a daisy chained USB hub extension with a few other components. Does anyone know what the power rating is for the dongle?

I developed some applications for ProC BLe uC's and I was able to protect rows from Creator 3.3 without problems. I flashed using Programmer and the chip became properly protected.

Some months ago we were forced to migrate future upcoming applications to PsoC BLE equivalent uC's. We're using PSoc Creator 4.0 basically due to new required components.

After developing and tested I tried to protect rows using the same process. Basically, Chip protection selection and later on configuring flash Security.

After that I tried to flash using programmer but I was not able to properly protect the chip. The chiop became unprotected. I check several configurations with no success.

Following the thread, I notice that hex files does not contain the protection information that I got for ProC. Following some comparison for a complete rows protection for both ProC and Psoc 4 families.

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

PSoc 4:

0200000490303A

:02000000A780D7

:0200000490402A

:4000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C0

:400040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000080

:0200000490501A

:0C00000000021A1711AA00011AA8B92A60

:0200000490600A

:0100000001FE

:00000001FF

ProC:

:0200000490303A

:020000001341AA

:0200000490402A

:40000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF00

:40004000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFC0

:0200000490501A

:0C00000000020E02119E00000E0F24DF13

:0200000490600A

:0100000002FD

:00000001FF

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

Before going on to check other possiibilities,

Is there any known bug in Creator 4.0 ?

What am I going wrong ?

Ignasi Villagrasa

In the datasheet for the BLE component 3.40, there is an image showing the architecture of the component that I also attached to this post.

In this image, there is a separation between the application and the profile API.

From what I understand, the profile API is allowed to make calls to the GATT DB and to the GAP/GATT in the host.

Those calls can also be made form the application, for example the CyBle_GattsWriteAttributeValue function, and should be made when implementing a custom profile.

In my custom profile, is the profile API part in the image my own implementation of the profile, and should it be completely separate, or is this only a visualization of how the standard profiles work?

I'm trying to use a Comparator component in a CY8C4146LQI-S432.

However, when I try to assign the output to a pin, I find that it won't let me assign it to any of the pins!  The only thing I can connect it to seems to be the Quadrature Decoder.

Is this right? Surely the comparator can be used for more things than that?

What am I doing wrong?

Hugo