I downloaded and tried to install this but the installer detected that I did not have CySmart 1.0.0.471 installed. That's true but I do have the latest 1.2 version.

Is there a better installer that I can use?

This is probably more of an Android problem rather than CYBLE, but I hoped someone might have some insight.

I have developed a server using CYBLE-022001-00 and am testing this with the CySmart app on some Android devices. On a Nexus 5X with Android 6.0.1 my server works as intended: With Security Mode: 'Mode 1', Security Level: 'Authenticated pairing with encryption', I/O Capabilities: 'Display', Bonding Requirement: 'Bonding', when I touch 'pair' in CySmart a dialog appears asking for a passkey. When I enter this the device is paired and I can read and write its characteristics.

However doing exactly the same thing with a Lenovo Yoga Tablet 2 with Android 5.0.1, CySmart does not prompt for the passkey and goes directly to "paired". When I go into the GATT database, I can enumerate the characteristics, but an attempt to read them is met with no response at all (not even an error message). The only way I was able to get the server working on this tablet was to set Security Level (on the CYBLE BLE Component) to 'No security. No Authentication, No Encryption'.

I have Googled this extensively, but cannot find any decent information on BLE support at different versions of Android or on different hardware. I do not know if this is something that does not work until Android 5.1 or 6, or if it is a hardware limitation with the Blootooth chip in this particular Tablet. The behavior is similar when I use pairing from the Android Settings Bluetooth page (prompts for passcode on the Nexus, pairs without this prompt on the Lenovo).

Any ideas anyone?

The Module have a dedicated VREF pad, but I guess it's only for bypass cap use?

If I import a battery monitor example it wastes a pin, example P3.3 that it calls Vref.

What is the difference between VREF and Vref?

I have access to LDO 3.3V voltage, would this help getting around wasting a pin?
​The 0.03Vdrop LDO is for a subsystem, so I do plan to run the BLE directly from li-po battery
and have it turn off the ldo when subsystem is sleeping.

Hello,

I use the device Cy8C4013LQI.

I must disable all components for power saving.
So I followed the instruction to change the debug interface to from SWD to GPIO.

Programming should always be possible.

But after download the firmware I can not connect the device anymore.
I use Segger-Jlink with the newest Firmware and software.

Here I found a similar problem.

http://forum.segger.com/index.php?page=Thread&threadID=2945

There are speaking about the version p, but in the download area only available version j.

So - how can I fix the problem? Now I blocked 3 prototypes.

Hello,

I tried a lot of different things, but nothing works really good.

System-Resourcen
1 digital Input with pullup (used for WakeUp Key)
1 digital Output on 3.2 PWM mode strong drive
Clock 12MHz

If I try the following:

CySysWdtDisable();
PWM.Stop();
CyDelay(50u);
Motor_SetDriveMode(Motor_DM_ALG_HIZ);
Key_PWR_SetDriveMode(Key_PWR_DM_ALG_HIZ);
CySysPmDeepSleep();

still I consume aprox. 670µA on 3.3V

But only if I run this after a fresh Power-On Reset.

If I start the PWM, and run then in the same Power-Off, i come to 1.8mA

How can I save more Power? The Hibernate-Mode don´t exists on this device.
In the Datasheet should be the Power-cosum in DeepSleep 4.5µA - this would be nice.

What must I do, to save the maximum power as possible. I will wakeup on Key-IRQ, I must not keep nothing in Ram - I can reinitialize all again.

Hi all,

Is there any SPI master ( UDB mode ) example codes that illustrates how to use multiple slaves with it ?