There are two kinds uf UARTS: USB based (Free pin routing) and SCB based (Pins are dedicated).
Use an SCB based for debugging. This is usually connected to the USB-UART bridge in the Kits having got a Kitprog.
Use the UDB based for your "normal" project-
thanks for the answer. RIght now i modified the project and use a "real" UART for the communication to the other uC and a SCB UART for the USB debug on Pins P1 and P1.
Unfortunately its still not working. I get no signal from the SCB UART to my FTDI USB debugger. It works however with the BLE_AlertNotification example which also uses a SCB UART.
Somehow i must have missed a configuration step in my project. I just dropped the SCB component to the TopDesign and configured it for UART with 115200 baud. I named it UART_DEBUG. In clocks i see that its attached to the HFCLCK.
DBG_PRINTF("BLE Heart Rate Sensor Example Project \r\n");
but nothing happens.
What makes you think that without any OS in the PSoC the function DBG_PRINTF() uses the UART_DEBUG component. (WHY CAPITAL LETTERS???)
Can you please post your complete project, so that we all can have a look at all of your settings. To do so, use
Creator->File->Create Workspace Bundle (minimal)
and attach the resulting file.
1 of 1 people found this helpful
project is working like a charm now, had to increase the Heap size in the memory manager.
Whay capital letters? Because its a redefinition of the printf function and define are in capital letters. Its exactly analogous to the debug.h file of Cypress' "BLE_Heart_Rate_Sensor" example project. Actual selection of the correct UART is done by tweaking the _write function in the debug.c file to use the correct UART.
Anyways, it was just the small Heap that crashed the program on the printf() call. I could solve it after a while with PSoC creator. Great IDE btw!