PSoC™ 6 Forum Discussions

I am using PSoC Creator 4.2 to write a BLE application for a CYBLE-416045-02 and the basics are all working very well.

Of the 3 custom services I have, one is a readable/writable 32-character UTFS8 string. The initial value set in the component is a null string.

As the app starts up, it looks to the EEPROM to read the name that has been given to the system previously and if none has been set, it creates a default name of 'No Given Name' which is 13 character long. I use the Cy_BLE_GATTS_WriteAttributeValueLocal() function to set the name.

When this is read by the client, it is a 32-character value that is null-padded after the actual string.

When I write to the service with (say) 'Test Lamp' I can see the 'handleValPair' structure has the new value and the 'len' parameter is 9 (which is correct).

I then use the Cy_BLE_GATTS_WriteAttributeValuePeer() function to write the value to the local database (and I also update the EEPROM).

However when I then read the service value, what I get is 'Test LampName'.

When I look at the full string sent to the client, it is the same ASCII character null terminated.

If I reboot the code, it will then correctly read 'Test Lamp' form the EEPROM and sets the value in the local GATTS database accordingly.

What do I have to do to save the name to the local database with the correct length (other than rebooting!)?

The code I use is:

case CY_BLE_EVT_GATTS_WRITE_REQ:        writeReqParameter = (cy_stc_ble_gatts_write_cmd_req_param_t*)eventParam;        if( CY_BLE_LOCATION_SETTING_CHAR_HANDLE ==                  writeReqParameter->handleValPair.attrHandle)        {             tLocalName newLocalName;             memset( &newLocalName, 0, sizeof( tLocalName));             memset( newLocalName.localName, ' ', sizeof( newLocalName.localName));             newLocalName.nameLength = writeReqParameter->handleValPair.value.len & 0xff;             memcpy(newLocalName.localName, writeReqParameter->handleValPair.value.val,             writeReqParameter->handleValPair.value.len & 0xff);             // Save to the EEPROM for the next reboot             EEPROM_Write(0, &newLocalName,sizeof(tLocalName));                         // Save to the local GATTS database             writeReqParameter->handleValPair.value.val = newLocalName.localName;             Cy_BLE_GATTS_WriteAttributeValuePeer(&writeReqParameter->connHandle,                            &writeReqParameter->handleValPair);        }        Cy_BLE_GATTS_WriteRsp(writeReqParameter->connHandle);   break;

You can see there my attempts to space-pad the name and also repoint the string pointer. (It doesn't mater if I don't do this and leave the 'val' pointer pointing to whatever it originally was.)

Susan

Hi!

I'm trying to use the Cypress API SPI_1_SetActiveSlaveSelect-function, on a CY8C6347BZI-BLD54 using PSoC Creator 4.2 with PDL 3.1.1.

The component name are SCB_SPI_PDL_v2_0.

When I select m_ss1 it seems to not be applied on the corresponding hardware pin.

The SPI component is located in SCB7, and the SCB7_SPI_CTRL register should be located at address 0x40680020 according to the datasheet.

After I've run the following code snippet for selecting m_ss1 (SPI1_LED_CS) I get this result in the control register:

while (SPI_1_IsBusBusy());
SPI_1_SetActiveSlaveSelect(SPI_1_SPI_SLAVE_SELECT1);
10000100 00000000 00000000 00000001
    ||
  SSEL[0-3]

But SPI1_LED_CS does not go low when writing data to the SPI bus, strange enough.

When I disconnect SPI1_DO_CS and SPI1_LED_CS from the SPI controller and control them manually it works just as expected.

So the question is if I'm missing something here?