Hello,
Referring to this post
http://www.keil.com/forum/59779/
Maybe it is time to remove the simulator from uv5 to prevent confusion...?
I'm actually using printf() debugging a lot.
I get information without stopping any real-time code and wrecking the interaction with timed operations.
And I normally always have enough CPU cycles and flash space that I can ship with trace functionality in place. Some few lines always enabled. Some possible to turn on/off on command.
It's nice to be able to sign in to a live unit out in the field and look at performance statistics etc.
Printouts might be very much 1980 but they just happen to work very well. It's often enough with a very minor hint to be able to visualize what a unit is doing and why. Especially since most issues tends to be caused by incorrect configurations.
Or we know what the hardware does, and can validate and test enough that a ROM'd boot loader is actually going to function out of the gate, or the library functions do what they are supposed to on any ARM7, ARM9 or CM3, etc.
The idea that the software devs get to *** around and cause the SoC IP to be respun multiple times is alien, yes.
Perhaps you should focus on why your documentation is incomplete and inaccurate.