PSoC™ 4 Forum Discussions
Hello,
I'm newbie in cypress, want to develop my bare-metal board with few touch buttons and proximity detection. I'm trying to choose right device for this (simplest which will fit). I was thinking about CY8C4045 but it doesn't support CapSense CSD component. I cannot figure out the benefit of using CapSense CSD compare to simple CapSense component, so I'd like to ask for short explanation of difference. Sensitivity is important for me (surface will be 4mm acryllic).
Show LessSince the OTA need bonding, So I add bonding to my project,and the security setting:mode1, no input no output, unauthenticated paring with encryption. But I found if the central more than 4, than the latest central seems can not bond to my peripheral, so my question is do I need to remove bonded central if the 5th central want to bond to it? I think the SDK will automatically remove the oldest central.
I use cybl10463 and BLE component version 3.10.
Show LessHi,
Does anyone have an example project showing PSOC4 or PROC4 BLE working with iOS BLE MIDI?
I saw a couple of guys on YouTube showing it working, but haven't seen an example project. I've read the Apple BLE MIDI spec, and the Cypress BLE guide, but would appreciate a setup example in Creator.
Thanks,
John
Show LessHi all,
I would like to be able to write new period to my timer, while the program is running. But when I'm trying to do that:
uint32 period;
UART_UartPutString("New Timer period");
UART_UartPutString("\r\n>");
period = UART_UartGetChar();
Timer_WritePeriod(period);
I'm not able to set it right. For example when I type 10000 the period is only 10 and I'm not sure what I'm doing wrong. I've uploaded my whole project. Thanks for any help.
Show LessHi, I am absolutely new in Cypress MCU. I did buy in Arrow.com CY8CKIT-143 and it seems I made a mistake. I thought I can use CY8CKIT-143 as a separate board but as I understood right after paying I should use CY8CKIT-143 in conjunction with CY8CKIT-042-BLE. I am disappointed ...
I have 2 demo boards: CY8CKIT-043 and CY8CKIT-049-42XX. Is it possible to use these boards with CY8CKIT-143 module ?
And also can I use CY8CKIT-143 module with my favorite STM32 ?
Actually all these boards are on the way to me, so now I can only ask you and wait.
Thank you.
Hello PSOC enthusiasts. I am playing with CYC8KIT 420 BLE kit and MPU 6050 accelerometer. I found a project done by Sam (http://samselectronicsprojects.blogspot.com/2014/07/getting-roll-pitch-and-yaw-from-mpu-6050.html).
The only change I made is that I update the files for CYC8KIT. The project should be printing accelerometer reading on TeraTerm screen. I am not able to get that except a message indicating that UART initialized.
Could some body have a quick look at my project and give me some insight. Thank you in advance.
Best,
Apoorva
Show LessHi
into my last project i tryed to set the security level to :"Unauthenticated pairing with encryption" and the same setting on Cysmart 1.2 on PC.
When i connect to the device and perform a read all caractheristics i receive this message : Read characteristic value failed. Insufficient encryption
Where is the problem? there is something to set on DB?
in any case Cysmart is able to write and read custom caractheristic but i receive this message.
thank
Show LessWill placing the CYBLE-012011-00 module on the back of the device (and hence facing the wall) degrade wireless performance?
There will be more than 10mm of clearance from the wall.
I have looked at the radiation patterns in "AN91445 - Antenna Design and RF Layout Guidelines" but not really sure how to interpret them.
The module has an integrated trace antenna.
Could anyone provide some advice?
Thank you.
Show LessAny tips on how to implement a secure server when the client uses the 'random' address type? I found that with "bonding requirement" set to "Bonding" my server would still accept a connection from an un-bound client. So I set the Advertising Filter Policy to "Scan request: Any | Connect request: White list" and wrote some code to keep the whitelist aligned with the bonded devices list. This worked well until I encountered a client device that used a random address for privacy (CyBle_GapGetPeerBdAddr returns type 1 in CYBLE_GAP_BD_ADDR_T:type). Now it works fine immediately after bonding, but gets locked out (because of whitelisting) when the address changes.
So how can I prevent un-bonded clients from connecting while allowing bonded clients which use random addresses?
EDIT: Arghh! On further research I tried:
case CYBLE_EVT_GAP_AUTH_REQ:
wrAuthInfo = (CYBLE_GAP_AUTH_INFO_T *)eventParam;
if (bond_closed) {
wrAuthInfo->bonding = CYBLE_GAP_BONDING_NONE;
wrAuthInfo->authErr = CYBLE_GAP_AUTH_ERROR_AUTHENTICATION_REQ_NOT_MET;
}
break;
In my event handler. This appears to be quantum code - if I have a breakpoint in the conditional it gets triggered and the pairing request is rejected as intended. However remove that breakpoint and pairing (with bonding) happens as if the conditional is false!
I am beginning to see why so much IoT technology gets shipped insecure! I've spent days banging my head against this brick wall - all my good intentions get thwarted by awful documentation and "insecure by default" APIs!
Help please!
Show Less