I think PSoC programmer can also read back code from a PSoC. So if you have a working KitProg, you could try this.
But having it appear as two devices is maybe even OK. Kitprog now supports switching between mass storage programming and normal mode - see http://www.cypress.com/blog/psoc-creator-news-and-information/kitprog-usb-mass-storage-programmer-now-available ) - maybe its just in the wrong mode?
I'm not sure if there are multiple version of theKitProg hardware out there - did you try the firmware from the -059 product page (http://www.cypress.com/documentation/development-kitsboards/cy8ckit-059-psoc-5lp-prototyping-kit-onboard-programmer-and )?
Well that is exactly what was 'wrong' with it... it was, in fact, in this new mass storage programming mode. I wasn't even aware that this new option existed. How it got in that mode is a mystery but, apparently at some point, I must have held the reset switch down on the target a few seconds too long with the KitProg still attached and accidently put it in that new mode. Pretty easy to do if you're not aware of the results.
You know, it seems to me that PSoC Programmer really should tell you in the Action/Results areas or on the status bar at the bottom of the window that the KitProg is in the mass storage programming mode because, as you can see, if a person is not aware of that new option, this is what happens. Things may 'look' broken when they really aren't. Do you have any pull with the devs to ask them to put some sort of notification in Creator and Programmer to alert a user to the fact that it's just in the 'wrong' mode instead of just not showing up at all?
Thank you for your accurate assessment and quick reply!
Glad you got it working. Sometimes it pays off to read all the Cypress blog posts :(
You could create a support case ('MyCases' in the top right menu) to notify Cypress of this problem.
Thanks everyone I just had this problem with the CY8KIT-059, I would add that it appears that the green status led breaths when in the mass storage mode and is constantly on when in the normal program mode.
Well I found the solution to my problem over here. Didn't know that mode existed. Now I can go back to debugging.