Hello everybody,

we are currently evaluating the possibility to enhance our products with a BLE interface. We want to use a CYBLE-022001-00 for this. I am trying to get a firmware on the module via our main processor (EFM32GG). I used the AN84858 application note as a template for my project (http://www.cypress.com/documentation/application-notes/an84858-psoc-4-programming-using-external-microcontroller-hssp?source=search&keywords=an84858).

The MCU is connected with the 5-pin debug port on the evaluation board of the EZ-BLE. When  the module is preprogrammed with the PsoC Creator I can easily update the module´s firmware with a heximage from my board. If the flash is erased/ the module is new my code fails in the DeviceAcquire() function. Right after the setting the IMO to 48MHz the PollSromStatus() returns an error. It fails at reading the suitable CPUSS_SYSREQ value.

I´m only comfortable with programming the EFM32 family yet, so I might have overlooked some details. Maybe someone has an idea.

Thanks and greetings from Berlin

Hi,

I have a very big problem with DeepSleep in my project.

I use the CY8CKIT-042-BLE with the CY8CKIT-043A device. I have a very big project with an SPI-RTC, an SPI-LCD-Display, an adc, an Op-Amp, a timer, a reset-watchdog and of course the BLE-Component.

The RTC generates an interrupt each second and triggers the adc to do a measurement. Beside that a timer-component generates a 40ms-Interrupt for the handling of the BLE. Thats o.k. It works perfect if I use the "Sleep" mode.

I used the Global-Signal component with the "AllPortInt" and a custom ISR to wake up the device from the GPIO-Interrupt from the external RTC.

If I try to use the "DeepSleep" according to the example, I see that the device wakes up one time and then it is stuck in an endless loop. In the picture I added you see that the DeepSleep is entered (first signal goes low). It is interrupted by the BLE-component for some milliseconds. But if the RTC triggers (falling edge) the DeepSleep is left and never entered again. At 5.5s it looks like the AllPortInt triggers again, but I don't know why. I clear the interrupt in the ISR by calling _ClearPending() in both, the single GPIO-ISR and the AllPortInt-ISR.
This is the call stack from this situation:

0 CySysPmSleep() .\Generated_Source\PSoC4\cyPm.c 52 0x0000874A (All)
1 ll_exit_low_power_mode() ?????? ?????? 0x0000DC06 (All)
2 ll_task_handler() ?????? ?????? 0x000112C8 (All)
3 llft_service_queue() ?????? ?????? 0x00011AAE (All)
4 llf_task_start_routine() ?????? ?????? 0x00011A06 (All)
5 CyBle_StackTaskHandler() ?????? ?????? 0x0000C3E6 (All)
6 OS_scheduler() ?????? ?????? 0x0000D276 (All)
7 CyBleStackMgr_ProcessBleEvents() ?????? ?????? 0x0000C116 (All)
8 CyBle_ProcessEvents() ?????? ?????? 0x0000BE38 (All)
9 main() .\main.c 98 0x00000444 (All)

I have no clue what I should do now?
I hope that anybody can help me!

Thanks Andreas

Hi All,

I am using SPI & UART in my project,

Initially i added  UART(v2.50) into my project , works everything as expected.

Later i added SPI Master Fullduplex macro  and getting this below error.

Pin guidance unavailable: Resource limit: Maximum number of Macrocells exceeded (max=32, needed=37).

If i add the originlal SPI Master (v2.50) aslo im getting same error

please provide me the solutions

Thanks,

Ashok R

​Reading data at low addresses changes depending on when I read it.

How big is the RAM overlay? I assume it is for the interrupt vector table and that the table can not be in Flash.

I'm trying to calculate a CRC on the firmware during initialization and also later while it is running.

Hello Community, This is Gaurav.

I have a sample program of Beacon which has 1 error and in not able to remove it. (out of my understanding). Please guide me how i can remove it.

Attached the bundle file below.

Thank you 

Hi,

I have a custom pcb with the PRoC BLE and so far so good... I can debug and program with the MiniProg3 attached via the 5 ways connector.

I just tried the sample code in Cypress AN92584 with this switch set DEEPSLEEP_ONLY... This is supposed to give a good idea about deep sleep current consumption and current leakage. Since I did program this simple app, PSoC Creator doesn't see the target... so I can't program it anymore.

Is there a way to retrieve control of the target? Have I bricked this device?

Any help appreciated...

Cheers

X

Hi all,

I'm trying to make it possible to read the battery level from my device using SAR ADC, but unfortunately I can't manage to connect it properly. I've been searching some info on the Internet and I was trying to make it similar to the solutions I've found. I've attached a scheme of my connection. Could someone give me a hand how to make it right?

I have been working with the PCF8574 chip which is set up to work in a 4 bit mode where P0-P3 from the 8574 chip  are connected to D4-D7 of the LCD and P4-P6  are connected to E, R/W and RS. P7 is connected to the Back Plane. I have been trying to use the I2C_LCD component which has not worked since it appears that the data is being transferred in an 8 bit format rather than upper and lower 4 bit nibbles. Are there any software solutions? I am hoping someone can point me in the right direction.

My PC board Layout design would be significantly simpler and I would be able to keep it to a single sided board if I could find an I2C solution rather than having to use the CHAR_LCD component to interface with the LCD.

Thanks