PSoC™ 4 Forum Discussions

Hello,

I have been using all 3 WDTs in the design: WDT1 - general watch dog with reset at 2 sec, and also used as 1 sec interrupt timer(in certain cases); WDT0 - 2 sec interrupt, WDT2 as 32 s period timer. As I know there is no way to use CySysWdtWriteMatch for WDT2. My question is if I want to have to change the period of WDT2, lets say 32, 16 and 8 seconds, how can I change the period? Is it even possible and if now can someone explain why?

Thank you!

Using the PSoC 4 BLE Pioneer board and the example project called "BLE Proximity Bonding- Peripheral" by GRSR I can connect to my iPad Air 2 using the "LightBlue" app just fine, and they both act as if they are bonded if I power down the Pioneer board and power it back up....unless I leave its power off for 7 minutes or more.   Less than 7 minutes and they re-connect as they should.  More than 7 minutes and it's as if they never heard of each other before.  I've also tried the same test using an app I created for the iPad with TechBASIC with the same results. 

Any thoughts or advice anyone?

Thanks,

Dennis

Hi All,

I've been able to power up my bluetooth module and see it advertising from my phone.

I've also been able to capture events transmitted from the module to my external MCU via UART.

Now, I am trying to write commands to the module... I do not seem to be getting the appropriate responses however. I just seem to be getting an echo back of whatever I send. eg. /ping will return to me /ping. I am terminating all the commands I try with '\r'.

I was thinking perhaps it has to do with this deep sleep mode mentioned in section 3.1.5.5 of the EZ-Serial User Guide. However, I imagine if the unit was truly in deep sleep, it wouldn't respond anything to my commands? In the guide I can't see anything about this behaviour, has anyone any experience with it?

Hello everybody,

My last problem, discussed in this thread https://community.cypress.com/thread/32891​, covered the issues that I encounter implementing the privacy feature. The last project attached contain a solution that works for 4.1 and 4.2 BLE phones with some problems on 4.0 and also on cypress dongle with 4.1 BLE.

Now I would like to add the OTA upgradeable stack and application example. I had the example running on older boards that we had manufactured but without privacy so I believed everything was ok but now with privacy I found out that I was overconfident. My problem is that if a bonded device trigger an upgrade the code will go to the stack project ok but there the BLE component has public address and the bonding info is not present and also the phone will need to authenticate again which is not desirable since the user should not do anything only to approve the upgrade.

My questions will be:

1) in order to keep the privacy, after an initial bonding only the bonded phone to be able to connect, do I need to duplicate the privacy code on the stack as well?

2) if I save the bonding with CyBle_StoreBondingData in application is the info available on stack if I retrieve it with CyBle_GapGetBondedDevicesList? (as I read the info should not be available) How can I pass this info from application to stack and back to application if the stack is not upgraded?

Thanks in advance!

I am using 4200M dev kit for a project. The PSOC is configuring an SCB as SPI Master in configured mode and talks to three slaves off board. Two of my slaves use the falling edge of the clock to clock in the data whereas one slave uses the rising edge of the clock to clock in the data. I am also using Firmware controlled chip select for each of the slave

Is it possible to change the SPI Sub mode for each of the slave at run time via any API?  I looked through the data sheet for the SCB component version 4.0 and could not find any.