PSoC™ 6 Forum Discussions

Hi There,

I have few questions. I am new to embedded programming. I got the Pioneer Kit. Completed hello world program ( Blinking LED ). But I am not sure what to do next. What can I do next. What should be the flow for me to learn embedded programming?

I can see the examples. But they are not clear. They are in bits and pieces.

Thanks In Advance!

Hello -

Another PSoC 6 crypto library question.

This page: PSoC 6 Peripheral Driver Library: Client Functions describes a pair of ECDSA functions (Cy_Crypto_ECDSA_SignHash/Cy_Crypto_ECDSA_VerifyHash), but the PDL documentation (3.1.2) for my PSoC creator install makes no mention of it.

Is this similar to the RSA 4096 bit support (coming to PDL in the future, and only on newer chips)?

Hello ,

I am testing the BLE DFU firmware update feature with CySmart 1.3 and CySmart mobile. Both of them fail to transfer my .cyacd2 file. ( You can find it enclosed)

CySmart log is as follows :

[13:56:56:811] : 'Establish Connection' request sent [13:56:56:811] : BD Address Type: PUBLIC_ADDRESS [13:56:56:811] : BD Address: 78:77:E8:50:A0:00:00:00 [13:56:56:813] : 'Command Status' event received [13:56:56:813] : Status: BLE_STATUS_OK [13:57:04:483] : 'Establish Connection Response' event received [13:57:04:483] : 'Enhanced connection complete' event received [13:57:04:483] : Status: 0x00 [13:57:04:483] : Role: 0x00 [13:57:04:483] : BD Address Type: PUBLIC_ADDRESS [13:57:04:483] : BD Address: 78:77:E8:50:A0:00:00:00 [13:57:04:483] : Local resolvable address: 00:00:00:00:00:00:00:00 [13:57:04:483] : Peer resolvable address: 00:00:00:00:00:00:00:00 [13:57:04:483] : Connection Interval: 15.00 ms [13:57:04:483] : Slave Latency: 0 [13:57:04:483] : Supervision Timeout: 200 ms [13:57:04:483] : 'Command Complete' event received [13:57:04:483] : Status: BLE_STATUS_OK [13:57:04:484] : 'Exchange GATT MTU Size' request sent [13:57:04:484] : MTU: 0x0200 [13:57:04:486] : 'Command Status' event received [13:57:04:486] : Status: BLE_STATUS_OK [13:57:04:514] : 'Exchange GATT MTU Size Response' event received [13:57:04:514] : MTU: 0x0200 [13:57:04:514] : 'Command Complete' event received [13:57:04:514] : Status: BLE_STATUS_OK [13:57:04:515] : 'Initiate Pairing' request sent [13:57:04:515] : 'Command Status' event received [13:57:04:515] : Status: BLE_STATUS_OK [13:57:04:530] : 'Data length changed notification' event received [13:57:04:530] : Connection maximum Tx octet: 251 [13:57:04:530] : Connection maximum Tx time: 2120 µs [13:57:04:530] : Connection maximum Rx octet: 251 [13:57:04:530] : Connection maximum Rx time: 2120 µs [13:57:04:544] : 'Negotiated pairing parameters' event received [13:57:04:544] : State: Pairing negotiated [13:57:04:544] : Security Level: 0x01 [13:57:04:544] : Encryption Key Size: 16 [13:57:04:544] : Bonding: 0x00 [13:57:04:544] : Pairing properties: NONE [13:57:04:681] : 'Negotiated pairing parameters' event received [13:57:04:681] : State: Pairing completed [13:57:04:681] : Security Level: 0x01 [13:57:04:681] : Encryption Key Size: 16 [13:57:04:681] : Bonding: 0x00 [13:57:04:681] : Pairing properties: NONE [13:57:04:681] : 'Command Complete' event received [13:57:04:681] : Status: BLE_STATUS_OK [13:57:04:681] : 'Misc Event Notification' received [13:57:04:681] : Event Code: 0x0029 (GAP_ENCRYPT_CHANGE) [13:57:04:681] : Event Data: Encryption ON [13:57:04:681] : Event Data: [01] [13:57:04:696] : 'Discover Primary Services by UUID' request sent [13:57:04:696] : UUID: 00060000F8CE11E4ABF40002A5D5C51B [13:57:04:696] : 'Command Status' event received [13:57:04:696] : Status: BLE_STATUS_OK [13:57:04:712] : 'Discover Primary Services by UUID Result Progress' event received [13:57:04:712] : Primary Service 1: [13:57:04:712] : ------------------------- [13:57:04:712] : Start Handle: 0x0010 [13:57:04:712] : End Handle: 0x0013 [13:57:04:743] : 'GATT Error Notification' event received [13:57:04:743] : Error Code: BLE_GATT_ERR_ATTRIBUTE_NOT_FOUND [13:57:04:743] : 'Discover All Characteristics' request sent [13:57:04:743] : Start Handle: 0x0010 [13:57:04:743] : End Handle: 0x0013 [13:57:04:743] : 'Command Status' event received [13:57:04:743] : Status: BLE_STATUS_OK [13:57:04:781] : 'Discover All Characteristics Result Progress' event received [13:57:04:781] : Characteristic 1: [13:57:04:781] : -------------------------- [13:57:04:781] : Attribute Handle: 0x0011 [13:57:04:781] : Characteristic Value Handle: 0x0012 [13:57:04:781] : UUID: 00060001F8CE11E4ABF40002A5D5C51B [13:57:04:781] : Properties: 0x1C [13:57:04:813] : 'GATT Error Notification' event received [13:57:04:813] : Error Code: BLE_GATT_ERR_ATTRIBUTE_NOT_FOUND [13:57:04:813] : 'Discover All Characteristic Descriptors' request sent [13:57:04:813] : Start Handle: 0x0013 [13:57:04:813] : End Handle: 0x0013 [13:57:04:813] : 'Command Status' event received [13:57:04:813] : Status: BLE_STATUS_OK [13:57:04:844] : 'Discover All Characteristic Descriptors Result Progress' event received [13:57:04:844] : Characteristic Descriptor 1: [13:57:04:844] : ------------------------------------- [13:57:04:844] : Attribute Handle: 0x0013 [13:57:04:844] : UUID: 0x2902 [13:57:04:844] : 'Command Complete' event received [13:57:04:844] : Status: BLE_STATUS_OK [13:57:04:844] : 'Write Characteristic Descriptor' request sent [13:57:04:844] : Attribute Handle: 0x0013 [13:57:04:844] : Value: [01:00] [13:57:04:844] : 'Command Status' event received [13:57:04:844] : Status: BLE_STATUS_OK [13:57:04:859] : 'Command Complete' event received [13:57:04:859] : Status: BLE_STATUS_OK [13:57:04:875] : 'Read Characteristic Descriptor' request sent [13:57:04:875] : Attribute Handle: 0x0013 [13:57:04:875] : 'Command Status' event received [13:57:04:875] : Status: BLE_STATUS_OK [13:57:04:898] : 'Read Characteristic Descriptor Response' event received [13:57:04:898] : Value: [01:00] [13:57:04:898] : 'Command Complete' event received [13:57:04:898] : Status: BLE_STATUS_OK [13:57:04:898] : 'Write Characteristic Value Without Response' request sent [13:57:04:898] : Attribute Handle: 0x0012 [13:57:04:898] : Value: [01:38:06:00:04:03:02:01:00:00:B7:FF:17] [13:57:04:898] : 'Command Status' event received [13:57:04:898] : Status: BLE_STATUS_OK [13:57:04:898] : 'Command Complete' event received [13:57:04:898] : Status: BLE_STATUS_OK [13:57:09:898] : 'Terminate Connection' request sent [13:57:09:900] : 'Command Status' event received [13:57:09:900] : Status: BLE_STATUS_OK [13:57:09:915] : 'Connection Terminated Notification' event received [13:57:09:915] : Reason: CONNECTION_TERMINATED_BY_LOCAL_HOST [13:57:09:915] : 'Connection Terminated Notification' event received [13:57:09:915] : Reason: CONNECTION_TERMINATED_BY_LOCAL_HOST

