PSoC™ 4 Forum Discussions
Does anyone know the details of the format of the following commands use in BLE Dongle
0400 | CyBleEvtGetDeviceIdRsp |
0401 | CyBleEvtGetSupportedToolVersionRsp |
0402 | CyBleEvtGetFirmwareVersionRsp |
0403 | CyBleEvtGetBleStackVersionRsp |
0404 | CyBleEvtMiscNotification |
0405 | CyBleEvtGetSupportedGapRolesRsp |
0406 | CyBleEvtGetCurrentGapRoleRsp |
0407 | CyBleEvtGetSupportedGattRolesRsp |
0408 | CyBleEvtGetCurrentGattRoleRsp |
0409 | CyBleEvtGetRssiRsp |
040A | CyBleEvtGetDeviceDescriptionRsp |
040B | CyBleEvtGetHardwareVersionRsp |
047E | CyBleEvtCmdStatus |
047F | CyBleEvtCmdComplete |
0500 | CyBleEvtCbfcConnectionIndication |
0501 | CyBleEvtCbfcConnectionConfirmation |
0502 | CyBleEvtCbfcDisconnectIndication |
0503 | CyBleEvtCbfcDisconnectConfirmation |
0504 | CyBleEvtCbfcDataReceivedNotification |
0505 | CyBleEvtCbfcRxCreditIndication |
0506 | CyBleEvtCbfcTxCreditIndication |
0600 | CyBleEvtDiscoverAllPrimaryServicesResultProgress |
0601 | CyBleEvtDiscoverPrimaryServicesByUUIDResultProgress |
0602 | CyBleEvtFindIncludedServicesResultProgress |
0603 | CyBleEvtDiscoverAllCharacteristicsResultProgress |
0604 | CyBleEvtDiscoverCharacteristicsByUUIDResultProgress |
0605 | CyBleEvtDiscoverAllCharacteristicDescriptorsResultProgress |
0606 | CyBleEvtReadCharacteristicValueRsp |
0607 | CyBleEvtReadUsingCharacteristicUUIDRsp |
0608 | CyBleEvtReadLongCharacteristicValueRsp |
0609 | CyBleEvtReadMultipleCharacteristicsValueRsp |
060A | CyBleEvtReadCharacteristicDescriptorRsp |
060B | CyBleEvtReadLongCharacteristicDescriptorRsp |
060C | CyBleEvtCharacteristicValueNotification |
060D | CyBleEvtCharacteristicValueIndication |
060E | CyBleEvtGattErrorNotification |
060F | CyBleEvtExchangeGattMtuSizeRsp |
0610 | CyBleEvtGattStopNotification |
0680 | CyBleEvtGetDeviceIoCapabilitiesRsp |
0681 | CyBleEvtGetLocalBDAddrRsp |
0682 | CyBleEvtGetPeerBDAddrRsp |
0683 | CyBleEvtGetPeerDeviceHandleRsp |
0684 | CyBleEvtUpdateConnectionParametersRsp |
0685 | CyBleEvtGetConnectionParametersRsp |
0686 | CyBleEvtGetScanParametersRsp |
0687 | CyBleEvtGetLocalDeviceSecurityRsp |
0688 | CyBleEvtGetPeerDeviceSecurityRsp |
0689 | CyBleEvtGetWhiteListRsp |
0690 | CyBleEvtConnectionTerminatedNotification |
068A | CyBleEvtScanProgressResult |
068B | CyBleEvtGenerateBdAddrRsp |
068C | CyBleEvtGenerateKeysRsp |
068D | CyBleEvtPasskeyEntryRequest |
068E | CyBleEvtPasskeyDisplayRequest |
068F | CyBleEvtEstablishConnectionRsp |
0690 | CyBleEvtConnectionTerminatedNotification |
0691 | CyBleEvtScanStoppedNotification |
0692 | CyBleEvtPairingRequestReceivedNotificaion |
0693 | CyBleEvtAuthenticationErrorNotificaion |
0694 | CyBleEvtConnectionCancelledNotification |
0695 | CyBleEvtGetBondedDevicesListRsp |
06FF | CyBleEvtInternalScanStopInProgressNotification |
FC00 | CyBleCmdGetDeviceId |
FC01 | CyBleCmdGetSupportedToolVersion |
FC02 | CyBleCmdGetFirmwareVersion |
FC03 | CyBleCmdGetSupportedGapRoles |
FC04 | CyBleCmdGetCurrentGapRole |
FC05 | CyBleCmdGetSupportedGattRoles |
FC06 | CyBleCmdGetCurrentGattRole |
FC07 | CyBleCmdInitBleStack |
FC08 | CyBleCmdHostDisconnectNotification |
FC09 | CyBleCmdHostTimedoutNotification |
FC0A | CyBleCmdGetDeviceDescription |
FC0B | CyBleCmdGetHardwareVersion |
FC0C | CyBleCmdGetBleStackVersion |
FC0D | CyBleCmdGetRssi |
FC0E | CyBleCmdResetBleStack |
FD00 | CyBleCmdRegisterPsm |
FD01 | CyBleCmdUnregisterPsm |
FD02 | CyBleCmdCbfcEstablishConnection |
FD03 | CyBleCmdCbfcSendConnectionResponse |
FD04 | CyBleCmdCbfcSendFlowControlCredit |
FD05 | CyBleCmdCbfcSendData |
FD06 | CyBleCmdCbfcSendDisconnect |
FE00 | CyBleCmdDiscoverAllPrimaryServices |
FE01 | CyBleCmdDiscoverPrimaryServicesByUUID |
FE02 | CyBleCmdFindIncludedServices |
FE03 | CyBleCmdDiscoverAllCharacteristics |
FE04 | CyBleCmdDiscoverCharacteristicsByUUID |
FE05 | CyBleCmdDiscoverAllCharacteristicDescriptors |
FE06 | CyBleCmdReadCharacteristicValue |
FE07 | CyBleCmdReadUsingCharacteristicUUID |
FE08 | CyBleCmdReadLongCharacteristicValue |
FE09 | CyBleCmdReadMultipleCharacteristicValues |
FE0A | CyBleCmdWriteCharacteristicValueWithoutResponse |
FE0B | CyBleCmdWriteCharacteristicValue |
FE0C | CyBleCmdWriteLongCharacteristicValue |
FE0D | CyBleCmdReliableCharacteristicValueWrites |
FE0E | CyBleCmdReadCharacteristicDescriptor |
FE0F | CyBleCmdReadLongCharacteristicDescriptor |
FE10 | CyBleCmdWriteCharacteristicDescriptor |
FE11 | CyBleCmdWriteLongCharacteristicDescriptor |
FE12 | CyBleCmdExchangeGattMtuSize |
FE13 | CyBleCmdGattStop |
FE80 | CyBleCmdSetDeviceIoCapabilities |
FE81 | CyBleCmdGetDeviceIoCapabilities |
FE82 | CyBleCmdGetLocalBDAddr |
FE83 | CyBleCmdSetLocalBDAddr |
FE84 | CyBleCmdGetPeerBDAddr |
FE85 | CyBleCmdGetPeerDeviceHandle |
FE86 | CyBleCmdGenerateBdAddr |
FE87 | CyBleCmdSetOOBData |
FE88 | CyBleCmdGetConnectionParameters |
FE89 | CyBleCmdSetConnectionParameters |
FE8A | CyBleCmdGetScanParameters |
FE8B | CyBleCmdSetScanParameters |
FE8C | CyBleCmdGetLocalDeviceSecurity |
FE8D | CyBleCmdSetLocalDeviceSecurity |
FE8E | CyBleCmdGetPeerDeviceSecurity |
FE8F | CyBleCmdGetWhiteList |
FE90 | CyBleCmdAddDeviceToWhiteList |
FE91 | CyBleCmdRemoveDeviceFromWhiteList |
FE92 | CyBleCmdClearWhiteList |
FE93 | CyBleCmdStartScan |
FE94 | CyBleCmdStopScan |
FE95 | CyBleCmdGenerateKeys |
FE96 | CyBleCmdSetAuthenticationKeys |
FE97 | CyBleCmdEstablishConnection |
FE98 | CyBleCmdTerminateConnection |
FE99 | CyBleCmdInitiatePairingRequest |
FE9A | CyBleCmdTerminatePairingRequest |
FE9B | CyBleCmdPairingPasskeyResponse |
FE9C | CyBleCmdUpdateConnectionParameters |
FE9D | CyBleCmdCancelConnection |
FE9E | CyBleCmdGetBondedDevicesList |
Hi,
I try to use the code example BLE_Battery_Level.
I change the target decice to use CYBLE-222014-01 eval board with the CY8CKIT-042-BLE Pioneer kit.
I connect the jumper from P3[5] to VREF on the Pioneer board
The reading it not good. It's 100% all the time.
How can I fix that?
Regards
Martin
Show LessHI
I have a small issue, I have made an application on a PSOC 4 BLE, and in this application I’m using
Custom characteristic some with Read and write properties, and one use Indicate.
Every things work fine with the CySmart dongle, a laptop with an internal Bluetooth radio and with my android phone.
But on windows 10 mobile I’m not getting a acknowledges form the mobile when it has received a data packet, when doing Indicate, read and write works fine here as well.
The Custom characteristic with Indicate, use a data length of 450 byte.
I’m not doing the windows software I’m just trying to help the software guy.
Has any of you experienced similar problems, please let me know. Thanks in advance.
best regards.
Show LessIm attempting to run the BLE101 example, everything compiles and runs fine in Android Studio and the BLE101 app launches on the device. When I click "Start Bluetooth" on the device "BLE has stopped, restart app" immediately pops up. I click the restart app on the device and the BLE101 app reboots. When I click "Start Bluetooth" I then get "BLE101 keeps stopping, close app".Clicking restart app on the device stops the Android Studio debug session. Any Ideas?
PC AMD A8; Windows10 Home64, Android Studio 3.0.1, latest updates installed
Samsung -SM-J727V Android ver 7.0, latest updates installed
Thanks Wayne
Show Lesshello every one
Message was edited by: maknight knight
Hello,
I am writing a Bootloader / Bootloadable project for the CYBLE-214009 chip which has 256K of Flash in two arrays of 128K bytes.
My Bootloader project compiles and only consumes the first 80k of the flash memory, stopping at byte (0x13A99) . My Bootloadable project however compiles and starts in the 2nd array at byte 0x02000. This seems very wasteful. I would like it to be placed immediately after the bootloader. Is this possible? I tried setting the manual placement value in the bootloadable module to 0x00014000. This resulted in the following error:
ERROR: section .text loaded at [00014000,000146df] overlaps section .cybootloader loaded at [00000000,0001ffff]
Is what I am trying to do even possible? I am starting to think it is a limitation.
Thanks.
- Chris
Show LessWe are planning to use the CYBLE-022001 (or CYBLE-022005) on several products.
1) Given that the CYBLE-022001 has 128kB of flash, how is this flash organized? What is the number of rows? We need this information to do firmware updates from a simple function in RAM.
2) Can we place UART Rx FIFO not empty and Tx FIFO empty ISR's in RAM to accomplish (1) above?
Show Lesshi,
I am using
PROJECT #045: PULSE OXIMETRY HEART RATE MONITOR
Example for my project.
when i open the example in psoc creator 4.1,topdesign file is showing only ble component,code is getting compiled and running succssfullly on Psoc4 ble pioneer board,
I need to add one more adc channel in same example project ,for that i need adc component,with configuration used in this project.
please help
Show LessI'm trying to create a characteristic that contains a string with a max length that will only return the parts of the data that are not 0.
So far, I couldn't figure out how to do it but I do think it should be possible because the first name in the weight scale example does it.
In my client the zeros that are send are filtered and ignored, but I have a problem with the tests with the Profile Tuning Suite.
Is it possible to do this in a custom service with a custom characteristic?
Show LessIn AN86233_PSoC_4_Low-Power_Modes_and_Power_Reduction_Techniques(2)_0.pdf I saw recommendation to reduce power by change debug pins to GPIO mode. See attached pic. After I done it I can`t acces to my device !
Programmer can`t acquire SWD
What to do ?
Show Less