PSoC™ 4 Forum Discussions

I need any example how work with Write Long Characteristic Value.

My device receive :

CYBLE_EVT_GATTS_WRITE_CMD_REQ

CYBLE_EVT_GATTS_PREP_WRITE_REQ

CYBLE_EVT_GATTS_EXEC_WRITE_REQ

What to do ? How response to this events ?

Jeff.

Are there any iOS or Android tutorial videos or docs w/ example source for basic file transfers to a CYSPP based server?

Also, does Cypress plan to devote continued resources for providing support and 'timely' updates to CYSPP as inevitable bugs begin to appear in the field with any new host platforms? This seems like a daunting task not necessarily within the historical Cypress core product offerings.

Thanks for any business plans insight.

Hello

I am trying to make a program to get temperature reading and send between two cy8ckit 042 ble kit. And want to see the results through UART. 

Till now i tried UART_BLE example from https://github.com/cypresssemiconductorco/PSoC-4-BLE/tree/master/100_Projects_in_100_Days

Can anyone help me how to proceed from here??

Thanks

Hello,

I am confused about the development kits and Proc devices currently available.

First I found an CYBLE-212019-00 PROC module BLE 4.1 with an appropriate development kit CY8CKIT-042-BLE for the PSOC 4 hardware.

But after checking the website at Cypress I got the information that a new development kit CY8CKIT-042-BLE-A with BLE 4.2 is out. Unfortunately this new kit seems not to be available everywhere or at any distributor.

As both kits seem to be based on the PSOC 4 I wonder if there is an difference in the software only and the hardware has not changed.

Is that right and I can buy an non A version kit and use or update with the newer software or am I wrong here ?

Same applies for the available CYBLE-212019-00 PROC module which is reported as 4.1 module. Can I update this module to 4.2 with the newer development kit or the updated non A kit ?

Or are there any diffs in the PSOC4 hardware or the older 4.1 devices locked in any way to this version ?

Can somebody please clarify because if I start with a new project I would like to get the latest version if ever possible.

Thank you very much for any usefull answer.

Good morning,

I am currently developping software with PSoC Creator 3.3 on a chip CYBLE-022001-00. My question is about the security. This is my configuration :

General :

GATT Server.
GAP Paripheral.

GAP Settings (Security) :

Security Mode : Mode 1.
Security Level : Authenticated pairing with encryption.
I/O Capabilities : Display Only.
Bonding requirement : No Bonding.
Encryption key size (bytes) : 16.

I have created 2 Services in a Custom profile : One for Read and one for write data. I have a bridge between BLE and I2C (i am using a project « Day035_I2C_BLE_Bridge » for that).

To have an higher security betweek two devices, i am using encryption and authentication. I used the project « Day016_Authentication » to have the same thing. The problem is : during the authentication, i enter the passkey in a smartphone (the passkey generated by the cyble-022001-00), but if i fail the authentication, i am still able to write data in a characteristic and i am able to read theses datas with the I2C component.

In the profile properties, all permissions need an encryption (encryption required) and an authentication (authentication required).

Do you know how it is possible to write (and read) in all characteristics even if the anthentication if fail ?

Thank you for your answer.

Kind regards.

My board design uses a MMA8653FC Accelerometer 
I defined an I2C SCB to communicate with it 
Set up the SCL and SDA pins per my board schematic. The part SendStart routine returns no error so I assume the SCB is configured properly 
The part spec describes the single byte register read as follows 

5.8.1 Single-byte read 
1. The transmission of an 8-bit command begins on the falling edge of SCL. After the eight clock cycles are used to send the command, note that the data returned is sent with the MSB first after the data is received. Figure 10 shows the timing diagram for the accelerometer 8-bit I2C read operation. 
2. The Master (or MCU) transmits a start condition (ST) to the MMA8653FC [slave address (0x1D), with the R/W bit set to “0” for a write], and the MMA8653FC sends an acknowledgement. 
3. Next the Master (or MCU) transmits the address of the register to read, and the MMA8653FC sends an acknowledgement. 
4. The Master (or MCU) transmits a repeated start condition (SR) and then addresses the MMA8653FC (0x1D), with the R/W bit set to “1” for a read from the previously selected register. 
5. The Slave then acknowledges and transmits the data from the requested register. The Master does not acknowledge(NAK) the transmitted data, but transmits a stop condition to end the data transfer. 

I'm having trouble translating steps 4 and 5 into code that uses the I2C SCB 
#5 implies that the register must be read immediately after the repeated start is sent. It's not clear how to do this in SCB I2C. 
The Accel_I2CMasterReadByte issued after Accel_I2CMasterWriteBuf returns 0xFF because the check if master is active in Accel_I2CMasterReadByte fails : 
Here is a routine I use

byte IIC_RegRead(byte address, byte reg) 
{ 
byte b = 0; 
byte repeatStartAddr = (address << 1) | 0x01;  /* slave address 0x1D with the R/W bit set to “1” for a read from the previously selected register. */
status = Accel_I2CMasterSendStart(address,DIR_WRITE); 

if(status == Accel_I2C_MSTR_NO_ERROR) 
{ 
Accel_I2CMasterWriteByte(address); // Send IIC "Write" Address 
Accel_I2CMasterWriteByte(reg); // Send Register 

Accel_I2CMasterWriteBuf(address,&repeatStartAddr,1,Accel_I2C_MODE_REPEAT_START); 

----These fail
b = Accel_I2CMasterReadByte(GENERATE_ACK); // *** Dummy read: reads "IIC_ReadAddress" value *** 
b = Accel_I2CMasterReadByte(GENERATE_ACK);  /* read the value */
status = Accel_I2CMasterSendStop(); 
} 
return b; 
} 
Your help is much appreciated. 

Hi All,

Could you help me to find out the document for CYREG_RADIO_TX_RX_MUX_REGISTER details please.

This is used in BLE_Power_Measurement project to route Tx and Rx radio signals onto PIOs. I would like to know can I route into any PIOs or 3.2 and 3.3 are fixed?

Thank you very much.

Hi,

I am trying to get an interrupt to change some data when an Android app sends a characteristic write request.  Both UUIDS are identical in Android Studio and PSOC Creator, however, this line never seems to match:

if(wrReqParam->handleValPair.attrHandle == CYBLE_DMX_CONTROLLER_CUSTOMCOLOR_CHAR_HANDLE)

The CYBLE_DMX_CONTROLLER_CUSTOMCOLOR_CHAR_HANDLE always has a value of 0x0014u, but the wrReqParam->handleValPair.attrHandle either has a value of 0x0010, or 0x0015.  I have checked and double checked when debugging that the app is sending the characteristic with the correct UUID (00000000-0000-1000-8000-00805f9b34f1), and cannot make sense of this.

Any ideas?

Thank you in advance.

Regards, Tom