PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
Hi,
When using CSX, the Cint caps have their return path to analog ground (VSSA). If I am using CSX and CSD widgets simultaneously, can I join the return paths for Cmod and Cints like this :
And a single trace connects this nod to analog ground (VSSA)
OR
is it better to split signals and have a trace to VSSA for Cmod separate from a second trace to VSSA for Cints:
Thank you!
Show Less
Hi,
in the PSoC 4100S Data sheet, we can see from the pin list that VSSD is connected to ''DN'' for 40-pin QFN chips https://www.cypress.com/file/230626/download.
I cannot find any reference to DN regarding to TQFP packages, in the document or anywhere else. Does it refer to the thermal pad? There is no DN pin in the document for 32-pin QFN chips though, so I find this confusing.
Thanks!
Show LessHello,
Does the EZ-serial firmware support bluetooth 4.2 data packet length extension ? if yes, how to take advantage of it ?
I am trying to maximize throughput, but I cannot get more than 16kB/s in cyspp unacknowledged data mode, and 1.3kB/s in cyspp acknowledged data mode. RX flow does not change these numbers.
I tried L2CAP too, but I can't get more than 13kB/s. In this case I get EZS_ERR_CORE_OPERATION_NOT_PERMITTED quite often when sending ezs_cmd_l2cap_send_data. each packet is 200 bytes:
- 8kB/s if wait 8ms or less between send_data (success ratio 33%)
- 11kB/s if I wait 14 ms between send_data (success ratio 50%)
- 13kB/s if I wait 15 ms between send_data (success ratio 100%)
It seems the errors are the main limiting factor. How can I reduce them without adding some delay ?
All these cases are using uart with flow control at 921600 bit/s, and transfer from peripheral to central.
Thanks
Show LessHello,
There is a data rate range recommended by the I2C master,
Can the I2C master select a data rate in the range of 0-100 kbps when the I2C slave setting is in Standard-mode and 0-400 kbps when it is in Fast-mode?
Best regards,
Yocchi
Show LessHi,
In a PsoC4 project attached below we demonstrate a PWM compare register write bug.
It appears like if reg is written by the CPU at the same time as TC occurs pwm output is forced high for the entire period, and within the next cycle the latest compare value is in effect.
We have tried combinations with RegSwap, which also appears buggy, at certain occasions it swapped immediately.
Looking forward to hearing you and your explanation and best work-around.
Kind regards,
Uros
Hi Sirs,
Customer use CY8CKIT147 the I2C Master to test Capsesnse(CapsenseMTKTool) ,But the driver can't support WIN7 ,Is there a driver that him to support WIN7?
Thanks,
LIN
Show Less
I've been working on this for a week, learned some, so let me restate my case. I'm using brand new, US big-name distributor, sealed CYBLE-012011-00 modules on two different perfboarded prototypes of different layouts.
I can program them with the downloaded hex file of EZ-Serial and they behave properly, visible under any OS, pair instantly. I have tried three different examples (only modified for switch/LED pin assignments) BLE_HID_Keyboard, BLE_HID_Mouse, BLE_Heart_Monitor. All of them program and verify correctly. All of them only pair with difficulty (hitting pair 50 times). All of the HID examples are not even visible under Windows. On the occasions that I have got the Keyboard to pair with Android it has worked functionally correct, but balky, with latency problems and the connection dropping. The power is good (batteries, different power supplies) and the layout keeps out of the antenna area. The distance is two feet.
What is going on? Could somebody post a hex file (with BLE) for the CYBLE-012011-00 so I can have a reality check? I'm running on the 3.66 BLE version, although I have tried 3.50 also. When I have added user parts to the code those parts have operated correctly within the constraints of the BLE part flakey.
Show LessDear Group Members,
I am using CY8C4014SXI-421 in Touch Applications. Due to some reasons VCCD & VSS Pins are getting shorted. What could be the problem. I have interfaced Optocoupler with Port Pin and I am controlling 24V Relay with the optocoupler. In the end I am controlling AC BULB AND AC FAN via Relay. So what is the reason of VCCD Pin and VSS Pin shorting.
Show LessHi, I would appreciate some clarification about using BLE Random Static Address as the BD_ADDR.
I understand that the 2 most significant bits of the 48 bit MAC address must be set to 1 (as described in [1] and [2]) to identify the address as a Random Static Address.
Having read around various posts and found the bit in the Bluetooth spec (described in Volume 6 Part B of the Bluetooth 4.0 specification (Section 1.3)), I am still confused as different sources seem to flip the order of bits as to which is LSB and MSB bits so I can't figure out what is correct for a MAC address as normally viewed.
So, for a given MAC address as reported by CySmart as Ax-xx-xx-xx-xx-xB (and most other tools), would byte A need to be 11xxxxxx or would byte B need to be xxxxxx11 or something else?
Also, are these 2 bits different to the U/L and I/G bit of the standard EUI-48 (MAC-48) address described on the wikipedia MAC address page here [3].
I appreciate this is probably a real noob question but I can't find anything anywhere that actually gives examples that are clear (for me at least) on this.
Any clarifications much appreciated.
thanks, Colin
MCU: PSoC4 - CYBLE-014008-00
[1]: https://www.novelbits.io/bluetooth-address-privacy-ble/
[2]: https://community.cypress.com/t5/Resource-Library/BD-ADDR-how-do-you-get-one/ta-p/246800
[3]: https://en.wikipedia.org/wiki/MAC_address
Hi ~ all,
I use Cap sense sample code but there are 2 error messages in the following description.
Could anyone know what happened ?!
main.c:121:55: error: 'CapSense_BUTTON0_WDGT_ID' undeclared (first use in this function)
CapSense_BUTTON0_WDGT_ID,
^
main.c:121:55: note: each undeclared identifier is reported only once for each function it appears in
main.c:122:55: error: 'CapSense_BUTTON0_SNS0_ID' undeclared (first use in this function)
CapSense_BUTTON0_SNS0_ID
^
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
Thank you so much.
Show Less