Welcome in the forum!
Debugging without RS232 is quite easy: there is a debugger already integrated into Cypress Creator.
When you want to print data from PSoC to PC screen, just use a terminal program as PuTTY. Within the PSoC board is an UART-USB bridge that uses an emulated com port on your PC.
Place an UART on your topdesign and configure it (baud rate, parity etc) Set the UART pins to p7_0 and p7_1 resp.
I'll give it a whirl and get back if I have any problems.
Hi Bob, I'm back again with a follow-up question -
I have done as you suggested. Putty found a port at COM3. Initially this port was running wide open (noise) until I put in "UART_1_Start()" into the main.c file. That stopped the idle line chatter. Baud rates match up between the UART (SCB 3.10) and what I am using with putty and teraterm.
Proceeding on, I invoked the STDIO library #include <stdio.h> into the main.c file. I then have a little "hello world" for loop that repeats itself. Here is where I'm stuck now, nothing is happening over in putty. Have I skipped a step with initializing the UART?
I suggest you to use
There is no OS, how should the compiler know where you want to send your data to when using only printf()
I've used this method before with the PIC processor so I get it. Thanks for the pointer.
Unfortunately, there doesn't seem to be a UART_1_PutString(); function available with the kit package, unless I've left out a #include of one sort or another. Sorry to be so thick...
Thinking this might be a C99 artifact I changed the compiler argument to permit C99 syntax and that didn't help.
Just so I don't look completely helpless :). It turns out for the CY8CKIT-043 board, using PSoC Creator 3.3, the function to use is named a little different.
instead of UART_1_PutString(), it really is UART_1_UartPutString() which works just fine.
Since the UART_1 Handle can be changed on the UART module, I guess that for a UART module named "FOOBAR" then the invocation would be FOOBAR_UartPutChar(). Just in case anyone innocently stumbles across this thread.
Yes, mis-spelled or mis-taken. I always advise to look at the datasheet of the components, which is just a mouse click far away when configuring. The "API" chapter shows all the functions.
BTW: I just recall that in the PSoC4-M are two different UARTs and for one of them there is a FOOBAR_PutString() and for the other a FOOBAR_UartPutString().