cy8ckit-042 connection to Bridge Control Panel SW using miniprog3 .

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
DoLo_351801
Level 3
Level 3
10 replies posted 10 questions asked 10 sign-ins

I 'm using Cypress CY8CKIT-042 and miniprog3 with your example SW "CapSense_CSD_P4_Proximity_Design01". The program works but I want to use the Bridge Control Panel for capsense tuning. I hooked up the miniprog 3 to the computer usb and it programs the chip.... I used the command they said to use in the bridge control panel but I don't get anything. I have used the bridge control panel with PSOC1 designs, so I am familiar with it. I don't know if I am using the correct Tx pin.

I;m sure this is easy but I am missing some information.

Thanks

0 Likes
12 Replies
BrandonP_16
Employee
Employee
5 sign-ins First question asked 10 solutions authored

Hi,

I think you are missing the additional work for HW connection in CY8CKIT-042.

Please refer the kit guide, CY8CKIT-042 PSoC 4 Pioneer Kit Guide Section 3.3 USB-UART Bridge.

If it is not solved, please attach the Bridge Control Panel screenshot.

Thanks,

Brandon

0 Likes

Brandon

Thanks for helping.

the document does not tell which pin is tx and which is rx. "The UART lines

from PSoC 5LP are brought to the P12[6] (J8.9) and P12[7] (J8.10) pins of

header J8. "

From another document, I think the rx port of the psoc5 is P12[6]. I've

tried both.

The bridge control panel does recognize the miniprog3 when I plug it in,

but it does nothing when I send a command.

The Bridge control panel does not recognize the onboard psoc5 serial port.

So I don't think it matters which pins are assigned at this point.

on page 8 of the CapSense Proximity Design document it says "2. Route the

Tx pin of the device to any available Rx which can connect to the PC Com

port. CY3240 (refer AN2397) or KitProg in CY8CKIT-040 can be used for this

purpose. In CY8CKIT-040, Pin 3[0] (Tx line) is directly connected to RX

line (P12[6]) of PSoC 5LP bridge (Zero Ohm R57 in the board needs to be

populated). "

I am using the cy8ckit-042 not the 040 and i do not see a R57 that needs to

be populated.

Additionally, the psoc programmer does not recognize the onboard

programmer.

0 Likes

I think the issue is that the onboard communication device in the psoc5 is not conne3cting to my computer. It makes a sound like it is connected but it does not show up in the device manager or anywhere else.

0 Likes

Below figure shows the connection between the RX and TX lines of the PSoC 5LP and PSoC 4.

pastedImage_0.png

More about the USB-UART bridge, you can read the kit guide document.

http://www.cypress.com/file/416971/download

0 Likes

Thank-you for the help.

I have read the doc and configured my CY8Ckit-042 as they suggest. The

problem is that my computer does not see the device when I plug it into the

USB port.

I tried another kit, the CY8Ckit-044. When I plug it in the computer

recognizes it as KitProg(1.2.3.3). This does not happen when I use the

CY8Ckit-042.

What am I missing? is the kit broken? is there a missing 0 ohm resistor I

need to add? Is there a new driver? Maybe I need a new firmware for the 042

kit?

0 Likes
lock attach
Attachments are accessible only for community members.
LinglingG_46
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 10 questions asked

The tuner project don't work as the function of bridge control panel test project directly.

If you want to out put the capsense parameter, I can give you a test project.

Please change the select port as GPIO like the below figure.

pastedImage_0.png

Hope it can be helpful for you!

0 Likes
lock attach
Attachments are accessible only for community members.

I gave up on the cy8ckit-042. I think it's broken.

I'm using cy8ckit-049 42xx.

I still can't connect to the capsense tuner.

I have the i2c hooked up to the miniprog3. I think I did everything the

documentation said to do. It sees the mini prog but doesn't transfer any

data.

the program is working because I can see the bi-color LED changing based on

the proximity sensor.

0 Likes

I think I make a mistake in the previous response.

Because the tuner use i2C, you don't need to connect any other wire.

If you use the kit-042 I2C tuner, you need to configure the I2C at P3.0 and P3.1.

And configure the address 8 instead of 08.

You should Enable all the interrupts.

  CyGlobalIntEnable; /* Uncomment this line to enable global interrupts. */

#include <project.h>

int main()
{
    /* Place your initialization/startup code here (e.g. MyInst_Start()) */

    CyGlobalIntEnable; /* Uncomment this line to enable global interrupts. */
    CapSense_EnableWidget(CapSense_PROXIMITYSENSOR0__PROX);
    CapSense_TunerStart();

   
    for(;;)
    {
        /* Place your application code here. */
        CapSense_TunerComm();
    }
}

/* [] END OF FILE */

0 Likes

Hi,

For CY8CKIT-042, please check the J9 connector. J9 connector must have one jumper socket to connect 5V or 3.3V. If not, PSoC5 for Kitprog is not working. (Cannot detect in PSoC Programmer.)

k042-J9.png

For CY8CKIT-049, it also must have additional working for I2C connection. Please refer kit guide.

http://www.cypress.com/file/141306/download

pastedImage_2.png

J6_04 should connect J2_3.0 or J1_4.0 and J6_05 should connect J2_3.1 or J1_4.1. (Depends on your pin assignment on project file.)

Thanks,

Brandon

0 Likes
lock attach
Attachments are accessible only for community members.

J9 is and was connected on the 042 .

Using 049: I program using miniprog3 using p3.2 and p3.3 Vdd and Gnd.

Works fine.

I have a separate I2C port for communication with the tuner using the same

Vdd, Gnd and reset pins but using 4.0 and 4.1instead of p3.2 and p3.3.(

connected to ezi2c)

I have attached the workspace bundle.

it just doesn't send any data to the tuner.

I'm probably doing something wrong. I would appreciate it if someone would

take a quick look at it.

Thanks

Doug

0 Likes
lock attach
Attachments are accessible only for community members.

Hi Douglas,

Please take out "CapSense_TunerComm();" out side of CapSense busy check condition.

I tested the attached code and it works fine in my 049 kit, refer the attachment.

Thanks,

Brandon

0 Likes

Brandon

Thanks. I got it working thanks to your help

0 Likes