I do not know why but suddenly CySmart sends out a "Terminate Connection" request.

The host and target has same security and connection parameters.

Any idea about what the reason could be?

Regards,

Hi,

I got a new CY8CKIT-062-WiFi-BT. When I try to program it using the PSOC creator. It is not being listed under the targets.

What would have been the issue. I am using PSOC Creator 4.2. First thing is I wanted to rule out the issues present on board if any. Kindly help me with this.

您好！

请问下PSOC6   BGA封装的开发板套件用的是几层板   ？我若选择好了PSOC6 BGA封装的型号，能否最后绘制成4层板？

谢谢。

Hello!

How many layers does the PSOC6 BGA development board package use?If I choose the PSOC6 BGA model, can I draw it into a 4-layer board?

thank you

Greetings!

This is a general product question.  When I'm using the PSOC6 (specifically, the 062 BLE Pioneer kit) in Creator, why doesn't the PSOC6 have components available such as digital filter blocks, and the sample-and-hold block?  The PSOC5 does have these blocks.

Hello All,

I would like to measure the voltage at pin VDDA.  On page 18 of the CY8C63x6/7 data sheet it states that the Capsense ADC can measure VDDA against an internal reference without using GPIO or external components.  However, I can find no information about actually doing this.

I've studied the documentation for the CSDADC middleware library.  I see how to connect the ADC to GPIO pins, but I can't figure out how to connect to VDDA.  Does anyone know how?

