PSoC™ 4 Forum Discussions

Hi everyone.

I'm working on communication client-server.

I have some questions

 - Attribute MTU Size in BLE datasheet
Maximum Transmission Unit size (bytes) of an attribute to be used in the design. Valid range is
from 23 to 512 bytes. This value is used to respond to an Exchange MTU request from the GATT
Client.

I don't understand exactly.

If MTU size increase 512 from 23 bytes. What effects are observed ?

In which situations should I increase or decrease mtu size?

Thanks,

I've been using a CY5677 BLE Dongle with my project based on a CY8C4248 PSoC 4 device and I just purchased a CY5672 RDK (http://www.cypress.com/documentation/development-kitsboards/cy5672-proctm-ble-remote-control-reference-design-kit-guide) which comes with a very similar BLE Dongle and I can't get CySmart1.2 to recognize the new dongle.

Looking in Windows Device Manager with the dongle plugged in I see several devices that aren't present when the dongle is removed:

1 USBUART  - No driver loaded

2 HID-compliant consumer control devices with a standard Windows driver

2 HID-compliant devices with a standard Windows driver

2 USB Input Devices with a standard Windows driver

I searched the Cypress website for a driver and came up empty.  I did find a few threads in the forums about similar issues but some had links to files that no longer exist or simply didn't include any viable answers.

What do I have to do to get CySmart to recognize the dongle that comes with the CY5672 RDK?

-lance

Hello, 

I am working with the S6SAE101A00SA1002 Solar-Powered IoT Device Kit and I am currently trying to change the advertisement rate of the CYBLE-022001-00 EZ-BLE PRoC Module to 10 minutes. 

The code I am looking at is the example code "EH_Motherboard". In the main.h file there is the following define: 

 #define ITRVL_SENSOR_ON                         (10240u) /* 10.24s */

First of all, the default value 10240 should lead to an advertisment of 10.24s. I measured the blink frequency of the "User LED" on the receiver, the LED blinks every 5.8s. (I assume the LED blinks as soon as a packet arrives?)

However, even if I increase the value ITRVL_SENSOR_ON , the LED still blinks every 5.8s. If I decrease the value, the LED blinks more often (at least...). 

The problem I see is that  ITRVL_SENSOR_ON is given to the function

CYBLE_API_RESULT_T Beacon_GappStartAdvertisement(uint32_t advertisingInterval)

and is therefore casted into a uint32_t. 

In the function itself the value is then casted to a uint16_t: 

      cyBle_discoveryModeInfo.advParam->advIntvMin = (advertisingInterval << 3) / 5;
      cyBle_discoveryModeInfo.advParam->advIntvMax = cyBle_discoveryModeInfo.advParam->advIntvMin;

I think it is not possible to increase the advertisement rate to 10 minutes using this code. Any suggestions on how I get the chip to send the data every 10 minutes? 🙂

Thank you a lot in advance for your help!

Best regards, 

sma

Hello,

does someone have the Android studio  application project source for CypressBLE-Beacon?

Thank you.

On a PSOC 4000s, 2 x SCBs are available. However I have a need for 3 x UART bi-directional interfaces. SCB1 is mappable to 2 different ports (P0, P3), SCB0 to a single port (P4).

Is it possible, during run-time in an application, to multiplex SCB1 between P0 and P3? I'm thinking build/synthesis only allows a fixed SCB-to-port mapping, but that would make a world of difference if this can be dynamic!

If not possible, I'm open to alternate approaches. UART is not a requirement, slow baud rade is okay (e.g. 9600) but flash memory is tight. SW UART component is Tx only. I feel writing my own Rx or protocol would be a time sink.

Thanks!

Hi, I've developed an application using the CY5671 PROC BLE MODULE, using the Pionner kit, it works withthe FindMe profile and also sends notifications for the battery value. It was tested with a mobile app and they are both working. After testing it I have changed the target to the CYBLE-022001-00 (using the Project/Device Selector) and changed the pins used (the application is using 3 output pins and one ADC input pin), in order to match the hardware design using the CYBLE-022001-00. I have currently no access to the CYBLE-022001-00, because the test is being done elsewhere, but I have been informed that they were able to see some advertising messages but they try to connect to the device and it fails, and also observe a strange behavior in the power supply, it is regulated to 4.2V, and with the software I sent it drops to 3.8V, but keeps at 4.2 with other firmware. My initial suspicion was that I might be using wrong pins (especially output pins) that could be causing some short circuit, but this isn't the case, we are only using 4 pins that have been confirmed...

Any idea of what could be the problem? Any particular care when migrating working code from the CY5671 module to the CYBLE-022001-00 module?

Best regards

Fernando

Hi,

I'm using EZ-Serial in binary mode and I'm unable to set the Device Name (it works flawlessly in Text Mode using "SDN,N=TEST"). My packet looks like this:

0xc0 0x04 0x04 0x0f 'T' 'E' 'S' 'T'

and, of course, the checksum. What am I doing wrong here?

Thanks,

Andreas