PSoC™ 4 Forum Discussions
Hello
I had used CY8C4014LQI-422.
When I Started using PSoC4000 series
there was only CSD solution.
now a day there is CapSense[v7.0] and CapSense CSD[v2.60].
What is different between them.
and which one is better performance?
Regards,
Sunghun noh
Show LessThe first CC interrupt either lags or happens before time. I always get a value PWM_ReadCounter of below 50. (as described in the picture below)
The issue is only happening on the first activation of PWM and PWM_Isr, following boot.
Next activations looks to work fine.
Code:
StartEx(isr_name) on startup.
Then I activate PWM, WriteCounter(1), PWM_ISr
Show Less
Hello
I will use IAR Workbench as my IDE and compiler.
Chip is CY8C4147AZI-S455.
I have TTBridge(CY3295) and miniprog3.
but there is no selective option for cypress tool.
can I use this cypress tool for debugger?
If it is possible, How can I set my environment?
Regards,
Sunghun noh
Show Lessmy ble device as central and peripheral mode.
1)how my BLE device switch from central to peripheral mode.
and when switch perticular random no.is match to mobile .then ble device is switch
regards,
atul gaikwad
Show LessHi all,
I tried out the EEPROM emulation example on PSOC4 with Creator 4.3.
Everything works fine and the counter is being updated and printed to serial line whenever I press the reset button on the pioneer board.
But when I program the board again, the content in the EEPROM section is reset/lost. I guess it is overwritten, because the emulation is located in flash and "program" might erasing the whole memory first.
How can I overcome this?
What I want to have is:
use EEPROM emulation, store some values, then continue developing my application, progam and debug it and keep the content.
Can I configure the "program" action to keep the EEPROM location in flash untouched?
Best wishes,
Stefan
Show LessHi all,
We want to use the pairing and whitelist features of the BLE module integrated in our product (CYBLE-212019-00 / CYBLE-212020-01). The BLE module is controlled via UART using the EZ-Serial API. The main problem is, when a smartphone is paired with the BLE module (the BLE module acts as peripheral / GATT server), if the whitelist is enabled it is not possible to reconnect the smartphone although bond and whitelist entries exist for the paired device. We followed the recommendations and parameter setting given in the “EZ-Serial BLE Firmware Platform User Guide” (No. 002-11259 Rev. *E), but we might have miss something.
It is possible to reproduce the problem using the BLE Pioneer kit and text commands (configuration details are given below). Note that our product uses the binary protocol and the result is the same.
Here are the instructions to reproduce the problem:
1) Factory reset of the BLE module (bond list has been cleared before)
→ /RFAC
@R,000B,/RFAC,0000
@E,0005,RFAC
@E,003B,BOOT,E=0101011A,S=03030035,P=0103,H=05,C=05,A=00A0504219E3
@E,000E,ASC,S=01,R=03 ← Advertisement is started automatically without whitelist
2) Connection of the smartphone
@E,0035,C,C=04,A=5E972F97FD49,T=01,I=0024,L=0000,O=01F4,B=00
@E,001D,CU,C=04,I=0000,L=0000,O=0000
@E,001D,CU,C=04,I=0000,L=0000,O=0000
@E,001A,W,C=04,H=000B,T=00,D=0200
4) Send pairing request with bond (Re-initialized by the smartphone)
→ /P,M=11,B=01,K=10,P=00
@R,0008,/P,0000
@E,001B,P,C=04,M=12,B=01,K=10,P=00 ← The smartphone send a pairing request, automatically accepted by the BLE module
@E,001D,CU,C=04,I=0000,L=0000,O=0000
@E,000E,ENC,C=04,S=01
@E,001B,B,B=04,A=5E972F97FD49,T=01 ← A bond entry is created
@E,000F,PR,C=04,R=0000 ← Pairing successful
@E,001D,CU,C=04,I=0000,L=0000,O=0000
5) Disconnection and reboot of the BLE module and smartphone Bluetooth
→ /DIS
@R,000A,/DIS,0000
@E,0010,DIS,C=04,R=0916
@E,000E,ASC,S=01,R=03
→ /RBT
@R,000A,/RBT,0000
@E,003B,BOOT,E=0101011A,S=03030035,P=0103,H=05,C=04,A=00A0504219E3
@E,000E,ASC,S=01,R=03
6) Activation of the whitelist for connection (tested with whitelist for connection only and whitelist for both advertisement and connection)
→ /AX ← Stop advertisement
@R,0009,/AX,0000
@E,000E,ASC,S=00,R=00
→ SAP,M=02,T=00,I=0030,C=07,L=02,O=0000,F=00 ← Set whitelist
@R,0009,SAP,0000
→ /A ← Start advertisement (also tested with all parameters)
@R,0008,/A,0000
@E,000E,ASC,S=01,R=00
7) Attempts to connect the paired smartphone
Advertisements are received on the smartphone, but when trying to connect, nothing happen!
In the CySmart log file no error. In nRF Connect log file a standard “Error 133 (0x85): GATT ERROR” is listed to inform that the connection failed.
Note: The connection may work if the Bluetooth on the smartphone is not reset. But as soon as the smartphone is restarted or Bluetooth on the smartphone is restarted, the connection is not possible.
😎 Additional verifications
→ GAP
@R,0030,GAP,0000,M=02,T=00,I=0030,C=07,L=02,O=0000,F=00 ← Advertisement parameters and whitelist are OK
→ /QB
@R,000E,/QB,0000,C=01
@E,001B,B,B=04,A=5E972F97FD49,T=01 ← A bond entry exists for the paired smartphone
→ /QWL
@R,000F,/QWL,0000,C=01
@E,0017,WL,A=5E972F97FD49,T=01 ← A whitelist entry exists for the paired smartphone
Configuration details:
* BLE Pioneer Kit (CY8CKIT-042-BLE) + BLE module CYBLE-212019-EVAL
* EZ-Serial version: 1.1.1 downloaded on 06.01.2020 (same version on our product)
* Tested smartphones:
- Samsung Galaxy A70, Android 9
- Sony Xperia XA, Android 7
- iPhone SE, iOS 13.3
* Software used on smartphone for connection and pairing: CySmart, nRF Connect
Other issues:
We also identified other issues related to pairing.
1) Bonds not cleared after factory reset
When the factory reset command is sent we expect that the bonds and white list are cleared. However, the lists persist.
→ /QB ← Query bonds
@R,000E,/QB,0000,C=01
@E,001B,B,B=04,A=79538A59996E,T=01 ← One bond entry
→ /RFAC ← Factory reset
@R,000B,/RFAC,0000
@E,0005,RFAC
@E,003B,BOOT,E=0101011A,S=03030035,P=0103,H=05,C=05,A=00A0504219E3
@E,000E,ASC,S=01,R=03
→ /QB ← Query bond
@R,000E,/QB,0000,C=01
@E,001B,B,B=04,A=79538A59996E,T=01 ← Still one bond entry
2) Delete bond command sometimes doesn’t work
The command for deleting bond entry sometimes fails although advertisement is stopped.
→ /AX ← Stop advertisement
@R,0009,/AX,0000
@E,000E,ASC,S=00,R=00
→ /QB ← Query bonds
@R,000E,/QB,0000,C=01
@E,001B,B,B=04,A=5DBAF31F5E73,T=01
→ /BD,A=5DBAF31F5E73,T=01 ← Delete the single bond entry
@R,000E,/BD,0108,C=01 ← Response indicate one remaining bond, Code 0108 “Operation not permitted”
→ /QB ← Query bonds
@R,000E,/QB,0000,C=01
@E,001B,B,B=04,A=5DBAF31F5E73,T=01 ← No bond deleted
3) Error on pairing response command “smp_send_pairreq_response (/PR, ID=7/5)” when rejected
When the auto-pairing response is disabled, the "smp_send_pairreq_response (/PR, ID=7/5)" command must be sent to accept or reject pairing. Accepting pairing using this command is no problem, but rejecting the pairing result in the error code 0x0104 "Unsupported feature". Using the C-API, the response of the pairing response is ignored by the parser.
→ /AX ← Stop advertisement
@R,0009,/AX,0000
@E,000E,ASC,S=00,R=00
→ SSBP,M=11,B=1,K=10,P=00,I=3,F=00 ← Disable auto-accept pairing request
@R,000A,SSBP,0000
→ /A ← Start advertisement
@R,0008,/A,0000
@E,000E,ASC,S=01,R=00
@E,0035,C,C=04,A=5CBDC8BB696D,T=01,I=0024,L=0000,O=01F4,B=00
@E,001D,CU,C=04,I=0000,L=0000,O=0000
@E,001D,CU,C=04,I=0000,L=0000,O=0000
→ /P,M=11,B=01,K=10,P=00 ← Send pairing request
@R,0008,/P,0000
@E,001B,P,C=04,M=12,B=01,K=10,P=00
@E,001D,CU,C=04,I=0000,L=0000,O=0000
→ /PR,C=00,R=0001 ← Send pairing response to reject pairing
@R,0009,/PR,0104 ← Command response with code 0104 “Unsupported feature”
@E,0010,DIS,C=04,R=0913
@E,000E,ASC,S=01,R=03
4) After more than 4 pairing, bond and whitelist entries are managed automatically, but it is undocumented
The documentation supposes that bonds may need to be removed when more than 4 devices are paired. See documentation, page 149, Section 7.2.7.3.
5) Small typo in documentation for “smp_bond_entry”
In “EZ-Serial BLE Firmware Platform User Guide” (No. 002-11259 Rev. *E), page 202, the binary header for the command “smp_bond_entry” mentions a length of 7, but the length is 8.
Thanks for your support,
David
Show LessNew to PSOC so maybe I'm missing something, but I seem to keep finding inconsistencies between the website and reference docs.
My starting requirements were pretty simple: 2 UART ports, 1 SPI, CapSense. Based on SCB documentation it seemed like that would mean 3 SCB blocks minimum.
Based on the "Getting started with PSoC 4" doc (https://www.cypress.com/file/46106/download), it seems like I should be able to use any PSoC 4 family for CapSense, but am limited to 4100S, 4100S+, 4100PS, 4200L, or 4500 for the SCBs. I bought the CY8CKIT-043 to test some things and immediately hit one contradiction, the datasheet and webpage for the chip on the devboard contradict the getting started doc on the number of SCBs. I figured this was a one-off but while looking for a cheaper and smaller chip for my purposes I kept running into things like this.
The final example that has really put me off is in regards to the CY8C4125AZI-M443 chip. I had to find it in the PSOC Creator device selector because the Cypress web-based parametric search doesn't seem to include CapSense (another thing I felt like I must be missing but just couldn't find) and DigiKey has some incorrect info. This chip is part of the PSoC 4100M series, which according to the getting started doc doesn't even exist. Now looking at the number of SCBs, Creator says it has 3, the webpage (https://www.cypress.com/part/cy8c4125azi-m443 ) says it has 4, the datasheet (https://www.cypress.com/file/139961/download ) says 4, and of course the getting started doc doesn't say anything. I created a project with this chip and in reality it seems to only have 2, as it refuses to build with 2 UARTs and an SPI (or 3 SPI that I did as a test, attached).
I really hope someone can make sense of this and explain how it's all consistent and what I'm missing. I would love to use Cypress chips, they seem to have some great features with the SCB and programmable analog stuff, but I just can't if I can't trust the documentation to be consistent, much less correct.
Show LessI am using CYBLE-012011-00 in my bluetooth keypad.When i am trying to use battery supply(CR2032 coin cell battery,micro lithium cell,3V) for this keypad,the supply voltage drop from 3V to 1.8V. If I disconnect the keypad it again shows 3V. Which battery supply is best suitable for bluetooth keypad application using CYBLE-012011-00 part???
Show LessDear Community and Support Team,
due a lack of S432 devices in market for our recent production we decided to go with the S422 also in a second lot.
My question is, if its possible to maybe go with same firmware somehow to ease production process and maintenance.
I worst case we would have to go with a second FW build into production.
Any ideas, suggestions or helpful comments?
Thanks, best,
FPic
Show Less