PSoC™ 4 Forum Discussions

Hi Everyone,

I am using a cyble-224116-01 BLE module along with PSOC Creator 4.2. I include the stdlib.h library and my code compiles correctly, however, a call to calloc() or malloc() always returns null. I was wondering if I had to do anything special for it to work properly? Or is calloc() and malloc() not operable for my device?

Regards, Uziel.

Hello,

I'm using the PSoC programmer on some custom boards with CY8C5868LTI-LP038.

I can program properly most of them.

However, for 2 of them I always get this error message:

"262144 FLASH bytes

Erase Succeeded

Programing of flash starting

Failled: Time out of SPC Polling

Lost communication with chip

Status=0x82"

For the other one the message ends with "Status=0x26".

I've inspected the 5 wire connection from the programmer to the board and every thing seems OK.

I was wondering if anyone could give me a hint of what these error codes mean, so I know what to look for.

Any feedback is appreciated.

Thank you.

Hello,

I am using CYBLE-224110-00 BLE module on a custom pcb with an application and the OTA upgradable stack in the Creator workspace.

The BLE component in the application is set at -6dBm tx power, and in the firmware  the PA/LNA is set in high power Mode in the BLE CYBLE_EVT_STACK_ON.

Shall these settings be applied to the BLE component in the Upgradable Stack project or bypass the PA/LNA?

The problem is: while switching to OTA bootloader, the device is not shown advertising by the Android client app, but it is detected normally when running the application. So there must be some issue with the tx settings while using the BLE component from the OTA upgrade firmware.

What is advisable to configure the BLE and PA/LNA for the OTA side?

Regards.

Dear friends,

now i am using CySmar v1.3  emulator tool ,but this toot only show unsupported device(Dongle model CY5677).please anyone help me how to solve this problem. I attached  getting problem screenshot int the mail.

Hello,

I would like to check the reason why MBR3 require pulled-up on I2C line if the pins is unsed.

Basically, I2C should be used by pulled-up but if I2C is not used and does not connect to anything device, MBR3 is not controlled ever after even if MBR3 enter stard condition. So I think we can be pulled-down on I2C line.

Please let me know the reason MBR3 need pulled-up.

Best regards,

We are planning to consider using CY8CKIT-049.
We are going to proceed with reference to "CY8CKIT-049-4xx PSoC R 4 Prototyping Kit Guide".
However, "CY8CKIT-049 4xxx Kit Only" and "CY8CKIT-049 4xxx Kit Setup" can not be installed.

Kit Only

Kit Setup

Therefore, We would like to provide us a sample project of "CY8CKIT-049-4xx PSoC R 4 Prototyping Kit Guide".

Regards,

We have a serious issue and cannot resolve it, please see if you can help.

On Android, when pairing, we get no services, once the pairing is accomplished via multiple reconnect events and it connects, it will work fine afterward.  We are prevented from going to production because of this concern.

When we pair, with a fixed pairing code, we get an error of no services, and sometimes the BLE stack gets stuck and thinks it is connected, but the app, ours or CYSMART gets a no services response.

1. We have the crystal trim code in our BLE start event

2. We have regenerated all UUIDs in 128 bit mode

Our bundle is attached, please help out as soon as you are able, this is an urgent matter.