PSoC™ 4 Forum Discussions

Ok guys, I've been trying to figure this out for quite some time now. Just need some direction.

From the PSoC example for CY8CKIT-024 for Proximity Gestures found here: http://www.cypress.com/documentation/application-notes/an92239-proximity-sensing-capsense, the example allows for air gesturing using capacative proximity sensing in either the X-Axis or Y-Axis direction depending on the settings you choose in the code. However, I want both Axis' to work at the same time. The only way Ive been able to get this to work is using two separate PSoC's each driving a different axis, one for Y-Axis, and one for X-Axis. I want to do this using a single chip if possible. I converted a second copy of the original gesture source/header files to have each driving a different axis, however no matter what I seem to do, it only ends up driving the LEDs for the axis coded into the original gesture files (in this case, the X-Axis). I am using an older CapSense component, CapSense CSD [V2.60] along with the CY8CKIT-042-BLE kit for this particular *attempt* at development.

My questions are:

-Is it in my code? 

-Would this potentially only be possible if I port my code over to use the CapSense [v4.0] component and split up the X-Axis and Y-Axis into 2 separate proximity sensors each using 2 sensing elements?

-OR am I shit out of luck on this idea on one PSoC?

I have attached a .zip Bundle of my workspace below

               Any Help Is Much Appreciated

Dear ,

I use PSoC Programmer 3.26.0 to program PSoC4 ,  it is successful.

but when I PPCLI.exe to Programming,when I use PSoC4_EraseAll, it will show error as follow:

>PSoC4_EraseAll

E

SWD respond packet contains Failed status!

PSoC4_EraseAll returned 80004005

80004005 OK

anybody can tell me why?

the detail as follow Picture.

I have a BLE project that communicates with a MAC OS using the BLE MIDI protocol. I have had this working for several years on the Broadcom (now Cypress) CYW20737S, but I'm porting it to the PROC CYBLE-012011-00. I stress this, to show that I trust the client implementation in the MAC OS.

The PROC device is configured to transmit every half second for testing. On the PROC device, after 5 or 10 minutes of operation, the AppCallBack() is called with event CYBLE_EVT_STACK_BUSY_STATUS, and eventParam 0x01, but the stack then never makes a corresponding CYBLE_EVT_STACK_BUSY_STATUS with eventParam 0.

Once in this busy state, my calls to CyBle_GattsNotification() (every half second) return CYBLE_ERROR_INVALID_OPERATION.

The only way I can find to get out of this state, is from the MAC to disconnect and reconnect the BLE.

Again, I stress that on the CYW20737S implementation it will run forever with no issues, so I trust the MAC client.

What would make the BLE stack permanently become busy, and how can I fix it?

Will the PROJECT #040: BLE GAME CONTROLLER (Project #040: BLE Game Controller | Cypress Semiconductor ) work with CYBLE-222014-01 and CYBLE-212019-00 ??

I am looking to make a swtich from Cypress to Ti but want to make sure that this application will work before I redo all of the work.

Regards

Mak

Hi all, I used RTC for my PSoC4 BLE project. And I used deepsleep mode. Now I faced an issue. After deepsleep mode the RTC can only hold the time information before the device goes into deepsleep mode. Does RTC run in DeepSleep mode in PSoC4 BLE?

Hi all,

I am using systick interrupt to adjust timing to drive 5 digit 7 segment and it works fine. But when I implement capsense, touch buttons works fine but displays don't blink as before. A problem occurs about display timing. What is the relation between capsense and systick interrupt?

Thanks