Paul

I try to communicate with an RFID-Click board with SPI.

For the first touch i decide to use the low level API from Cypress.

Now i´m stuck while i try to read the ID of the Chip.

I hock up a Oscillocop on the SPI bus.

When I watch the Transfer all seems to be okay.

When I plot the Values readed from the rxBuffer I don´t get the expected results.

txBuffer[20]=0;

rxBuffer[20]=0;

void ClearSPIBuffer(){

}

for Write i used:

void SPIWrite(length){

     Cy_SCB_SPI_WriteArrayBlocking(SPI_1_HW,txBuffer,length);

     while(!Cy_SCB_SPI_IsTxComplete(SPI_1_HW)){

          vTaskDelay(0);

     }

}

read i try with:

txBuffer[0]=ID_CMD;

SPIWrite(1);

ClearSPIBuffer();

txBuffer[0]=read_CMD;/*reading cmd specify by the RFID Chip*/

txBuffer[1]=0xFF;/*Send Dummy Byte for reading*/

txBuffer[2]=0xFF;

txBuffer[3]=0xFF;

...

txBuffer[16]=0xFF;

txBuffer[17]=0xFF;

SPIWrite(18);

while(Cy_SCB_SPI_GetNumInRxFifo(SPI_1_HW)!=18);

Cy_SCB_SPI_ReadArray(SPI_1_HW,rxBuffer,18);

for(uint8_t i=0;i<18;i++){

     printf("recived %u: %u\r\n",i,rxBuffer[0]);

     vTaskDeleay(0);

}

On the Oscilliskop i can See the Correct ID but on the Serial Consol i Just get 0x06 what is the resulst from Polling and Echo command what I´m using bevor.

I try to get the correct Code from the SPI_MAST_LOW_LEVEL example.

What do i making wrong to read from an SPI Device?

Is the rxBuffer Updatet by write with Cy_SCB_SPI_WriteArrayBlocking(SPI_1_HW,txBuffer,length) ?

Hi Sir,

I have some question want to ask next,

  (1)PSoC6 UDB part concrete can do?

（2）what is the difference between it and CPLD or relationship, as well as the specific usage, as well as the specific how many resources, whether can realize a little more complicated point of application, to do some algorithm, its peaceful LUT lookup table of commonly used exactly is what relationship, if we can develop a serial port?

（3）Whether UDB can do sequential logic？

Thanks

Paddy

Hi -

All of the examples for PSoC 6 RSA seem to demonstrate the use of 2048-bit RSA keys.

Some of the PDL docs mention 4096 bits ("Also referred to as Public Key encryption. To receive a message, you publish a very large public key (up to 4096 bits currently), and I see "CY_CRYPTO_RSA4096_MESSAGE_SIZE" defined in the PDL documentation (PSoC 6 Peripheral Driver Library: Macros ), but not in the ".h" file in my PDL 3.1.2 installation.  So, I'm unsure if 4096-bit keys should be expected to work or not.

When I try to use a 4096-bit key, Cy_Crypto_Rsa_Proc() returns 0 (CY_CRYPTO_SUCCESS), but the buffer passed to it for output has not been touched (it seems to be a no-op).

I don't know if the issue is with my use of the functions, or if the PDL just doesn't support 4096-bit keys.

If the latter, do the "direct" crypto-core functions support larger keys than the client/server functions that I'm currently using?

Thanks for any advice.

EDIT: I'm using PSoC Creator, in case that makes a difference.