You are here

Looking for the output of DBG_PRINTF() used in sample projects such as BLE_HID_Keyboard | Cypress Semiconductor

Looking for the output of DBG_PRINTF() used in sample projects such as BLE_HID_Keyboard

Summary: 4 Replies, Latest post by Bob Marlowe on 26 Sep 2016 11:56 PM PDT
Verified Answers: 2
Last post
Log in to post new comments.
mark_1539621's picture
User
3 posts

I am outputing a veriety of debug comments using the DBG_PRINTF() that is supplied in the example projects.

The problem is that I can't find the output. Do I have to open a command prompt and type something?

I've done this before and I remember that it is pretty simple once you find it, but I also remember that it is not very easy to find. I am returning to a project that I have not worked on in about a year.

It does not output to the Output window or anything else I could find in the IDE.

To be clear, I am just looking for the DBG_PRINTF() output that is used in several of the example projects so that I can read the comments to aid my debugging efforts.

user_1377889's picture
User
10102 posts

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"

 

Bob

mark_1539621's picture
User
3 posts

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.

mark_1539621's picture
User
3 posts

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.

user_1377889's picture
User
10102 posts

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.

 

Happy coding

Bob

Log in to post new comments.