...it seems to be that the unixTime is the internal accumulator,... This is not quite the case.
When the time is incremented by the clock interrupt there is a complete different set of variables to check for alarm times. This is handled in the RTC_DATE_TIME structure which shows all significant values in BCD.
So the unix time format is mostly because you may need it.
I suppose a higher-level question might be, why are calling RTC_UnixToDateTime in the aforementioned 'get' methods? Are there two side-by-side internal formats being maintained?
When RTC_Update is called, it increments the RTC_unixTime (which is why I referred to it as an internal accumulator). Also, the other lines of code in there (ifdef'd out for me) all refer to unix time.
This is just curiousity at this point, as this is my first project using the PROC BLE and I'm trying to understand the system code better so I can void pitfalls - I corrected my previous bugs, so my code runs fine now.
Are there two side-by-side internal formats being maintained? Yes, the unix date format and the struct RTC_DATE_TIME.
When RTC_Update is called, it increments the RTC_unixTime (which is why I referred to it as an internal accumulator) Yes, you're right.
This is just curiousity at this point, as this is my first project I can assure you that I very rarely look into the generated sources, the documentation is quite sufficient to answer any questions and to use the component. And: the RTC component seems to be a rather complicated one with many APIs available/needed.
Thanks Bob! As I said, I ran into a freeze/crash which is why I started digging in and came up with my question.