PSoC™ 4 Forum Discussions
How frequency need to call CyBle_ProcessEvents?
I use RTOS and BLE connection interval 100ms.
Calling CyBle_ProcessEvents evry 10ms, is enough? Or need less?
Or need, like in your example, all time call CyBle_ProcessEvents in loop?
Show LessHello all,
Is there a way to store and load different profiles? For example if I had two HID over GATT profiles (one for mouse, another for gamepad) is there a way to store both in flash and select them on boot?
Thanks,
Rendman
Show LessPSoC Creator 3.1 is the new version of the IDE that includes support for the new Bluetooth Low Energy devices from Cypress - PSoC 4 BLE and PRoC BLE.
Also included with this release is the new BLE Component, which abstracts the entire Bluetooth Low Energy v4.1 Core Specification into a simple, easy-to-use Component that can easily be dragged and dropped onto your design. The new BLE Component allows easily and quick configuration of the entire Bluetooth Low Energy Protocol Stack using the GUI-based configuration tool. Also included with the BLE Component are a set of new BLE-specific APIs that enable easy communication over the BLE wireless link.
Grab an Early Acess (Beta) version of PSoC Creator 3.1, here: www.cypress.com/CreatorEA
(this will not overwrite you current installation of PSoC Creator 3.0)
Show LessPSoC 4 BLE = ARM Cortex-M0 + Programmable Analog Front Ends + Programmable Digital + CapSense + Bluetooth LE Radio with integrated Balun --> all in a one-chip solution!
Learn all about our latest PSoC device for the IoT, PSoC 4 BLE at www.cypress.com/PSoC4BLE
Implement your own Bluetooth LE (Smart) design using the brand new BLE Pioneer Kit at www.cypress.com/cy8ckit-042-ble
Get early access to PSoC Creator 3.1 (Beta) with a new Bluetooth LE (Smart) Component at www.cypress.com/CreatorEA
PSoC 4 BLE is your one-chip solution for low power wireless, sensor-based systems for the IoT
Show LessPSoC 4 BLE is a single-chip SoC that integrates the following:
- ARM Cortex-M0 CPU up to 48 MHz
- 256/32Kb, 128/16Kb Flash/SRAM (128Kb sampling now, 256Kb coming soon)
- 2.4 GHz Bluetooth Low Energy Radio with Integrated Balun
- 4 x Opamps (operational in Deep-Sleep Mode)
- 2 x Comparators (operational in Deep-Sleep Mode)
- 1 x SAR ADC 12bit, 1-Msps with 8-ch Sequencer
- 1 x CapSense CSD block for touch-sensing
- 4 x TCPWM (Timer/Counter/PWM) blocks
- 2 x SCB (Serial Communication UART/SPI/I2C) block
- 4 x UDB (Universal Digital Blocks, PLD-based programmable logic) blocks
- 1 x Segment LCD block
- 36 GPIO
- Five low-power modes (Active, Sleep, Deep-Sleep, Hibernate, Stop Modes)
A block diagram of the device can be see here: PSoC 4 BLE Block Diagram
The device datasheet (prelim) is available here: PSoC 4 BLE Datasheet
Show LessI have searched around but have not found an answer on how to do this.
I read the SCB documenation but the interrupt information doesn't make much sense to me.
What I want is to have an interrupt fire on every byte received.
I have attached an external interrupt (I think this is the right one, it says for 8 bytes or less use an external)
In advanced I have selected RX FIFO not empty and RX FIFO full. The UART is working but it just does not seem to fire the interrupt.
I have attached my code if someone can spot the error.
Show LessFollowing is an example project for implementing a simple , PSoC 4 Based Proximity Detection. A documentation explaining the same has also been attached.
Show LessI am making a simple state machine for an alarm system using the PSoC 4 Pioneer.
However the build is failing saying I have used too many unique pterms. I have no idea what these are?
Bundle is attached
*********************************************************************************************************************************************
Resource Type : Used : Free : Max : % Used
============================================================
Digital clock dividers : 2 : 2 : 4 : 50.00%
Pins : 15 : 21 : 36 : 41.67%
UDB Macrocells : 19 : 13 : 32 : 59.38%
UDB Unique Pterms : 67 : -3 : 64 : 104.69%
Error: mpr.M0014: Resource limit: Maximum number of UDB Unique Pterms exceeded (max=64, needed=67). (App=cydsfit)
UDB Total Pterms : 72 : : :
UDB Datapath Cells : 0 : 4 : 4 : 0.00%
UDB Status Cells : 0 : 4 : 4 : 0.00%
UDB Control Cells : 0 : 4 : 4 : 0.00%
Interrupts : 0 : 32 : 32 : 0.00%
Comparator/Opamp Fixed Blocks : 0 : 2 : 2 : 0.00%
SAR Fixed Blocks : 0 : 1 : 1 : 0.00%
CSD Fixed Blocks : 0 : 1 : 1 : 0.00%
8-bit CapSense IDACs : 0 : 1 : 1 : 0.00%
7-bit CapSense IDACs : 0 : 1 : 1 : 0.00%
Temperature Sensor : 0 : 1 : 1 : 0.00%
Low Power Comparator : 0 : 2 : 2 : 0.00%
TCPWM Blocks : 0 : 4 : 4 : 0.00%
Serial Communication Blocks : 0 : 2 : 2 : 0.00%
Segment LCD Blocks : 0 : 1 : 1 : 0.00%
Show Less