Howdy, I'll second the above: you'll know if it's not good enough (or soon will).
Recent project required synchronization of position of multiple uC units.
I thought internal RTC would be good enough..... WRONG !!
Actual spec has RTC "typical" 1000uS BUT +/- 300uS (!!!!!).
I hadn't read/acknowledged this... My Bad.
I was using RTC as a cadence for communications' & position update.
Primary clock is 14.7MHz xtal, BUT RTC uses an internal clock "independent" of any other clock.
SO, since you can't adjust it, you either use it or not...
Turned out I had units at 1.97Hz, up to 2.15Hz, values spread between...
... talk about slow drift out of sync!
Since position updates are encoder reads, this introduced a creeping error.
Worked around it by using another Timer channel synced to the xtal source.
Now all units read 2.00Hz cadence (but what a wakeup call).
I won't fault Freescale for this, But I will bear umbridge that it's neither trimmable or syncable to a known source.
Just when you think you know what time it is.... G.H. <<<)))