PSoC™ 4 Forum Discussions
Hi,
We are using CYBLE-012012-10 in our project and Biometric sensor is connected over UART. We need send breakout for 50ms. Please let me know, How to send breakout.
Thanks and Regards,
Sankar.K
Show LessHi,
I justed reveive 2 new cyble-202007-eval board, used with my pioneer kit. I'm used to work with cyble-222014-01 module without problem.
I just start a new project from Find me sample project nothing fancy. I changed nothing in the project and I received the following message in debug
CYBLE_ERROR_OK 0x20007FC6 (All) enum {CYBLE_ERROR_OK, CYBLE_ERROR_INVALID_PARAMETER, CYBLE_ERROR_INVALID_OPERATION, CYBLE_ERROR_MEMORY_ALLOCATION_FAILED, CYBLE_ERROR_INSUFFICIENT_RESOURCES, CYBLE_ERROR_OOB_NOT_AVAILABLE, CYBLE_ERROR_NO_CONNECTION, CYBLE_ERROR_NO_DEVICE_ENTITY, CYBLE_ERROR_REPEATED_ATTEMPTS, CYBLE_ERROR_GAP_ROLE, CYBLE_ERROR_TX_POWER_READ, CYBLE_ERROR_BT_ON_NOT_COMPLETED, CYBLE_ERROR_SEC_FAILED, CYBLE_ERROR_L2CAP_PSM_WRONG_ENCODING, CYBLE_ERROR_L2CAP_PSM_ALREADY_REGISTERED, CYBLE_ERROR_L2CAP_PSM_NOT_REGISTERED, CYBLE_ERROR_L2CAP_CONNECTION_ENTITY_NOT_FOUND, CYBLE_ERROR_L2CAP_CHANNEL_NOT_FOUND, CYBLE_ERROR_L2CAP_PSM_NOT_IN_RANGE, CYBLE_ERROR_GATT_DB_INVALID_ATTR_HANDLE, CYBLE_ERROR_DEVICE_ALREADY_EXISTS = 39, CYBLE_ERROR_FLASH_WRITE_NOT_PERMITED, CYBLE_ERROR_MIC_AUTH_FAILED, CYBLE_ERROR_HARDWARE_FAILURE, CYBLE_ERROR_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE, CYBLE_ERROR_FLASH_WRITE, CYBLE_ERROR_CONTROLLER_BUSY = 254, CYBLE_ERROR_MAX, CYBLE_ERROR_NTF_DISABLED, CYBLE_ERROR_IND_DISABLED, CYBLE_ERROR_CHAR_IS_NOT_DISCOVERED, CYBLE_ERROR_INVALID_STATE, CYBLE_ERROR_STACK_BUSY}
thanks
Martin
Show LessDear All,
We have downloaded the iOS source code from the web.
However, Error exists when we run the source code.
Does anyone know how to fix it?
Best Regards,
Louis
Show LessUp until now all my custom characteristics have had a single data field, e.g. one uint8. When using multiple data fields, how are they individually managed? Here is my code that updates a characteristic:
void Updatecharacteristic(uint8* Data, uint16 len, uint16 attrHandle)
{
/* 'Handle' stores data parameters */
CYBLE_GATT_HANDLE_VALUE_PAIR_T Handle;
/* Update handle with new values */
Handle.attrHandle = attrHandle;
Handle.value.val = Data;
Handle.value.len = len;
/* Update the attribute value. This will allow
* Client device to read the existing values over
* characteristic */
CyBle_GattsWriteAttributeValue(&Handle,
FALSE,
&cyBle_connHandle,
CYBLE_GATT_DB_PEER_INITIATED);
/* Send the response to the write request received. */
CyBle_GattsWriteRsp(cyBle_connHandle);
}
Thanks
Rich
Show LessHello,
I want to change the device name dynamically, it's working correctly when the device is powered.
But after the reset, the content of data in flash is the inizialisation value of the constant & with the value stored in flash
I declare a constant with initialisation value (is it not supposed to be initialised only once ?)
const char8 deviceNameInFlash[20] = {'D','e','f','a','u','l','t')};
----------------------------
In the stack :
case CYBLE_EVT_STACK_ON: /* This event is received when component is Started */
CyBle_GapSetLocalName(deviceNameInFlash);
CyBle_GappStartAdvertisement(CYBLE_ADVERTISING_FAST);
break;
---------------------------
if(CYBLE_SHUTBASSCV_DEVICENAME_CHAR_HANDLE == wrReqParam->handleValPair.attrHandle)
{
for(i=0;i<wrReqParam->handleValPair.value.len;i++)
{/*Client has to write the ASCI values of the characters that are in the name*/
tempName=wrReqParam->handleValPair.value.val;
}
StoreInFlash(tempName, wrReqParam->handleValPair.value.len);
communHandle.attrHandle = CYBLE_SHUTBASSCV_DEVICENAME_CHAR_HANDLE;
communHandle.value.val = (uint8*) tempName;
communHandle.value.len = wrReqParam->handleValPair.value.len;
CyBle_GattsWriteAttributeValue(&communHandle,FALSE,&connectionHandle,FALSE);
}
void StoreInFlash( char8 *newData, uint8 length)
{
CYBLE_API_RESULT_T result;
CyBle_ExitLPM();
do
{
result = CyBle_StoreAppData((uint8*)newData, (uint8*)&deviceNameInFlash,length,0);
}
while (result!=CYBLE_ERROR_OK);
CyBle_GapSetLocalName((const char *)newData);
}
If the user replace the name by "test" , when disconnect/reconnect we have 'test'
But after device reset we have : "testult"
So the data in flash is reseted, and i don't understand why, "const " is not supposed to mean initialized once ?
Thanks for your answers.
Show LessHello,
I am creating a dmx transmitter. Iam creating a break on a pin with the XXX_Write(Bolean); command and it works find. After the break it goes high to a MAB and i want to swith the output from digital write with a command to the UART so the UART can send the DMX data.
While writing the digital pin high and low with the Hardware Connection connected to the pin it goes low but in a curve. When turning the pin on and off it should become a square but the falling edge isn't straight down.
How can i do this?
I was thinking of turning on and off the Hardware Connection of my pin when iam commanding the break and turning it on when the UART is going to send data, but i can't find a register or something that can turn it on and off mid program. (short said connect and disconnect it from the UART block)
Thank you!
ps: i have the CyCKIT-044 PSoC 4 M-series pioneer kit with a PSoC 4200M device
Show LessIs this possible? We are hoping to change between PLL1 which is ECO trimmed to Direct_Sel or something else that can be sourced from IMO and USB trimmed. The reason why is that when power is disconnected from the host Laptop, the communication timing appears to change a little bit, and when the clock is trimmed by the host it seems to handle it better. I am hoping to change the clock source whenever VBus is detected but return to normal when it is disconnected to keep good timing on a CAN bus also connected to the micro.
Show LessI have:
Read all available posts on this error.
Checked to see that my uart buffer is 64 bytes.
Updated all components (using psoc 4.1)
Triple checked the dependencies in the bootloadable object to verify hex and elf point to the bootloader's hex and elf files.
Cleaned and rebuilt and reloaded the bootloader.
Running the bootloader host that came with 4.1.
Bootloader and bootloadable projects are in the same workspace.
Still get this error message.
Show Less