PSoC™ 4 Forum Discussions
Hi guys, happy Holidays. We're currently programming our design that is using a PSoC 4000S. We're using the example code from CE210311 http://www.cypress.com/file/230881/download to measure the voltage from a pin connected to a sensor in our device. When a voltage threshold is met we have a LED light up.
We flashed the code into the system and the device was successfully programmed for about 10 times today. However after we stimulated the sensor for a while our device became unresponsive and could no longer successfully connect and be programmed again. We tried restarting the PSoC Creator and reconnecting the device to no avail.
Does anyone have any suggestions as to what's causing the issue? We're going to solder a new board again tomorrow, but any tips are appreciated. Thanks!
Show LessHi Everyone,
I have planned to develop an BLE 4.2 using cypress PSOC CY8C4248LQI-BL543 kindly suggest how to design antenna.
Enclosure plastic (Poly carbonate)
Thank you
K.Dhanasekar
Show LessWhat can it be when the function (while(0u == (nRF_SPI_GetMasterInterruptSource() & nRF_SPI_INTR_MASTER_SPI_DONE))) goes to infinite loops?
void SPI_wait_done() {
nRF_SPI_ClearMasterInterruptSource(nRF_SPI_INTR_MASTER_SPI_DONE);
while(0u == (nRF_SPI_GetMasterInterruptSource() & nRF_SPI_INTR_MASTER_SPI_DONE))
; /* Wait while Master completes transfer */
/* Clear interrupt source after transfer completion */
nRF_SPI_ClearMasterInterruptSource(nRF_SPI_INTR_MASTER_SPI_DONE);
}
Show LessHi,
I have been using a CE221653 - PSoC 4 Bootloader and Bootloadable project for CapSense (Using Proximity). Instead of Bootloader Host from PSoC creator 4.2 to program generated .cyacd file. However, would like to flash cyacd file using my software I2C utility as I will be using CapSense on one of the products. Can you please sahre whether .hex or .cyacd file needs to be flashed? And is there any document or reference code if available to know how BootLoader Host tool flashes the firmware in Capsense?
I appreciate if you can provide your inputs.
Thanks,
Bhavik
Show LessHello,
I wonder I can add bit fields under custom characteristic field for GATT settings in BLE component.
I see adopted characteristic shows the sub-bit fields of field like following,
I tried to add non adopted characteristic for testing using custom characteristic but I don't know how to add sub bit fields.
I assume it doesn't allow it. Is my understanding correct?
Thank you,
Sang
Hi All
I' convert a BLE project for CYBLE-022001-00 from PSOC Creator to Keil uVision 5.21.
All conversion is OK but unfortunatly at the end of compilation this message appear:
".\UVBuild\UserInterface.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST."
This mean that compiler is unable to find these sections.
The generated file cm0start.c doesn't contain any of these section and Keil suggest to include a startup.s files to avoid this error.
Someone convert a Creator project to uVision project ?
There is a startup.s files to include to avoid this error ?
There is a particular scatter file for linker to avoid this error ?
Let me know
Thanks
Show LessHello,
I am using PSOC 4 BLE (4.2).
I have been using the Fixed Stack bootloader project for quite some time now with our bootloadable application and everything has been working fine.
Recently, we added the feature of bonding to the bootloadable application and also added the saving of the bonding data to the flash using the cypress API CyBle_StoreBondingData.
We see that whenever the bonding data is stored using that API then if we perform a reset to the device, it loads and gets stuck within the function Bootloader_Start() and doesn't respond anymore.
If we erase that single line (CyBle_StoreBondingData) from the bootloadable application then everything works fine.
We tried using both CyBle_StoreBondingData(1u) and also CyBle_StoreBondingData(0u) and both provoke the same result.
What should we do? We still want to save the bonding data to the flash but if the bootloader gets stuck after reset, it is a huge problem.
What should we do?
Thanks,
David
CapSenseはスキャン完了ごとに、Interruptを発生させることが可能ですが、
このInterruptで、SleepModeからのwakeup可能でしょうか。
I 'm using Cypress CY8CKIT-042 and miniprog3 with your example SW "CapSense_CSD_P4_Proximity_Design01". The program works but I want to use the Bridge Control Panel for capsense tuning. I hooked up the miniprog 3 to the computer usb and it programs the chip.... I used the command they said to use in the bridge control panel but I don't get anything. I have used the bridge control panel with PSOC1 designs, so I am familiar with it. I don't know if I am using the correct Tx pin.
I;m sure this is easy but I am missing some information.
Thanks
Show LessSomething I found useful and i would like to share with the community.
The cover glass is one of the most important components of a touch sensor.
Cover glass selection is all about the trade-off between the sensitivity of the touch sensor and its mechanical and/or optical properties. There are many ways down the road to improve the touch sensor’s sensitivity (e.g. different electrode patterns or different stack-up materials). However, the sensor’s structural integrity is (literally) make or break when it comes to this selection.
This article discusses the main considerations of a touch sensor designer when choosing the sensor’s cover glass. First, we focus on common mechanical and optical design problems. Then we go into some more specific problems, in more intricate touch sensor designs.
Cover glasses’ mechanical properties:
1. Thickness
A thicker cover glass results in a sturdier touch sensor. Thicker cover glasses are usually preferred for applications in harsh (e.g. industrial) environments. In devices like smartphones and smartwatches the designs need to be as thin as possible. So designers focus on trimming thickness, and the cover glass is no exception. A general rule of thumb to keep in mind is that the thinner the cover glass, the less it affects the performance of the touch sensor.
2. Weight
The material of the cover glass and its thickness affect the sensor’s weight. Again, smartphones and smartwatches are expected by the consumers to be lightweight so designers resort to lightweight materials. In touch sensors that are mounted on other devices (e.g. on white goods) weight is not a driving force on design choices. In these cases, designers go for the most cost-effective material and thickness solution.
3. Scratch resistance:
The need to mitigate the scratches is crucial in most of the industries. A cover glass that easily scratches can compromise both the functionality of the sensor and its cosmetic appearance. So, in smartphones and smartwatches, scratch resistance is a design priority. Customers simply expect their device to be able to withstand a moderate amount of scratches.
In harsh and industrial environments, the touch sensor is almost expected to be subject to scratches. The designer has to take this into account and select a cover glass durable enough to withstand them.
Finally, in healthcare, touch sensor should remain as smooth as possible so that it can be easily sterilized. Having scratches on their surface means a rougher surface that is harder to clean.
4. Drop resistance
Similar to scratch resistance, a basic level of drop resistance is something that customers expect from their products. In fact, drop resistance is so important that the latest version of Corning Gorilla glass is designed to withstand 15 drops from 1m without shattering. Again, smartphones and industrial devices are more likely to need such protections, while mounted devices are not likely to need it.
These are, in a nutshell, the mechanical properties a touch sensor designer should account for before making a cover glass design choice. Next up, we’re going to examine the most important optical features to consider.
Taking into account the mechanical properties of the cover glass when designing your touch device can minimize the instances where this happens.
Cover glasses' optical properties:
5. Transmittance
The general consensus regarding touch sensor designs that are on top of screens is that the whole sensor should have a transparency of more than 90%. As far as the cover glass is considered, the transparency lost on it is negligible. Most of the light is blocked by the electrodes. The material electrodes are made of, be it ITO or one of its alternatives, is not perfectly transparent. However, this doesn’t mean there aren’t other optical performance parameters to be considered.
6. Anti-glare
Anti-glare is the ability of a glass to diffuse the mirror-like reflections off its surface, enabling the viewer to better see what’s behind the glass. So, anti-glare is used to increase the visibility of what’s behind the touch sensor. If there isn’t a screen behind the cover glass sensor, this property can be omitted. However, if there is one and the device is going to be used outdoors (e.g. in a POS device) then having such a property can vastly improve the usability of the device.
7. Anti-haze
Again, in any device that features a screen behind the touch sensor, anti-haze coating is a must. Hazy or cloudy glass can reduce the clarity of what’s shown on the screen. This reduces the usability and its cosmetic appearance of the product.
Cover glasses’ geometrical properties:
8. Finger’s angle and distance relative to the electrodes
Designing a touch sensor that features a curved cover glass instead of a flat one can create problems on its own. Consider a flat sensor with a slightly bent cover glass, or a cover glass with curved edges. The glass will have a different effect on the performance of the design. This happens because the distance between the finger of the user and the electrodes will differ in the non flat areas. The difference will alter the coupling between the two and affect the sensor’s design.
But the problem magnifies if the cover glass forms a bigger curve angle. In this case, it is not only the distance between the finger and the electrodes, but also the orientation of the finger when it’s near the sensor that changes. Since the curve is bigger, the tip of the finger will probably have a different orientation that it does on the flat areas. This will introduce a different geometry to the sensor and again, alter the coupling between the two.
We also have to mention the case in which a stylus will be used to operate the touch sensor.
A stylus has a significantly smaller area than the fingers. So the general train of thought here is that in order to operate a sensor via a passive stylus you’ll need a more sensitive sensor than one you’d operate with a finger. In terms of cover glass selection, if you know that a stylus will be used, you might want to opt for a thinner cover glass or one with a higher relative permittivity.
9. Signal-to-Noise Ratio
Signal-to-noise ratio, or SNR, is a constant headache for touch sensor designers. Thankfully, proper cover glass selection can you help increase the SNR. Without going into too much detail, keep in mind that thicker cover glasses result in a worse SNR.Thinner cover glasses or ones made of a material with a higher permittivity lead to a better SNR.
If you want to learn how to achieve the best properties for your touch sensor you can read more here