Welcome in the forum, Mark.
The output goes to an emulated com-port on your PC. Use a terminal program as PuTTY to display the data. There is some explanation to find in the Kitprog guide under "USB UART bridge"
That's it! Thanks for the quick reply. I don't see it in the doc but I only had a second to look. I will post back when I get a chance. Thanks again.
That worked great. All I had to do is look up the COM port that is used by KitProg in the Windows device manager and then open a serial connection with the same COM port and settings in PuTTY.
Everything else is so simple and easy to set up in the Pioneer Kit that I think it is a little odd to make the Debug output something so obscure that it's buried on 73rd page of the guide. Reading the output of debug statements is very important to people new to the environment and it seems like something you would always want up front. Hopefully I will be able to find these instructions next time I have to jump into this real quick.
1 of 1 people found this helpful
The "Debug" output is something to use as an additional tool. Mainly you can use the built-in capabilities to set breakpoints, inspect variables and analyze the call stack. Your Pioneer kit will help you to get in contact with the PSoC world. Really challenging will be to develop a gadget that does its work stand-alone as a real embedded application does. This is where the prototyping kits jump in as the CY8CKIT-043 You can snap off the programmer / debugging part (and use it for something else) and solder the kit with sensors and actuators.
Thanks! It looks like the CY8KIT-043 is just what I am looking for to prototype the circuitry into my project.
Have you used it with BLE? Do you know which BLE needs to be soldered on, and whether software updates are required after soldering it on?