PSoC™ 4 Forum Discussions

In our design the user may change the device name with a custom name, up to 20 characters.

This only seems to work if I "reserve" the 20 characters in the GUI dialog for device name.  For instance if the name in the gui is set to "test" and I programmatically change it to "abcdefghij" the name is saved as "abcd".  If I save the name as "testabcdefghij" in the GUI then I can change the name to anything that length or shorter.  I hope that makes sense.

Is this normal?  Seems dodgy.

Rich

Is this possible? We are developing a wearable technology and want the user to upgrade the firmware OTA but using our app not the CYSmart phone app.

Best,

Nick

My BLE device design requires a password.  The password will be entered via a phone app.  There will be a hard coded default.  What is the best way to handle this?

Perhaps:

Create a custom characteristic, write only, called password.

Save new passwords to NV memory.

Thanks

Rich

This problem does not involve any Cypress Kits or the programming/configuration of the BLE 4.1 device.  I have scoured the forums but found nothing that might answer this.

I have a sealed third-party BLE device which apparently uses the EZ BLE part number CYBLE-022001-00 which is supposed to be BLE 4.1 compliant, yet when it is advertizing I am unable to discover it under Windows 7 with several different BLE 4.0 USB dongles (eg. CSR 8510).  Also it is not discovered by and Android 4.3 phone (Galaxy S3). However it can be discovered by a Toshiba Satellite laptop (integral BLE 4.0) and most newish Android phones and iPhone 5.  I know the BLE 4.0 USB dongles on the Win7 PC are working because they can discover the Android 4.3 phone and the Toshiba Satellite laptop BLE.

I was under the impression that BLE 4.0 (Smart ready) and BLE 4.1 are compatible, so should be able to discover each other when made discoverable.  Why can't a BLE 4.0 USB dongle discover the CYBLE-022001-00 BLE 4.1 device?

Hi everyone,

CYBLE_EVT_GAP_DEVICE_CONNECTED  This event is generated at the GAP Peripheral end after connection is completed with peer Central device

CYBLE_EVT_GATT_CONNECT_IND             This event is generated at the GAP Peripheral end after connection is completed with peer Central device

I use both of them  Server-Client application. I analyze with debug. When the connection is established,  enters in two event.

    
• What is difference CYBLE_EVT_GATT_CONNECT_IND and CYBLE_EVT_GAP_DEVICE_CONNECTED events?
    
• What are the drawbacks of using both of them?
    
• Which should I use ?
   

I have followed the AN97060 PWMExample instructions for building a fixed-stack OTA sample application. There appeared to be two fixes required - (1) main.c: missing underscore in "OTA_Optional.h" (2) ota_optional.c: missing definition of mainTimer. After making these fixes the project built successfully.

I am installing on a standalone CY8CKIT-142, without a CY8CKIT-042BLE baseboard. I am using CySmart 1.2 and a CY5670 dongle to test.

CySmart successfully scans the device and allows me to start an OTA upgrade. The upgrade fails on the last step (transfer firmware image).

The serial debug output is:

<code>

> BLE OTA Fixed Stack Bootloader     Application Started
> Version: 1.40
> Compile Date and Time : Aug  1 2017 10:36:57

> BLE OTA Fixed Stack Bootloadable   Application Started
> Based on BLE HID Keyboard Example Project
> Version: 1.30
> Compile Date and Time : Aug  1 2017 10:45:30

Bluetooth On, StartAdvertisement with addr: 00a050000508
EVT_ADVERTISING, state: 3
EVT_GATT_CONNECT_IND: 0, 4
EVT_GAP_DEVICE_CONNECTED
CYBLE_EVT_GATTS_XCNHG_MTU_REQ, final mtu= 23
OTHER event: 33
EVT_AUTH_REQ: security=1, bonding=0, ekeySize=10, err=0
EVT_GAP_ENCRYPT_CHANGE: 1
EVT_GAP_KEYINFO_EXCHNGE_CMPLT
AUTH_COMPLETE: security:1, bonding:0, ekeySize:10, authErr 0
OTHER event: 57
EVT_GATT_DISCONNECT_IND
EVT_GAP_DEVICE_DISCONNECTED
EVT_ADVERTISING, state: 3

</code>

Workspace archive attached.

Hello,

I am developing a product using the CY8CKIT-143A module, but the datasheet says "The CY8CKIT-143A module is intended for development purposes only. Users are advised to test and evaluate this module in an RF development environment. This module is not a fnished product and when assembled may not be resold or otherwise marketed unless all required authorizations are frst obtained."

So I am not allowed to use this module, but is there any alternative module which is compatible? Maybe this one: CYBLE-224110-EVAL? I don't need pin compatibility, as long as the code is compatible and only has to be recompiled. I read that this module is certified too, but I don't see anything about using it in a final product.

And if I use any pre-certified Bluetooth module, do I have to register and pay the Bluetooth fees?

Thanks in advance.

So I'd REALLY like to keep my bonding information after an OTA update but invariably I get INSUFFICIENT_ENCRYPTION_KEY_SIZE when I try to pair after OTA.  I assume some key information or bonding data is getting lost. I'd happily save and restore whatever is getting lost but I'm not having any luck there.  I've tried saving and restoring all the key data but apparently I'm not doing this correctly or I'm missing something entirely.  I'd greatly appreciate any help, hints or suggestions.  Thanks in advance!!