PSoC™ 4 Forum Discussions

It's written that the Ram status is not retained at stop mode. Does that mean the device removes the peer devices and needs to get paired everytime when he needs to communicate?

Hi All

I am working in a direction to use SysTick timer in order to record a time period in between two events and save it in a variable. SysTick Timer has not any dedicated API to get time period from it. Can anybody please guide me to resolve this?

I am using your example code UART_to_BLE_central and UART_To_BLE_peripheral to test serial communication between two devices CY8C4248LQI-BL483 (Peripheral) and the PRoc Dongle (Central).  I am trying to find the best insertion point for our code.  Data will be transmitted from the central device to the peripheral.   Instead of being transmitted out through the UART on the peripheral device, we will be collecting the data to be sent out to a display instead.  So on the Peripheral side, the serial transmission touches HandleUartRxTraffic in app_UART.c which points to UART_SpiUartPutArray in the UART_SPI_UART.c file.  This in turn touches UART_SpiUartWriteTxData in the same file.  

What I am noticing is when I put a breakpoint on any one of these routines and start typing data in from the Central device via Tera Term, I will break multiple times on the same routine for a single character typed.  I can set conditional break points to ensure I am getting all the characters which I transmitted ( in this case, at least I know how many characters to receive);  However, I am not certain how to handle this in my code.   So the questions are, why am I invoking the same function over and over again for a single piece of data, and how can I get around this so I know each piece of data sent is unique?  

Clearly this is doable since the receive terminal does not duplicate characters, though it's a mystery at this point why it does not.

Hi,

Due to the unsupported situation of BLE Qt class in Windows OS, I just installed Linux Ubuntu OS.

However, not only Qt in Ubuntu cannot find our BLE dongle, but also the bluetooth application in Ubuntu cannot find a BLE device.

Since CySmart/PSoC Creator/Programmer does not support Linux OS, could anyone tell me, how could I find BLE dongle in Linux OS?

Thank you!

Hi to all,

I have done a simple program for testing the consumption of the EZ PRoC Module (CYBLE-022001-00). With that code the outcomes are as follows:

- Normal Mode: 12.47mA

- Deep Sleep: 1.48mA

- Hibernate: 0.24mA

The measures have been done according to the recommendations on the page 85, BLE Pioner Kit Guide for CY8CKIT-042-BLE documentation.

The code is attached. It uses Timer1 for create an interruption 5 seconds after starting. When the interruption happens, the module entries on one of the low power mode: or Deep Sleep or Hibernate, according to the mode the user has selected before the compilation and flashing.

According to the documentation (EZ-BLE PRoC Module, page 13), values should be near to the next:

- Normal Mode: 13.14mA

- Deep Sleep: 1.3uA

- Hibernate: 150nA

Does anyone could tell me why the values I have measured for low power are so far than it should be expected?

In advance, I appreciate a lot any suggestion.

I'm trying to establish the lowest power level (ie, hibernate/sleep/deep sleep) to which I can take the 4200 and still recover my PRS state information at wakeup..   the datasheet talks about PRS_sleep/wakeup, but its not clear about are any restrictions, caveats, etc. concerning level of sleep and the effects of recovery after a reset coming back up from some of the lower power sleep states (ie, deep sleep)...

I'd like to put the device into the lowest power mode possible and still recover the PRS state.. as I don't want the PRS to reinit each time.. the repetition would be very obvious to the user and bad for the product :)..

The device is likely to stay idle for very long periods -- weeks/months, between activity periods where it will be used for a few hours and then put away again..

Hi,

I'm having problems saving settings to the flash after manual runtime tuning. Psoc4 Capsense design guideline says following ->

Note After finishing the manual tuning, you should change the tuning method in the Component configuration form
“Manual with run-time tuning” to “Manual”. The “Manual” option stores the tuning parameters in flash and these
cannot be changed during run-time.

After I have powered off/on the device, the old settings appear.

Does anybody know when exactly the settings are stored to the flash and what is the exact procedure?

I'm using Psoc Creator 3.1 SP2.

Br,

Kari