PSoC™ 4 Forum Discussions
If anyone can give me some help,thanks!
Hello -- are there example implementations of Cypress DFU/OTA within the context of Android or iOS?
Looking for something like this, ideally: GitHub - NordicSemiconductor/IOS-Pods-DFU-Library: OTA DFU Library for Mac and iOS, compatible with nRF5x SoCs
Thank you in advance!
--Bill
Show LessIs there any firmware update for CY8CKIT-042-BLE to support BLE Mesh as per SIG BLE Mesh specification v1.0?
Mesh Networking Specifications | Bluetooth Technology Website
Show LessHello,
I use a PRoC in a project where it communicate with an uart to an other device (the main device).
The user use his phone to send commands and or parameters to the main device, and the phone app should be able to tell him that the orders have been correctly received by the main device.
So after a command, the PRoC receive the data, send it throught UART, the device make some action according to the received command and send an UART frame to confirm that it have take the command into account.
Where it's not clear it's how i should create characteristics.
Does i have to create many characterisitics for each parameters, or few big ones :
1)
Few larges characteristics, with a 20 bytes arrays, and each one contains many parameters (like 5-6 parameters)
The problem with that solution is, that if the user change one parameters on the phone the app phone have to read the entire caracteristics and then change only one parameter with a mask.
2) one parameter per characteritic, its very structured, but the problem is that we have a lots of parameters to read and lots information to read from the main device (like date of first entry into service, software version etc, lots of large 32 or 64 bits long parameters). So with that solution, i need like at least 30 differents characteristics.
Other question, about the verification ( be sure that the data have been received by the main device).
Does i have to use :
1)
one characteritics write and read per parameters ( or set of parameters) : the phone app send data to the caracteristic in the BLE device, but the handle is updated only when and if the confirmation is returned from the main device by an uart frame.
2) 2 characterisitics, one for the phone app to write the data and the other one to read the data (this second one is only writed by the main device with uart frame). The uart app suscribe from notification on the read characteritics
3) Just write the data in characteritics and assume that the data have been correctly delivered to the main device
What approches are best suited for our application ?
Thanks for you help.
Show LessHi guys,
I am wanting to be able to program the CYBLE-022001-00 chip. Having to solder (by hand) and desolder (by heat gun) to these teensy tiny pin pads is a pain.
Do you make some kind of socket that would fit this chip? The .762 mm or .030" pin pitch does not seem to be standard in any way.
Or do you have any other idea of how one might do this more sensibly? There must be a whole lot better way!
Show LessHello !
Firstable please don't blame me for my english level ^^"
Could someone help me with my code ? I'm trying to create a 3x3 tactile matrix keyboard with PSoC Creator 4.
I'm working with a CY8CKIT-059 (PSoC 5LP) and using the CapSense unit of the MCU.
I've found out a post on this forum with alike problematic. There was a code example in the answers below to use CapSense unit
with a 3x3 tactile matrix. Here is the link of the topic I'm speaking about.
Re: Matrix Button on CY8CKIT-059 (PSoC 5LP)
I've decided to use this code example to create my project. From this code, I wrote something that is right according to PSoC Creator
but it doesn't work with my matrix button component (an electrical card with tin matrix button link to a ground-plan made with Protheus).
More precisely, I think I can't get the X/Y key's coordinates back. Actually, I want that a LED blink when you put the finger on one of the 9 keys.
But it doesn't blink at all ^^". I know the matrix component and the MCU successfully communicate, and the code is running well.
I think that maybe i don't use really well the functions in this code and hope someone can help me.
I include my project with my code below. Thanks a lot for your help and have a nice day !
Show LessI had written this post on my other recent thread, but since it really is a different question, it will probably be much better and more organized to start a new thread on it.
I bought the CYBLE-022001-PROG EZ-BLE™ Module Programming Kit. Programming chips using that socket, the BLE Pioneer kit, and PSoC Programmer seems to work. However, I cannot figure out how to change the UUID or send other commands to the chip.
When I first clamp down on the chip in the socket, Tera Term shows this message:
@E,003B,BOOT,E=0101011A,S=03030035,P=0103,H=03,C=01,A=00A0504D7B26
@E,000E,ASC,S=01,R=03
Then, attempting to enter in any commands result in the doubling of characters. For example, entering UUID results in UUUUIIDD being displayed in the terminal, and upon sending the command the display of this message:
@E,000B,ERR,E=0203
Any ideas?
Show Lessdear all,
i am using CY8C4245AXI-483 in my product. up to date i had used thousand of chips.
i am using miniprog3 and my standard product pcb.
i was using creator 3.1 and now 4.1
i have recently purchased 320 chips and for that i am facing following problems.
i am always using miniprog as 5v, reset cycle, 1.6 MHz.(as my default)
pin no 13 and 14 gets connected to miniprog via 330E resistances.
chip detection by miniprog display for 2 to 3 sec. and get disappears. after removing and again connecting miniprog chip does not get detected
nothing is going hot, failure of usb supply etc
so i checked VCCD voltage it comes to near 200mV from 1.7V. (VCCD is bypassed with 1uF)
XRES remains to zero.
please help.
.
Show LessDoes the 4200-L support an external crystal? I need a low power, small package solution that has better main oscillator accuracy of +/- 2% and do not want to have to calibrate every device to get the internal oscillator option more accurate.
Thanks
Show Less