PSoC™ 4 Forum Discussions
Using the project UART_to_BLE_peripheral, I am getting errors when compiling.
These are identifiers not declared for usage in app_ble library
CYBLE_SERVER_UART_SERVER_UART_TX_DATA_CLIENT_CHARACTERISTIC_CONFIGURATION_DESC_HANDLE
CYBLE_STATE_ADVERTISING
Any idea where and how should be declared?
Show LessHi,
I use the CYBLE-222014-01 (BLE 4.2) module as a master to control a few I2C slaves. The hardware design requires to power down the whole I2C bus most of the time (controlled by a GPIO of the Cypress module). The module doesn't have to go to any sleep modes (for now). I'm wondering what is the best way is to do this? Do I have to call I2C_Start() when to bus is powered or it doesn't matter? Do I have to call I2C_Stop() before powering the bus down or can I just leave the component running? Of course, I do not do any I2C transactions on the bus while the bus is powered down.
-Tamás
Hello,
We need to generate accurate timing / waveform output using PSoC4 device.
PSoC4 does not have a built in crystal oscilltor support.
Internal IMO is +-2%, trimmable to certain range, (this is not sufficient and correct compare to crystal oscillator)
External crystal oscillators are expensive and consumes more power.
Do you have any suggetion on this issue?
Regards,
Vinay
Show LessI've a CYBLE-022001-00 BLE PRoC module and it is configured as GAP peripheral device. My intention is to only allow it to be discovered by a single GAP central device. Therefore, I've tried to choose "Connectable directed advertising" type in the GAP Settings (also to populate the target Random device address in the advertising packet). However, this option is not available in the dropped down list. I would appreciate if someone has an idea/suggestion. Thanks!
Show LessI have been working on a project using the CYBLE-222005-00 module (BLE 4.1) and nicely developed all the required features including BLE beaconing, deep sleep, etc. Now the hardware platform has moved to CYBLE-222014-01 (BLE 4.2) and certain functionalities of my software stopped working (I guess related to deep sleep mode but I can't confirm that). I didn't expect this at all, I thought this would be a fairly painless move. Before getting deep into debugging and wasting a lot of time I thought to ask if there's a migration guide for the new module? If not anyone with more understanding could maybe point out differences or potential incompatibilities between the two modules? I tried both PSoC Creator 3.3 and 4.0. Any help is appreciated. Thanks!
-Tamás
UPDATE: It seems that the I2C module behaves strangely. I do an I2C_Stop() call before deep sleep and I suspect this causes the code to crash. Is it possible that I2C is different on the BLE 4.2 module?
Show LessHi,
I downloaded the capsense one button example from here
I tried to open it with PSoC Creator 3.3 CP2 (3.3.0.7343)
But I am getting following message:
Unable to open the project ".\CE210291_CapSense_P4_One_Button.cydsn\CE210291_CapSense_P4_One_Button.cyprj": Requested value 'CortexM0p' was not found.
Is it possible to open this example?
Br, Ville
Show LessWe are using the CYBLE-022001-00 module in a project and need to send some commands to another device via the I2c bus. Is anyone aware of a sample project that covers this application?
Show LessI'm trying to build a device which has a single device SPI plus I2C devices. I want to use the CYBLE-224116-01 module (BLE 4.2 + PA/LNA) -- but what I say below also applies to the BLE 4.1 version, CYBLE-224110-00. I'd like to have SWD available for programming and debugging.
But I don't see how to make it work. Because:
1. SCLK 0 is only available on p0.7, which is needed for SWD, or p1.7, which doesn't come out of the module.
2. And you can't use SPI on SCB1 at all, since SCB1 MOSI does not seem to come out of the module on ANY pin.
To get around this, I'd have to add jumpers for "programming mode" in order to program, and wouldn't be able to use the debugger while keeping SPI live. This seems like a serious oversight, and will both make production programming and development more annoying than necessary.
Could things really be this screwed up?
Show LessThe only way to program the module is the PSoc Creator? I need that a user can change the bluetooth name without use the PSoc Creator.
Is it possible? How can ask at bluetooth module to change the name?
Show LessHello,
Can some one explain to me how exactly can I create the following behavior?
I want that any client that wants to connect to a peripheral, server device to be asked a password provided in advance and only when the correct password is given to connect, see the profile,etc. Next I want that the client to be able to make a pair action to the device and every time the device is near to connect automatically to it. I know that some parts of this behavior should be accomplish by the client like the automatically connection to the device but I am aware that something should also be done in peripheral which is a PSOC 4.
I already go through the examples like privicy(017), oob pairing(032) and bonding (015) but somehow I cannot fully understand them to implement my scenario. Also it would be great if you can also explain the state(event) in which a particular action should take place. For example I used CyBle_GapFixAuthPassKey (1, 123456); in CYBLE_EVT_STACK_ON and I was able to pair in CYSmart with this code but I am not sure this is all. My Ble is set as Mode 1 security Authenticated pairing with encryption and I/O capabilities KeyBoard and Display(even if my device doesn't have such, I personally am not sure why are those used) and Bonding.
Thank you!
Show Less