PSoC™ 4 Forum Discussions

I had a file get corrupted recently on my project not long after updating to PSoC creator 4.1. I restored from an older copy and have had nothing but problems trying to get back to working. This project was previously working great. At this point, I'm getting errors that say "storage class specified for parameter <parameter name>" all over my project, including standard header files. I have no clue what this is. Can anyone help?

Hello everyone and good afternoon, I'm trying to set 6 interruptions in the "Port 0", the problem that I have is that I don't have too much idea of how to set one interruption for a specific pin to trigger when sensed a falling edge (they are set as pull-up resistive input pins) and another interruption for the same pin to sensed the rising edge, in other words, the pressing of a push button. As far as I know when we are talking about a component pin (several pins triggered by one dedicated interrupt for that specific port ), we need to use the function "<name of the port block>_ClearInterrupt()" to get the value from the pin register, that tells us which pin triggered the interrupt (I have already done that), but my main problem is with the rising and falling edges that I haven't managed to make it wor. 

Hello ,

I am Jagir,I am Novice to PSoC Technology.

I want to know what is extra functionality available in PSoC than SoC ?

What is benefits of PSoC Over SoC.

Hello,

I am newbie to PSoC 4 BLE & i came across a term named descriptor in profile->service->characteristic->descriptor hierarchy.

I ant to know about use case of descriptor . And There are different predefined example available for any characteristic,So where that can be used ?  

I recently upgraded to PSoC Creator 4.1 Update 1 from version 4.0 and the part I've been working with EZ-BLE PRoC 222014-00 is no longer supported.  I couldn't find any documentation going over the changes between that and the replacement part 222014-01.  If possible, I'd like to see what those changes are.  More importantly, will code built for the new part run on the old part?  Or what features won't work correctly? Etc.

Good afternoon (o;

According to the "Bootloader and bootloadable datasheet" the application checksum is defined as:

"The basic summation checksum is computed by adding all the bytes (excluding the checksum) and then taking the 2’s complement ."

So for the SCB_Uart example it writes in the checksum field the byte 0x60...

But when I walk through the hex file and sum up all bytes I get "0x8F"...

Does "excluding the checksum" mean it includes the other meta fields at address 0x7FC0 as well like application length and so on?

Hello,

I have hard time figuring out how, i could pairing and  bond with a device having only 1 button, and a smartphone with resolvable random adress.

The device has only 1 button, the user can pair his smartphone with it, but for the other uses, the device have to be bond (mostly because this single button is not very accessible.

It run on a BLE 4.1 PROC/PSOC4

So from what i see there are some possibilities :

Because only 1 button: where are in NoInput/NoOutput : so unauthenticated connection + encrypted data

1) The good one :

Use the button to change the advertissement mode : - in normal mode : scan request : white list ;  connect list white list :

                                                                                    -  in pairing mode (button pressed) :  scan request any : connect list : any

But the problem is that we can't use whitelist because the smartphone now use resolvable random adress.

(And if we want a good compatibility we can't use the BLE 4.2 with all the things, irk resolved in the other layer, im right ?)

2)

Use the button to discard connection when we are in the connected states :

In the CYBLE_EVT_GAP_DEVICE_CONNECTED  state

if (ButtonPressed)

{

cyBle_authInfo.authErr = CYBLE_GAP_AUTH_ERROR_NONE;

}

else

{

cyBle_authInfo.authErr = CYBLE_GAP_AUTH_ERROR_PAIRING_NOT_SUPPORTED;              

}

That work perfectly when we pair for the first time, but for the reconnection we have to compare the device adress, with the bonded device adress list.

So can i use something like that  ? :

So in the connected state :

use GapGetPeerBdAddr to get the device Adress

and compare it to the list of previous bonded device that we get with : CyBle_GapGetBondedDevicesList (that we call in disconnected state for exemple)

Is that ok to do that  ? I didn"t see something similar in examples

Thank you.