PSoC™ 4 Forum Discussions
The default Tx power is set to 0 dBm in the BLE component
Are there known calibrated RSSI valules @ 1 meter ( or 0 meters) for each dBm step?
Or do they need to be calculated dynamically by the client application?
If so, are there any pointers to samples/documentation?
Thank you
Andy
Show LessI'm starting to develop a system for smartphone interface.
The idea is to develop some services that work together for example HID and ANCS/ANS.
All this functions are possible to work without APPs on the smartphone.
In your opinion it is possible to have this kind of services in your micro?
Of course this means an implementation ad hoc because all the suppliers work with APPS.
I'm very interesting in this matter, if someone could give me a response, I'll appreciate very much.
Show LessI bought the kit cy8ckit-049 -42xx. Downloaded the files from the kit page. Watched the video and followed the instructions. Built and created the .cyacd file. using PSoC Creator version 3.1 (no errors on the unchanged project 'Bootloadable Blinking LED') (no errors on changing the timing as the video).
\Flash_Example01\Bootloadable Blinking LED.cydsn\CortexM0\ARM_GCC_484\Debug\Bootloadable Blinking LED.cyacd
Used the bootloader Host to download the .cyacd file into the target device on a fast blink (ie bootloader mode). I then get
04:15:41 PM - Verify Started
04:15:45 PM - The flash row is not valid for the selected array.
Verify completed in 3554ms.
and the target device enters program run mode but runs the default program and not the downloaded. Please can anyone finally deal with the error "The flash row is not valid for the selected array".
From my viewpoint this intro device and software does not work. It came straight out of the box.
Thanks
Mike
Show LessI have read in many places that 23 is the minimum MTU size for BLE, and that devices may negotiate up to 512 depending on the MTU size of the central and peripheral. However in working with the PRoC CYBLE 02201 it seems that 23 is the maximum and that any number less than that is supported. This is demonstrated by this code:
case CYBLE_EVT_GATTS_XCNHG_MTU_REQ:
{
uint16 cyBle_mtuSize;
if(CYBLE_GATT_MTU > ((CYBLE_GATT_XCHG_MTU_PARAM_T *)eventParam)->mtu)
{
cyBle_mtuSize = ((CYBLE_GATT_XCHG_MTU_PARAM_T *)eventParam)->mtu;
}
else
{
cyBle_mtuSize = CYBLE_GATT_MTU;
}
(void)CyBle_GattsExchangeMtuRsp(((CYBLE_GATT_XCHG_MTU_PARAM_T *)eventParam)->connHandle, cyBle_mtuSize);
}
break;
Then when observing the declaration of CyBle_GattsExchangeMtuRsp it says explicitly that the maximum is 23. So for this module my MTU can only ever be 23 to fall within spec?
I have a few other questions about the implications of this.
First, can this be increased by adjusting the L2CAP Settings when configuring BLE? It has an option for MTU size which is currently set to 23.
Second, if 23 is the maximum does that mean I am hard limited to 23 bytes of data per connection interval?
Third, if I am limited to 23 bytes of data per connection interval would that preclude using any characteristics with a data size of more than 23? For example if my characteristic were of size 25 would the L2CAP layer still be able to split that into two transmissions or would data be lost?
Show LessHi,
I have a CYBLE-224110-00 on a Pioneer board and I cannot get the BLE scan to work. CyBle_GapcStartScan() returns OK but I don't get any CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT events. I've tried setting the BLE component up as a Central and as an Observer but no luck. I saw elsewhere that I should try setting cyBle_discoveryInfo.discProcedure, but again, no luck. I've tried using the example projects from '100_Projects_in_100_Days', Day006_Central_IAS and Day011_Central_Observer.
The scan works fine if I use the CY8CKIT-143A development board which I thought was based on the same PSoC hardware, although it is Bluetooth v4.2, whereas the CYBLE-224110-00 is Bluetooth v4.1.
Any ideas?
Regards,
Andy
Show LessHi all,
Today I have bought 2pcs CY8C4248AZI-L485, when I received it, I confirm the mark number is right on the chip, and then I solder it on my PCB, and use the MiniProg3 to try to download my program, in the PSOC creator, I found the software defect the chip part number is CY8C4246AZI-L433. and then I go to solder the second chip, it is same, PSOC creator defect the chip part number is still CY8C4246AZI-L433.
Why it is? TKS!
Show LessI am using a PWM to drive an LED but am wondering how to get around the reset pulse when the compare matches the period at 100% duty cycle. Is there a way to eliminate this pulse when running the PWM at 100% duty cycle?
Show LessHello,
This is regarding file transfer between BLE USB dongle and Connected BLE peer device.
My requirement is that I need to breakdown a file in small packets and send packets to the peer device.
Peer device will send me acknowledgement after receiving a packet. if response is Pass i need to continue with further packets else stop the transfer and inform the user about error.
I'm preparing to reuse the Notification Logger example for my requirement. This is available online as api_examples .
As in this example Connection to peer device is already set.
I need to work on the mechanism of send packet and receiving acknowledgement part. I'm planning to use like below
use instance of ICyL2CapMgr interface to send and receive the data. Kindly let me know if the approach is correct.
If the approach is not correct kindly suggest alternative method the fulfill my requirements.
regards
-Sandeep
Show LessI am attempting to measure the battery level using the 1uF capacitor method. There is an example project BLE_Temperature_Measurement doing exactly this. The project uses the CYB10563-56LQXI with a jumper from p3[0] to VREF and works flawlessly. However when I select the CYBLE-022001 with a jumper from p5[0] to VREF (and change the pins) the measurements no longer work. At 3.3 V in I am getting a reading of 1137mV and at 2.8V in I read 1024mV. What am I missing? What configuration changes need to be made to port the example project to the CYBLE-022001?
Thanks in advance for the help!
I have attached a simplified project to demonstrate the issue
Show Less