Hi, if you don't care about leap seconds and daylight saving time it's easy; i've done that with portable data types (uint8_t, int16_t etc.) and functions which also calculate the calendar week, day of year etc. from/to time(NULL) on MSP430. With __DATE__ and __TIME__ it's easy to get a good approximation for time(NULL) on MSP430.
I'm using the same code for a RTAI kernel module for generating a DCF77 signal because with Kernel 2.6 there is no function in kernel space which returns year, month, day etc. so i have to calculate them from do_gettimeofday. Regards, Rolf [email protected] schrieb am 07.07.05 23:13:02: > > Well, I see a bunch of date conversion examples out there, mostly don't care > about code > size or are C++ (OO). That's all fine and dandy, but the question still > stands, > conversion of the existing functions (which would work out of the box) for > mspgcc. The > only things I see that would need to be defined are defined in externs to the > existing > library. These could simply be defined in the main source code so the > functions would > work properly. > > Any thoughts? I do not know what is involved in porting a standard library > over to > mspgcc but am willing to at least look at it. > > thanks > -Mark > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Sergei Sharonov > Sent: Thursday, July 07, 2005 3:42 PM > To: [email protected] > Subject: [Mspgcc-users] Re: time.h ? > > Hi, > > No, I'm using the internal 32k crystal to maintain the time with the basic > timer. ......... > > maintaining the UNIX time variable (this is very easy), but need an easy way > to have a > > human enter that time (and I don't think telling them to go to a converter > > and > get the > > number is viable). > > I did exactly the same thing. There is a piece of code floating on the net > that > implements time functions. You just need to provide tick increment every > second. > Do not have the code handy.. just google for it. > It does add a bit of code space ~3 kB, and some funcs have internal > static strings that will eat into your ram. > As I recall the whole board was drawing 15 uA and most of it was going into > the 3.3V regulator output ;-). Should provide 7.7 years of operation from > 1000 mA battery. > > Sergei > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening > July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual > core and dual graphics technology at this free one hour event hosted by HP, > AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
