PSoC™ 4 Forum Discussions

I need an example of CYBLE connect to a bluetooth keyboard hid (or mouse) and acquire push button.

Are there an example?

I need a missing pulse detector on a PSOC 4. My Signal is 500ms low and 500ms high. If the Signal is low or high for more than 500ms, the output goes to low.

Is this possible (only with digital blocks / no software) ?

Thanks Andreas.

Helle,

I am Using PSoC 4 CY8CKIT-049  Prototyping Kit.

Does any one can help me out to implement RS485 on PSCO4.

Thank you.

I cannot place breakpoints in modules other than main.c.  This appears to be a known probelm...

Any fix coming Cypress????

In the meantime I have been unable to migrate back to 4.0 successfully.  I want to keep the cysch and cydwr configurations/files.

Is there a know good way to migrate back?

Rich

Is there an application note for TQFP device soldering?

For example Cypress has lots of helpful information about QFN packages like AN72845 "Design Guidelines For Cypress Quad Flat No-Lead (QFN) Packaged Devices". They also have lots of information about BGA packages.

No information for TQFP. I recently purchased a few 64-pin 4100M, 4200M MCUs and would like to create some models in Eagle CAD.

As far as I know there is AVRCP in Classic Bluetooth and the sound volume of smart phone can be controlled through it.

However there isn't AVRCP in BLE.

Is there any way to realize the volume control through BLE? fyr I'm using CYBLE-014008-00 module.

Thank you for your advice in advance.

I have a need to modify contents of the hex file for a psoc4 device. It is no problem to read the data and modify it. The data is put back into hex format correctly. (This was verified by just unpacking and repacking the file with no changes, then doing a file bit compare). This works down to the metadata line at 9050.  This changes when the file data changes. The only description of this that I have found is in "PSoC 3 Device Programming Specifications, Document # 001-62391 Rev. *L " where it says "Internal Use: The 4-byte data is used internally by the PSoC Programmer software. It is not related to actual device programming and need not be used by programmers of third-party vendors.". 

For the psoc4, this part seems to be 14 bytes and the psoc programmer certainly does care what it is. Any hex file changes change the metadata and the psoc programmer gives an "unknown record type error".  Changing one bit in the file changes the line checksum and the 16 bit checksum and I have taken those into account properly. The one bit change in the source code changes the  metadata value by 1 in the last digit as well as the line checksum so at least part of it is a checksum of sorts

Is there a detailed description of the contents of the metadata available?

I can not seem to get Creator to program a CY8C4247AZI using a MINIPROG3.  I am using the ISSP 5 pin connection on the MINIPROG.  What aim i doing wrong ... do i need to use a different setup to code this part?  I would sure appreciate some help in getting my CPU programmed in circuit.

PSOC4 S series and PSOC6 have CapSense module, which has both CSD and CSX.

I am interested in the CSX now, I want to make it woks with CSD together.

I read the document of PSOC4 S and PSOC6 (#002-10129 and #002-18176). From the description of CSX, I have the following understanding:

(On the figure 32-11 in the page 404 of the DOC #002-18176, )

1. One cross point (TX/RX) need support from both pins of Cmod-GPIO and Csh_tank-GPIO, the working way is very closed to CSD mode. Of course Cmod-GPIO and Csh_tank-GPIO could be re-used for different point;

2. Meanwhile, the Mutual CAP sensor scan needs support from IDAC-A (LEG1) and IDAC-A (LEG2);

The following will be my question about it

If my mutual CAP sensor panel is N*M (like N of TX, M of RX), based on the above method, the whole mutual cap sensor panel scanning need to be repeated for N*M times. is it true?

Thanks,

Qiuliang