PSoC™ Creator & Designer Forum Discussions

I downloaded both the ISO and the basic install file from you site, they both error on install

on a cab file being corrupted.

psoc_creator_3.3_cp3_b9648.iso

PSoCCreatorSetup_3.3_cp3_b9648.exe

https://www.cypress.com/documentation/software-and-drivers/psoc-creator-software-archive

Regards, Dana.

Hello to all,

I am using BLE v3.30 and am testing authentication fail situations. One of them is also to enter wrong pin code.

I also read Bluetooth Low Energy v3.30.pdf document.

I put some traces into the ble event handler just to see what is happening and I found out following:

- an event CYBLE_EVT_GAP_AUTH_FAILED is send

- structure passed with this event is of type CYBLE_GAP_AUTH_INFO_T.

- I checked the parameters and there is a parameter called "authErr" which should describe the error.

- When I print the value of the "authErr" after I entered invalid PIN code I see that the value is 0 ??? which means CYBLE_GAP_AUTH_ERROR_NONE.

- The parameter "bonding" is set to value 0x04 which is also strange

I double check everything and implementation is ok:

       CYBLE_GAP_AUTH_INFO_T status = *(CYBLE_GAP_AUTH_INFO_T *)eventParam;               
               
       char* dummy = "CYBLE_EVT_GAP_AUTH_FAILED: bonding, authErr";
       SW_Tx_UART_1_PutString(dummy);
       SW_Tx_UART_1_PutCRLF();

       SW_Tx_UART_1_PutHexByte(status.bonding);
       SW_Tx_UART_1_PutCRLF();

       SW_Tx_UART_1_PutHexByte(status.authErr);
       SW_Tx_UART_1_PutCRLF();

So the question is, why do I get OK if for invalid PIN number I should get some error. And actually the device don't connect over the bluetooth, so this is working fine. To me it looks like this 2 parameters are inverted.

Another question is, what does the BLE send back if I enter invalid PIN code? So that the application on the other side could properly handle the error?

From the CySmart application and when using the source code with the Android studio I found out it get this information:

      D/CySmart Android: PCF: pair: registering mPairOnConnectStatusReceiver

      I/Timeline: Timeline: Activity_idle id: android.os.BinderProxy@3b88ef84 time:520152927

      D/CySmart Android: HPA: pair: BluetoothDevice.BOND_NONE

       BondingProgressDialog: pair: dismissing dialog 582622311

      D/BluetoothGatt: onClientConnectionState() - status=22 clientIf=7 device=00:A0:50:00:00:00

      I/CySmart Android: onConnectionStateChange: status: 22, newState: 0

       BluetoothLeService: action: com.example.bluetooth.le.ACTION_GATT_DISCONNECTED

status=22 was taken from the Android-BLE-Library/GattError.java at 5e0e2f08c309a6de2376d9b8705c83f9e9a80d56 · NordicSemiconductor/Android-BLE-Library…  and it means GATT_CONN_TERMINATE_LOCAL_HOST. But I don't see an error describing that wrong PIN number.

Any further information on how BLE handles wrong PIN code and what does it actually returns back over the BLE would be really helpful. Or is it option that I can send something back?

Thanks for the answer, Frenk

Hi,

I'm using PSoC Creator 4.3 with device PSOC4100S  CY8C4125AXI-S433, in my design I'm using Flash to emulate EEprom and I'm following the relative code example, and here I have a problem, the variable "Em_EEPROM_em_EepromStorage" within the generated file Em_EEPROM.c, is declarated only if defined "CY_PSOC6", and it is not here the case.

#if ((CY_PSOC6) && (Em_EEPROM_1_STORAGE_EM_EEPROM))

    CY_SECTION(".cy_em_eeprom") CY_ALIGN(CY_FLASH_SIZEOF_ROW)

    const uint8 Em_EEPROM_1_em_EepromStorage[Em_EEPROM_1_ACTUAL_SIZE] = {0u};

#endif /* ((CY_PSOC6) && (Em_EEPROM_1_STORAGE_EM_EEPROM)) */

Probably I'm wrong ... Have you any suggestions?

Thanks

Renato

I'm using PSoC creator 4.3

In the Workspace Explorer window, when I create a folder in my source files folder, I would like that folder to also be created where those source files exist on my hard disk.  It seems that PSoC creater only creates these folders "virtually" in the project file.   Is there an option or method to have PSoC creator maintain these files on disk, as they appear in Workspace Explorer?

