PSoC™ 4 Forum Discussions
Hi,
I am wondering if I can manually tune the CapSense in my custom board over the MiniProg3. Do I have to solder wires onto pins that can be used as I2C, or can the Debug lines be used? Please let me know if anyone has done this before. I am using the example program, and cannot figure out how to get the tuner connected to my board.
Thank you,
Tom
Show LessI used the BLE_HID_mouse example and adapted some lines to get the mousewheel data as 4th byte:
#define MOUSE_DATA_LEN (4u) //instead of 3
and added:
abMouseData[3u] = bScrollWheel_value; (I tested 120 or -120)
Also in the BLE component HID-profile I changed:
- "Human interface device"
- "Boot mouse input report: Boot mouse input report value" from 3 to 4 bytes to include the extra wheelvalue byte
- "Report In: Report value" also from 3 to 4 bytes to include the wheel byte
No errors, and I even see in cysmart on my PC that the 4th byte is being transmitted and it's received correctly.
But it doesn't seem to scroll, what am I doing wrong, maybe a Bug in version 3.1 SP3 or some characteristics needs to be reported?
Show LessHi,
I am not sure if this is the most appropriate forum but as my question is related to the PSOC 4200, I thought I would start here.
We have a product that uses the CY8C4245PVI-482.
We are about to contract out assembly of 1000 of our product
What I want to do is supply the contract company a pre-programmed controller. Each must have a serial number.
1) Is there a service that can perform production programming (or do you know if we can purchase from Cypress pre-programmed with our firmware)
2) Does the device have a unique serial number built-in we could use or would we need to have the firmware somehow serialized ? We do not care what the numbers are as long as we can derive unquiqe value between 1 and 65535.
In other products we use the Dallas serial number IC but we have no room or pins available on the board for this.
Show LessNot sure if this goes here or in the USB forum but since it's part of the PSoC 4xxx prototype boards I decided to post it in here:
Someone in a forum asked for a cheap and easy USB to I2C Dev Kit, so I suggested using the break off USB Serial part of the CY8CKIT-049.
As my example I used an RTC clock based on the PCF8563 chip from NXP
So first I open the Cypress USB-Serial Configuration Utility after plugin in the board to my PC USB port, and selected my USB-Serial (Single Channel) target and clicked on Connect:
I left the USB configuration alone, but you can change the VID/PID manufacturer and product strings etc, also left the IO levels to CMOS (you can select TTL) and clicked on the SCB tab:
Next I selected the mode to be I2C and clicked Configure
Note that you can set the notification LEDs to use GPIO pins to drive transmit and receive individual LEDs or a single one for both tx/rx
Selected 400KHz and set it to be in Master mode and ok.
Back to the previous screen click on program.
And it will come back with success (if everything is setup right).
I added two 2.2K Ohm pull-up resistors as required for 400Kbps
Altered the I2cmaster example that came with the USB-Serial Software Development Kit
http://www.cypress.com/?rID=83110
I'll include the code at the end of the post.
I did probe the SCL and SDA to make sure I was reading/writing the right data:
And it worked great:
So that little chip that we use for communicating with the boot loader has other uses, it can also do UART of course, and SPI.
Here is the code (Windoes based):
Hello,
I am working with psoc 4. I am Interfacing LCD with PSOC 4. I tried with the example project given in Creator. But I am getting error. I am attaching my workspace
anyone can tell me why I am getting error ?
Show LessHello,
I have a PSOC4 BLE acting as a GAP peripheral device. In my application, the peripheral device can initiate a disconnect from its peer as well as receive a disconnect from the peer device. I invoke the CyBle_GapDisconnect function to send the request. I receive a CYBLE_EVT_GAP_DEVICE_DISCONNECTED event after issuing the disconnect request or when the peer device sends a disconnect. According to the BLE component datasheet, a pointer to a uint8 disconnect reason code is returned with the event. I cannot find in the documentation or in the BLE component header files where this reason code is defined. I am overlooking something?
Thanks,
Jason
Show LessHello, I have a feeling, that I missed something, but anyway.
I have a cy8ckit -049-42xx Psoc 4 prototyping KIt. I installed PSoC creator 3.1 SP 2 and opened default example for devkit CY8CKIT-049-42xx - SCB_bootloader. I modified a little bit the default project (added one more LED to blink) compiled bootloadable application and wrote it to the PSoC. Everything is fine ther - both LEDs are blinking, but after I disconnected a board and connected it again, I see the default bootloader behaviour - only embedded blue LED is blinknig.
Am I missed something and forgot to protect the program from erase?
Or program was written to the RAM and because of this it is cleared after power off? Can bootloader write the program to flash? How?
Or my devkit is broken?
I have two boards. I re-writed the bootloader as it is written in '4 dollars programmer' articale. Same result. Where I can find the explanation?
Thanks.
Show LessHello,
My question will be:
Will Blue Tooth Link will be the correct solution for the following application?
Application:
One Common receiver in a room of approximate 30 x 30 Ft. size.
There will be approximate 60 Nos. Transmitter in the room.
Each transmitter will have 4 buttons on them without any other external peripherals / LEDs etc.
When any one of the 4 button is pressed, it should transmit the button number along with unique transmitter id to the common receiver, which receives the code and stores the button choice information for that transmitter.
Possibility of simultaneous transmission by any of (or all of) 60 users should be taken care of.
How to achieve robustness of detection of button choice among multiple transmitter to a common receiver.
Additional wish list / specs.:
Low power - long lasting battery life for each transmitter (CR2032 coin cell battery operation)
Capsense button detection (saves on mechanical button costs)
Common receiver connects to a PC on USB link - as a CDC serial device, for data transfer.
Lowest cost for each transmitting device.
Like to have ideas, suggestions towards implementing above application, suitability of BLE technology for the same. Failing which what kind of RF link solution may be used in the application. (IR optical link is not a preferred solution)
Regards,
Vinay
Show LessHi
I am trying to get this code to work.
It compiles and loads correctly.
I connect with phone and it disconnects like it's suppose to
But when the button is pressed it says something like
Monday 00:00:00 00:00:47
It still counts up but does not work correctly
Hope its an easy fix
Show Less