I am using an EPM900 emulator to debug a LPC935 application that uses serial output. However, I get nothing in any of the serial windows of uV4 when I run it. I decided to start at the very beginning and loaded the "Hello" example project. Under simulation it works fine and I get the "Hello World" message repeated ad infinitum in the UART#1 window. Under EPM900 emulation it downloads fine and the LEDs flash correctly and the printf(..) instruction is being executed. However, I get nothing in any of the UART windows, including the Debug (printf) viewer. As an aside issue, why does uV4 need 3 UART windows PLUS a Debug (printf) window?
The answer to your first question is "I doubt it". I doubt if the simulator actually does a parallel to serial (async) to parallel conversion. It probably just passes the data in the TX buffer to the UART window handler - but I'm not sure. When I first tried the example under simulation the CPU clock was set to 7.373MHz, but the baud rate generator was set of 9600 baud, but with values for a 12MHz CPU clock and it worked fine. Also there is no facility to select the baud rate for the simulator. As for the second question, I can't answer that as I don't have the design for the bond out chip.I assume the serial to USB is carried out by the bond out chip I simply took an example program provided by Keil. It has three targets: - Simulation, MCB900-Run and EPM900-Emulator. The example code assumed a system clock of 12MHz, but since I am using the on-board clock of 7.373MHz I changed BRG0 and BRG1 register values to give me a Baud rate of 9600 baud
I just wanted to point out the issues with baudrate.
Have you tried an oscilloscope to verify what serial data the chip sends out from the UART, before you transfer the serial data to your PC?