Thanks!

Hi,

We installed Psoc Creator 4.4 on a brand new Windows 10 machine. We copied an existing old working PSoC3 project (using the same Keil version C51 compiler: DP8051 9.51).

When building the project we get ther error:

ERROR: C:\Program Files (x86)\Cypress\PSoC Creator\4.4\PSoC Creator\import\keil\pk51\9.51\C51\INC\intrins.h:19: missing ';' before 'extern'

We veriified the build settings between the 2 computer systems (the old one running PSoC Creator 4.2). They are equal.

What causes this error?

Thanks for your reply

Kris

Hello Community,

I am currently evaluating RTC backup time after POR in PSoC6 BLE PIONEER KIT. As mentioned in the schematic there is a supercapacitor connected to VBACKUP for backing up the RTC time(Refer 'CY8CKIT-062-BLE_Kit_Guide' page 33).

I tried flashing the example project '002-16825_CE216825' and '002-18964_CE218964' .

In both the projects, the time is ticking when the kit in on condition. But after a POR the previous time is not retained by the RTC like mentioned in the TRM/datasheet.

Kindly, help to resolve this issue ASAP. As in our design the decision to add an additional IC to retain the time or not totally depend on this. 

I have 7 calls to an external function within one source file. ONLY FOUR generate this error. I have tried copying one of the "good ones" over the bad ones.. no change.

I tried putting an extern.. line for the external function just above the function calls. No change.

I commented out these 4 lines to verify: I am not out of flash, and I am not out of RAM.

Help!

Hi all, since I started using a new computer PSoC Creator is extremely slow to boot: it can take up to 10 minutes... I have the splash screen and nothing else. Same with PSoC Programmer.

I re-installed without a change, tried 4.2, 4.3 and 4.4. All the same.

Have you seen this?

I am using the psoc6 and trying to debug a function in the m4 core. When I enter a function that has a 2K byte array the stepping takes about 10 seconds. I read some other post here that show this happens if you have a watch window open but all my watch/memory windows are closed. If I make the array global everything works fine.

I am new to cypress tools and keep thinking there must be some other type of memory window still open but I can't find it. What else could it be?

Thanks

David

I'm using PSoC creator 4.3 and PDL 3.1.3

I created an SPI block as a master (see screen shot).  There are two slave devices, one is write-only and a data width of 9 bits.  The other is read-only and has a data width of 11 bits.

According to the UDB editor, if the Tx and Rx data widths are not the same, you have to use the "National Semiconductor" sub mode.

I selected "National Semiconductor" and it built fine.  However, when I run the code, during SPI initialization there is an exception generated by an ASSERT which checks if "National Semiconductor" mode is selected when the Tx/Rx sizes are different.   I found that the reason for this assertion is that for some reason, the generated SPI config code does NOT set sub-mode to "CY_SCB_SPI_NATIONAL", but instead uses "CY_SCB_SPI_TI_COINCIDES".  (see code snippet below)

I'd like to know if this is a bug, or if I am doing something wrong.

cy_stc_scb_spi_config_t const SPI_DISPLAY_config =

{

    .spiMode  = CY_SCB_SPI_MASTER,

    .subMode  = CY_SCB_SPI_TI_COINCIDES,

    .sclkMode = CY_SCB_SPI_CPHA0_CPOL0,

    .oversample = 16UL,

    .rxDataWidth              = 11UL,

    .txDataWidth              = 9UL,

    .enableMsbFirst           = true,

    .enableInputFilter        = false,

    .enableFreeRunSclk        = false,

    .enableMisoLateSample     = false,

    .enableTransferSeperation = false,

    .ssPolarity               = ((((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT0) | \

                                 (((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT1) | \

                                 (((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT2) | \

                                 (((uint32_t) CY_SCB_SPI_ACTIVE_LOW) << SPI_DISPLAY_SPI_SLAVE_SELECT3)),

    .enableWakeFromSleep = false,

    .rxFifoTriggerLevel  = 0UL,

    .rxFifoIntEnableMask = 0x0UL,

    .txFifoTriggerLevel  = 0UL,

    .txFifoIntEnableMask = 0x0UL,

    .masterSlaveIntEnableMask = 0x0UL

};