good afternoon

any ideas on why callback registered (successfully) with cy_wcm_register_event_callback() is never called when wifi disconnect from AP ?

i would be glad to get your experience on such issues.

many thanks

best regards

Hello,

I receive over SPP a batches of bytes larger than 256 (varying between 81 bytes and 800 bytes per batch with max 1000 bytes per second). By HCI tracing I was able to see that the byte batches received completely.

This batch should be send to an external MCU by use of PUART (without HW handshake). The PUART is set up properly and tested okay on 115k and 38400 baud. 

I am using in the callback function from SPP  spp_rx_data_callback the buffer-pointer p_data and the buffer length data_len to send the by wiced_hal_puart_synchronous_write(p_data, data_len)  it appears that large batches  are not  transferred correctly, say for batches larger than 256 bytes the maximum number of bytes transferred is around 256.

For batches smaller than 256 bytes (say 242) I get the correct 242 bytes plus some additional from the begin of the buffer plus some that are not assignable. 

Is there a limit of 256 bytes in the TX buffer ? 

Or is there a limit in the SPP reception buffer ?

How can I send securely these number of bytes?

    WICED_BT_TRACE("###############################\n");

    WICED_BT_TRACE("%s handle: %d len: %d %02x-%02x\n", __FUNCTION__, session_handle, data_len, p_data[0], p_data[data_len - 1]);

    WICED_BT_TRACE("###############################\n");

     wiced_hal_puart_print("\n########## BEGIN #############\n");

    wiced_hal_puart_synchronous_write(p_data, data_len);

    if (data_len>0)

    {

    wiced_hal_puart_synchronous_write(p_data, data_len);

    }

 wiced_hal_puart_print("\n##########  END  #############\n");

I walked into a PSOC 5LP design where it was assumed the SAR was running a full 12-bit unsigned resolution in single ended mode. This didn't appear to be the case and after struggling with settings both high level as well as low level register settings I can't seem to make it work as a 12-bit single-ended unsigned ADC. Is this possible with this device? If so, please tell me how to use it that way. Also, please add this question to the list of FAQs for these devices.

Hi,

Could you please help me with Schematic and firmware design support to drive Segment LEDs using the PSoC 5LP chip?
We have to drive a seven-digit seven segment display with various segment current from 16-bit serial input.

Regards,

Mari 

I am trying to compile a C/C++ makefile project using the Eclipse IDE for ModusToolbox (Version:  2.2.0, Build ID: 2181) for CY8CKIT-062-BLE  target.  I am able to compile  *.c and *.cpp files but *.cc files  is excluded from the compilation.

If I add following in the Makefile:

SOURCES = $(wildcard extlib/*.cc) 

The build console displays following error message:

../mtb_shared/core-make/latest-v1.X/make/core/build.mk:386: *** Incompatible source file type encountered while constructing explicit rule: extlib/utils.cc. Stop.

 I tried creating a project for the CY8C6245 processor on PSOC Creator 4.4.

  It is not in the list of allowable processors.  The PSOC 62 processor version  246 and 247 parts are there, but not the 245.

  What can I download to support the CY8C6245 on PSOC Creator?

Hi,

Previously it was possible to see a list of forum posts, which I originated, and another one where I participated. Are there such options in new forum?

How can I find my recent posts?

/odissey1

Hi everyone,

I want to configure the DS-1 port of CY611 EZ-USB HX3PD EVK to supply 12V. But when I try to configure  using EZ-USB HX3PD configuration Utility - PD Controller- Port 1, it shows me error - Atleast one 5V PDO should be enabled in Source PDO. But if add another source PDO of 5V, it does not save the configuration.

Can anyone help please ?

Thanks

Sugreev

I  have programmed a CY8C428-LQI-BL583 succesfully with some code  that is stable and works as a datalogger.

The BLE component has a device address as follows;

I have been using CySmart to analyse the bluetooth environment, and am confused as the reported Bluetooth address is different to that set above.

Can anyone explain why they are different ?