Folks,
Simple UART communication shouldn't be this difficult. Embarrassed to admit it, but I'm having problems setting up and using the app_uart.c/.h module from the SDK version 4.4.2 (limited to that version because I have 'C0' version devices right now). Am trying to use this module (with no flow control) in the radio_test_example project (also contained in the same SDK), substituting for the non-interrupt-driven UART code there. (Don't ask me why I made the change, but I will need the interrupt version later anyway :)
BTW, the hardware on my boardfrom the chip out to the comm port in the FET works. I verified that with simple_uart in an earlier test app.
Problem appears to be that the app hangs on transmitting the first character of the welcome message "RF Test....", presumably waiting for an interrupt on TXRDY that never arrives. My uart-event-handler routine is certainly never called. (Have to check again whether the IRQ routine inside app_uart.c is ever called. Don't remember.)
I won't bother you with code details (at least until I finish my line-by-line review, with product spec, PCN and PAN docs in hand, to make sure I'm not doing something stupid :-) Rather, I'll just ask the following general questions: Anybody else ever see this sort of thing? Is there a complete app that uses app_uart.c available that I can use as a template? (None was found in the SDK.)
TIA,
Mike
PS: The Keil MDK shows a "Power" enable/disable register in the UART register block, which is not described in product spec.or anywhere else in the docs that I can find :) Suspect this register is supposed to be hidden and part of the internal logic to power down the UART when HW flow control is used and based on the RTS line. Comments? Does this have any bearing on the issues I see?
