The I2C connections on the Kitprog2 don't come to the 5 pin breakaway connect. That has the SWD signals, XRES, VDD and GND. You need to connect I2C SDA and SCL to J8_05 and J8_04 on the Kitprog2 board, if you got it from the -043 kit. The signals need to go to P12-1 and P12-0 on the P5 on the KitProg2. They should be labeled on the silkscreen on the bottom side of the board.
About the KitProg2 I2C connection, agree with Mike.
Don't have to has a host mcu to configure MBR3. Using Ez-Click, MBR3 can be tuned well.
Of course, considering that the long term plan for this chip is to operate as a touch screen and connect to an MCU, there is a flexible way to 'control' the chip by a 3rd party MCU. You may have known the reference code of PSoC4 host. Install MBR3 Evaluation Kit files, you will find the host example code in its installing folder(such as: C:\Program Files (x86)\Cypress\CY3280-MBR3 EVK\1.0\Firmware).
It should be not very hard to migrate the code onto a 3rd party MCU. Configuring/Upgrading MBR3 is always through controlling its fixed I2C register map. FYI.
Thank you for the responses. I have indeed been attempting to connect through the P12-1 and P12-0 on J5. When I open PSoC Programmer, I get the following screen:
As you can see, under protocol, I2C is greyed out and cannot be selected. Could this have anything to do with why I am unable to detect the chip? Here is also a picture of my setup if it helps. I know it is difficult to see, but I am quite sure I have it connected properly.
You should be able to choose the programming connection type without even plugging in your board-to-program. Try unplugging it, and see if you can configure it to I2C then?
You shouldn't be using the Programmer. You are not reprogramming the MBR, you are just updating configuration registers in the part over I2C. You should see if you can connect with the Bridge Control panel. If you connected correctly, with power, gnd and SDA and SCL, You should be able to connect to the KitProg and List to see the device address.