Recently I ran into a problem with printf(). Right away I noticed that the firmware was caught in a function named os_error(). In the function the comments state to look at RTL.h to for error codes. However, the error code that I have 0x48=72 is not listed.
What is the best way to find out what error 72 is?
I am using MDK-ARM 4.11 for my toolchain.
Yes. This is debugger problem that I met a lot. The easy way for me to inspect the true contents of parameters in such case is watching the registers (if they not overwrite - the first parameter is passing in R0 and so on).
There is similar bug with local variables, that the debugger doesn't show their true content sometimes. So I track for the in the disassembly code and watch the matching register (at least with uVision version that I work with - 3.90).